Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!cs.utexas.edu!sun-barr!olivea!spool.mu.edu!yale.edu!jvnc.net!darwin.sura.net!Sirius.dfn.de!Urmel.Informatik.RWTH-Aachen.DE!acds.physik.rwth-aachen.de!kuku From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) Newsgroups: comp.unix.bsd Subject: bad sector table corrupt Message-ID: <1992Sep23.174324.16625@Urmel.Informatik.RWTH-Aachen.DE> Date: 23 Sep 92 17:43:24 GMT Sender: news@Urmel.Informatik.RWTH-Aachen.DE (Newsfiles Owner) Reply-To: kuku@acds.physik.rwth-aachen.de Organization: I.Physikalisches Institut RWTH-Aachen Lines: 31 Nntp-Posting-Host: acds.physik.rwth-aachen.de I have a 2 drive IDE system, one WD 2120 and a Maxtor 7120 as a second drive. Everything running fine until today when I wanted to remote copy a 386BSD distributtion to the second drive (for source patchkit preparation). During the rcp I suddenly got bad block messages on the console screen in some high block number. The system got hung. After resetting and rebooting I was left in single user mode with a failed fsck on wd1c (I was using wd1c as a /u filesystem). As I was unable to fsck the disk again (bad argument) I tried to disklabel it. surprisingly /sbin/disklabel had permissions r-xr-s--- bin . OK, x for world would be fatal, but why can't root execute it? Anyway, not as important as the fact that when I wanted to re-label it I got a message "bad sector table corrupt". While I'm typing this, a re-format of the drive is running and I will try again later to re-label it. The above raises two questions: Given that a sector in the range of the last sectors of the disk was accessed during the rcp, could it be that the disk ran full and , instead of flagging a disk full the copy (rcp) process ran into using non-existing blocks? Might this be caused by wrong disk labeling? Does anyone have a correct disktab entry for the MXT 7120? Is bad144 envolved here ? Should I run bad144 over the disk? I read about bad144 problems in recent messages. Any comments appreciated. -- --Chris Christoph P. U. Kukulies kuku@acds.physik.rwth-aachen.de *** Error code 1 Stop.