I just uploaded ubuntu3 version of mdadm that address this problem. It
should be available in the archive within a few hours.
Fabio
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Fix Released
--
System does not boot anymore
https://launchpad.net/bugs/59066
--
ubuntu-bugs mailing li
To clarify the problem:
During the "initramfs" stage, there are no /dev/disk/by-uuid/xxx made
for the raid devices so the new booting by filesystem uuid stuff for
grub will not work.
This should have been fixed with the latest mdadm upload (
2.4.1-6ubuntu2) but even with this new version my syste
I believe this problem is more related to mdadm, and that it should have
been fixed in a recent upload (but wasn't)
** Changed in: dmraid (Ubuntu)
Sourcepackagename: dmraid => mdadm
--
System does not boot anymore
https://launchpad.net/bugs/59066
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
The package was gnome-menus i changed it to dmraid trying to get it
closer to the real package.
--
System does not boot anymore
https://launchpad.net/bugs/59066
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I don't think this has to do with dmraid, which is used for fakeraids
(bios raid). LCID Fire, do you have the dmraid package installed at all?
Sounds like you are using the real software raid.
--
System does not boot anymore
https://launchpad.net/bugs/59066
--
ubuntu-bugs mailing list
ubuntu-bu
A messed up screen is a screen with colorfull vertical stripes in it.
Appearently there are 2 problems:
1. usplash really doesn't seem to work with 2.5.17 for me.
2. isn't uuid the hardware id to boot of? How is it supposted to find something
to boot on a software raid 0 - it has no hardware id!?
I changed the package that it was reported against because gnome-menus
have nothing to do with kernel not booting. Do you have a log in
/var/crash from apport on it.Can you describe a messed up screen or
provide a pic of it. Can you boot it if you take the word splash out of
the boot options in gr
