I've also spent numerous hours over the last several weeks chasing ghost errors and cryptic messages like "Adamm Mover Error: GetDriveInfo Failure", and I've determined three things.
1. Always install latest firmware for drive and loader (if applicable) and always make sure latest drivers for controller card are installed. This is a no brainer, but there are still some of us who insist on ignoring these items.
2. That error occurs most often when the tape drive itself is busy. I have an Exabyte VXA loader, but the error returned when some other process has locked the drive is the same as you're seeing. Could be not responding for some reason, or other scsi timeout type problem, or it simply might be in use by a process at the time you're trying to access it.
3. The best way to trouble shoot the problem is to install the Dell management utilities for that drive, stop all BE services, run the utility, and see if the problem(s) still exist. My problems were non existent in that scenario, so it quickly eliminates many variables.
BTW - My issues were caused by the controller card (aha39160) scsi transfer rate. As soon as I throttled it down from 160 to 80... no more time out, device not ready, or any of the other reported errors. Go figure... that card was recommended by the HW mfg specifically because of the higher transfer rate. Odd that the transfer rate is not a problem when running diagnostics and utils supplied by the hardware mfg, it's only when I introduce B/U Exec into the mix that the trouble starts. Perfect example of the problems that arise by layering one mfg on top of another, on top of another (Symantec, Exabyte, Tandberg, & Adaptec... in my case).
-M
Message Edited by Mike_Wild on
08-29-2007 04:25 PMMessage Edited by Mike_Wild on
08-29-2007 04:34 PM