Date: Wed, 26 Feb 1997 19:19:07 -0500 From: "Jeffrey M. Metcalf" <metcalf@snet.net> To: questions@freebsd.org Cc: Jeffrey_M._Metcalf@ccmail.bms.com Subject: Using bad144 to scan for bad blocks Message-ID: <3314D2FB.41C67EA6@snet.net>
next in thread | raw e-mail | index | archive | help
Hello, I recently wrote questions@freebsd.org to ask about a FreeBSD program for scanning a hard disk for errors. I was told that bad144 was the way to go. However, when I run the following bad144 -s -v /dev/wd0s2 I get the following (abbreviated) ----------------------------------------------------- bad block information at sector 1024065 in /dev/wd0s2: cartridge serial number: -2097151993(10) bt_flag=8875(16)? sn=62466193, cn=15491, tn=100, sn=181 sn=28224, cn=7, tn=0, sn=0 sn=70657159, cn=17524, tn=4, sn=139 sn=116335303, cn=28853, tn=0, sn=7 bad144: /dev/wd0s2: bad flag in bad-sector table bad144: /dev/wd0s2: bad magic number bad144: cyl/trk/sect out of range in existing entry: sn=62466193, cn=15491, tn=1 00, sn=181 bad144: bad sector file is out of order bad144: cyl/trk/sect out of range in existing entry: sn=70657159, cn=17524, tn=4 , sn=139 bad144: cyl/trk/sect out of range in existing entry: sn=116335303, cn=28853, tn= 0, sn=7 bad144: cyl/trk/sect out of range in existing entry: sn=135217463, cn=33536, tn= 1, sn=248 bad144: cyl/trk/sect out of range in existing entry: sn=58282122, cn=14453, tn=1 17, sn=255 bad144: cyl/trk/sect out of range in existing entry: sn=263274849, cn=65296, tn= 20, sn=117 bad144: cyl/trk/sect out of range in existing entry: sn=54708625, cn=13567, tn=1 00, sn=181 bad144: cyl/trk/sect out of range in existing entry: sn=42840, cn=7, tn=232, sn= 0 bad144: cyl/trk/sect out of range in existing entry: sn=262128576, cn=65008, tn= 255, sn=255 bad144: cyl/trk/sect out of range in existing entry: sn=202846215, cn=50307, tn= 133, sn=12 -------------------------------------------- and many more lines similar to the last few are displayed. I am not at all sure how to interpret this. Does the fact that the hard drive I am using is set up to dual boot with WIN95 and FreeBSD have anything to due with the following error: bad block information at sector 1024065 in /dev/wd0s2: Is it also responsible for all of the out of range errors as well? If so, is there a way that I can get bad144 to only analyze and report on the portion of the hard drive with the FreeBSD slices? If not, are there any other FreeBSD utilities for scanning hard drives for errors? I don't imagine that I can convince DOS/WIN95 versions of scandisk to search for physical errors on my FreeBSD partition. Thank you, -- Jeffrey M. Metcalf metcalf@snet.net http://ruddles.stat.uconn.edu/~jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3314D2FB.41C67EA6>