Date: Mon, 31 Oct 2005 14:17:24 +0100 From: Edward Lichtner <elichtner@wanadoo.fr> To: "Andrew P." <infofarmer@gmail.com>, Glenn Dawson <glenn@antimatter.net> Cc: f-q <freebsd-questions@freebsd.org> Subject: Re: File system check fails on boot Message-ID: <BF8BD7F4.2FAC%elichtner@wanadoo.fr> In-Reply-To: <cb5206420510310216y70da128an6328a31ca6850f20@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 10/31/05, Edward Lichtner <elichtner@wanadoo.fr> wrote: >> Hi all, >> There's fire in the house... I recently inserted a USB memory stick and = my >> 5.4 Stable machine rebooted suddenly. I now get the following on boot : >>=20 >> Starting file system checks : >> /dev/ad0s3a: UNKNOWN FILE TYPE I=3D2900154 >> /dev/ad0s3a: UNEXPECTED SOFT UPDATE INCONSISTENCY: RUN fsck MANUALLY. >> Automatic file system check failed; help! >> Oct. 30 20:14:53 init: /bin/sh on /etc/rc terminated abnormally, going t= o >> single user mode >>=20 >> When I run fsck, I get the folllowing : >>=20 >> ** Phase 1 - Check Blocks and Sizes >> UNKNOWN FILE TYPE I=3D2900154 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >>=20 >> CLEAR? [yn] >>=20 >> ** Phase 2 - Check Pathnames >> DUP/BAD I=3D2900154 OWNER=3Droot MODE=3D100644 >> SIZE=3D93 MTIME=3DMar 25 04:13 2004 >> FILE=3D/usr/ports/net/ldapbrowser/distinfo >>=20 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >>=20 >> REMOVE? [yn] >>=20 >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> LINK COUNT DIR I=3D2 OWNER=3Droot MODE=3D40755 >> SIZE=3D512 MTIME=3DOct 30 17:20 2005 COUNT 21 SHOULD BE 20 >> ADJUST? [yn] >>=20 >> UNREF FILE I=3D471058 OWNER=3Droot MODE=3D100644 >> SIZE=3D72 MTIME=3DOct 30 19:03 2005 >> RECONNECT? [yn] >>=20 >> CLEAR? [yn] >>=20 >> I then get similar messages for a dozen files, then : >>=20 >> ** Phase 5 - Check Cyl groups >> SUMMARY INFORMATION BAD >> SALVAGE? [yn] >>=20 >> BLK(S) MISSING IN BIT MAPS >> SALVAGE? [yn] >>=20 >> FREE BLK COUNT(S) WRONG IN SUPERBLK >> SALVAGE? [yn] >>=20 >> And so on... Should I just answer yes to all questions and hope for the >> best, or is there a better way of saving the day ? Needless to say, my w= hole >> system is on /dev/ad0s3a. >> Also, what could have caused the problem ? I recently updated my kernel = to >> include HFS support. Could it be linked ? >> Thanks all, >> Edward >>=20 >>=20 >> _______________________________________________ >> 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" >>=20 >=20 > If you have no idea, what's happened and what's > damaged, I'm afraid, you'll have to run fsck -y (or > place fsck_y_enable=3D"YES" in /etc/rc.conf to > always dangerously agree to everything) - and > hope for the best. >=20 Hi Andrew and Glenn, fsck -y did the trick and the system is now back on its feet=8A (Andrew, for a married man like myself, dangerously agreeing to everything is common practice ;-) Thanks guys, Edward
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BF8BD7F4.2FAC%elichtner>