Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!mips!darwin.sura.net!udel!louie!udel.edu!neal From: neal@neal.ctd.comsat.com (Neal Becker) Subject: Help! Bad Spot on Disc?? Message-ID: <NEAL.92Jul22092722@neal.ctd.comsat.com> Sender: usenet@udel.edu (USENET News Service) Nntp-Posting-Host: neal.ctd.comsat.com Organization: COMSAT Labs Date: Wed, 22 Jul 1992 14:27:22 GMT Lines: 32 I have 386-40 generic board, WD1007SE2 controller, and a 150MB Micropolis ESDI drive. (1022 cyl, 8 h, 35 s/t). No jumper were changed on the controller board from their defaults. The drive was low-level formatted without using the sector sparing option. Surface verification was done. All this using the BIOS on the controller. No problems. Try #1) After loadfd bin01, extract reports "bin01.11 corrupt". I renamed bin01.11 to junk, and loaded another copy of bin01.11. Now extract succeeds. When fsck -p was run, it reported "unknown inode type...". When fsck run I cleared several of these, but each time fsck is run again the same errors are reported! Looks like a bad spot, right? But why? Doesn't the software recognize the sectors already marked bad on the disk? Try #2) Rerun surface verification. Repartion. Reload software. Now, same thing but bin01.12 is bad. That's cause last time I gave dos 40 Mb, and this time 20Mb. Trying cp bin01.12 junk gives io error, confirming a problem accessing the disk. Again, mv bin01.12 junk and reload bin01.12. This time boots OK. Running fsck shows no problems. But now a new problem. This message keeps showing up (a lot): swap_pager_finish: clean of page xxx failed Sounds nasty. Is this a different problem? Or related to disk access? HELP! Does anyone know what's wrong? This seems to be a very generic setup.