Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!eplet.apana.org.au!werple.apana.org.au!gfm From: gfm@werple.apana.org.au (Graham Menhennitt) Newsgroups: comp.os.386bsd.questions Subject: [FreeBSD 1.1.5.1] bad block scanning Date: 15 Oct 1994 22:48:26 GMT Organization: werple public-access unix, Melbourne Lines: 24 Message-ID: <37pm7q$gf6@eplet.apana.org.au> NNTP-Posting-Host: werple.apana.org.au X-Newsreader: TIN [version 1.2 PL1] I have just installed FreeBSD 1.1.5.1 successfully. I have a 1.3 Gb Conner SCSI drive connected to a Adaptec 1542B controller. I seem to have a bad block on the disk! At some time soon after installation, I always get a corrupted directory. It usually happens when unpacking the source distribution (I have tried five times I think). I reboot and fsck always comes up with something like: DIRECTORY CORRUPTED I=165237 OWNER=bin MODE=40755 SIZE=512 MTIME=JuL 4 10:29 1994 DIR=? If I fix it, it comes back again soon after. (As an aside, I am fairly sure that this error is sometimes picked up by "fsck -p" but not just "fsck" -- that seems very strange but I have not yet got far enough to be able to check.) So my question is: What bad-block scanning software is available for use with FreeBSD. I have seen the "bad144" command but you need to know what blocks are bad to use it (Does it work with SCSI disks anyway?). Thanks for any help, Graham