- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- SCSI Data Overrun on Storagetek L700 Library Contr...
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
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
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
тАО05-16-2005 10:59 PM
тАО05-16-2005 10:59 PM
SCSI Data Overrun on Storagetek L700 Library Controller
It allways happens after a Data Overrun on the Contrller:
May 13 08:39:43 uxbupn05 vmunix: SCSI: Data Overrun -- lbolt: 5784081, dev: cb065000
Does anyone know how I can trace back the Dataoverrun or have a Clue what could produce this Error ?
regards
oliver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 12:04 AM
тАО05-17-2005 12:04 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
There could be SCSI cable/terminator problem, even a poor grounding can cause lbolt errors. I am not very sure about "data overrun", may be some thing to do with buffer or SCSI cumulative patch!!
Analyse the lbolt errors as below.
=================================
Lbolt error itself a time stamp.
For example if you receive vmunix: SCSI: Request Timeout; Abort -- lbolt: 120842710, dev: cd061000, io_id: 6684ee3
The SCSI error occurred after 120842710 milliseconds of system reboot. You can find out system uptime
By #uptime and calculate when the SCSI lbolt occurred.
The second useful field is ├в dev├в . From example dev:cd061000, the ├в cd├в stand for major number of the device in hex.
The decimal value for ├в cd├в is 205.
#ll /dev/(r)dsk/*
or
#ll /dev/rmt/*
Check for major number 205.
06 is bus number. Using ioscan we can findout Bus number.
#ioscan ├в kfnC ext_bus
check for bus number 6.
10 is SCSI id 1 and lun 0.
Once the you identify the bus/device, make sure all the cables are secured properly.
Replace the cables/terminators if suspected.
Make sure latest SCSI/IO Cumulative patches are installed.
If it is disk device change timeout value with pvchange ├в t option.
Also see the driver associated with the device may need t
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 12:31 AM
тАО05-17-2005 12:31 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
dev: cb065000 is the Library Controller(/dev/rac/pickers and /dev/rac/c6t5d0).
The Terminator as well as the Cable have allready been replaced and we also tried a different Driver. Changing the Driver only made Things worse cause since then we also encounter hangs on the SCSI-BUS which forces us to reboot the Library to get it back to working normal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 12:45 AM
тАО05-17-2005 12:45 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
1. How long has this environment been up and running?
2. Is this a new configuration/setup?
3. How many drives from the L700 do you have
4. What kind of SCSI (Differential) cards do you use and how many?
I suspect you've daisy chained the robot along with one or 2 drives. I always hook up a Tape library's robotics to its own SCSI port if it is directly attached to a server.
You may also look at updating your SCSI patches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 01:02 AM
тАО05-17-2005 01:02 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
Along with robotics is there many devices in the same SCSI bus? Are you up to date with HWE and QPK patches? (consider minimum SCSI patches).
How often this error comes? During that time was this SCSI busy with some other device?
See also
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=721761
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2005 01:36 AM
тАО05-17-2005 01:36 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
The Error occurs on an unregular basis. 1 week nothing then twice in 4 days. The Controller was Daisy-chained with a Drive but we changed that about 2 Weeks, with no Improvement.
There's a total of 16 Drives, 6 through SAN on NT-Hosts, 1 on an NS700(NDMP) and 9 are connected to the UNIX-Host(direct through SCSI).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2005 07:48 AM
тАО05-18-2005 07:48 AM
Re: SCSI Data Overrun on Storagetek L700 Library Controller
Since you have already replaced the cables and terminator that leaves the Library and the HP SCSI controller. I'd suggest replacing the HP SCSI controller. If that doesn't fix the problem, then replace the L700 controller.
Regards,
Michael Lampi