Hey all, Whilst trying to upgrade one box from Debian Lenny to Debian Squeeze I have run into some problems with mdadm and the RAID labeling. Kernel: 2.6.32-41 mdadm version: v3.1.4 Disks: 4 RAID devices: /dev/md0 - boot - RAID1 - ext3 /dev/md1 swap /dev/md2 - "/" - RAID1 - ext3 /dev/md3 - "/var/lib/mysql" - RAID10 - xfs When doing the dist-upgrade and replacing the kernel + udev the system changes the RAID devices to md124, md125, md126 etc. As far as I have read, this makes sense - as mdadm is changing superblock and has to recalculate the whole RAID. This is big problem, if you have devices into /etc/fstab, like we do. As this is kinda from the past, we have tried to label the RAID devices in order to boot up using labels. As in the future migrations, no one knows if this can arise again and using labels would prevent us from having these kind of problems. We used e2label for the ext3 partitions and xfs_admin for the XFS one. Everything was fine when checking with blkid. We could see the labels fine in /dev/mdX. When rebooting, the machine won't boot up: ALERT! /dev/disk/by-uuid/c018-etc-etc... does not exist If we re-check the labels we can see all the devices got the same label (the one assigned to md0, md1 etc), so probably grub is trying to boot from single devices, and not from the md0 which is /boot This is blkid's output: /dev/sdb1: LABEL="boot" UUID="6d15111c-d2d9-4636-b2a5-7954ddcbcae2" SEC_TYPE="ext2" TYPE="ext3" /dev/sdb2: LABEL="swap" UUID="af027073-b59e-4886-9e5a-e3bad38ae466" TYPE="swap" /dev/sdb3: LABEL="/" UUID="c8e78ff4-b165-45d4-9382-ed669e5650dc" SEC_TYPE="ext2" TYPE="ext3" /dev/sdc1: LABEL="boot" UUID="6d15111c-d2d9-4636-b2a5-7954ddcbcae2" SEC_TYPE="ext2" TYPE="ext3" /dev/sdc2: LABEL="swap" UUID="af027073-b59e-4886-9e5a-e3bad38ae466" TYPE="swap" /dev/sdc3: LABEL="/" UUID="c8e78ff4-b165-45d4-9382-ed669e5650dc" SEC_TYPE="ext2" TYPE="ext3" /dev/sdd1: LABEL="boot" UUID="6d15111c-d2d9-4636-b2a5-7954ddcbcae2" SEC_TYPE="ext2" TYPE="ext3" /dev/sdd2: LABEL="swap" UUID="af027073-b59e-4886-9e5a-e3bad38ae466" TYPE="swap" /dev/sdd3: LABEL="/" UUID="c8e78ff4-b165-45d4-9382-ed669e5650dc" SEC_TYPE="ext2" TYPE="ext3" <snip> /dev/md0: LABEL="boot" UUID="6d15111c-d2d9-4636-b2a5-7954ddcbcae2" SEC_TYPE="ext2" TYPE="ext3" /dev/md1: LABEL="swap" UUID="af027073-b59e-4886-9e5a-e3bad38ae466" TYPE="swap" /dev/md2: LABEL="/" UUID="c8e78ff4-b165-45d4-9382-ed669e5650dc" SEC_TYPE="ext2" TYPE="ext3" /dev/md3: LABEL="mysql" UUID="e627f664-f929-4be8-815e-9e3cf559e512" TYPE="xfs" As we have to migrate loads of machines, using labels is the fastest and cleanest way to do it. Just create the labels and change /etc/fstab across all the machines and voilá. But we cannot get it running. Is there any workaround to work with labels and avoid all the disks in the raid to get them as well?. Using UUID doesn't seem like a good idea, as they may change with future dist-upgrades, mdadm upgrades etc. Has someone had same/similar problem with mdadm? Thanks a lot Manuel -- 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
