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 lis
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
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 ra
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.
--
** 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
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 applyi
