- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Decoding SCSI lbolts from AutoRAID 12H
Disk Enclosures
1752339
Members
5665
Online
108787
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО08-18-2005 01:57 AM
тАО08-18-2005 01:57 AM
Decoding SCSI lbolts from AutoRAID 12H
I am getting SCSI lbolts in syslog reported thus:
vmunix: SCSI: First party detected bus hang -- lbolt: 6745401, bus: 0
vmunix: lbp->state: 3060
vmunix: lbp->offset: 40
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 29, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 0000000a
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6745301, lbolt_at_start: 6744801
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 980dff00 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005
vmunix: SCSI: Resetting SCSI -- lbolt: 6745501, bus: 0
vmunix: SCSI: Reset detected -- lbolt: 6745501, bus: 0
vmunix: SCSI: First party detected bus hang -- lbolt: 6746601, bus: 0
vmunix: lbp->state: 1060
vmunix: lbp->offset: f8
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 00000000
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6746501, lbolt_at_start: 6746001
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 78342000 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005
Plus other very similar messages.
How do I work out which disk is at fault?
Thanks in advance,
Mark
vmunix: SCSI: First party detected bus hang -- lbolt: 6745401, bus: 0
vmunix: lbp->state: 3060
vmunix: lbp->offset: 40
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 29, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 0000000a
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6745301, lbolt_at_start: 6744801
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 980dff00 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005
vmunix: SCSI: Resetting SCSI -- lbolt: 6745501, bus: 0
vmunix: SCSI: Reset detected -- lbolt: 6745501, bus: 0
vmunix: SCSI: First party detected bus hang -- lbolt: 6746601, bus: 0
vmunix: lbp->state: 1060
vmunix: lbp->offset: f8
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 00000000
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6746501, lbolt_at_start: 6746001
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 78342000 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005
Plus other very similar messages.
How do I work out which disk is at fault?
Thanks in advance,
Mark
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 02:04 AM
тАО08-18-2005 02:04 AM
Re: Decoding SCSI lbolts from AutoRAID 12H
More information:
Now I've thought about this a bit more, I'm not even sure it's the 12H at fault.
I suppose the same question still applies though, I would expect the lbolt error to tell me some device information, and I can't spot it (I could be going blind of course!)
Thanks again
Mark
Now I've thought about this a bit more, I'm not even sure it's the 12H at fault.
I suppose the same question still applies though, I would expect the lbolt error to tell me some device information, and I can't spot it (I could be going blind of course!)
Thanks again
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2005 04:21 AM
тАО08-18-2005 04:21 AM
Re: Decoding SCSI lbolts from AutoRAID 12H
Hi Mark,
vmunix: bp->b_dev: cb001002
is the device having the problem. This is c0t1d0 device.
cb ---> is the hex value of the device major number. 203 is the major number of the device giving this error.
001002 ---> c0t1d0 is the device file for that major number.
to confirm which device major classification 203 belongs to,
# lsdev | grep 203
With regards,
Mohan.
vmunix: bp->b_dev: cb001002
is the device having the problem. This is c0t1d0 device.
cb ---> is the hex value of the device major number. 203 is the major number of the device giving this error.
001002 ---> c0t1d0 is the device file for that major number.
to confirm which device major classification 203 belongs to,
# lsdev | grep 203
With regards,
Mohan.
Attitude, Not aptitude, determines your altitude
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP