On Tue, Jun 16, 2009 at 04:26:58PM -0700, walt wrote: > Billy Crook wrote: >> ... the letter naming of block >> devices in /dev/ is arbitrary and should be presumed unreliable. It >> is dependant on the order in which the devices were detected. In your >> case, it is likely that modules are being loaded in another order than >> before. This could happen for a variety of reasons including module >> renames, removals, or additions. >> >> To reliably reference block devices, use LABEL=, or UUID= in fstab, or >> /dev/disk/by-*/* anywhere else... > > Thanks, that's helpful info. The reason this came up is that the sata > disk on the onboard controller is the boot disk, and it's annoying to > have the boot fail because the ESATA disk is powered on or off, as the > case may be. > > The kernel chooses the root partition based on its own value of rdev, Which on most distros is the initrd image (/dev/ram0)? You _need_ to have an initrd image. Then rdev points to (1,0 - /dev/ram0) and executes the /init process which takes care of scaning the disks for the labels and pivots in a root filesystem depending on the label (or the LVM if that is there). -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
