Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!noc.near.net!uunet!faculty!nmrdc1!dsc3pzp
From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
Newsgroups: comp.os.386bsd.questions
Subject: SCSI sense error?
Message-ID: <C4G1zI.Aoz@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 25 Mar 93 12:14:04 GMT
Organization: Naval Medical Research & Development Command
Lines: 23
While installing bindist using Tiny 386BSD 0.1, I got a couple SCSI
sense errors, then the message saying bin01.49 is corrupted (while
running "extract bin01"). I have a SCSI drive, which my Adaptec 1542
BIOS (verify) and MS-DOG say is free of defects, so naturally I was
suprised. Could it be that:
1) The floppy driver read in a bad file, but only the SCSI driver
checks the CRC when the file is read back? Installing bin01
worked for me a few times, then failed twice consecutively with
the above error (I am trying to get clean bin01/src01 for putting
in patch 0.2.2).
2) 386BSD SCSI driver sees HD errors that the BIOS verify and MS-DOG
don't?
Any comments appreciated...
--
==============================================================================
phil perucci | "Any opinions expressed are my views,
dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil | not the position of any organization"
==============================================================================