On Fri, 2011-08-19 at 14:41 +0100, Dave Howorth wrote:
James Pifer wrote:
We're moving a bunch of sles servers to a new SAN. This process changes the ID of the hard drives. ... What is best practice for modifying/updating a system that now has a new device id?
Use UUIDs or volume labels instead
Can you elaborate? What I mean is this. When we install SLES it sets up menu.lst to look like: module /boot/vmlinuz-2.6.32.36-0.5-xen root=/dev/disk/by-id/scsi-200d0b29d2d000a00-part2 resume=/dev/disk/by-id/scsi-200d0b29d2d000a00-part1 splash=silent showopts vga=0x317 I can change that to whatever I want, such as root=/dev/sda2, and get the system to boot, but when a kernel update runs, it changes it back to the old format with the wrong disk id. So how would change to using UUIDs or volume labels help here? Thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org