I checked out bug 1404143 and can confirm that was the same error I got. I just for some reason on two systems only got it on the RAID and not on the freestanding partiitions.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1405531 Title: encrypted mdadam raid cannot be unlocked with udev 218 Status in systemd package in Ubuntu: Fix Released Bug description: Running Ubuntu vivid (alpha) with systemd. Bug same in my customized dracut initramfs , Ubuntu's initramfs-tools initramfs, or post boot from the command line. Udev package is udev_218-2ubuntu3_amd64.deb and its related udev packages. Using udev 217 or earlier cryptsetup opens my 3 disk mdadm raid volume at boot along with two cryptsetup volumes on SDD partitions. Using udev 218 the single device encrypted partitions all open fine, but the RAID volume does not, instead generating "could not remove ioctl" errors listing further details "device temporary-cryptsetup-(various numbers)." It would try five times and give up. The RAID itself does comes up, trying to open it from the command line gave me the errors reported above. A Startpage search said this kind of thing normally come from issues with udev rules. The udev rules for mdadm are not included with the udev packages, I am guessing they are in the mdadm packages so they were not changed by this update. Rolling back to udev 217 fixed this and allowed the mdadm raid volume to unlock normally. On this machine reproduction is simple: update to udev 218, make a new initramfs and try to reboot. The "cryptraid" volume hosted on the 3 disk raid will not unlock and cannot be unlocked post boot-not even be removing the hard drives and putting them back in their hotswap trays. Hardware is AMD FX 8120/Radeon HD 6750, motherboard uses FX 990 chipset. The three 2 TB drives are partitioned, the mdadm volume is assembled from the 3 partitions, the cryptsetup volume hosted on it is not partitioned, contains a single large (6TB) ext4 filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1405531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
