Thanks to
"John J. Francini" <francini_at_progress.com>
for his reply.
The evidence is still inconclusive as to whether this is hardware or not. I
suspect that it is not, as it finally installed, and there were no errors
once it decided to go. I did two things, physically, that may have had an
impact: I unplugged the drive and restarted the machine with no hard drive,
and I unplugged the tape drive from the SCSI chain. My suspicion is that
the tape drive was confusing matters (I remember something about the CAM
drivers doing tapes).
Original post below.
-- Bennet
>To: tru64-unix-managers_at_ornl.gov
>From: Bennet Fauber <bfauber_at_ucdavis.edu>
>Subject: Hard Disk Errors
>
>Hello,
>
>I have a DEC 2000, Model 300 AXP, ROM 2.2, Firmware version 370. I
initially installed DU 4.0B on this machine. On my first attempts at the
installation, I was getting errors when it went to copy the files to the
hard drive. Today, when I came in fresh and ready to write down everything
from the word go, things went OK.
>
>I would still like to know what was going wrong before.
>
>The messages I was getting came when it began installing. It switched to
the blue screen, said it made the filesystems, began doing its thing, and
the following would occur on what appeared to be every file copy
>
>Hard Error Detected
>Seagate ST15150N 0023
>Active CCB at time of error
>CCB request completed with an error
>Error, exception or abnormal condition
>ABORTED COMMAND - Target aborted command
>cam_logger: CAM_ERROR packet
>cam_logger: bus 0 target 0 lun 0
>cdisk_complete
>Retries exhausted
>
>Can anyone offer insight about what I did wrong? I used the GUI to do the
partitions, and I got the same error when I defined a single partition for
all filesystems. I was able to escape to the Unix shell, run newfs and fsck
on the disk and have it come back as OK, too.
>
>Thanks, -- Bennet
<----- oOo ----->
Bennet Fauber
Social Science Data Service
University of California, Davis
Received on Wed Oct 27 1999 - 17:01:10 NZDT