Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!olivea!bu.edu!rpi!usc!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!roundup.crhc.uiuc.edu!uivlsisd.csl.uiuc.edu!terry From: terry@uivlsisd.csl.uiuc.edu (Terry Lee) Newsgroups: comp.unix.bsd Subject: Re: Bad144 sector mapping tips Keywords: bad144 Message-ID: <l78speINNhtb@roundup.crhc.uiuc.edu> Date: 27 Jul 92 22:05:34 GMT References: <l70u7lINNbh2@roundup.crhc.uiuc.edu> <HSU.92Jul27045602@laphroaig.cs.hut.fi> Reply-To: terry@uivlsi.csl.uiuc.edu Organization: Coordinated Science Lab., Univ. of Illinois at Urbana-Champaign Lines: 18 NNTP-Posting-Host: uivlsisd.csl.uiuc.edu Earlier, I had posted a series of steps for bad144 bad sector mapping. Unfortunately, the problem with bad144 handling is even worse than I realized. The problem appears to be when a write is attempted on a bad sector that has been mapped out. So for now, the steps I posted DO NOT work. My advice would be to re-low-level format the hard drive and use bad sector sparing if your hard drive controller supports it and you have the time. Otherwise, a bad sector in the inode list (or any other critical file system area) can be nasty. Also, a couple of people have experienced problems with corrupted bad sector file, which I also ran into. My solution was to write an /etc/disktab entry and completely re-disklabel the disk. Using bad144 after that didn't cause any more bad-sector corruptions. But again, bad144 handling really doesn't work right now anyway. ---------- Terry Lee terry@uivlsi.csl.uiuc.edu