DJA wrote:
Thanks. I'd already done that. But still couldn't get a clean boot.

That was because, on editing fstab, I used paths to the LVM Logical Volumes as "/dev/mapper/VolGroup00/LogVolnn..." instead of the proper "/dev/VolGroup00/LogVolnn". That because I was using the mount path as shown from within the Disk Repair context. Looking at another box's fstab file straightened me out.

I cannot stress enough:

Label your filesystems and mount by label.

All modern filesystems(*) support some sort of filesystem label. Use that in fstab as the source device (LABEL=/, etc) instead of pointing to the device or volume directly. That way, everything can be autodetected no matter what type of underlying device it may reside upon.

The only time this is apt to become a problem is when you stick another disk from another system into your machine and attempt to boot -- if the labels on the other disk match labels on your disk, then the mount syscall will simply take the first one it finds (which may not be the correct one). However, most of us don't swap around disks so often. Even if we did, it might be a better idea to use one of those external usb/1394 disks and attached it after the system was booted. yay hotplug!

(*): All modern *linux* filesystems, that is. Other operating systems may vary (and probably do).

-Kelsey



--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to