- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- need help to identify device causing lbolt errors
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
тАО07-13-2009 07:39 AM
тАО07-13-2009 07:39 AM
need help to identify device causing lbolt errors
Jul 13 08:56:23 mars vmunix: SCSI: Resetting SCSI -- lbolt: 25628054, bus: 0 Jul 13 08:56:23 mars vmunix: SCSI: Reset detected -- lbolt: 25628054, bus: 0 Jul 13 08:56:34 mars vmunix: SCSI: First party detected bus hang -- lbolt: 25629154, bus: 0
Jul 13 08:56:34 mars vmunix: lbp->state: 5060
Jul 13 08:56:34 mars vmunix: lbp->offset: f8
Jul 13 08:56:34 mars vmunix: lbp->uPhysScript: 81fbc000
Jul 13 08:56:34 mars vmunix: From most recent interrupt:
Jul 13 08:56:34 mars vmunix: ISTAT: 02, SIST0: 02, SIST1: 10, DSTAT: 80, DSPS: 00000000
Jul 13 08:56:34 mars vmunix: lsp: 0000000000000000
Jul 13 08:56:34 mars vmunix: lbp->owner: 000000004f3cdd00
Jul 13 08:56:34 mars vmunix: bp->b_dev: cb001002
Jul 13 08:56:34 mars vmunix: scb->io_id: 65
Jul 13 08:56:34 mars vmunix: scb->cdb: 12 00 00 00 80 00
Jul 13 08:56:34 mars vmunix: lbolt_at_timeout: 25629054, lbolt_at_start: 25628554
Jul 13 08:56:34 mars vmunix: lsp->state: 5
Jul 13 08:56:34 mars vmunix: scratch_lsp: 000000004f3cdd00
Jul 13 08:56:34 mars vmunix: Pre-DSP script dump [ffffffff81fbc020]:
Jul 13 08:56:34 mars vmunix: 00000000 00000000 41010000 81fbc290
Jul 13 08:56:34 mars vmunix: 78342000 0000000a 78351000 00000000
Jul 13 08:56:34 mars vmunix: Script dump [ffffffff81fbc040]:
Jul 13 08:56:34 mars vmunix: 0e000005 81fbc540 e0100004 81fbc7f8
Jul 13 08:56:34 mars vmunix: 870b0000 81fbc2d8 98080000 00000005
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 07:47 AM
тАО07-13-2009 07:47 AM
Re: need help to identify device causing lbolt errors
Please have a look on c98t8d0
Regards
Sanjeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 07:57 AM
тАО07-13-2009 07:57 AM
Re: need help to identify device causing lbolt errors
That is highly doubtful!!!
The device is:
Jul 13 08:56:34 mars vmunix: bp->b_dev: cb001002
0xcb = 203 --> ctl [from 'lsdev']
0x00 = 0 --> bus number
0x1 = 1 --> target
0x0 = 0 --> lun
0x02 --> flags
So this is: c0t1d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 08:00 AM
тАО07-13-2009 08:00 AM
Re: need help to identify device causing lbolt errors
Yes, you are 100% correct, sorry for understanding it wrong :-)
Regards
Sanjeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 08:01 AM
тАО07-13-2009 08:01 AM
Re: need help to identify device causing lbolt errors
It looks scsi reset initiated by the controller itself. You could also check the device c0t1d0.
Normally you should find the device file like this..
b_dev: cb001002 --> middle 3 digits represents the device file. In this case 010 which is c0t1d0
Involve HP to analyse and replace the part.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 08:10 AM
тАО07-13-2009 08:10 AM
Re: need help to identify device causing lbolt errors
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 07:11 PM
тАО07-13-2009 07:11 PM
Re: need help to identify device causing lbolt errors
Try running the disk information tool from cstm on the disks.
cstm/mstm/xstm.
or try diskinfo
Thanks
Shiv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 10:39 PM
тАО07-13-2009 10:39 PM
Re: need help to identify device causing lbolt errors
So, far it tape library related issue. If your tape drive attached with SCSI cable, then reseating SCSI cable & terminator and check that issue.
Rgds//
Taifur