- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Daisychaining HP Surestore C9264CB
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
тАО12-07-2010 08:28 AM
тАО12-07-2010 08:28 AM
Daisychaining HP Surestore C9264CB
Thinking the Dell unit may be defective I purchased an identical C9265CB, set it's SCSI ID to 6 and brought everything up. SCSI BIOS saw both devices, Linux also saw them assigning the same /dev/sg0 and /dev/sg1 to them but again trying to interact with the device on ID 6 I get the same failures
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 24
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: Field in Error = 03
mtx: Request Sense: BPV=yes
mtx: Request Sense: Error in CDB=yes
mtx: Request Sense: SKSV=yes
mtx: Request Sense: Field Pointer = 00 00
READ ELEMENT STATUS Command Failed
I have the SCSI cable going into the bottom interface of the first tape robot, a small 18 inch cable from the top interface of the first robot to the bottom interface of the second robot and a terminator on the top interface of the second robot.
Both robots have 3 DLT cartridges loaded, both power up without errors.
I have been able to write to the tapes in the /dev/sg0 with a linux tar -zcvf /dev/st0 filenames and able to read the tapes successfully. My problem is I need to have both tape robots available for full and differential backups in a week's time, can't be changing tapes manually.
Is there a problem daisychaining two DLT robots together?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 08:39 AM
тАО12-07-2010 08:39 AM
Re: Daisychaining HP Surestore C9264CB
Depending on the settings there are 1 or 2 SCSI addresses per device (robot and drive) or it does LUN mode (e.g. 6:0 is robot, 6:1 is drive) with a single ID per box.
You should check for unique SCSI IDs.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 10:30 AM
тАО12-07-2010 10:30 AM
Re: Daisychaining HP Surestore C9264CB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 10:44 AM
тАО12-07-2010 10:44 AM
Re: Daisychaining HP Surestore C9264CB
...
The HP StorageWorks 1/8 Ultrium 232, Ultrium 448 and Ultrium 960 Tape Autoloader models
and the DLT VS80 Tape Autoloader models occupy one SCSI ID.
...
All other Tape Autoloader models occupy two SCSI IDs...
So check if a single box occupies 1 or 2 SCSI IDs.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 11:52 AM
тАО12-07-2010 11:52 AM
Re: Daisychaining HP Surestore C9264CB
I reset the SCSI ID on the original unit to use ID 3 and cycled the power on the tape robot as it instructed. I rebooted the linux machine, the BIOS saw both tape robots at the correct SCSI IDs. Linux booted and saw both devices at the correct SCSI IDs.
If I run
mtx -f /dev/sg0 inventory
the original robot scans all slots.
I then run
mtx -f /dev/sg1 inventory and it too scans all slots.
I run mtx -f /dev/sg0 inquiry
and same for sg1 and both return information.
mtx -f /dev/sg0 inquiry
Product Type: Tape Drive
Vendor ID: 'BNCHMARK'
Product ID: 'VS640 '
Revision: '5032'
Attached Changer: No
[root@vrod sg]# mtx -f /dev/sg1 inquiry
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'C9264CB-VS80 '
Revision: '5E40'
Attached Changer: No
[root@vrod sg]#
Running mtx -f /dev/sgX status produces:
mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full
Storage Element 2:Full
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full
Storage Element 6:Full
Storage Element 7:Full
Storage Element 8:Full
[root@vrod sg]#
[root@vrod sg]# mtx -f /dev/sg1 status
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 24
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: Field in Error = 03
mtx: Request Sense: BPV=yes
mtx: Request Sense: Error in CDB=yes
mtx: Request Sense: SKSV=yes
mtx: Request Sense: Field Pointer = 00 00
READ ELEMENT STATUS Command Failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 01:36 PM
тАО12-07-2010 01:36 PM
Re: Daisychaining HP Surestore C9264CB
you have a server with a HBA
you have two autoloaders
first autoloader is a 1/8 with a VS80 tape drive
second autoloader is a Dell with a DLT drive
your goal is to daisy chain both unit on the single scsi chain.
well for what I know:
the HP 1/8 with VS80 use a single SCSI id and two luns (lun 0 and lun 1) so you should be sure you enable lun scanning in your HBA bios
the Dell autoloader is unknown to me, but I may suppose that it use two SCSI id, one for the drive and one for the robot (could be also it use LUN mode, it should appear in next step)
at this point, you should first be sure that during POST of your pc, when the control is passed to the HBA Bios, you can see all the four devices (two robots and two drives) it is not important if it is a LUN or a SCSI ID, all four device should appear in the list at that moment.
if you cannot see all four device, try to attach one at a time, and identify what can be seen and what cannot.
when all four devices are listed in the hba bios, then you can proceed further
I'm not a Linux specialist, but from your last output it looks like you can see only the two tapes one a vs80 and another is a SDLT640, both are probably the LUN 0 of the relative scsi ID > then probably it is enough to enable LUN scanning in your HBA Bios
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-07-2010 02:02 PM
тАО12-07-2010 02:02 PM
Re: Daisychaining HP Surestore C9264CB
So to be clear, I have two C9264CB Autoloader 1/8 devices, the first (working) at SCSI ID 3, the second (not working) at SCSI ID 6.
I don't know how to get into the Proliant's onboard SCSI configuration to enable LUN scanning.
Why would one unit work and the other not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2010 07:02 AM
тАО12-08-2010 07:02 AM
Re: Daisychaining HP Surestore C9264CB
I do not know for the autoloader with the VS640
did you observed the server monitor during POST? did you see the HBA scanning? did you identify what is detected? during the POST, when you see the HBA banner, you shoudl probably see also a message like "press CTRL A or press F8" to enter the bios... this is the key to enter and enable lun scanning
(usually raid controllers do not support lun scanning, and do not support tape drive)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-08-2010 04:29 PM
тАО12-08-2010 04:29 PM
Re: Daisychaining HP Surestore C9264CB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-09-2010 03:43 PM
тАО12-09-2010 03:43 PM
Re: Daisychaining HP Surestore C9264CB
[root@vrod sg]# mtx -f /dev/sg1 status
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 24
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: Field in Error = 03
mtx: Request Sense: BPV=yes
mtx: Request Sense: Error in CDB=yes
mtx: Request Sense: SKSV=yes
mtx: Request Sense: Field Pointer = 00 00
READ ELEMENT STATUS Command Failed
The above is an error message saying that the READ ELEMENT STATUS command sent by mtx was illegal with this device. It points to an error in byte 3, bit 0 of the CDB which is a field called "STARTING ELEMENT ADDRESS". It doesn't say waht value was in that field of the CDB but appently mtx is sending a value that the autoloader doesn't support.
That is a really old autoloader. I'm not able to look and see if mtx was supported with that autoloader or not.
You might check and see if that is new enough that it has a configuration for "Random" mode or "Sequential" mode. If so set it to "Random" as the READ ELEMENT STATUS command isn't allowed when in Sequential.