Comment 16 for bug 103148
Revision history for this message
| Russell Montgomery (russell-russellonthenet) wrote | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
My machine's history is a little different than what I saw. Approximately 10 days ago I upgraded from 7.04 to Feisty. It went pretty well. I have been installing updates as they came along.
Two days ago the console freezes, the mouse stops working, but the clock is still running. Eventually I found that the problem (at least for me) was related to Grub. Through trial and error I figured out that Grub now had swapped its root indicators. i edited my menu.lst and swapped all hd1 to hd0 and the hd0 to hd1. Things improved and I could boot but failures were occuring later. Eventually I edited /etc/fstab and converted the UUID references back to device references for all file systems (/dev/sdb2 instead of UUID).
My suspicion is that it is a combination of Grub and the use of UUID references. If I could figure out how to get kinit to use hard references (/dev/sdb70 instead of 'by-uuid" references i suspect the issue will be resolved.
I'm no expert but the majority of my problems seemed to be related to Grub's indexing my drives differently even though I haven't changed the cables to them.