DAT72 drive dmesg error

[MR COLLARD]

This tape drive worked without problem since months.

But yesterday, I encounter the following problem:
tar tvf /dev/st0
tar: /dev/st0: Cannot open: No such device
tar: Error is not recoverable: exiting now

I tried to reboot the server; to shutdown all and to restart the tape drive first: without luck.

In POST, the drive is detected (C7438A).

In dmesg, there is the following message:
Starting timer : 0 0
blk: queue f7fc4a18, I/O limit 4095Mb (mask 0xffffffff)
(scsi1:A:3): 40.000MB/s transfers (20.000MHz, offset 32, 16bit)
Starting timer : 0 0
(scsi1:A:3:0): parity error detected in Data-in phase. SEQADDR(0x75) SCSIRATE(0x95)
(scsi1:A:3:0): parity error detected in Data-in phase. SEQADDR(0x74) SCSIRATE(0x95)
(scsi1:A:3:0): parity error detected in Data-in phase. SEQADDR(0x75) SCSIRATE(0x95)

I have opened a hardware call:
- I tried another tape drive, with no luck.
- I am waiting for another SCSI card (= mother board) from HP.

In the meantime, is there something that I can check in Linux ?

(There was no modifications [hardware and software] in this system since weeks)

Thanks in advance for your help.

Best regards.

Frederic


References:
Software:
- Red Hat Linux Enterprise 3
Hardware:
- HP DAT72 external SCSI tape drive (Q1523A)
- HP Proliant ML370 G3 (352531-421)

[Stuart Browne]

Wow.. Purdy.. Umm, what controller is the tape drive plugged in to?

Is it plugged into a RAID controller (SA something (cciss driver)), or the Adaptec controler (aic7xxx driver)?

[MR COLLARD]

The Adaptec controller.

[Ivan Ferreira]

It seems a real hardware problem, may be the controller, terminator or cable.

[Bejoy C Alias · Accepted solution]

Check whether ur dat is listed in /proc/scsi/scsi ,there should be an entry for the dat drive. it is not necessary that the drive will work if it is shown in the dmesg o/p . The necessary driver modules also should be loaded , check 'lsmod st' , 'depmod -a' . If this is not working then there may be a pblm with the scsi card , as u r telling that another drive is also not working with the same scsi card .

[MR COLLARD]

That was a Adaptec SCSI controller problem.

A new system board solved it.

Thanks for your help.

Frederic

[MR COLLARD]

The SCSI controller was "out".

Frederic