- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ioscan -fnC tape - software state is SCAN
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
Forums
Discussions
Discussions
Discussions
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
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
10-22-2004 05:04 AM
10-22-2004 05:04 AM
Other admin rebooted server to see if that would clear up the lbots...
No luck:
# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/0/0.0.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/1m /dev/rmt/1mnb /dev/rmt/c4t0d0BESTn
/dev/rmt/1mb /dev/rmt/c4t0d0BEST /dev/rmt/c4t0d0BESTnb
/dev/rmt/1mn /dev/rmt/c4t0d0BESTb
tape 2 0/1/0/1.1.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/2m /dev/rmt/2mnb /dev/rmt/c5t1d0BESTn
/dev/rmt/2mb /dev/rmt/c5t1d0BEST /dev/rmt/c5t1d0BESTnb
/dev/rmt/2mn /dev/rmt/c5t1d0BESTb
tape 9 0/2/0/0.0.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/9m /dev/rmt/9mnb /dev/rmt/c6t0d0BESTn
/dev/rmt/9mb /dev/rmt/c6t0d0BEST /dev/rmt/c6t0d0BESTnb
/dev/rmt/9mn /dev/rmt/c6t0d0BESTb
tape 10 0/2/0/1.2.0 atdd SCAN DEVICE IBM 03590E1A
/dev/rmt/10m /dev/rmt/10mnb /dev/rmt/c7t2d0BESTn
/dev/rmt/10mb /dev/rmt/c7t2d0BEST /dev/rmt/c7t2d0BESTnb
/dev/rmt/10mn /dev/rmt/c7t2d0BESTb
tape 3 0/3/0/0.1.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/3m /dev/rmt/3mnb /dev/rmt/c8t1d0BESTn
/dev/rmt/3mb /dev/rmt/c8t1d0BEST /dev/rmt/c8t1d0BESTnb
/dev/rmt/3mn /dev/rmt/c8t1d0BESTb
tape 4 0/3/0/1.3.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/4m /dev/rmt/4mnb /dev/rmt/c9t3d0BESTn
/dev/rmt/4mb /dev/rmt/c9t3d0BEST /dev/rmt/c9t3d0BESTnb
/dev/rmt/4mn /dev/rmt/c9t3d0BESTb
tape 5 0/5/0/0.2.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/5m /dev/rmt/5mnb /dev/rmt/c10t2d0BESTn
/dev/rmt/5mb /dev/rmt/c10t2d0BEST /dev/rmt/c10t2d0BESTnb
/dev/rmt/5mn /dev/rmt/c10t2d0BESTb
tape 6 0/5/0/1.3.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/6m /dev/rmt/6mnb /dev/rmt/c11t3d0BESTn
/dev/rmt/6mb /dev/rmt/c11t3d0BEST /dev/rmt/c11t3d0BESTnb
/dev/rmt/6mn /dev/rmt/c11t3d0BESTb
tape 0 0/8/0/0.0.0 atdd CLAIMED DEVICE IBM ULT3580-TD2
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c12t0d0BESTn
/dev/rmt/0mb /dev/rmt/c12t0d0BEST /dev/rmt/c12t0d0BESTnb
/dev/rmt/0mn /dev/rmt/c12t0d0BESTb
tape 11 0/8/0/1.3.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/11m /dev/rmt/c13t3d0BEST /dev/rmt/c13t3d0DDS
/dev/rmt/11mb /dev/rmt/c13t3d0BESTb /dev/rmt/c13t3d0DDSb
/dev/rmt/11mn /dev/rmt/c13t3d0BESTn /dev/rmt/c13t3d0DDSn
/dev/rmt/11mnb /dev/rmt/c13t3d0BESTnb /dev/rmt/c13t3d0DDSnb
tape 7 0/9/0/0.1.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/7m /dev/rmt/7mnb /dev/rmt/c14t1d0BESTn
/dev/rmt/7mb /dev/rmt/c14t1d0BEST /dev/rmt/c14t1d0BESTnb
/dev/rmt/7mn /dev/rmt/c14t1d0BESTb
tape 8 0/9/0/1.0.0 atdd CLAIMED DEVICE IBM 03590E1A
/dev/rmt/8m /dev/rmt/8mnb /dev/rmt/c15t0d0BESTn
/dev/rmt/8mb /dev/rmt/c15t0d0BEST /dev/rmt/c15t0d0BESTnb
/dev/rmt/8mn /dev/rmt/c15t0d0BESTb
Bad Scsi card? Tape library has no errors on drive...any ideas as to why the software state is SCAN?
Rgds...Geoff
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:09 AM
10-22-2004 05:09 AM
Re: ioscan -fnC tape - software state is SCAN
Sorry for the stupid question, but what about duplicate SCSI ID ?
Good luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:11 AM
10-22-2004 05:11 AM
Re: ioscan -fnC tape - software state is SCAN
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:11 AM
10-22-2004 05:11 AM
Re: ioscan -fnC tape - software state is SCAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:12 AM
10-22-2004 05:12 AM
Re: ioscan -fnC tape - software state is SCAN
remove using rmsf and add again using insf.
It might be just the kernel not able to identify the device state properly.
Hope this helps
Prashant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:16 AM
10-22-2004 05:16 AM
Re: ioscan -fnC tape - software state is SCAN
If this is a SAN connected device, it may be locked by another server and is not availble for use by this node at present.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2004 05:21 AM
10-22-2004 05:21 AM
Re: ioscan -fnC tape - software state is SCAN
We couldn't talk to robot from server - so we powered off the drive - voila - we could talk - so we re-installed the devices files (after poering up the drive) - using IBM utils (Not insf)....
Evrything is fine now.
Thanks for the input.