[Bug 85822] Re: /dev/md0 construct not supported in Feisty
I can confirm that this does not happen in Hardy. I guess this can be closed. -- /dev/md0 construct not supported in Feisty https://bugs.launchpad.net/bugs/85822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85822] Re: /dev/md0 construct not supported in Feisty - Beta
Update from beta installation attempt - failure. The raid, which is configured as /dev/md0 is ignored, and the installer is consistently looking for /dev/md/* which it cannot find. ln /dev/md0 /dev/md/0 -s did the trick. BUT lvm is now broken. My lvm sits on top of the raid. I can define a new logical volume, but it can not be selected from the list of partitions. ALL logical volumes are listing correctly, but selecting any one of them (including, of course the newly created one) returns to the same screen. There is NO message in the log screen when this happens (alt-f4). Yakov. -- /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
Re: [Bug 85822] Re: /dev/md0 construct not supported in Feisty
Hi, Yes, Herd5 is also broken, and even the workaround I had for Herd4 does not work this time, because the mere existence of a raid partition on the disks causes Herd5 installer to say boot partition not found (and I have more than a dozen partitions on my two drives, only two of them are raid). Thanks for the update. arcterex wrote: As a note this may still is happening in herd5 - alternate. An install on root raid after initial reboot drops down to initramfs with the 'no job control' error message. I fixed this by following the instructions at http://ubuntuforums.org/showthread.php?p=2272436 Not sure if this is the exact same issue. However, it appears from other bugs here that feisty and root raid aren't mixing well :( -- /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
Re: [Bug 85822] Re: /dev/md0 construct not supported in Feisty
Brian Murray wrote: Thanks for your bug report. Did this occur with the Herd 4 release of Feisty? Thanks in advance. ** Changed in: Ubuntu Assignee: (unassigned) = Brian Murray Status: Unconfirmed = Needs Info That is correct. Herd 4 - alternate. Regards, Yakov. -- /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
[Bug 85822] /dev/md0 construct not supported in Feisty
Public bug reported: 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. 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 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- /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
[Bug 85822] Re: /dev/md0 construct not supported in Feisty
** 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
