Re: File System Corrupted Due to didn't Umount cause by power failure

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: misc <misc@...>, Peter_APIIT <peterapiit@...>
Date: Thursday, March 27, 2008 - 7:22 am

Peter_APIIT wrote:

man pages are available on-line, see front page of website.

> Enter shell path name or return to sh : I press enter

what did you do to change that? It should prompt you with a
default thatworks.

> Return me unknow terminal type, i tried it with tty00 and others No use.

you can't type random things there, at least the wrong random things.
Assuming it is an i386 or amd64 with a monitor attached, it would
be "vt220"

> After that, i try ffschk_ffs and ffschk but still cannot solve it.

(no error message, but we can pretty well guess what it would be)

AGAIN, typing random stuff isn't how you solve computer problems.
The command is "fsck" or "fsck_ffs" (either will work), and that
command was told to you in the error message (which was probably
scrolled off the screen due to your bumbling the terminal type
question).

> OpenBSD drop me to single user and kernel security level is .

If things are really messed up, you may prefer (or need) to boot
from bsd.rd, either from your disk or from a CD or floppy, then
fsck all your partitions.

Easiest way to proceed would be to look at the error message you
get at boot, it will be complaining about a particular partition,
let's assume it is /dev/wd0d. You will enter in the following
command:
fsck /dev/wd0d
When it finds errors, it will ask you if you want to fix them,
say "y". If it starts irritating you with how many things it is
asking you to fix, hit "F" (upper case!), and it will just assume
"y" for all remaining questions.

Once this fsck is done, it may ask you if you want to write the
fixes to disk. If so, DO SO! Otherwise, you just wasted your
time. :) (I'm drawing a blank at the moment if OpenBSD is one
of the OSs I've worked with that asks that question).

Now, do a "mount -a". The system may now report another
partition needs to be cleaned, so repeat the process with the
next partition, and so on, until your system comes up with a
mount -a. Note, this "mount -a" trick attempts to mount
everything in your /etc/fstab file, so if you booted from
bsd.rd, this doesn't work. In that case, you need to look at
your disklabel or the etc/fstab file on your disk.

Nick.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: File System Corrupted Due to didn't Umount cause by powe..., Nick Holland, (Thu Mar 27, 7:22 am)