Comment 17 for bug 103148

Revision history for this message
Russell Montgomery (russell-russellonthenet) wrote :

Sorry I failed to read the previous entry before submitting it. Hopefully this one is clearer.

My machine's history is a little different than what I saw here. Approximately 10 days ago I upgraded from Edgy to Feisty. Things ran pretty well for a few days. 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 (hd0 is now references as hd1 and hd1 is not referenced as hd0). i edited my menu.lst and swapped all hd references (hd1 to hd0 and hd0 to hd1.) Things improved and I could boot but failures were occurring later after trying to mount the additional file systems. Eventually I edited /etc/fstab and converted the UUID references to device references for all file systems (/dev/sdb2 instead of UUID). Everything seems to boot well at this point. My sound is no longer working when I'm fully booted though I get all the music related to the login, but none of the audio, even the bell, seem to work now.

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/sdb7 instead of 'by-uuid" references i 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