Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 03 Nov 2007 11:43:26 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        <lawrence.petrykanyn@sympatico.ca>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: fsck gave up on me!
Message-ID:  <44bqabibc1.fsf@Lowell-Desk.lan>
In-Reply-To: <BAY105-F237BE2B2EC8C7E021F462D838D0@phx.gbl> (lawrence petrykanyn's message of "Fri\, 02 Nov 2007 21\:39\:15 %2B0000")
References:  <BAY105-F237BE2B2EC8C7E021F462D838D0@phx.gbl>

next in thread | previous in thread | raw e-mail | index | archive | help
<lawrence.petrykanyn@sympatico.ca> writes:

>   Hi,
>   I have been using FreeBSD 6.2 for a couple of months now with no major
>   snags.  Until now.  I did a portupgrade this morning and afterwards,
>   when I logged in as a user into Gnome, my desktop was missing most of
>   the programs (Accessories, System Tools, etc.).
>   I rebooted the machine and "that other" terminal screen came up
>   (Single User?) and I was prompted to "run fsck manually" so I did so.
>   Well, fsck gave up on me.  I have no idea what happened or why.  Can
>   anyone help me understand what is going on with my machine and any
>   possible actions I can take to resolve this?
>
>
>   Script started on Fri Nov  2 17:13:22 2007
>   You have mail.
>   root# fscd[Kk
>   ** /dev/ad1s1a (NO WRITE)
>   ** Last Mounted on /
>   ** Root file system
>   ** Phase 1 - Check Blocks and Sizes
>   CANNOT READ BLK: 524544
>   CONTINUE? [yn] y
>   THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
>   ** Phase 2 - Check Pathnames
>   ** Phase 3 - Check Connectivity
>   ** Phase 4 - Check Reference Counts
>   ** Phase 5 - Check Cyl groups
>   CANNOT READ BLK: 524544
>   CONTINUE? [yn] y
>   THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
>   CG 2: BAD MAGIC NUMBER
>   FREE BLK COUNT(S) WRONG IN SUPERBLK
>   SALVAGE? no
>   SUMMARY INFORMATION BAD
>   SALVAGE? no
>   fsck: /dev/ad1s1a: Segmentation fault: 11
>   kirkwood# exit
>   exit
>   Script done on Fri Nov  2 17:14:23 2007


Either your disk is going bad or you have been extraordinarily unlucky
to lose a critical sector.  Try to run manufacturer's diagnostic tools
on it; failing that, you could try smartmontools (which, I guess, you
would need to boot and run from other media, like a CD).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44bqabibc1.fsf>