Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2807 comp.os.386bsd.questions:15581 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!uwm.edu!news.moneng.mei.com!hookup!news.sprintlink.net!EU.net!news.eunet.fi!KremlSun!satisfy.kiae.su!kiae!relcom!elvisti!store!office.elvisti.kiev.ua!stesin From: stesin@elvisti.kiev.ua (Andrew V. Stesin) Subject: Help! File system damaged after normal reboot! X-Newsreader: TIN [version 1.2 PL2] Sender: usenet@store.elvisti.kiev.ua (USENET subsystem) Nntp-Posting-Host: office.elvisti.kiev.ua Organization: Electronni Visti InformAgency (ElVisti) Message-ID: <D1uD3I.Ep@store.elvisti.kiev.ua> Date: Tue, 3 Jan 1995 18:09:18 GMT Lines: 23 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!!! fsck -b 32 doesn't help; anyway, when I go singleuser, I can mount the file system and `cp` the affected file (without any trouble!) to another location, then unmount it and launch `fsck -y` to make the beast happy. Please, anybody share your wisdom with me! Maybe hardware need to be fine tuned, or what? -- With best wishes -- Andrew.