- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- SCSI Domain Validation problems with LTO-4 drive a...
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-07-2007 11:51 PM
тАО11-07-2007 11:51 PM
SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
I'm having a hard time to get our Overland Neo 4100 Lib (should be identical to MSL6060) with two HP Ultrium 1840 drives (OEM FW B12H) to negotiate correctly with the SCSI HBAs. At the moment both drives are only doing U160.
The server has two U320 LSI HBAs (20320) one of the controller is directly connected to a drive, the other controller is connected to the drive and the Lib. I updated both controllers to the current (non RAID) firmware. For testing I also added an Adaptec U29320 controller - no change.
I'm running Debian Etch, but I've also tried other distros. During boot time I get the kernel message that the drives are only connected with U160 speed. I already compiled the latest LSI modules for my debian kernel, but this didn't change anything (same for Adaptec modules).
mptbase: ioc0: mpt_send_handshake_request start, WaitCnt=1
Vendor: HP Model: Ultrium 4-SCSI Rev: B12H
Type: Sequential-Access ANSI SCSI revision: 05
Disabling QAS due to noQas=01 on id=1!
target5:0:1: Beginning Domain Validation
target5:0:1: Ending Domain Validation
target5:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 64)
The write speed is also limited:
# ./hptapeperf -o /dev/nst1 -i 3 -r 8192 -R -b 131072
16384.00 Mbytes transferred in 144 seconds, 113.78 Mbytes/sec.
16384.00 Mbytes transferred in 137 seconds, 119.59 Mbytes/sec.
# dd if=/dev/zero of=/dev/nst1 bs=262144 count=50000
50000+0 Datens├дtze ein
50000+0 Datens├дtze aus
13107200000 Bytes (13 GB) kopiert, 96,4847 Sekunden, 136 MB/s
I had contact to the LSI kernel module developer, he claims that the drives are not able to do U320. Debugging informations shows that the controllers offers U320 (0x08), but the drives do not accept that offer.
debug information:
(http://pastebin.ca/765223)
1. mptbase: ioc0: Initiating bringup
2. ioc0: LSI53C1030 C0: Capabilities={Initiator,Target}
3. mptbase: ioc0: PortPage0 minSyncFactor=8
4. mptspi: ioc0: saf_te 0
5. scsi5 : ioc0: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=66
6. mptspi: ioc0: id=0 Requested = 0x00000a00 ( factor = 0x0a @ offset = 0x00 )
7. mptspi: ioc0: id=1 Requested = 0x00000a00 ( factor = 0x0a @ offset = 0x00 )
8. Vendor: HP Model: Ultrium 4-SCSI Rev: B12H
9. Type: Sequential-Access ANSI SCSI revision: 05
10. Disabling QAS due to noQas=01 on id=1!
11. mptspi: ioc0: id=1 min_period=0x08 max_offset=0x7f max_width=1
12. target5:0:1: Beginning Domain Validation
13. mptspi: ioc0: id=1 Requested = 0x00000a00 ( factor = 0x0a @ offset = 0x00 )
14. mptspi: ioc0: id=1 Requested = 0x00000a00 ( factor = 0x0a @ offset = 0x00 )
15. scsi 5:0:1:0:
16. command: Inquiry: 12 00 00 00 60 00
17. scsi 5:0:1:0:
18. command: Inquiry: 12 00 00 00 60 00
19. scsi 5:0:1:0:
20. command: Inquiry: 12 00 00 00 60 00
21. scsi 5:0:1:0:
22. command: Inquiry: 12 00 00 00 60 00
23. mptspi: ioc0: id=1 Requested = 0x20000a00 ( Wide factor = 0x0a @ offset = 0x00 )
24. scsi 5:0:1:0:
25. command: Inquiry: 12 00 00 00 60 00
26. scsi 5:0:1:0:
27. command: Inquiry: 12 00 00 00 60 00
28. scsi 5:0:1:0:
29. command: Inquiry: 12 00 00 00 60 00
30. mptspi: ioc0: id=1 Requested = 0x207f0a00 ( Wide factor = 0x0a @ offset = 0x7f )
31. mptspi: ioc0: id=1 Requested = 0x207f0803 ( Wide factor = 0x08 @ offset = 0x7f IU DT )
32. mptspi: ioc0: id=1 Requested = 0x207f0803 ( Wide factor = 0x08 @ offset = 0x7f IU DT )
33. mptspi: ioc0: id=1 Requested = 0x207f0823 ( Wide factor = 0x08 @ offset = 0x7f IU DT RDSTRM )
34. mptspi: ioc0: id=1 Requested = 0x207f0833 ( Wide factor = 0x08 @ offset = 0x7f IU DT WRFLOW RDSTRM )
35. mptspi: ioc0: id=1 Requested = 0x207f0873 ( Wide factor = 0x08 @ offset = 0x7f IU DT WRFLOW RDSTRM RTI )
36. mptspi: ioc0: id=1 Requested = 0x207f08f3 ( Wide factor = 0x08 @ offset = 0x7f IU DT WRFLOW RDSTRM RTI PCOMP )
37. scsi 5:0:1:0:
38. command: Inquiry: 12 00 00 00 60 00
39. scsi 5:0:1:0:
40. command: Inquiry: 12 00 00 00 60 00
41. scsi 5:0:1:0:
42. command: Inquiry: 12 00 00 00 60 00
43. mptspi: ioc0: id=1 Read = 0x20400902 ( Wide factor = 0x09 @ offset = 0x40 DT )
44. scsi 5:0:1:0:
45. command: Test Unit Ready: 00 00 00 00 00 00
46. scsi 5:0:1:0:
47. command: Test Unit Ready: 00 00 00 00 00 00
48. scsi 5:0:1:0:
49. command: Test Unit Ready: 00 00 00 00 00 00
50. scsi 5:0:1:0:
51. command: Test Unit Ready: 00 00 00 00 00 00
52. target5:0:1: Domain Validation skipping write tests
53. target5:0:1: Ending Domain Validation
54. mptspi: ioc0: id=1 Read = 0x20400902 ( Wide factor = 0x09 @ offset = 0x40 DT )
55. target5:0:1: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 64)
The LTT tool also warns about the U160 mode:
The current SCSI configuration is likely to be limiting the performance of the drive.
Please check that your HBA is the correct type for the drive and that the cabling is good.
The SCSI configuration referenced is the one for which device analysis was run and/or the support ticket was pulled.
If this is not via your backup server then you may not have an issue.
Current SCSI speed limit: Ultra3 or faster.
Recommended: Ultra3 or faster.
Current SCSI transfer rate limited to: 160 MB/sec.
Recommended: 320 MB/sec. or better.
I'm a bit frustrated at the moment because I've spend several days with compiling new modules and adding different SCSI HBAs.
Any idea what to check next? Does anyone use LTO-3/4 drives correctly in U320 mode (with which controller)?
Ralf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 03:15 AM
тАО11-09-2007 03:15 AM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
There could be some hardware in the Neo that prevents running at U320 or Overland may have special firmware that limits the speed for some reason.
One issue I have seen quite a bit is that the bus must be absolutely clean and it is very difficult to get a bus that has two devices negotiate to U320 speeds. We typically see domain validation forcing the bus to U160 if there is more than one device connected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 10:49 PM
тАО11-09-2007 10:49 PM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
***** SPI HARDWARE VERSIONS AREA *****
Shuttle: 01 (LTO capable)
Passthru: 00
Vertical: 01 (Geared head)
Touch: 00
Drives 0-1: 07 (Fan stall capable, Ultra320 capable)
Drives 2-3: 07 (Fan stall capable, Ultra320 capable)
Only one of the two drives shares a controller with the Lib. The other drive is directly connected to the second controller. So everything seems to be ok and was installed as documented in the manual.
I'm not sure which version of HP's firmware is the equivalent to Overlands B12H firmware. But it's the most recent I could find.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2007 10:53 PM
тАО11-10-2007 10:53 PM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
http://support.overlandstorage.com/jive/entry!default.jspa?categoryID=3&externalID=4824&fromSearchPage=true
Problem: Slow throughput using LTO3 SCSI tape drives with a Ultra 320 SCSI card.
Solution: Disable Domain Validation.
Domain Validation uses a sequence of I/O commands to determine the optimum transfer rate between the SCSI card and the SCSI device on initial boot. In the same way that a modem will step down the transfer rate based on a telephone line quality to ensure data integrity, Domain Validation will limit the bandwidth to a device to guarantee reliable data transfers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2007 11:44 PM
тАО11-10-2007 11:44 PM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2007 02:15 AM
тАО11-14-2007 02:15 AM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
Right now LSI support tells me that the attached HP LTO-4 drives are not able to do U320.
#### quote lsi support ####
What I see happening the device was asked if it could negotiate at U320,
however it came back with U160. The reason you see the same results
with the adaptec driver is the same spi transport driver is shared
between both my driver, and there's.
Here is where U320 negotiation was sent:
> mptspi: ioc0: id=1 Requested = 0x207f08f3 ( Wide factor = 0x08 @ offset = 0x7f IU DT WRFLOW RDSTRM RTI PCOMP )
Then three inquiries sent
> st 5:0:1:0:
> command: Inquiry: 12 00 00 00 60 00
Then negotiation parameters read back. The device said it could do
U160:
> mptspi: ioc0: id=1 Read = 0x20400902 ( Wide factor = 0x09 @ offset = 0x40 DT )
#### quote end #####
On the other hand, overland is telling me that it's not a problem ot the lib. If there is a problem it must be with the LTO-4 drives. Their only "solution" right now is -> disable domain validation. But this is not possible with the lsi linux driver and not recommended at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2007 08:54 PM
тАО11-18-2007 08:54 PM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
It seems that Overland either has a problem with their Lib's firmware/SCSI backplane, or their OEM drive firmware is too old or buggy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2007 04:35 AM
тАО11-20-2007 04:35 AM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
where is your terminator located ?
The termination have to be on the Drive
Regards
Roland
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2007 08:50 AM
тАО11-20-2007 08:50 AM
Re: SCSI Domain Validation problems with LTO-4 drive and several SCSI HBAs
I've already backed up >10TB and have not seen any scsi errors. It's just the speed and the limit to U160 that is wrong. Maybe it's just an not-up2date firmware that overland uses as OEM firmware. The lib's fw is B12H, the fw of the U320 capable HP drive was B22D.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2007 02:56 AM
тАО11-21-2007 02:56 AM