- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- STK9840 fiber drive
StoreEver Tape Storage
1747973
Members
3525
Online
108756
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-29-2000 10:26 PM
тАО06-29-2000 10:26 PM
STK9840 fiber drive
when trying to access the drive I get a device busy. The tape2 driver is claimed
in ioscan.HPUX11.x is the OS, is there a new tape2 or stape driver needed.
Thank
-Tyrone
in ioscan.HPUX11.x is the OS, is there a new tape2 or stape driver needed.
Thank
-Tyrone
STK9840 fiber drives
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2000 02:25 AM
тАО06-30-2000 02:25 AM
Re: STK9840 fiber drive
Tyrone,
Can you provide us with some more information, please?
How did you try to access the tape drive? Omniback or a UNIX command like tar or pax?
Have you tried to find out if someone else uses the device by 'fuser?
Can you provide us with some more information, please?
How did you try to access the tape drive? Omniback or a UNIX command like tar or pax?
Have you tried to find out if someone else uses the device by 'fuser
There is no good troubleshooting with bad data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2000 10:33 PM
тАО07-08-2000 10:33 PM
Re: STK9840 fiber drive
Here are some wild guesses for you - we don't really have enough info...
Focus first on the FC - patching and firmware are a fairly common issue.
1. If you are using an FC MUX check firmware in the MUX/update if necessary
2. Consider OS patches for SCSI, TAPE, STAPE, FC...
3. Reset the FC MUX at some point...
Is this a SAN? Are the tape drives accessable from several servers?
If so the other server may be holding the lock...
Load a tape into the drive.
With a tape in the drive try this..
diskinfo -v /dev/0mbest
(of course use the correct /dev/.. path for YOUR tape drive...)
If you get some info about the tape drive then things are probably working at the OS level.
If you get device not available (or some such) then look to drivers and hardware issues - or the drive really is locked.
Are you using Omniback. Get recent Omniback patches.
http://ovweb.external.hp.com/cpe/patches/ob/ob.html
After you get OB patches in place, call for Omniback support - there may be an unreleased patch too.
In UX you usually have multiple special files for one drive (0m, 0mbest,c6t0d0...)
Might anything else be holding the drive locked (tar, fbackup...)
In Omniback you can have multiple drive names for a single physical drive also - if so be sure to use the ADVANCED option LOCK NAMES.
If it is a SAN - later versions of Omniback allow for some advanced locking.
Good Luck.
Focus first on the FC - patching and firmware are a fairly common issue.
1. If you are using an FC MUX check firmware in the MUX/update if necessary
2. Consider OS patches for SCSI, TAPE, STAPE, FC...
3. Reset the FC MUX at some point...
Is this a SAN? Are the tape drives accessable from several servers?
If so the other server may be holding the lock...
Load a tape into the drive.
With a tape in the drive try this..
diskinfo -v /dev/0mbest
(of course use the correct /dev/.. path for YOUR tape drive...)
If you get some info about the tape drive then things are probably working at the OS level.
If you get device not available (or some such) then look to drivers and hardware issues - or the drive really is locked.
Are you using Omniback. Get recent Omniback patches.
http://ovweb.external.hp.com/cpe/patches/ob/ob.html
After you get OB patches in place, call for Omniback support - there may be an unreleased patch too.
In UX you usually have multiple special files for one drive (0m, 0mbest,c6t0d0...)
Might anything else be holding the drive locked (tar, fbackup...)
In Omniback you can have multiple drive names for a single physical drive also - if so be sure to use the ADVANCED option LOCK NAMES.
If it is a SAN - later versions of Omniback allow for some advanced locking.
Good Luck.
Omniback and NT problems? double check name resolution, DNS/HOSTS...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP