> > have you tried putting the actual device node instead of the LABEL=/ > > option? > > e.g. kernel /whatever ro root=/dev/hda2 > > (or whichever /dev/hdaX your / Filesystem is) df will tell you this > > ( I assume you can still boot with an old kernel?) > > e.g: [stuart@laptop stuart]$ df Filesystem 1K-blocks > > Used Available Use% Mounted on /dev/hda7 6048320 > > 4815104 925976 84% / none 517712 0 > > 517712 0% /dev/shm /dev/hda8 21204420 3317020 > > 16810244 17% /home /dev/sda1 241263968 62852732 > > 166155652 28% /mnt/disk > > > > so in my case root=/dev/hda7 > > Stuart, > > thanks for the quick reply. I am going to assume that /dev/sda2 is my root > filesystem - right? according to the output of df, yes. This may not be the only problem you have, it's always my firswt port of call when dealing with filesystem labels though. incidentally, my first tactic would have been to try the edit in in /boot/grub/grub.conf - the kernel takes the root= argument from settings in there. This is the point at which your boot is failing. /etc/fstab is not read for a while after that (by /etc/rc.d/rc.sysinit if you need to know). let us know if it makes any difference to your boot process. Stuart -- Stuart Sears RHCE, RHCX Quidquid latine dictum sit, altum viditur -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
