[opensuse] updating HD device id, best practice
We're moving a bunch of sles servers to a new SAN. This process changes the ID of the hard drives. We're able to modify menu.lst and fstab to use /dev/sda1, etc, but when you do a kernel update, the grub gets re-written using the old had drive ID. I found /boot/grub/device.map has the old ID in it, but I'm not sure if changing that is enough. What is best practice for modifying/updating a system that now has a new device id? thanks, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
On Fri, Aug 19, 2011 at 10:35:51AM -0400, James Pifer wrote: [ 8< ]
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?
Nothing would change. Plese follow the approach you've guessed initially and update /boot/grub/device.map This information is taken into account when a kernel update gets installed and new lines are added to grub's menu.lst Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Fri, 2011-08-19 at 17:24 +0200, Lars Müller wrote:
On Fri, Aug 19, 2011 at 10:35:51AM -0400, James Pifer wrote: [ 8< ]
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?
Nothing would change. Plese follow the approach you've guessed initially and update /boot/grub/device.map This information is taken into account when a kernel update gets installed and new lines are added to grub's menu.lst
Thank you for the confirmation!! James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/08/19 09:36 (GMT-0400) James Pifer composed:
We're moving a bunch of sles servers to a new SAN. This process changes the ID of the hard drives. We're able to modify menu.lst and fstab to use /dev/sda1, etc, but when you do a kernel update, the grub gets re-written using the old had drive ID.
I found /boot/grub/device.map has the old ID in it, but I'm not sure if changing that is enough.
What is best practice for modifying/updating a system that now has a new device id?
I always specify LABEL/by-label during installation, but it appears DEVICE_NAMES= in /etc/sysconfig/storage may be what controls this and what you need to change. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Dave Howorth
-
Felix Miata
-
James Pifer
-
Lars Müller