Date: Mon, 29 Mar 2004 17:58:04 -0500 From: Bill Vermillion <bv@wjv.com> To: freebsd-hackers@freebsd.org Subject: Re: fsck fails - mark sectors as bad? Message-ID: <20040329225804.GA67918@wjv.com> In-Reply-To: <20040329200043.E089616A507@hub.freebsd.org> References: <20040329200043.E089616A507@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Message: 4 > Date: Sun, 28 Mar 2004 18:43:03 -0500 > From: "Dan Langille" <dan@langille.org> > Subject: fsck fails - mark sectors as bad? > To: freebsd-hackers@FreeBSD.org > Message-ID: <40671CB7.1003.71EBDCAB@localhost> > Content-Type: text/plain; charset=US-ASCII > I had a hard drive failure. I'm trying to get as much data off it as > I can before I restore from backup. I have mounted the drive in > another box and I'm attempting to salvage what I can. > I thought I might be able to mark the bad sectors as bad, and get the > file system mounted. [fsck out put deleted in this reply - wjv ] ... > this froze up and I found this in /var/log/messages: > Mar 28 17:11:31 tmp /kernel: ad2s1a: hard error reading fsbn 6399 of > 3168-3295 (ad2s1 bn 6399; cn 0 tn 101 sn 36) trying PIO mode > Mar 28 17:11:31 tmp /kernel: ad2: DMA problem fallback to PIO mode > Mar 28 17:11:36 tmp /kernel: ad2s1a: hard error reading fsbn 6415 of > 3168-3295 (ad2s1 bn 6415; cn 0 tn 101 sn 52) status=59 error=4 > 0 > Mar 28 17:11:41 tmp /kernel: ad2s1a: hard error reading fsbn 3187 > (ad2s1 bn 3187; cn 0 tn 50 sn 37) status=59 error=40 > Mar 28 17:11:46 tmp /kernel: ad2s1a: hard error reading fsbn 3188 > (ad2s1 bn 3188; cn 0 tn 50 sn 38) status=59 error=40 > Mar 28 17:11:51 tmp /kernel: ad2s1a: hard error reading fsbn 3189 > (ad2s1 bn 3189; cn 0 tn 50 sn 39) status=59 error=40 > Mar 28 17:11:56 tmp /kernel: ad2s1a: hard error reading fsbn 3190 > (ad2s1 bn 3190; cn 0 tn 50 sn 40) status=59 error=40 > Mar 28 17:12:01 tmp /kernel: ad2s1a: hard error reading fsbn 3191 > (ad2s1 bn 3191; cn 0 tn 50 sn 41) status=59 error=40 > Mar 28 17:12:06 tmp /kernel: ad2s1a: hard error reading fsbn 3192 > (ad2s1 bn 3192; cn 0 tn 50 sn 42) status=59 error=40 > Mar 28 17:12:11 tmp /kernel: ad2s1a: hard error reading fsbn 3194 > (ad2s1 bn 3194; cn 0 tn 50 sn 44) status=59 error=40 > Mar 28 17:13:24 tmp /kernel: ad2: READ command timeout tag=0 serv=0 - > resetting > Mar 28 17:13:24 tmp /kernel: ata1: resetting devices .. ata1-slave: > ATA identify retries exceeded > Mar 28 17:13:24 tmp /kernel: done > Definately some bad sectors there. But you should be able to moun that drive in a read only mode. In read only you can get by without an fsck, and often this is the only way to be able to get to the data. When you get the data off be sure to check it's integrity as depending on what is read or how it is read you could have blocks of junk or blocks of nulls. I've been lucky and never had one corrupt this badly needing to mount RO in at least 10 years, so I've never had to do this on a current BSD type FS - just the old S51 and early FFS on commercial Unix systems. Bill > End of freebsd-hackers Digest, Vol 54, Issue 1 > ********************************************** -- Bill Vermillion - bv @ wjv . com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040329225804.GA67918>