Re: Improper Shutdown


Subject: Re: Improper Shutdown
From: Patrick Callahan (pac1@tiac.net)
Date: Wed Jul 11 2001 - 19:10:47 MDT


This happens to me all the time.

Several annoying but not particularly harmful things can happen when you do
this depending on what was running when it was shut down.

When you start up, fsck runs to check the file systems. Every time you shut
down, the filesystems are unmounted and marked as unmounted. Since you did
not shut down properly, the file systems will not be marked as unmounted.
This will cause the fsck to check each one you are attempting to mount for
integrity.

Usually, if things were quiet on your machine, fsck finds one or two things
wrong and fixes them automatically.

If your machine was engaged in any activity at the time, there may be more
substantial things wrong. fsck will attempt to put things right, and you
might lose part or all of some file that was open when you shut down.

If things are really messed up, you will not be able to mount one or more
file systems. Then the fun really begins. This doesn't happen to me very
often, but in case it does, I have three partitions with YDL installed so I
just switch out an other one, reinstall the one that's messed up and proceed.
If things are really that screwed up, pay attention to the console messages
about fsck. You get additional chances to run fsck manually in single user
mode or reboot

Basically I don't worry much about it. My wife has standing instructions to
kill the power anytime she gets annoyed by the whine of the disk drive.
Someday I'll get around to showing her how to do it right or provide a button
to klick that does it for her. In the meantime, my blue G3 rev1 is not a
production machine and its just bits on a disk that get trashed. No hardware
gets clobbered by shutting the thing off.

-pat

On Wednesday 11 July 2001 08:06, you wrote:
> Hello,
> A few days ago my mum accidently shut down my Mac running YDL 2.0.
> Hereby terminating all processes without a proper shutdown. I haven't
> used the machine since. What do I do to start it up again and to get
> it to work again properly?
> Thanks in Advance



This archive was generated by hypermail 2a24 : Wed Jul 11 2001 - 18:15:20 MDT