- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- DLT Loader Problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2004 10:20 PM
тАО02-16-2004 10:20 PM
DLT Loader Problem
HARD ERROR
Failed to load tape into Drive
Plunge control System
Detected an over voltage
Failed Move
From Storage Slot 1 To Drive 1
2004-02-17
Code 62, Qualifier 10,
Sequence 115,53,131,54,53,135
Any help in this regard will be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2004 01:21 AM
тАО02-17-2004 01:21 AM
Re: DLT Loader Problem
Check the power coming to the tape drive.
Mohamed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2004 03:08 AM
тАО02-17-2004 03:08 AM
Re: DLT Loader Problem
The picker had difficulty putting the tape in the drive. Is this repeatible, or did it happen just once?
If you would, install HP Library & Tape Tools (www.hp.com/support/tapetools), run the tool, select the library/autoloader, and then generate a support ticket (from the support tool icon). Save this to a file, and then email it to ltt_team@hp.com, and we can review the error logs.
Alternately, if you have the remote management interface installed/configured, you can save off the report page.
Don't update firmware until AFTER you have collected the ticket/report. The current code is 1.62/2.62 (depending on which product you have).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2004 11:08 AM
тАО02-17-2004 11:08 AM
Re: DLT Loader Problem
code 60 qual 10 indicate that the robotic couln't load the tape and detect an overvoltage on the picker
you hava also several bugcheck logged on the DLT, these indicate problem to the DLT, may be a Dropped leader.
Anyway, try to upgrade first the firmware form 23.30 to the actual 26.00
Be sure you have a good electrical power distribution and good grounding
marino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2004 02:47 PM
тАО02-17-2004 02:47 PM
Re: DLT Loader Problem
The A209 bugchecks in the drive are a problem called "full whir" (although they can be dropped leaders too).
If you look in the drive/media log of the library, there are errors saying "tape drive rejected load of tape".
The logs show that the tapes came from a number of different slots, but its hard to tell if they are the same or different tapes, as there are no barcodes. (Always a good idea to use barcodes with the 1/9 and 2/20 family products, as they aid in logging the tape that had problems).
Definately update to 2.60 firmware. You can use the "details" button on the "get files from web" to see the fixes in the various releases between 2.30 and 2.60. There were some changes around tape unload, but not specifically for an overforce.
One possible cause could be oxidation on the brush tracks. With 2.60 firmware, run the "Full Sweep" test for 100 cycles - that will clean the tracks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2004 04:26 PM
тАО02-18-2004 04:26 PM
Re: DLT Loader Problem
Just for updating you. I have applied the following remedies but the problem unchanged.
-I ran the sweeptest 100.
- Cleaned the white notch, shown inside eper left corner.
-Firware revision upgraded
It is very important to tell you that when start the arcserve manager, it continuously rotating the cartridge for indefinite time. when I stop the tape engine, it goes in loop, and does not release the mouse untill I logoff the session.
Sometime it shows the message.
Could not start the ARCserve Tape Engine service on local computer.
Error 183: Cannot create a file when that file already exist
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2004 07:18 PM
тАО02-18-2004 07:18 PM
Re: DLT Loader Problem
I'm sorry the suggestions did not solve your problem so far.
> It is very important to tell you that when start the arcserve manager, it continuously rotating the cartridge for indefinite time. when I stop the tape engine, it goes in loop, and does not release the mouse untill I logoff the session.
It's hard to tell if that is a hardware problem or a software problem.
Can you collect another LTT support ticket (after disabling the backup services), and we can see if there are any new entries in any of the logs? The firmware update will clear the library logs, so any errors will be new.
If there are no errors there, we should look at the windows event logs.