Comment 53 for bug 75681
Revision history for this message
| Aurelien Naldi (aurelien.naldi) wrote | #53 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have just tested upgrading to the debian udev package and (beside being painfull) it completly broked my system.
I think that people here are experiencing two different bugs, as _for_me_ /dev/sd* files are created normally, just with a few seconds of delay, making mdadm blocked after trying to assemble an array for which some devices are still missing.
* I could not use prevu to upgrade to the debian udev package as its version number (0.105) is lower than this of the ubuntu package (103), thus lvm2 complains that it will break this old version of udev.
* after upgrading the version number, building the packages by hand and rebooting I got stucked and _NO_ devices was created at all. Maybe some ubuntu patches should be applied to make it work ??
* after reinstalling the older version (thanks to an other working feisty install), I could boot again. But booting does still require several attempts or adding "break=mount" option and running the mdadm script once my devices are created.
One thing changed since my last comment: if I wait for the busybox shell, I do not see a half-created /dev/md0 anymore, so something improved at least ;)