Date: Wed, 19 Sep 2012 11:41:07 +0100 From: Steve O'Hara-Smith <ateve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: fsck not working on messed-up file system Message-ID: <20120919114107.663a9cf0fd188a3ef9b4107b@sohara.org> In-Reply-To: <85.11.23206.2D899505@smtp02.insight.synacor.com> References: <85.11.23206.2D899505@smtp02.insight.synacor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Sep 2012 06:05:06 -0400 "Thomas Mueller" <mueller23@insightbb.com> wrote: > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, > 0.2% fragmentation) > > ***** FILE SYSTEM STILL DIRTY ***** > > ***** PLEASE RERUN FSCK ***** > > Script done on Wed Sep 19 04:17:27 2012 > > > Would this indicate a software bug, or is my Western Digital Caviar Green > 3 TB hard drive failing? Either something was referencing sectors off the end of the disc, or the drive is failing. I'd be inclined to copy the data off somewhere safe and subject the disc to extensive tests with smartctl from smartmontools, then if it passes recreate the fileystem(s) and restore the data. -- Steve O'Hara-Smith <ateve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120919114107.663a9cf0fd188a3ef9b4107b>