Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request From: cosgrok@nyssa.cs.orst.edu (Kevin Cosgrove) Newsgroups: comp.sys.sun Subject: "Bad Block" on Sun-3/50 (SunOS 4.1) Keywords: Miscellaneous Message-ID: <710@brchh104.bnr.ca> Date: 8 Dec 90 22:07:00 GMT Sender: news@brchh104.bnr.ca Organization: Sun-Spots Lines: 14 Approved: Sun-Spots@rice.edu X-Original-Date: Wed, 05 Dec 90 16:14:03 GMT X-Sun-Spots-Digest: Volume 9, Issue 397, message 2 X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu I don't have all the specifics since my Sun-3/50 is presently 90 miles from here, but I got a call from the keeper of my Sun. She said that my Sun was spewing "Bad Block" messagess when she got home. Eventually, after a power cycling, the system repeated "bad block 96... run fsck". 'fsck' reported a bad block 96 and asked if to continue, the answer was yes. After this bad blocks were found all over the place, 103, 104, 105, etc.... after which 'fsck' terminated with an error "filesystem not mounted" and produced a "#" prompt. I'm guessing that I need to reformat. Can anyone confirm (or deny) this suspicion of mine? Are there any ways short of reformatting (if that will even work) to correct errors of this type. Kevin Cosgrove