From owner-freebsd-questions Sun Mar 16 20:25:17 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6241437B404 for ; Sun, 16 Mar 2003 20:25:15 -0800 (PST) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 460CE43F75 for ; Sun, 16 Mar 2003 20:25:13 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 5F59051A58; Mon, 17 Mar 2003 14:55:11 +1030 (CST) Date: Mon, 17 Mar 2003 14:55:11 +1030 From: Greg 'groggy' Lehey To: charles pelletier Cc: Brian McCann , freebsd-questions@FreeBSD.ORG Subject: Re: Dirty shutdown and I'm now stuck Message-ID: <20030317042511.GL4895@wantadilla.lemis.com> References: <20030317013408.GH4895@wantadilla.lemis.com> <000b01c2ec3a$40cd2640$05040101@socrates> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z9sQuz+HmDh2hVO4" Content-Disposition: inline In-Reply-To: <000b01c2ec3a$40cd2640$05040101@socrates> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --z9sQuz+HmDh2hVO4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 16 March 2003 at 22:04:05 -0600, charles pelletier wrote: > On Sunday, March 16, 2003 7:34 PM, Greg 'groggy' Lehey wrote: >> On Sunday, 16 March 2003 at 19:58:25 -0500, Brian McCann wrote: >>> Ok...I just had a system crash that I was working on. When coming back >>> up, I got an error that says it cannot read a block on the disk, and to >>> run fsck manually. When I run "fsck -f /dev/adwhatever" it just says >>> the same thing, listing the blocks it can't read, asks "Continue [yn]", >>> and no matter what I choose, I still can't mount it. Anyone have any >>> ides on how to fix this? >> >> Looks like it's time to dig out your backups. "Can't read a block" >> normally means that the disk is dying. >> >> You may be able to salvage something by mounting read-only and trying >> to copy to a new disk. You don't need a clean file system for a >> read-only mount. > > this may not be the solution, but, i've had similar experiences with various > machines i've had, and i was able to run fsck, BUT, i had to run it multiple > times, upwards of 7 or 8 times every once in awhile. Mind you, these were > pentium Is or IIs with very old hardware, but, it still worked. > good luck and i hope you find the final solution :) If the disk's dying, this is counterproductive. The first thing you want to do is get the data off before things get worse. Greg -- See complete headers for address and phone numbers --z9sQuz+HmDh2hVO4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+dU4nIubykFB6QiMRAiqPAKCFgG53yuTSvHuE4r5vD+PHn8omPACgnY/u 107x/3eW6oICEmTUGWUI9N0= =1Plg -----END PGP SIGNATURE----- --z9sQuz+HmDh2hVO4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message