"Toshikazu Aiyama, Ph.D." <[EMAIL PROTECTED]> writes: > --- Goswin wrote > >> That would be the initrd and not the 2nd stage. Most likely the initrd >> is missing the right module for your sata controler. Check the >> contents or just try adding the right module in /etc/mkinitrd/modules >> before creating the initrd. > > I also thought initrd is the problem. But it has all the right module, > however imperfect may be at this time. Rather sarge properly identifies > sda, and sdb, but sid somehow identifies empty SCSI MO as sda, and nv_sata > as sdb, and sdc. If I turn off SCSI MO, sid reboots properly. I wonder > why there is a discrepancy of SCSI device handling order between sarge and > sid.
Different kernels have modules in a different order. Whatever gets loaded first becomes sda. This realy sucks and mkinitrd should realy strongly suggest and support using e2lables or uuid for the root device instead. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]