Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2815 comp.os.386bsd.questions:15656 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!werple.mira.net.au!gfm From: gfm@werple.mira.net.au (Graham Menhennitt) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: Help! File system damaged after normal reboot! Followup-To: comp.os.386bsd.bugs,comp.os.386bsd.questions Date: 6 Jan 1995 03:52:04 GMT Organization: Mira Networking Pty Ltd, Australia Lines: 19 Message-ID: <3eiep4$88f@eplet.mira.net.au> References: <D1uD3I.Ep@store.elvisti.kiev.ua> <D1wCMG.2ru@luva.lb.bawue.de> NNTP-Posting-Host: werple.mira.net.au X-Newsreader: TIN [version 1.2 PL1] In article <D1uD3I.Ep@store.elvisti.kiev.ua>, Andrew V. Stesin <stesin@elvisti.kiev.ua> wrote: >Greetings, > >my FreeBSD-1.1.5 started suddenly to show an unusual and annoying >behavior when booting up after a normal `halt` or `reboot`. >The machine -- 486dx50 with VESA IDE, manufactured by SOYO(tm) >and 2 Conner 420Mb disks -- randomly suffers a trouble. > >fsck tells that there are "unexpected inconsistencies", >"DUP/BAD" and shows some inode No. Last time it happened, fsck >tried to remove libc.a!!! I had a similar problem with a Conner disk. This was a 1.0 Gb SCSI though. It had something to do with multi-sector reads being corrupted. It was NOT due to anything wrong on the disk. I have since replaced the disk and so I don't see it any more. Graham