- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Resetting SCSI syslog messages-what is this?
Operating System - HP-UX
1752252
Members
5222
Online
108785
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
Go to solution
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
тАО06-29-2007 04:18 AM
тАО06-29-2007 04:18 AM
Can someone tell me what's going on here? We had a va7100 controller failure on our RP5450 running UP-UX 11.11, controller replaced, then tape drive problems. But this is now ongoing, messages from /var/adm/syslog/syslog.log:
Jun 29 11:14:38 icgstx1 vmunix: SCSI: Resetting SCSI -- lbolt: 437922830, bus: 0
Jun 29 11:14:38 icgstx1 vmunix: SCSI: Reset detected -- lbolt: 437922830, bus: 0
Jun 29 11:14:43 icgstx1 vmunix: SCSI: Unhandled interrupt -- lbolt: 437923331, dev: cb001002
Jun 29 11:14:43 icgstx1 vmunix: lbp->state: 6060
Jun 29 11:14:43 icgstx1 vmunix: lbp->offset: ffffffff
Jun 29 11:14:43 icgstx1 vmunix: lbp->uPhysScript: f87be000
Jun 29 11:14:43 icgstx1 vmunix: From most recent interrupt:
Jun 29 11:14:43 icgstx1 vmunix: ISTAT: 0a, SIST0: c1, SIST1: 00, DSTAT: 80, DSPS: 00928800
Jun 29 11:14:43 icgstx1 vmunix: lsp: 0000000068712500
Jun 29 11:14:43 icgstx1 vmunix: bp->b_dev: cb001002
Jun 29 11:14:43 icgstx1 vmunix: scb->io_id: 1e5762
Jun 29 11:14:43 icgstx1 vmunix: scb->cdb: 12 00 00 00 80 00
Jun 29 11:14:43 icgstx1 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Jun 29 11:14:43 icgstx1 vmunix: lsp->state: 5
Jun 29 11:14:43 icgstx1 vmunix: lbp->owner: 0000000000000000
Jun 29 11:14:44 icgstx1 vmunix: scratch_lsp: 0000000068712500
Jun 29 11:14:44 icgstx1 vmunix: Script dump [000000005f659000]:
Jun 29 11:14:44 icgstx1 vmunix: 09000080 00928800 e25c0004 f87be7f8
Jun 29 11:14:44 icgstx1 vmunix: 80080000 f87be090 80080000 f87be090
Hundreds of the above messages. Thank you.
Jun 29 11:14:38 icgstx1 vmunix: SCSI: Resetting SCSI -- lbolt: 437922830, bus: 0
Jun 29 11:14:38 icgstx1 vmunix: SCSI: Reset detected -- lbolt: 437922830, bus: 0
Jun 29 11:14:43 icgstx1 vmunix: SCSI: Unhandled interrupt -- lbolt: 437923331, dev: cb001002
Jun 29 11:14:43 icgstx1 vmunix: lbp->state: 6060
Jun 29 11:14:43 icgstx1 vmunix: lbp->offset: ffffffff
Jun 29 11:14:43 icgstx1 vmunix: lbp->uPhysScript: f87be000
Jun 29 11:14:43 icgstx1 vmunix: From most recent interrupt:
Jun 29 11:14:43 icgstx1 vmunix: ISTAT: 0a, SIST0: c1, SIST1: 00, DSTAT: 80, DSPS: 00928800
Jun 29 11:14:43 icgstx1 vmunix: lsp: 0000000068712500
Jun 29 11:14:43 icgstx1 vmunix: bp->b_dev: cb001002
Jun 29 11:14:43 icgstx1 vmunix: scb->io_id: 1e5762
Jun 29 11:14:43 icgstx1 vmunix: scb->cdb: 12 00 00 00 80 00
Jun 29 11:14:43 icgstx1 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Jun 29 11:14:43 icgstx1 vmunix: lsp->state: 5
Jun 29 11:14:43 icgstx1 vmunix: lbp->owner: 0000000000000000
Jun 29 11:14:44 icgstx1 vmunix: scratch_lsp: 0000000068712500
Jun 29 11:14:44 icgstx1 vmunix: Script dump [000000005f659000]:
Jun 29 11:14:44 icgstx1 vmunix: 09000080 00928800 e25c0004 f87be7f8
Jun 29 11:14:44 icgstx1 vmunix: 80080000 f87be090 80080000 f87be090
Hundreds of the above messages. Thank you.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2007 04:39 AM
тАО06-29-2007 04:39 AM
Re: Resetting SCSI syslog messages-what is this?
The major/minor number of the device cb001002 points to the SCSI controller attached to /dev/dsk/c0t1d0s2. The device name is odd for a PA-RISC system since only IPF devices follow that nomenclature. Would help if you could post the output of:
# lssf /dev/dsk/c0t1d0s2
# ioscan -f /dev/dsk/c0t1d0s2
# lssf /dev/dsk/c0t1d0s2
# ioscan -f /dev/dsk/c0t1d0s2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2007 04:49 AM
тАО06-29-2007 04:49 AM
Re: Resetting SCSI syslog messages-what is this?
# lssf /dev/dsk/c0t1d0s2
lssf: /dev/dsk/c0t1d0s2: No such file or directory
# ioscan -f /dev/dsk/c0t1d0s2
ioscan: Can't open /dev/dsk/c0t1d0s2: No such file or directory
### there is not even a /dev/dsk/c0t1d0
lssf: /dev/dsk/c0t1d0s2: No such file or directory
# ioscan -f /dev/dsk/c0t1d0s2
ioscan: Can't open /dev/dsk/c0t1d0s2: No such file or directory
### there is not even a /dev/dsk/c0t1d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2007 05:03 AM
тАО06-29-2007 05:03 AM
Solution
This isn't a disk device.
cb001002
CB identifies the major device number.
00 -- controller instance
1 -- SCSI ID (target)
0 -- LUN
02 -- device dependent
do an lsdev CB hex = 203 decimal and 203 probably is sctl (scsi pass-thru).
Do a man scsi_ctl to further explain the bits in the minor number.
Now to find the actual device (which may well be some tape library robotics) do this:
find /dev -type c -exec ls -l {} \+ | awk '{if ($5 == "203") {print $0}}'
and look for anything listed that has a minor device number equal to 0x001002
You could add that condition to the above awk matching $6.
cb001002
CB identifies the major device number.
00 -- controller instance
1 -- SCSI ID (target)
0 -- LUN
02 -- device dependent
do an lsdev CB hex = 203 decimal and 203 probably is sctl (scsi pass-thru).
Do a man scsi_ctl to further explain the bits in the minor number.
Now to find the actual device (which may well be some tape library robotics) do this:
find /dev -type c -exec ls -l {} \+ | awk '{if ($5 == "203") {print $0}}'
and look for anything listed that has a minor device number equal to 0x001002
You could add that condition to the above awk matching $6.
If it ain't broke, I can fix that.
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