Failed to update Surestore 718 autoloader update

[Ben Helthuis]

After reading the following message from Curtis Ballard dd. nov 12, 2002,
I decided to update my Surestor 718, because I had the same problem.

---------------------------------------------------------------------------------------
Message:
LTT should update a C6280 with 2.07 just fine.
The only limitation I am aware of is when the inquiry string has been changed.
If the inquiry string is not set you need to use the "CONFIG *" menu and change the "INQUIRY TOGGLE" setting then LTT should recognize it. That setting forces the factory default inquiry string to be reported.
After download the inquiry string will change back to whatever it had been set to.
If you need it to stay at the defaults go back into "CONFIG *" and reset it after the download.
End message.
---------------------------------------------------------------------------------------

After changing "INQUIRY TOGGLE", my computer detected the autoloader correctly.
So I started to update from 2.07 to 2.12.

After about 30 seconds, the progress bar stopped (Showing 3 blocks).
The display of the autoloader displays "scsichpbdint".

About 3 minutes later there is a popup window telling: "Waiting for pending I/O request to complete".

5 minutes later there is a popup window saying: Firmware update failed.

After rebooting, LTT detects C6280 but no tape device.

Trying to update the C6280 again gives the same result.

Is there anything I can do to resolve this problem.

Kind regards,

Ben

[CA713937]

I'll let Curtis respond on this one. I think it's getting an expected interrupt during the code download.

[Curtis Ballard]

Dave is correct. The autoloader is seeing an illegal signal on the SCSI bus during the firmware update process.

To do a firmware update the autoloader loads only the minimum software required for SCSI communication and erases all other memory. This minimum SCSI module is unable to handle any events other than normal firmware update. Illegal bus events can't be handled. The normal firmware is able to handle many bus problems so you may not see it but it is still a problem which will probably impact performance.

This problem only occurs when there is some problem with the HBA, cabling, or terminator. I'd remove the drive from the bus and use only the cable from the host to the controller with the terminator on the controller and try updating again.

The drive will not show up on the SCSI bus until the library controller tells it what ID to use but that portion of the library controller firmware has been erased to make room for the new firmware so the drive won't be available until the firmware update is complete.

[Ben Helthuis]

I followed your advice and after disconnecting the tape-drive from the SCSI-bus, upgrading ran perfectly!
LTT showed my C6280 to be upgraded to v2.12

Then I reconnected the tapedrive to the bus.
During the boot-proces my machine detects a C6280 and a Quantum DLT 7000.

But LTT and Windows do not detect the Quantum DLT 7000.

LTT and Windows detect a
"QEAFTEM DTT 0 0 2 6D" as an unknown device.

Did I blow my tapedrive firmware?
Anything I can do now?

Ben

[CA713937 · Accepted solution]

> LTT and Windows detect a
> "QEAFTEM DTT 0 0 2 6D" as an unknown device.
__QUANTUM DLT7000 <- what it should be.

Notice how every other character is messed up?

Something is wrong with the upper bus (the DLT drive is 16 bits, the autoloader only 8).

What HBA do you have, how is it cabled, and how is it terminated?

You should also check for bent pins on all the connectors.

[Ben Helthuis]

Thank you David,

you solved my problem.

The HA is the original one AHA-2940 ultra/ultraW with Bios V2.20.0

I did not see anything unusual after inspecting my scsi cable.

After changing from external cable to
internal cable, I did have succes.
So I expect to a faulty cable or the external HA connector is expected.

How is this possible after just trying to
upgrade the autoloader?

Thank you for helping me out!

Ben

[Ben Helthuis]

Now that everything is working again, I like
to tell you what was the reason I wanted to update.

Well, Windows registry tells me there is an unknown medium changer connected.
Tapeware is running fine, but maybe there is other software which expects a known medium changer.
Any suggestion here?

Ben

[CA713937]

Usually the backup applications use something called NT miniport and their own drivers, so its OK if it says "unknown media changer" in device manager.

There is a driver file that provides a windows driver for most of the HP and Compaq autoloaders. I'll see if I can find the URL for you.