Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Disk unmount

0 views
Skip to first unread message

John Maas

unread,
Dec 25, 1999, 3:00:00 AM12/25/99
to
The first time I logged on my new Linux install, I got off by pulling the
plug on the computer, rathar than a proper log off. Anyway, I now have a
problem. When I go to start Linux I get a message that such and such drive
was not properly dismounted and this triggers an automatic check that takes
a few minutes and produces the result that there are a problems with some of
the files. Otherwise the system runs ok.

How do I clear this up?

John

Al Morgan

unread,
Dec 25, 1999, 3:00:00 AM12/25/99
to
That is basically the linux equivilent of M$'s "scandisk", it should only
run once, and if you shut down your computer properly, then it shouldn't
happen again.

Al Morgan [ mua...@proaxis.com ]

John Maas <jm...@execpc.com> wrote in message
news:38653f79$0$13...@news.execpc.com...

Tracy Williams

unread,
Dec 26, 1999, 3:00:00 AM12/26/99
to
You'll need to post the exact messages that you're seeing. If they go by too
fast, you should be able to view them in the /var/log/messages file.

To soft reboot (like ctrl+alt+del in windows) the machine type:
shutdown -r -y 0

To shudown Linux so you can can power off the machine:
shutdown -h -y 0

Tracy

TJ Johnson

unread,
Dec 26, 1999, 3:00:00 AM12/26/99
to
Remember the days of Dos 3.3, when you could shutdown a machine by
hitting the power button? Sometimes I miss those care-free days. Ah
well, back to the present.

You need to run fsck interactively, or at least fool the machine into
thinking you are. You should get some sort of disk name with your
error. At the first prompt you get, try: fsck -y /whatever/drive
where /whatever/drive is the disk name the error gave you. The -y tells
fsck to automatically fix any errors it finds. After it successfully
completes, run fsck again without the -y so that you can see any
errors. If you get many errors the second time, there is a good chance
that partitions is what is technically known as "hosed" and there is a
reload in your future. If the second fsck comes up clean, type: reboot
now (not shutdown). Your machine should come up without complaining
about the drive.

TJ
I need a netname.

0 new messages