Local Internal Hard Disk Gets Renamed Once SAN Is Attached on OL6.
(Doc ID 2183093.1)
Last updated on AUGUST 20, 2018
Applies to:Linux OS - Version Oracle Linux 6.7 with Unbreakable Enterprise Kernel [3.8.13] and later
On : Oracle Linux 6.7 with Unbreakable Enterprise Kernel [3.8.13] version, Other Linux Issues or Packages
Local internal hard disk gets renamed once SAN is attached.
The server initially was installed with the internal disk attached only, the local disk was named /dev/sda, once the SAN disks get attached, new devices are detected and the local disk gets renamed to a different device name.
The server is still able to boot from the internal local disk, even though the disk received a new name, because the configuration on /etc/fstab is setup to use the disk UUID.
Using the blkid we can obtain the disk UUID.
/dev/sda1: UUID="7b903d64-022f-429c-b9c3-c6921da9feab" TYPE="ext4"
Server is able to find the boot device because, it will look for UUID instead of name.
UUID=7b903d64-022f-429c-b9c3-c6921da9feab /boot ext4 defaults 1 2
/dev/mapper/VolGroup-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
When new luns are attached to the server and on the next reboot the local disk once named /dev/sda receives another name.
Internal disk was device /dev/sda1 but is now /dev/sdaq1 after SAN was attached.
As shown below:
/dev/sdaq1 499656 91916 371044 20% /boot #boot mount point was mounted on sdaq1 instead of sda1
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document