The winners are Udo Grabowski and Johan Brusche. 10,000 points to each.
The points have no redeeming value, like (insert witty comment here).
The responses are below. The synopsis is; add in a new density into
ddr.dbase and (of course) to compile it when finished.
We used this in the GLOBAL entry of ddr.dbase;
scsi_tape_density[0x4a] = "225000_bpi" 225000 0
The order of entries in this table should be
scsi_tape_density[0x48]
scsi_tape_density[0x49]
scsi_tape_density[0x4a]
We found the drive density from Quantum manuals to be "225000_bpi".
All is working well for now.
/*** Johan Brusche ***/
You probably have only changed the entry for the DLT itself. In upper
part of ddr.dbase you have also the density table where the line;
scsi_tape_density[0x4a] = "225000_bpi" 225000 0
is missing and/or on top of the table is the entry
scsi_density_table_size = 0x50 , shouldbe 0x51
Do not forget to compile --> ddr.db afterwards.
Rgds,
Johan.
/*** Udo Grabowski ***/
Hello,
we have an SDLT 160/320, you have to add the density codes at the
beginning of the GLOBAL section of the ddr.dbase. Our entries for
the lower densities 160/320 are
scsi_tape_density[0x48] = "131000_bpi" 131000 0
scsi_tape_density[0x49] = "190000_bpi" 190000 0
Code 0x4a is the native,highest 600 MB density code, probably 233000
(233k is the advertised bpi density). So the native entry certainly is
scsi_tape_density[0x4a] = "233000bpi" 233000 0
Run 'ddr_config' after changing that file, otherwise the kernel
does not know about it.
Hope that the number is correct.
/*** Thanks to Martin Andersen; ***/
Martin reminds us to be wary of over used tapes, the possibilities of
bad tapes or dirty tape read/write heads in our systems.
As always - The Admins of Tru64 provide stellar support.
Ed Notari
-----Original Message-----
From: tru64-unix-managers-owner_at_ornl.gov
[mailto:tru64-unix-managers-owner_at_ornl.gov] On Behalf Of Notari, Ed
Sent: Wednesday, September 06, 2006 7:50 PM
To: tru64-unix-managers_at_ornl.gov
Subject: SDLT 600 Density Errors
We have an SDLT600 attached to an ES40 running Tru64 v5.1A. It is fully
patched. The correction for SDLT160/320 tapes has been applied to the
ddr.dbase
We have been experiencing errors as shown below. Specifically when
Legato Networker kicks off.
Does any one know how to correct this?
Binary Error Log
Active CCB at time of error
Hardware parity error detected.
Active CCB at time of error.
ctape_error_event_cb
Soft error reported
Active CCB at time of error
CCB request completed with an error
Created FRU table binary error log packet
Created FRU table binary error log packet
Active CCB at time of error
CCB request completed with an error
MEDIUM ERROR - Nonrecoverable medium error
Active CCB at time of error
CCB request completed with an error
MEDIUM ERROR - Nonrecoverable medium error
Protocol error detected by CHIM.
Active CCB at time of error.
Messages
Sep 6 18:42:39 arcnet vmunix: [0/2/0] ctape_ioctl: unmapped scsi
density code (0x4a) - DDR entry needed
Sep 6 18:42:39 arcnet last message repeated 2 times
Sep 6 18:43:17 arcnet vmunix: [1/4/0] ctape_ioctl: unmapped scsi
density code (0x4a) - DDR entry needed
Received on Tue Sep 12 2006 - 12:31:28 NZST