From owner-freebsd-questions Mon Mar 26 15:56:29 2001 Delivered-To: freebsd-questions@freebsd.org Received: from itouch.co.nz (itouch.co.nz [203.99.66.188]) by hub.freebsd.org (Postfix) with ESMTP id 0D32237B719 for ; Mon, 26 Mar 2001 15:56:26 -0800 (PST) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by itouch.co.nz (8.11.2/8.11.1) id f2QNuKS41513; Tue, 27 Mar 2001 11:56:20 +1200 (NZST) (envelope-from jonc) Date: Tue, 27 Mar 2001 11:56:20 +1200 From: Jonathan Chen To: Frog Man Cc: freebsd-questions@FreeBSD.ORG Subject: Re: System boot Message-ID: <20010327115620.A41297@itouchnz.itouch> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bonzo81@hotmail.com on Mon, Mar 26, 2001 at 11:44:47PM +0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 26, 2001 at 11:44:47PM +0000, Frog Man wrote: > While performing an ftp get from a server, my 4.2 FreeBDS machine was > unplugged. Upon restart, I got the following message: > > The following file system had an unexpected inconsistency: /dev/ad0s1f > (/home) > Automatic file system check failed. > > I then am taken to single user mode wher I run fsck > > Upon doing that I get the following error message: > ad0: Hard read error blk# 694400 status=59 error=40 > Cannot read: blk 65600 > > I press yes to continue on, but them am prompted to run fsck again. I do, > but to no avail. Um. Hard read error tends to indicate drive failure. Try checking your hard-drive cables and make sure they're seated firmly - if that doesn't fix your problem, your hard-drive may be trashed. Good luck! -- Jonathan Chen ----------------------------------------------------------------------- "One, with God, is always a majority, but many a martyr has been burned at the stake while the votes were being counted." -- Thomas B. Reed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message