From owner-freebsd-stable Mon Nov 26 12:58:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rooster.creighton.edu (rooster.creighton.edu [147.134.2.73]) by hub.freebsd.org (Postfix) with ESMTP id DDA6137B417 for ; Mon, 26 Nov 2001 12:58:33 -0800 (PST) Received: by rooster.creighton.edu (Postfix, from userid 1000) id 0E95162D02; Mon, 26 Nov 2001 14:58:24 -0600 (CST) Date: Mon, 26 Nov 2001 14:58:24 -0600 From: Sean Kelly To: stable@freebsd.org Subject: Plague of dscheck - b_bcount woes Message-ID: <20011126145824.A22147@rooster.creighton.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Last week, I set out to install a new IBM Deskstar 60GXP drive into my machine. After putting in the drive, I set out to reinstall FreeBSD and then restore my files from a second hard drive. Unfortunately, the restore process was cut short by a stream of errors which I had never seen before. They were of the form: dscheck(#ad/0xN): b_bcount N is not on a sector boundary (ssize 512) So I was unable to restore my files from my secondary 20GB Maxtor drive. I figured the drive was hosed and have been too busy since to mess with it. Unfortunately, that wasn't the end of it. About twenty minutes ago I arrived here at work where I also run FreeBSD. Note that this is an entirely different system with no similar hardware. The first thing I saw when my monitor came out of standby was: dscheck(#ad/0x20000): b_bcount 1 is not on a sector boundary (ssize 512) dscheck(#ad/0x20000): b_bcount 1 is not on a sector boundary (ssize 512) dscheck(#ad/0x20000): b_bcount 1 is not on a sector boundary (ssize 512) dscheck(#ad/0x20000): b_bcount 1 is not on a sector boundary (ssize 512) This is from two different hard drives in two different systems, both issuing the same error. Both machines run FreeBSD 4.4. The first machine experienced the problem both in -RELEASE and in -STABLE, and the second (work) machine is running -STABLE from Nov 19th. I see others reporting this error on the -stable list, but I have yet to find a reply telling what the error is and what could cause it. So my question is twofold. What the hell is this damn error and why does it keep following me around ever since last week? Was there some sort of magnetic shift at the poles I'm not aware of, or are all my drives just committing suicide at the same time? Help! -- Sean M. Kelly smkelly@rooster.creighton.edu URL: http://www.sean-kelly.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message