With older SDLT320 drives I had a similar problem; although new media
faired a little better.  For SDLT320 there was a calibration track
written to the media when it is first written.  If a bad drive writes
this track other drives have a problem reading it.  Based on tapes I
send to Quantum/ATL they replaced certain drives.   This doesn't
sound like your problem though.. your saying new media on either drive
will produce the write error.

It being LVD scsi attached, I'd definitely check/swap out cables and
terminators.  Check /etc/system and make sure you have no scsi-options
line throttling the bus.

Robert Maiello
Pioneer Data Systems


On Wed, 20 Jul 2005 11:37:10 +0200, Bolay, Vincent
<vincent.bolay AT MEDTRONIC DOT COM> wrote:

>Hello,
>
>This is my config:
>
>SunOS lau-backup2-b 5.9 Generic_117171-05 sun4u sparc SUNW,Sun-Fire-280R
>Patch: 113277-24 SunOS 5.9: st, sd and ssd Patch
>Sun StorEdge(TM) Enterprise Backup 7.2.Build.172 Network Edition/35
>Storagetek Library L80 with Quantum SDLT320 drives firmware rev 80, SCSI LVD
>
>I often get the following messages:
>
>/nsr/logs/daemon.log:
>
>07/20/05 01:32:41 nsrd: media notice: sdlt320 tape DEX066 on /dev/rmt/0ubn
is full


>07/20/05 01:32:41 nsrd: media notice: sdlt320 tape DEX066 used 28 GB of 160
GB capacity
>07/20/05 01:32:59 nsrd: media notice: Volume "DEX066" on device
"/dev/rmt/0ubn": Block size is 32768 bytes not 131072 bytes. Verify the
device configuration. Tape positioning by record is disabled.
>
>/var/adm/messages:
>
>Jul 20 01:32:41 lau-backup2-b scsi: [ID 107833 kern.warning] WARNING:
/pci@8,700000/pci@1/scsi@2/st@1,0 (st50):
>Jul 20 01:32:41 lau-backup2-b   Error for Command: write
Error Level: Fatal
>Jul 20 01:32:41 lau-backup2-b scsi: [ID 107833 kern.notice]     Requested
Block: 9579                      Error Block: 9579
>Jul 20 01:32:41 lau-backup2-b scsi: [ID 107833 kern.notice]     Vendor:
QUANTUM                           Serial Number:  P    i
>Jul 20 01:32:41 lau-backup2-b scsi: [ID 107833 kern.notice]     Sense Key:
Media Error
>Jul 20 01:32:41 lau-backup2-b scsi: [ID 107833 kern.notice]     ASC: 0xc
(write error), ASCQ: 0x0, FRU: 0x0
>
>It can happen on any drive and with new or used tapes. The tapes are
labeled always the same way.
>I know that this is a known issue, but nobody (Sun, Sunmamagers, Google)
has been able to provide a solution yet.
>
>TIA for your replies
>
>Vincent Bolay
>Systems Engineer
>Medtronic Europe S�rl
>Route du Molliau 31
>Case postale
>CH-1131 Tolochenaz
>Switzerland
>Phone: (+41 -21) 802 75 34
>Fax: (+41 -21) 802 79 11
>E-mail: vincent.bolay AT medtronic DOT com
>
>--
>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
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=