> On 10/31/05, Edward Lichtner <[EMAIL PROTECTED]> 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 : >> >> Starting file system checks : >> /dev/ad0s3a: UNKNOWN FILE TYPE I=2900154 >> /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 to >> single user mode >> >> When I run fsck, I get the folllowing : >> >> ** Phase 1 - Check Blocks and Sizes >> UNKNOWN FILE TYPE I=2900154 >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> >> CLEAR? [yn] >> >> ** Phase 2 - Check Pathnames >> DUP/BAD I=2900154 OWNER=root MODE=100644 >> SIZE=93 MTIME=Mar 25 04:13 2004 >> FILE=/usr/ports/net/ldapbrowser/distinfo >> >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> >> REMOVE? [yn] >> >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> LINK COUNT DIR I=2 OWNER=root MODE=40755 >> SIZE=512 MTIME=Oct 30 17:20 2005 COUNT 21 SHOULD BE 20 >> ADJUST? [yn] >> >> UNREF FILE I=471058 OWNER=root MODE=100644 >> SIZE=72 MTIME=Oct 30 19:03 2005 >> RECONNECT? [yn] >> >> CLEAR? [yn] >> >> I then get similar messages for a dozen files, then : >> >> ** Phase 5 - Check Cyl groups >> SUMMARY INFORMATION BAD >> SALVAGE? [yn] >> >> BLK(S) MISSING IN BIT MAPS >> SALVAGE? [yn] >> >> FREE BLK COUNT(S) WRONG IN SUPERBLK >> SALVAGE? [yn] >> >> 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 whole >> 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 >> >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "[EMAIL PROTECTED]" >> > > 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="YES" in /etc/rc.conf to > always dangerously agree to everything) - and > hope for the best. > Hi Andrew and Glenn, fsck -y did the trick and the system is now back on its feetĀ (Andrew, for a married man like myself, dangerously agreeing to everything is common practice ;-) Thanks guys, Edward
_______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"