Return to BSD News archive
Xref: sserve comp.os.linux:31204 comp.os.386bsd.questions:1053 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!caen!usenet.cis.ufl.edu!usenet.ufl.edu!gatech!udel!darwin.sura.net!dtix.dt.navy.mil!mimsy!nmrdc1!dsc3pzp From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) Newsgroups: comp.os.linux,comp.os.386bsd.questions Subject: Connor SCSI CP30200 Message-ID: <C4Gx5E.HwM@nmrdc1.nmrdc.nnmc.navy.mil> Date: 25 Mar 93 23:27:00 GMT Organization: Naval Medical Research & Development Command Lines: 28 Maybe it is just me, but... I don't think the Connor SCSI CP30200 is very good for 386BSD or Linux. There seems to be a problem with the bad-block mapping. First, I was suspisious, since w/my Adaptec 1542B formatting did not cause the drive LED to light. Verify caused only a little (very little) blinking. Eventually, both format and verify came back, seemingly OK. The drive SEEMED to format OK, both with 386BSD and MS-DOG. But... Later testing with both 386BSD and MS-DOG showed bad blocks. The bad-block mapping seems to be a Bad Thing (tm). This drive is going BACK WHERE IT CAME FROM! Not that I MINDED twice waiting for 1/2 hour for tech help only to have the line hang-up... (Connor tech help). Shame really - Connor seems to be able to handle a lot of shock (G-force)... MAYBE it was a bad drive - but the symptoms sure sounded a lot like an e-mail I got from someone having Linux problems with a Future Domain card (and the same CP30200)! -- ============================================================================== phil perucci | "Any opinions expressed are my views, dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil | not the position of any organization" ==============================================================================