Date: Fri, 25 Oct 2002 14:43:34 +0300 From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: undisclosed-recipients: ; Subject: Re: fsck lasting several hours (and then forever) after crash Message-ID: <20021025144132.S44766-100000@atlantis.atlantis.dp.ua> In-Reply-To: <20021025044650.GA46167@dru.dn.ua.lucky.freebsd.stable> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Fri, 25 Oct 2002, Vladislav V. Zhuk wrote: > > Now that is a good idear! Thanks. I dropped to single user mode and did > > dd if=/dev/ad4s1h of=/dev/null bs=64k. It appears that fsck is not the problem > > but my disk is going bad. > > 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. Sincerely, Dmitry Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE 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?20021025144132.S44766-100000>