bad shutdown
I think I have a CD-ROM going south. I started the KDE CD ripper flummy, and
then immediately stopped it. I wound up with a kaudiocreator process hung up
eating system CPU cycles and making my hard disk do unpleasant sounding
things filling the log up with "hdd lost interrupt" messages. The system was
stable, but I didn't want to leave it doing that.
So I closed everything out, logged off, waited a bit, and then rebooted. The
last thing I saw before the reboot was a warning that /home was busy, and so
was not umounted.
I booted into unclean/check forced mode on home and / both. Fortunately,
there were no serious problems.
Sure, I was having weird kernel interrupt problems, but it seems poorly
conceived to me for the init scripts to take one shot at something as
important as umounting everything, and then just say OK, to hell with it,
let's reboot anyway.
I'm not sure what could have been done at that stage of the game, but I'm
miffed I didn't even get the chance to try.
Anyone have any suggestions what I should do about this to increase the odds
that this won't happen again. (Other than getting rid of the CD ripper
flummy and trying to remember not to try to use the damn CD-ROM until I get
it replaced, I mean.)
--
Michael McIntyre ---- Silvan <dmmcintyr@users.sourceforge.net>
Linux fanatic, and certified Geek; registered Linux user #243621
http://www.geocities.com/Paris/Rue/5407/
http://rosegarden.sourceforge.net/tutorial/
Reply to: