Hi, We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta Cirrascale, up to date with patches. We have had a couple of instances in which the hard drives have become renamed after reboot (e.g. drive sda is renamed to sdc after reboot). One time this occurred when we rebooted following the installation of a 10GB NIC card, another time after we tried to install mellanox drivers (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64). Currently we are unable to boot because that drive has been renamed. Our questions are * Has anyone else experienced similar issues? * What can we do to prevent such renaming in the future -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley at mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301
Pat Haley wrote:> > We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta > Cirrascale, up to date with patches. We have had a couple of instances > in which the hard drives have become renamed after reboot (e.g. drive > sda is renamed to sdc after reboot). One time this occurred when we > rebooted following the installation of a 10GB NIC card, another time > after we tried to install mellanox drivers > (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64). Currently we are unable to > boot because that drive has been renamed. > > Our questions are > > * Has anyone else experienced similar issues? > * What can we do to prevent such renaming in the future >In the past. To resolve you could use (*UGH*) the no-possible-way-to-remember UUID, or you could label the filesystems, and refer to them that way. I strongly prefer the latter.
On 5/24/2016 2:08 PM, Pat Haley wrote:> > We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta > Cirrascale, up to date with patches. We have had a couple of instances > in which the hard drives have become renamed after reboot (e.g. drive > sda is renamed to sdc after reboot). One time this occurred when we > rebooted following the installation of a 10GB NIC card, another time > after we tried to install mellanox drivers > (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64). Currently we are unable > to boot because that drive has been renamed. > > Our questions are > > * Has anyone else experienced similar issues? > * What can we do to prevent such renaming in the futuredon't use device names in your fstab, use labels, or use LVM, or whatever. -- john r pierce, recycling bits in santa cruz
I've run into this with ZFS on Linux. The 'blkid' is useful to identify the target device and then add that to your fstab. I don't use device names at all anymore, too ambiguous (depending on the circumstance) in my opinion. On Tue, May 24, 2016 at 3:04 PM, John R Pierce <pierce at hogranch.com> wrote:> On 5/24/2016 2:08 PM, Pat Haley wrote: > >> >> We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta >> Cirrascale, up to date with patches. We have had a couple of instances in >> which the hard drives have become renamed after reboot (e.g. drive sda is >> renamed to sdc after reboot). One time this occurred when we rebooted >> following the installation of a 10GB NIC card, another time after we tried >> to install mellanox drivers (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64). >> Currently we are unable to boot because that drive has been renamed. >> >> Our questions are >> >> * Has anyone else experienced similar issues? >> * What can we do to prevent such renaming in the future >> > > > don't use device names in your fstab, use labels, or use LVM, or whatever. > > > > -- > john r pierce, recycling bits in santa cruz > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
----- Original Message ----- From: "John R Pierce" <pierce at hogranch.com> To: centos at centos.org Sent: Tuesday, May 24, 2016 5:04:24 PM Subject: Re: [CentOS] Hard drives being renamed On 5/24/2016 2:08 PM, Pat Haley wrote:> > We are running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64 on a Quanta > Cirrascale, up to date with patches. We have had a couple of instances > in which the hard drives have become renamed after reboot (e.g. drive > sda is renamed to sdc after reboot). ?One time this occurred when we > rebooted following the installation of a 10GB NIC card, another time > after we tried to install mellanox drivers > (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64). Currently we are unable > to boot because that drive has been renamed. > > Our questions are > > ?* Has anyone else experienced similar issues? > ?* What can we do to prevent such renaming in the futuredon't use device names in your fstab, use labels, or use LVM, or whatever. -- john r pierce, recycling bits in santa cruz Use blkid to get the UUIDs then use UUID="..." in fstab. ?Be aware that nothing is failsafe, changing filesystems on a partition will change the UUID and "dd ing" a partition to another drive but leaving it in the system without manually changing the UUID of one of the partitions will result in duplicate UUIDs and corresponding confusion - "been there, done that". _______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
On Tue, May 24, 2016, 3:08 PM Pat Haley <phaley at mit.edu> wrote:> > Our questions are > > * Has anyone else experienced similar issues? > * What can we do to prevent such renaming in the future >Yes. You can't, it's non-deterministic. Use fs volume UUID instead, both in grub.cfg command line for root= parameter and fstab. Chris Murphy