** Description changed: During install, a raid was not recognized. Apparently the installer searches for /dev/m/0 where the existing raid is defined to reside on /dev/md0. "ln /dev/md0 /dev/md/0 -s" enabled me to continue with the install successfully. - Further on, the system wont boot. after applying the above line to the - target volume, I was able to boot. + Further on, the system wont boot. At thie stage I generated an + mdadm.conf which seemed to force generating the raid. + + In Dapper and Edgy these operations and especially the creation of + mdadm.conf where not necessary. From looking at the log it seems that + /dev/md0 WAS created during the kernel boot but was closed in favor of a + "/dev/md/n" construct (which might be good for newly generated raids but + not for existing ones). ProblemType: Bug Date: Sat Feb 17 18:52:37 2007 DistroRelease: Ubuntu 7.04 Uname: Linux study-linux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
-- /dev/md0 construct not supported in Feisty https://launchpad.net/bugs/85822 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
