From owner-freebsd-questions  Mon Apr  9 12:29:16 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from ns-exch05.jccc.net (ns-exch05.jccc.net [198.248.56.5])
	by hub.freebsd.org (Postfix) with ESMTP id 209D837B423
	for <freebsd-questions@freebsd.org>; Mon,  9 Apr 2001 12:29:13 -0700 (PDT)
	(envelope-from ndunker@jccc.net)
Received: by ns-exch05 with Internet Mail Service (5.5.2653.19)
	id <HZT7SFK3>; Mon, 9 Apr 2001 14:27:10 -0500
Message-ID: <C18E28011272D41180AD00B0D0496C0801C02155@ns-exch05>
From: Noah Dunker <ndunker@jccc.net>
To: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org>
Subject: Can't boot - Bad Blocks?
Date: Mon, 9 Apr 2001 14:27:06 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I recently upgraded to 4.2-RELEASE on my trusty P-90 Laptop.  The 
system came to a deadlock when I ejected a PCMCIA Modem, and
when I brought it back up, it wanted to fsck, so I let it.  When it got to
/usr though, it started going ape:

ad0: HARD READ ERROR blk# 3725983 status=5b error=40
/dev/ad0s1f: CANNOT READ: BLK 3407936
/dev/ad0s1f: UNEXPECTED INCONSISTANCY; RUN fsck MANUALLY.
...
...
THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTANCY:
	/dev/ad0s1f (/usr)
...

So I ran fsck manually on ad0s1f:

** /dev/ad0s1f
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
ad0: HARD READ ERROR blk# 3725983 status=5b error=01

CANNOT READ: BLK 3407936
CONTINUE? yes

ad0: HARD READ ERROR blk# 3725996 status=5b error=40
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 3408013,
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl Groups
105960 files, 1093814 used, 791692 free (54116 frags, 92197 blocks, 2.9%
fragmentation)

***** FILE SYSTEM STILL DIRTY *****

***** PLEASE RERUN FSCK *****



Okay, obviously my hard drive is having issues.  I re-run fsck and get the
same errors
on the same blocks every time.  Is there any way to tell the filesystem to
"ignore" 
certain bad blocks, or am I just up a creek here?

Thanks,
Noah Dunker, CCSE
Systems Analyst/Technician
Johnson County Community College 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message