From owner-freebsd-questions Thu Feb 27 04:07:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA21343 for questions-outgoing; Thu, 27 Feb 1997 04:07:53 -0800 (PST) Received: from cliff.bms.com (cliff.bms.com [140.176.1.102]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21338 for ; Thu, 27 Feb 1997 04:07:50 -0800 (PST) Received: from ccgate0.bms.com by cliff.bms.com (PMDF V5.0-7 #15142) id <01IFWH7ZAUV400HK26@cliff.bms.com>; Thu, 27 Feb 1997 07:04:47 -0500 (EST) Received: from ccMail by ccgate0.bms.com (SMTPLINK V2.11 PreRelease 4) id AA856975887; Wed, 26 Feb 1997 08:18:57 -0500 (EST) Date: Wed, 26 Feb 1997 08:18:57 -0500 (EST) From: "Jeffrey M. Metcalf" Subject: Re[2]: Checking FreeBSD disk for errors To: Andrew Cc: metcalf@snet.net, questions@freebsd.org Message-id: <9701268569.AA856975887@ccgate0.bms.com> Content-transfer-encoding: 7BIT Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thank you for the information. I ran bad144 on my hard drives last night, but found the information to be quite cryptic. I also got a lot of errors (bad block flag error, cylinder/track/sector parameters out of range). It occurred to me that there are perhaps special concerns when my hard drive has both DOS and FreeBSD resident. Bad144 seemed to want to scan the entire disk, however wouldn't that then be meaningless in the dual install case? My DOS slice is considered /dev/wd0s1 and my FreeBSD slices are /dev/wd0s2a ... etc Is there a way to get bad144's scanning capabilities to only identify with the FreeBSD slices if that is in fact my problem? Also, is there documentation somewhere that might help me to learn to interpret the output of bad144? Thank You, J. Metcalf ______________________________ Reply Separator _________________________________ Subject: Re: Checking FreeBSD disk for errors Author: Andrew at *Internet* Date: 2/25/97 10:26 AM On Tue, 25 Feb 1997, Jeffrey M. Metcalf wrote: > I am writing to ask if there is a FreeBSD command for checking > hard drives for errors (IDE and SCSI). I am aware of fsck, Try bad144 Andrew