- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Ejecting Stuck Media on a DLT8000 Drive
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
тАО11-01-2002 11:47 AM
тАО11-01-2002 11:47 AM
I have a stuck tape that does not respond to 'Unload All Tapes' command from the front panel, and the uma utility from the command line.
Unload All Tapes returns an Error: Drive Failure.
On HPUX11i, what's the right command to eject the tape?
# uma -ioctl /dev/rac/c6tod0
/dev/rac/c0t6d0>stat
shows that Slot 11 is Empty beacuse the tape is in the drive. From /dev/rac/c6t0d0, how do I eject the tape.
# man uma <- shows that there is a 'offl drive' command but when I use it, it tells me that there is no such option. How do you use this option.
Also, will the command mc works in ejecting a stuck tape in a 20-Slot DLT8000?
How about the command mt? How do you use it? What's the difference between all these, uma, mc, mt?
Thanks.
Jimmy
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2002 10:05 AM
тАО11-03-2002 10:05 AM
Solutionlive free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2002 11:19 AM
тАО11-03-2002 11:19 AM
Re: Ejecting Stuck Media on a DLT8000 Drive
if you will not be able to eject tape by HPUX command(s) and front panel operations then call HP for drive replacement.
Please inspect ALL tapes inside your library for broken, unseated, or misaligned tape leaders (read lib's manual for more info).
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2002 02:20 PM
тАО11-03-2002 02:20 PM
Re: Ejecting Stuck Media on a DLT8000 Drive
Other than the checking for the bad tapes, I would also check that your firmware is up to date, both for your drive(s) and your tape library.
With omniback make sure that you have the following items.
st_ats_enabled set to '0' in your system kernel.
Make sure that your tape library attempts to ejects tapes for failed sessions.
Devices --> Select Library, right click,
Control --> Select 'Eject Medium' as the
busy drive handling option and not 'Abort'
Disable the EMS monitoring for SCSI tape drives, see attached document.
To move a stuck tape without using 'uma'
e.g.
# mt -t /dev/rmt/1m rew (rewind the tape)
# mt -t /dev/rmt1m offl (take the drive off-line)
# mc -p /dev/rac/c0t6d0 -sD1 -dS1 (move the tape from drive one to slot 1, see the man page for 'mc')
Run a library barcode scan, so that your library and omniback database are in sync.
I would also like to suggest you set a proper robot controller device. See my next answer for the attachment.
HTH
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2002 02:22 PM
тАО11-03-2002 02:22 PM
Re: Ejecting Stuck Media on a DLT8000 Drive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2002 01:18 PM
тАО11-04-2002 01:18 PM
Re: Ejecting Stuck Media on a DLT8000 Drive
Some questions for Michael:
>Other than the checking for the bad tapes, I
>would also check that your firmware is up to
>date, both for your drive(s) and your tape
>library.
What would be the right firmware revision?
>With omniback make sure that you have the
>following items.
>st_ats_enabled set to '0' in your system
>kernel.
My current setting for st_ats_enabled is '1'.
This must be the default setting. What would
it do if I set it to '0'? Is there a reason
why default setting is '1'?
>Make sure that your tape library attempts to
>ejects tapes for failed sessions.
Usually, the tape library ejects the tape in
cases of failed sessions. What happened was
that the directory was changed during the
backup session. The session failed but
somehow the tape was not ejected. Another
session started and the RAC took the next
tape but did not do anything with it - just
held it. So, it ended up being one tape in
the drive and another in the RAC.
>Devices --> Select Library, right click,
>Control --> Select 'Eject Medium' as the
>busy drive handling option and not 'Abort'
I don't see the Eject Medium option. Sorry,
but I should have mention my OBII vesion is
3.5.
>Disable the EMS monitoring for SCSI tape
>drives, see attached document.
To move a stuck tape without using 'uma'
e.g.
# mt -t /dev/rmt/1m rew (rewind the tape)
# mt -t /dev/rmt1m offl (take the drive off-line)
# mc -p /dev/rac/c0t6d0 -sD1 -dS1 (move the tape from drive one to slot 1, see the man page for 'mc')
Run a library barcode scan, so that your library and omniback database are in sync.
Thanks Michael. Thanks to everyone.
I'll let you how it goes.
Cheers,
Jimmy