Subject: Hardware failures
From: "Marty James" [EMAIL PROTECTED]
Date: Wed, 22 Mar 2000 12:44:25 +1100
Hi guys (and the girls to if there's any out there on this list!),
I've been experiencing frequent but non-the-less erratic Hardware
Failures over the last couple of months.
I run about 75 clients (all macs) off a 7300/200, to a Sony DSS tape
drive. I've been marking the tapes that come up with Hardware errors,
to see if there's a pattern. Also, I've tried disconnecting
EVERYTHING and letting the tape drive cool for like 8 hours. Also,
I've been head cleaning almost twice a week.
I can't seem to correlate my actions with any specific
results...sometimes one of the options above will seem to help for a
few days but then BOOM...Hardware Failure? Is this a buffer underrun
proplem or something or is the media (Tapes) the problem?
I ordered a new head cleaning tape and 10 new DSS tapes, but does
anyone recognize this problem and if so, what do you recommend I do?
Cheers
Marty.
-R-I-P---C-U-R-L-
Marty James
PC Specialist
IT Departmente-mail: [EMAIL PROTECTED]
Rip Curl,office: +61 3 5261 0075
Torquay, Victoria, 3228 mobile: 0419 61 0075
Australia. fax: +61 3 5261 5432
--'the-surfing-company'--
Use of the RIP CURL trademarks by Rip Curl Pty. Ltd. under
license from Rip Curl International Pty. Ltd.
I have this problem and I decided to get a new tape drive. I had been using
a Sony SDT-5200 and I couldn't never get the firmware updated so I
"procured" a new HP DDS drive and it even can use the tapes where I use to
get Media Error. I used to get Media errors all the time even with new
tapes. I would use it once, do a full backup and the next time I ran an
incremental it would forward to the end of the last full and give me a 206
Device trouble: 2-Backup Keenan Terry, error 206 (drive
reported a failure: dirty heads, bad media, etc.)
Additional error
information for device "Sony DAT" [0:2],
Sense f0 00 03 00 00 00 29
12 00 00 00 00 3b 08 00 00 44 00
(SONY|SDT-5200|3.02)
I also was getting these periodically which was being blamed on network
problems:
Bad backup set header found (0x0e00 at 532,480).
Bad
backup set header found (0x37313430 at 532,572).
Bad backup set header
found (0x1000 at 614,400).
I had the drive repaired awhile ago but it never really was quite the same
as new. I had hoped that updating the firmware would fix the problem but I
needed a PC to do that with a SCSI card and when that combination was found
they usually had problems accessing the drive anyway. It turns out I needed
to upgrade to a previous firmware first and then go to the latest. Maybe if
I have time later I'll look into this.
JWS
883x8750
--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Problems?: [EMAIL PROTECTED]
