Error in event log for legato server...

[LeDam]

Everyday we have some errors in the event log of our server:


1) qntmdlt

Event log error:

The device, \Device\Tape3, has a bad block. (envent id 7)

Legato log:

Apr 06 19:52:18 hn100: NetWorker media: (warning) \\.\Tape3 opening: Warning: tape drive \\.\Tape3 requires cleaning
Apr 06 19:52:24 hn100: NetWorker media: (warning) \\.\Tape3 opening: Warning: tape drive \\.\Tape3 requires cleaning
Apr 06 19:58:04 hn100: NetWorker media: (warning) \\.\Tape3 reading: Data error (cyclic redundancy check).
Apr 06 20:03:50 hn100: NetWorker media: (warning) \\.\Tape3 reading: Tape label read: Data error (cyclic redundancy check).
Apr 06 20:13:44 hn100: NetWorker media: (warning) \\.\Tape3 opening: Warning: tape drive \\.\Tape3 requires cleaning
Apr 06 20:13:48 hn100: NetWorker media: (warning) \\.\Tape3 opening: Warning: tape drive \\.\Tape3 requires cleaning
Apr 06 20:19:29 hn100: NetWorker media: (warning) \\.\Tape3 reading: Data error (cyclic redundancy check).
Apr 06 20:25:10 hn100: NetWorker media: (warning) \\.\Tape3 reading: Tape label read: Data error (cyclic redundancy check).

since this messages, Tape3 is "disable"

2) aic78xx

Event log error:

The device, \Device\Scsi\aic78xx2, did not respond within the timeout period (envent id 9)

Legato log:

Apr 06 10:18:34 hn100: NetWorker media: (info) wrote End-of-File marks on 000181
Apr 06 10:18:48 hn100: NetWorker media: (warning) \\.\Tape4 moving: tape_bsf bsf failed: The request could not be performed because of an I/O device error. (268436573)
Apr 06 10:18:48 hn100: NetWorker media: (info) wrote End-of-File marks on 001262

Apr 06 23:24:27 hn100: NetWorker media: (emergency) could not position 000463 to file 387, record 1053
Apr 06 23:24:36 hn100: NetWorker media: (warning) \\.\Tape2 reading: The request could not be performed because of an I/O device error.
Apr 06 23:24:39 hn100: NetWorker media: (warning) \\.\Tape2 reading: The I/O bus was reset.
Apr 06 23:24:44 hn100: NetWorker media: (warning) \\.\Tape2 reading: The semaphore timeout period has expired.
Apr 06 23:24:53 hn100: NetWorker media: (warning) \\.\Tape2 reading: The request could not be performed because of an I/O device error.
Apr 06 23:24:58 hn100: NetWorker media: (warning) \\.\Tape2 reading: The I/O bus was reset.
Apr 06 23:25:00 hn100: NetWorker media: (notice) Volume "000463" on device "\\.\Tape2": Block size is 32768 bytes not 65536 bytes. Verify the device configuration. Tape positioning by record is disabled.
Apr 06 23:25:00 hn100: NetWorker media: (warning) verification of volume "000463", volid 2915190273 failed, can not read record 1053 of file 387 on dlt7000 tape 000463
Apr 06 23:25:00 hn100: NetWorker media: (notice) verification of volume "000463", volid 2915190273 failed, volume is being marked as full.

Apr 07 08:28:20 hn100: NetWorker media: (warning) \\.\Tape4 moving: fsr 1501: The semaphore timeout period has expired.
Apr 07 08:28:20 hn100: NetWorker media: (emergency) could not position 001271 to file 244, record 1502
Apr 07 08:28:27 hn100: NetWorker media: (warning) \\.\Tape4 reading: The request could not be performed because of an I/O device error.
Apr 07 08:28:31 hn100: NetWorker media: (warning) \\.\Tape4 reading: The I/O bus was reset.
Apr 07 08:28:38 hn100: NetWorker media: (warning) \\.\Tape4 reading: The semaphore timeout period has expired.
Apr 07 08:28:45 hn100: NetWorker media: (warning) \\.\Tape4 reading: The request could not be performed because of an I/O device error.
Apr 07 08:28:49 hn100: NetWorker media: (warning) \\.\Tape4 reading: The I/O bus was reset.
Apr 07 08:30:20 hn100: NetWorker media: (notice) Volume "001271" on device "\\.\Tape4": Block size is 32768 bytes not 65536 bytes. Verify the device configuration. Tape positioning by record is disabled.
Apr 07 08:30:20 hn100: NetWorker media: (emergency) inactive ssid

 

[MoshiachNow]

Some questions:

1.Tape type (DLT,etc) ?
2.Operating system ? "Long live king Moshiach !"

 

[LeDam]

1) dlt7000
2) Windows 2000

 

[MoshiachNow]

Now I understand.

With DLT7000 we see these patterns for last 6 years.
Quantum have admitted problems and issued multiple FW versions (we now have 105),which helped a bit,but did not solve all problems.

We have switched to AIT long time ago,and have more peace of mind. "Long live king Moshiach !"

 

[LeDam]

So there is nothing to do????

 

[MoshiachNow]

Well,

with DLT8000 we had a better success rate reading files written on DLT7000 ...

1.Verify drives are properly and periodically cleaned.
2.Is it a certain tape problem? (then get rid of ut ..)
3.Is it a certain drive problem ? (then replace it ...) "Long live king Moshiach !"

 

[Till]

Hi LeDam !

I have had the same problem once before. I have 2 DLT 7000
drives in a Overland Jukebox, but they are Single-Ended devices and so the bus length is limited to 3 m. Using
shorter cables has fixed this problem in my case.

Hope it helps

Till

 

[MoshiachNow]

Yes,

But normally only in case that you realy see scsi errors in the system log .
Otherwise - these will be internal DLT7000 errors,of which I've seen thousands and can make a PHD on analising them,unfortunately.
I wish I had 100$ for each ...I would have been reach by now. "Long live king Moshiach !"

 

[Dagni]

Microsoft has acknowledged there is a problem -

http://support.microsoft.com/default.aspx?scid=kb;en-us;319313

Unfortunately, you have to specially request the patch.

 

[Rexxy]

I would also get the Firmware checked out as Levw suggested, we have had issues in the past also which we were lucky to fix after the firmware was upgraded or downgraded....

if it doesnt fix the problem, at least you cant scratch this off your troubleshooting list for this problem....

 

[cloner]

we had the same problem half a jear ago.

on our Quantum SDLT Drives we diabled the cleaning required option by maufacture ( its set in the Firmware of the Drives by quantum SDLT Drives every 30 days). So we have no automatic cleaning but no errors too.

cloner