Dear group,
The original question was if my new DLT7000 should work correctly on a WS
500-5/266 with DU 4.0b or that I probably received a defective unit.
>From the responses I received I must conclude the unit was defective, so I
sent it back.
There were two short responses included here.
Thanks guys.
-------------------------------------------------------------
Alan Row, alan_at_nabeth.cxo.dec.com
---------------------------------
You may want to see what the errors are. On V4.0 and later you
should use dia(8) (DECevent) to print the error log. On earlier
systems you can use uerf(8). When using uerf(8) use the option
"-o full" to print the full error log entry since what is the
only way to get the useful device specific information. Device
errors will typically have Request Sense data associated with
them which is the last thing printed in the entry. Protocol
errors detected by the driver won't have Request Sense data.
For device errors you can check the documentation on the drive
to see what it suggests. For protocol errors, start checking
cables, connection, termination, etc.
I've heard that the DLT7000 has a more frequent cleaning cycle
than previous DLT drives. The couple of hours you run between
errors is well under what I've heard it to be, but it is
something to check.
---------------------------------------------------------------------------
Jeff Payne, payne_at_solg2.bnsc.rl.ac.uk
--------------------------------------
I've been using the DEC variant on an Alpha Server
1000A 5/333 DU4.0B for several months without a problem.
Might even be on a narrow connector along with a 4/8Gb DAT.
The DLT is the last device of 2 on the bus and has a wide
active terminator.
It gave problems when a narrow Exabyte was added - mainly
devices not appearing, but no errors. This was due to a
termination problem, which I resolved by moving the
Exabyte elsewhere.
---
I also use it with Networker , but Version 4.2B
However as this verion of Networker does not cover the tz89 I set up
Networker with 'Devices' set to tz88 with both 'Volume default capacity' and
'Volume current capacity' at 70Gb and mount the
device using /dev/nrmt0h. If I did not do that Networker said that
the tape was full at 15Gb.(compressed)
It now quite happily backs up over 30Gb uncompressed data.
I have also done direct tar backups at +25Gb and recovers ok
----------------------------------------------------------------------------
---
Received on Fri Nov 07 1997 - 13:20:50 NZDT