The Wednesday 2004-04-07 at 19:50 -0400, Lists wrote:
On Tue, 2004-04-06 at 15:32, Carlos E. R. wrote:
The Monday 2004-04-05 at 15:46 -0400, Lists wrote:
That's what you should have done first thing; what failed after the update is that you did not run lilo after it.
I take it that the update would have run lilo if it had completed normally? The error essentially left the system in an in-between state.
No, it should have put a pop up message telling you to run lilo in the case you use lilo as boot manager, or nothing if you use grub. It seems there is no sure way of knowing which one we use automatically, so they just put a reminder. Some patches ago the message was unclear, it said something like "remember to run lilo"; thus people using grub run lilo, and prety weird things happened - it was comented on the list :-)
You forgot to edit /etc/fstab. When changing disks, you have to edit both lilo.conf (or grub) and fstab. That error you report is consistent with a mismatching fstab file, because that's the place the system is looking for partition types.
Now that you point it out, it makes perfect sense. It never even occurred to me at the time I was pulling my hair out. Every time I start getting cocky about my l33t 5ki1z, something comes up to thoroughly humble me. Thanks for helping me figure this out. Now, I have something to play with this weekend. <G>
Welcome :-) Experience is just the sum of ours errors - I just happened to walk that path first ;-) -- Cheers, Carlos Robinson