Comment 14 for bug 29858
Revision history for this message
| Henrik Hjelte (henrik-evahjelte) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Still there on Feisty.
I just had this problem (Stans, except I only have a boot partition and a ubuntu partition, no Fedora) when upgrading to feisty using apt-get dist-upgrade. After rebooting, feisty doesn't see my VolumeGroup /dev/mapper/vg1, stalling around the the line look"device-mapper: 4?-ioctl initialized.
have finally managed to boot into an old kernel 2.6.15-26. This was actually a surprise, when booting into the old kernel the boot procedure stalled about five minutes (something about waiting for raid), but now finally I have a root terminal open. Sorry I can't be more specific now, but I am afraid to reboot again until I have solved the problem. Now at least I have got some clues from the answers above, thanks.
If apt-get dist-upgrade is an obsolete and dangerous method of updating, maybe one could add a clear Warning message when trying to do it? Now I read afterwards on a forum that there is a new safer method of updating, I should probably have tried that instead. It would be nice if apt-get had told me too. Maybe a script that filters out dist-upgrade and shows warnings before calling the real apt-get.