You are not alone. We have had ongoing problems with SDLT media and similar
errors. Tru64 server, HP ESL9326 library. On average, we probably get 2 of
these a week.
.......
06/20/05 11:27:05 nsrd: media warning: /dev/ntape/tape0_d1 writing: I/O error,
at file 89 record 12307
06/20/05 11:27:05 nsrd: media notice: dlt tape S02079 on /dev/ntape/tape0_d1 is
full
06/20/05 11:27:06 nsrd: media notice: dlt tape S02079 used 132 GB of 220 GB
capacity
06/20/05 11:28:32 ansrd: RPC error: Unable to send
06/20/05 11:28:32 ansrd: chunk2 to nsrmmd failed
06/20/05 11:28:33 nsrd: media warning: /dev/ntape/tape0_d1 reading: No such
file or directory
06/20/05 11:28:33 nsrd: media notice: Volume "S02079" on device
"/dev/ntape/tape0_d1": Block size is 32768 bytes not 98304 bytes. Verify the
device configuration. Tape positioning by record is disabled.
06/20/05 11:28:33 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:34 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:35 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:35 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:36 nsrd: media warning: /dev/ntape/tape0_d1 moving: rewind Bad
file number
06/20/05 11:28:36 nsrd: media warning: /dev/ntape/tape0_d1 moving: fsf 89: Bad
file number
06/20/05 11:28:36 nsrd: media warning: /dev/ntape/tape0_d1 moving: rewind Bad
file number
06/20/05 11:28:37 nsrd: media warning: /dev/ntape/tape0_d1 moving: fsf 89: Bad
file number
06/20/05 11:28:37 nsrd: media warning: /dev/ntape/tape0_d1 moving: rewind Bad
file number
06/20/05 11:28:38 nsrd: media warning: /dev/ntape/tape0_d1 moving: fsf 89: Bad
file number
06/20/05 11:28:38 nsrd: media emergency: could not position S02079 to file 89,
record 12303
06/20/05 11:28:39 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:39 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:40 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:40 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:40 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:41 nsrd: media warning: /dev/ntape/tape0_d1 reading: Bad file
number
06/20/05 11:28:41 nsrd: media warning: verification of volume "S02079", volid
3045564673 failed, can not read record 12303 of file 89 on dlt tape S02079
06/20/05 11:28:42 nsrd: media notice: verification of volume "S02079", volid
3045564673 failed, volume is being marked as full.
06/20/05 11:28:42 nsrd: media notice: Save set (3054809857) baggio:<102>CCS:CCS
volume S02079 on /dev/ntape/tape0_d1 is being terminated because: Media
verification failed
06/20/05 11:28:42 nsrd: baggio:<102>CCS:CCS done saving to pool 'LongTerm'
(S02079) 1556 MB
.......
Cheers,
Ryan.
>>> phillip_young AT I2 DOT COM 20/06/2005 1:15:43 pm >>>
All,
I am perplexed by a problem that appears to be getting worse, not better,
over time. Media verification failures using brand-new Fuji SDLT tape in a
new SDLT320 drive driven by a known-good SCSI bus and cable. Below the log
file snippet is a summary of stuff I've tried so far...
Environment: Solaris 8, running NetWorker 7.1
Jun 19 20:51:10 server scsi: [ID 107833 kern.warning]
WARNING: /pci@1f,4000/scsi@4/st@5,0 (st33):
Jun 19 20:51:10 server Error for Command: write
Error Level: Fatal
Jun 19 20:51:10 server scsi: [ID 107833 kern.notice] Requested Block:
9270 Error Block: 9270
Jun 19 20:51:10 server scsi: [ID 107833 kern.notice] Vendor: QUANTUM
Serial Number: P i
Jun 19 20:51:10 server scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jun 19 20:51:10 server scsi: [ID 107833 kern.notice] ASC: 0x0 (<vendor
unique code 0x0>), ASCQ: 0x17, FRU: 0x0
Jun 19 20:51:10 server root: [ID 702911 daemon.notice] NetWorker media:
(critical) TapeAlert flag "Clean now" has been posted for /dev/rmt/4cbn
Jun 19 20:51:10 server root: [ID 702911 daemon.notice] NetWorker media:
(warning) /dev/rmt/4cbn writing: Bad file number, at file 50 record 9272
Jun 19 20:51:10 server root: [ID 702911 daemon.notice] NetWorker media:
(notice) sdlt320 tape FRZ694 on /dev/rmt/4cbn is full
Jun 19 20:51:10 server root: [ID 702911 daemon.notice] NetWorker media:
(notice) sdlt320 tape FRZ694 used 101 GB of 160 GB capacity
Jun 19 21:00:19 server root: [ID 702911 daemon.notice] NetWorker media:
(warning) /dev/rmt/4cbn moving: fsr 9267: drive status is Media Error,
Cleaning Requested
Sun has recommended that with the latest st driver and patch that no
modification is necessary to the st.conf. Is that an acceptable
recommendation? Not sure.
I'm really at wit's end here folks. Any feedback would be very much
appreciated. Since I only bought the library four months ago and am
already having problems on my third drive, I'm about ready to tell STK to
swap out the drive for an LTO.
TIA
-ty
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
**********************************************************************
This message has passed through an insecure network.
Please direct all enquiries to the message author.
**********************************************************************
This message has passed through an insecure network.
Please direct all enquires to the message author.
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
