From owner-freebsd-questions Tue Dec 10 15:48:58 2002 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 8D38137B401 for ; Tue, 10 Dec 2002 15:48:56 -0800 (PST) Received: from hotmail.com (f64.sea2.hotmail.com [207.68.165.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 198DB43EA9 for ; Tue, 10 Dec 2002 15:48:56 -0800 (PST) (envelope-from mingrone@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 10 Dec 2002 15:45:47 -0800 Received: from 209.205.181.165 by sea2fd.sea2.hotmail.msn.com with HTTP; Tue, 10 Dec 2002 23:45:47 GMT X-Originating-IP: [209.205.181.165] From: "Joey Mingrone" To: questions@freebsd.org Subject: drive problem solved? Date: Tue, 10 Dec 2002 17:45:47 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Dec 2002 23:45:47.0886 (UTC) FILETIME=[439838E0:01C2A0A6] 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 A few days ago I noticed the drive activity light on my box was solid and then I noticed my screen was frozen black. When I rebooted, /usr wouldn't mount and I was left in single user mode. The errors were something like: /dev/ad0s1g: Unkown file type I = 1236807 /dev/ad0s1g: unexpected softupdate; run fsck manually I ran fsck manually, but the results were not promising. I got lots of errors that included stuff like: hard error reading fsbn ?? status 59 and I can remember reading status 5b. I checked a few of the errors on google and I found a few identical to mine. All the responses to people asking what these errors were, were "your drive is hosed". When I rebooted the problem persisted so I figured I was just unlucky and my 3 month old drive had died. I managed to mount /usr read-only and saved almost all of my data. I went to file an RMA with Western Digital, but, as they recommend, I ran their diagnostics first. To my surprise the diagnostics reported no problems with the drive? Today I mounted /usr again as read-only and ran fsck (this is about the 10th time I've run it) and for some reason the next time the system booted fine? Drive: WD1000JB IDE Controller: atapci1: port 0xa000-0xa00f irq 0 at device 17.1 on pci0 (on board of a asus a7v266e) A friend, who has the same motherboard and drive had the same problem a few months ago, but he just ended up getting a new drive and starting over. I also swappped IDE cables a few times, and once right before the successful fsck. I'm running 4.7-RELEASE-p2 So my questions... Should I trust WD diagnostics? Why would fsck all of a sudden fix the problem? ..if it did fix it? Has anyone else with the same/similar hardware experienced these problems. Thanks, Joey _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message