AHh - think I've fixed it. I'd appreciate it if someone could check that what I've done makes sense though !!
I noticed on reboot, that the "blkid" command was showing the problem devices as TYPE-mdraid, but with the same UUID's Looking at the mdadm utility, I noticed that you could use the Assemble options to rename the UUID's as part of the assemble process. I used: sudo mdadm /dev/md1 --assemble --update=uuid /dev/sde1 /dev/sdf1 And the missing "md1" nvidia array appeared correctly. It now comes up on reboot also. I'm still not sure why renaming the UUID's has fixed it, because even after running the assemble process with the UUID rename, both devices still have a duplicated UUID (albeit new ones!) Also, unlike the Feisty release, these devices don't appear under /dev/mapper .. which makes me a bit worried that I'm going to get a conflict between mdadm and dmraid. I guess I'm just going to have to give it a go and see what happens - at least the raid array is now visible. -- Cannot start from dmraid device anymore https://bugs.launchpad.net/bugs/141435 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
