Date: Fri, 25 Oct 2002 16:02:55 +0300 From: "Vladislav V. Zhuk" <admin@dru.dn.ua> To: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: fsck lasting several hours (and then forever) after crash Message-ID: <20021025130255.GB1101@dru.dn.ua> In-Reply-To: <20021025144132.S44766-100000@atlantis.atlantis.dp.ua> References: <lists.freebsd.stable.20021024152331.GA43887@xor.obsecurity.org> <lists.freebsd.stable.20021024161227.GA248@Deadcell.ant> <3DB8228B.90203@vpop.net> <20021024201833.GA259@Deadcell.ant> <20021025044650.GA46167@dru.dn.ua.lucky.freebsd.stable> <20021025144132.S44766-100000@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 25, 2002 at 02:43:34PM +0300, Dmitry Pryanishnikov wrote: > > Every harddisk will be bad one day. fsck MUST be able to mark bad blocks > > and recover residuary data on the disk. Or freebsd must have another tool > > for recover data from harddisk with bad blocks. > > Actually, it has one, see badsect(8). Not to recover data (it's already lost > when sector gone bad), but to mark sector as unusable. In my case this program useless. fsck don't show anything. On the console only: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ata0-slave: ATA identify retries exceeded done Is this ATA bug??? -- Vladislav V. Zhuk (06267)3-60-03 admin@dru.dn.ua 2:465/197@FidoNet.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021025130255.GB1101>