Hi. Our HP Proliant RedHat EL3.4 server is hanging after we make a backup with the HP Ultrium Tape autoloader. The server has been running backups for a year without any problems. The tape loader shows error code :13 00 *R*, but i cant find any error code descriptions.
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
these units have 2 different possible power supplies. KM88 or KM 86 KM88 are more rectangular, km86 have an angle cut in it. you could send it in to a repar facility like Top Ten USA, or try to solder the fuse yourself.
I have two of these Quantum SuperLoader 3 (with LTO3 drives) and one does keep giving me the same hassle. I haven't figured out how to fix this, but I've gotten past the error: disconnect the autoloader from the host computer (i.e. or stop rsm, mtx, or whatever controlling sofware you use), reboot the autoloader, get the tape out of the drive (e.g. move command from the autoloader's console or web interface), insert a cleaning tape (a few times), reconnect everything (i.e. start back up your controlling service).
Mixing brands can be an issue because different brands might use different lubricants on the tape it self. I would check with the vendor - are are you positive you are using the excact same LTO version?
I have to admit this is a tough one. You seem to have tried most things i would try 1st.
I would suggest trying to download an eval coy of another backup program such as backup exec 12.5 from the symantec website and trying that.
This enables you to eliminate the backup software from your enquiries and if you also enable BUEX to use its own drivers (rather than the standard windows drivers) then that is another thing eliminated.
http://www.trilan-it.com/ are pretty good near the Berkshire area if you need a field call to help sort the issue but i would try BUEX 1st as that will help diagnose the problem even if you dont wish to continue with their software
The problem you described is not a driver problem. So long as you are using the Veritas drivers you should be good to go.
SCSI time-outs and disconnects are hardware problems.
Sometimes they can be resolved by changing the throughput settings on the SCSI controller connected to the drive. Controllers usually default to very high speeds because they are used for hard drives. Lowering the speeds to support the slower throughput of tape drives can sometimes help.
During the POST there should be a key combination you can press to access the setup for the controller and modify the throughput settings.
Aside from that you have to replace the SCSI controller or tape drive until you figure out which one is causing the problem. Maybe the SCSI card is not seated properly.
Try changing the autoloader SCSI ID and the tape drive SCSI ID at the front panel:
Use this option to view or change the SCSI IDs used by the autoloader. The autoloader occupies two SCSI
IDs, one ID is assigned to the autoloader and the second ID is assigned to the tape drive.
The default SCSI ID for the autoloader's SCSI controller is 0. The default SCSI ID for the tape drive is 5.
You only need to change a SCSI ID if there is another device, or devices, already assigned to these IDs.
NOTE: This option is primarily used if the autoloader is in an error state. However, any
backups that have not been verified as complete should be considered lost.
NOTE: If you changed the SCSI ID, you may also need to cycle power on the host
system and reconfigure your backup software before you can use the
autoloader. Consult your hardware and software manuals for more information.