The sas card itself may be at fault, or maybe check device manager and see if the sas card is reporting an error there, maybe it doesn't like the driver.

you could connect the sas card to a different system and see if the error follows it.

I've got an engineer on standby to replace the card but it seems odd that it will do everything required apart from sustained writes. In the old days on HP kit the first thing to check with this sort of problem was cables and terminators - short bursts of activity would be fine but anything strenuous would overload the bus.

I guess even SAS cards have internal terminators. Yesterday I was trying to find a best practice guide to see if it would indicate which port(s) are recommended on the card and library.

Cheers

Was this ever resolved?? We have the same issue with unexpected data in ITDT. The LTO4 drive is fine as we swapped it from a TL4000 to a TL2000. It seems it doesn't like the TL4000 which is connected via SAS to an HP P411 in a DL160G6 running win2008 R2. The TL2000 is connected via iSCSI.

Hi,

We did resolve it in the end, there was a later version of the LTO6 driver on IBM's website (6.2.6.0 I think) and we changed ports on the Dell SAS card so there still may be a problem but we've bypassed it for now - backups have been fine for the last 3 weeks.

Lots of things to check from the P411 side of things though, particularly if you've got the Insight Manager agents installed on the DL160 - turn off the Storage Agent (which will turn off the Foundation Agent) if it's running. Latest P411 firmware that I can see is 6.64. Also try the port swap.

W

what version do you run? there on v9.1 at the moment

do you there an issue with the drive , can you do a dump of the logs?

I'm currently running IBM Tape Diagnostic Tool - Graphical Edition - v9.1.0.20161006.

I've pulled the drives and put them in a TL2000 with the same Library firmware C.30. The drives show no issues when routed through the iSCSI to SAS card on the TL2000.

I will check the couple of things Witchy_UK later tonight and report back. I don't really want to hijack this thread but I may or may not create a new one if what Witchy says doesn't resolve it.

Thanks guys!

I've started my own post and this seems to be driver related. However my post is awaiting a moderator to approve the post. I assure you it's more detailed than required.

Thanks,

Pat