- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: robot and tape drive H/W path unmatch
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
тАО10-15-2001 06:47 PM - last edited on тАО09-02-2014 02:20 AM by Maiko-I
тАО10-15-2001 06:47 PM - last edited on тАО09-02-2014 02:20 AM by Maiko-I
robot and tape drive H/W path unmatch
I have a Overland Data robotic tape library connected to the physical path of 10/8. I can see my robot at path 10/8 from the ioscan output, however I would like to know why my tape drive is showing 10/4/8 H/W path. Isnt it should show 10/8 as well? Another question is that why my robot is using c720 driver and my tape drive is using a scsi1 driver? And why, although I have added in the schgr driver for autochanger in my kernel, it will still not being detected in my ioscan. Attached is my ioscan. Please help.
P.S. This thread has been moved from General to Tape Libraries and Drives. - Hp Forum Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2001 09:36 PM
тАО10-15-2001 09:36 PM
Re: robot and tape drive H/W path unmatch
The c720 is for scsi interfaces (look at the interfaces in your ioscan ).
You should hook your machine to the FWD interface with nothing else daisychained on it. It looks like your tapedrive is connected to an SE ( single ended ) SCSI interface.
Rgds
Alexander M. Ermes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2001 09:46 PM
тАО10-15-2001 09:46 PM
Re: robot and tape drive H/W path unmatch
Do you mean that I should never connect a tape drive using a SE port?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2001 10:00 PM
тАО10-15-2001 10:00 PM
Re: robot and tape drive H/W path unmatch
Some tape drives are not configured internally
for SE ports, only FWD. You are probably lucky
to see anything at all. You will need to attach
this drive to a FWD interface. As already
suggested by Alexander, you should only attach
these types of drives on their own interface.
They should not be shared.
HTH
-Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2001 10:33 PM
тАО10-15-2001 10:33 PM
Re: robot and tape drive H/W path unmatch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-16-2001 12:17 AM
тАО10-16-2001 12:17 AM
Re: robot and tape drive H/W path unmatch
I have checked physically that the drive is using a SE card and thus I dont think it is because of the card problem