Return to BSD News archive
Newsgroups: comp.sys.ibm.ps.hardware.storage,comp.os.386bsd.bugs,comp.sys.ibm.ps.hardware.systems Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!news.alpha.net!news.mathworks.com!udel!gatech!howland.reston.ans.net!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 NetNode Message-ID: <D28xwH.LJ2@store.elvisti.kiev.ua> Date: Wed, 11 Jan 1995 15:05:02 GMT Lines: 60 Hello, I think that the best place to ask about Conner drives will be the place where most PC hardware gurus reside. So I'm crossposting this. in brief, the questions are: did someone notice any kind of "strange" behavior of Conner HDDs of any kind (IDE, SCSI)? What's the c.s.ibm.pc.hardware.* people's opinion about what HDD brandname is _really_ trusted? Maxtor? Seagate? Quantum? IBM? WD? Anything else? Pointer to a FAQ? Surely we people who are running young and rapidly developing OS like FreeBSD or Linux need to have trusted hadware first of all... Thanks in advanse! The discussion which is the source of my question, follows. [ Article crossposted from comp.os.386bsd.bugs,comp.os.386bsd.questions ] [ Posted on Tue, 10 Jan 1995 13:20:03 GMT ] [ Author was Fred L. Schneider ] #>Graham Menhennitt (gfm@werple.mira.net.au) wrote: #>: 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. # # For what it is worth: After about 2 years of error free-operations under # NetBSD-0.9, I began experiencing something very similar. The HD concerned? # A Conner CP30200 (212 MB SCSI). Repeated re-formats and reinstalls with # various partitioning schemes resulted in no change. Behavior was the same # after installing NetBSD-1.0. Solution: A new (Quantum 541mb SCSI-2) drive # solved the problem. BTW: the SCSI controller here is an AHA-1542B. # # It is curious that there seems to be a common denominator in the Conner HD's. # Wish I could have some hard data to report, though. # -- With best wishes -- Andrew Stesin, Elvisti.Kiev.UA sysadmin.