Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 May 2006 12:08:10 +0200
From:      Florian Meister <florian.meister@medienhaus.at>
To:        Harman <harman0@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Problem with possible hdd crash
Message-ID:  <4455DE0A.4060902@medienhaus.at>
In-Reply-To: <be7e23600604301937n1544320clf2d57b03b4dbd3be@mail.gmail.com>
References:  <be7e23600604301937n1544320clf2d57b03b4dbd3be@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Harman wrote:
> I installed Fbsd 6.0 a few days ago. I had X running one day and I
> come back to it and move my mouse a bit and my comp freezes up and the
> screen has some fragmentation lines on it. I do a hard reboot and I
> find that the image is very distorted, including the manufacturer
> before the bootloader. The distorted text was only the first reboot
> after this happened, however. I boot fbsd and I get some weird errors
> everytime:
> 
> fsck: exec fsck_msdos for /dev/ad1s2 in /sbin:/usr/sbin: No such file
> or directory
> fsck: exec fsck_msdos for /dev/ad1s2 in /sbin:/usr/sbin: No such file
> or directory
> THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
>              msdos: /dev/ad1s2 (/media)
> Unknown error; help!
> init: /bin/sh on /etc/rc terminated abnormally, going to single user mode

looks like you have some fat-formatted partitions in your fstab
(/media). IMHO FreeBSD only starts if all partitions are marked clean.
Through the hard reboot the partitions are not marked as "clean",
because the "marking" is done at the unmount of the fs. So FreeBSD wants
to check the fs, but does not find the program "fsck_msdos" to check the
msdos partition. So it drops you into single-user-mode.

> 
> Now.. when I go into single user mode, no command seems to work
> besides cd and ls. I've checked this out with a linux live cd and the
> dir on this fs are all named wrongly with most having an asterisk in
> the middle of them, and some just missing alot of what they're named.
> 
Ouch, that can be some fs-problem. you can try to boot from a
freebsd-installation-cd and start a emergency-holographic-shell and then
do a fsck on all of your fs.

> I'd like to know what this possibly could have been, and how I can
> mount the fbsd fs from a live cd to get some config files off of it to
> make a reinstall easier, and see if I can maybe fix this by removing
> /dev/ad1s2 from my fstab. I did some stupid things with my X packages
> recently and uninstalled all of them, and then had to pkg_add all of
> them back, I was thinking this *might* have had something to do with
> it.

You can also try to remove the /media partition from your fstab. Maybe
the obligatorily fs-checks of the other partitions have no problems.
Booting from a freebsd-installation-cd and backup your data for a
reinstall is another possiblity.
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"

-- 

florian meister

EMAIL:       florian.meister@medienhaus.at
TELEPHONE:   +43 5572 501 134
FAX:         +43 5572 501 97134
ADDRESS:     gutenbergstrasse 1
             6858 schwarzach
             vorarlberg
             austria
WWW:         www.medienhaus.at

 o If practice makes perfect, and nobody's perfect, why practice?
 o The solution of this problem is trival and is left as an exercise for
   the reader.
 o Recursive,adj.; see recursive.
_______________________________________________________________________________






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4455DE0A.4060902>