From owner-freebsd-stable Fri Jun 12 12:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16577 for freebsd-stable-outgoing; Fri, 12 Jun 1998 12:02:10 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA16373 for ; Fri, 12 Jun 1998 12:01:08 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ykZ4P-0002KB-00; Fri, 12 Jun 1998 12:01:01 -0700 Date: Fri, 12 Jun 1998 12:00:59 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Jason Evans cc: freebsd-stable@FreeBSD.ORG Subject: Re: fsck infinite loop In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Jun 1998, Jason Evans wrote: > wd0s2e: soft error reading fsbn 132033 of 132032-132143 (wd0s2 bn 787393; > cn 97 tn 82 sn 19) wd0; status 58 error 1 > > So, questions: > > 1) Is this a hardware or a software (logical disk corruption) error? Hardware. > 2) If it's a software error, what could cause fsck to loop infinitely? fsck is not looping. The wd driver is looping because it is retrying again and again. > 3) Is there anything I can do to fix this short of re-installing, possibly > on a new disk? Try a couple of extended power cycles. You may get lucky and the disk may decide to behave, but you should plan a reinstall on a new disk. > Thanks, > Jason > > Jason Evans > Email: [jasone@canonware.com] > Web: [http://www.canonware.com/~jasone] > Home phone: [(650) 856-8204] > Work phone: [(408) 774-8007] > Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message