From owner-freebsd-stable Fri Jun 12 09:38:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17020 for freebsd-stable-outgoing; Fri, 12 Jun 1998 09:38:59 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from keaggy.canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16858 for ; Fri, 12 Jun 1998 09:38:19 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by keaggy.canonware.com (8.8.8/8.8.7) with SMTP id JAA22182 for ; Fri, 12 Jun 1998 09:34:43 -0700 (PDT) (envelope-from jasone@canonware.com) Date: Fri, 12 Jun 1998 09:34:42 -0700 (PDT) From: Jason Evans To: freebsd-stable@FreeBSD.ORG Subject: fsck infinite loop 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 This morning I finished up with a 'make world' and a new kernel installation to bring a system from 2.2.5 to -stable. When I rebooted I got the standard error unmounting file systems (apparently due to open nfs mounted files). I've had that happen many times before, with nothing more than a completely successful fsck. However, this morning, fsck went into an infinite loop with the following message: 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? 2) If it's a software error, what could cause fsck to loop infinitely? 3) Is there anything I can do to fix this short of re-installing, possibly 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message