I don't know, what the proble, but the fstab workaround functioniert: form: /dev/sda3 / xfs defaults 0 1 to: UUID=7c167a53-30ff-4d47-a206-ce8caf2397ba / xfs defaults 0 1
in this fix switched form device name to UUID based fstab. the uuid-s queried with /lib/udev/vol_id program /*sorry for bad english*/ On 1/19/08, Lars Callenbach <[EMAIL PROTECTED]> wrote: > I have a question concerning the ordering of devices during the boot process > and I hope that the kernel mailing list is the right place for this > question. > In my computer are two raid controllers with one raid array connected to > each of them (/dev/sda, /dev/sdb). In the debian 2.6.18 boot process the > ordering is root @ /dev/sda and data are on /dev/sdb. This behaviour has > changed in the plain 2.6.23.1 (and 2.6.23.8) kernel. The /dev/sd(a|b) > devices have switched so that root @ /dev/sdb. So my standard fstab does not > work. > What determines the device ordering during the boot process? What is a > workaround for this problem? > > Thank you very much for some hints, > Lars > > -- > Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten > Browser-Versionen downloaden: http://www.gmx.net/de/go/browser > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Thanks, Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
