In RHEL 5 same as RHEL 6 you can get the UUID by using blkid. On Tue, Feb 28, 2012 at 7:21 PM, Barry Brimer <lists@xxxxxxxxxx> wrote: > > The problem; I guess is that the system is discovering & naming the disks > > in different order everytime the server is rebooted. For example the > > /dev/sda which represents the raid5 device created on local internal SAS > > disk is discovered as /dev/sdew ... and I guess this is the reason I am > > being dropped into the maintenance shell. I tell this because after I > > login to the maintenance shell I see that the /dev/sda represents a 500G > > SAN disk instead of a 600G internal disk. The internal disk is named > > /dev/sdew and if I disconnect the fibre cables; the server boots just > > fine. > > > > Is there a way to make sure that the disks are named consistently across > > reboots? > > Please suggest or point me in the right direction. > > Your /etc/fstab and /etc/grub.conf (really /boot/grub/grub.conf) should use > LABELs to identify filesystems, not devices. RHEL 6 also allows you to > specify > filesystems by UUID. I don't know if that works in RHEL 5 or not. > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
