Update: So I was really hopeful given the google find of this link: http://superuser.com/questions/346719/how-to-change-the-name-of-an-md-device-mdadm as instructed I stopped my devices, that went well. mdadm --stop /dev/md122 mdadm --assemble --update=super-minor /dev/md5 /dev/sdb7 /dev/sda7 but the --assemble command errors with the message: no devices found for /dev/md5 note: the devices /dev/sda7 and /dev/sda7 *DO* appear with fdisk -l do I need to --force the command or something? Randall ________________________________________ From: linux-raid-owner@xxxxxxxxxxxxxxx [linux-raid-owner@xxxxxxxxxxxxxxx] on behalf of Randall C. Grimshaw [rgrimsha@xxxxxxx] Sent: Monday, November 28, 2016 3:34 PM To: Phil Turmel; linux-raid@xxxxxxxxxxxxxxx Subject: RE: md prefered minor has been renumbered Phil: Thank you for responding, it is much appreciated. This is a recently assigned system so I must apologize for not having all of the history re fstab. But when I try to boot into the 'normal' system it continues to use the new numbering, the mounts fail, (the duplicate md122 obviously fails), and the system panics. I suspect the answer will have something to do with the command I googled: mdadm -A --update=superminor /dev/mdNEWNUMBER /dev/sd... . but I have zero experience with it. Randall ________________________________________ From: Phil Turmel [philip@xxxxxxxxxx] Sent: Monday, November 28, 2016 2:58 PM To: Randall C. Grimshaw; linux-raid@xxxxxxxxxxxxxxx Subject: Re: md prefered minor has been renumbered On 11/28/2016 12:26 PM, Randall C. Grimshaw wrote: > I have made the mistake of booting a centos-6.8 live cd to manipulate a centos 5 system. > as a result md5 has become md122, md2 has become md125, md4 has become md126, md0 has become md127, and most unfortunately md3 has also become md122. This is normal and expected for a livecd -- the numbering comes from the mdadm.conf file in the initramfs, unless that mdadm.conf file excludes arrays for later assembly (when the rootfs is available). Many livecd initramfs scripts try to assemble everything, so the numbers are allocated from 127 down. Usually you can find a boot parameter to suppress assembly. > smartctl shows that the WD brand drives do support SCT > mdadm --examine was used to reveal the mish-mash using uuid numbers compared with the file /etc/mdadm.conf also referencing /etc/fstab. Eww. You should not be counting on /dev/mdX numbering in your fstab. Specifically for this reason. Use LABEL= or UUID= syntax in fstab. > can someone kindly tell me the mdadm command to put the correct numbers back. No need. When you boot back into your normal system, its initramfs will supply this information. If you are changing the info, make sure you rebuild your initramfs, so the updated mdadm.conf file is included. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
