HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI Errors
Operating System - HP-UX
1832619
Members
2798
Online
110043
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
Forums
Discussions
Discussions
Discussions
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
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
05-29-2002 02:26 PM
05-29-2002 02:26 PM
SCSI Errors
scb->cdb: 28 00 02 13 a8 00 00 00 80 00
scb->cdb: 2a 00 00 07 0d c0 00 00 04 00
SCSI: Resetting SCSI -- lbolt: 20766441, bus: 5
SCSI: Reset detected -- lbolt: 20766441, bus: 5
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors
What might this be? Please advise?
Vito
scb->cdb: 2a 00 00 07 0d c0 00 00 04 00
SCSI: Resetting SCSI -- lbolt: 20766441, bus: 5
SCSI: Reset detected -- lbolt: 20766441, bus: 5
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors
What might this be? Please advise?
Vito
Lifes too short to stress out, Enjoy every day you have on earth!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 02:57 PM
05-29-2002 02:57 PM
Re: SCSI Errors
Vito,
Do you happen to have more information in syslog? Something like:
scsi: abort tag--lbolt:, dev:1f079000, io_id:7c9db5e
What I would be interested in is the hex address after the 'dev:' listing. This would point to a specific device. This may just be an issue of increasing the timeout on the disk with pvchange -t.
Let us know of any other information that you have.
Regards,
Eric
Do you happen to have more information in syslog? Something like:
scsi: abort tag--lbolt:
What I would be interested in is the hex address after the 'dev:' listing. This would point to a specific device. This may just be an issue of increasing the timeout on the disk with pvchange -t.
Let us know of any other information that you have.
Regards,
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 06:46 PM
05-29-2002 06:46 PM
Re: SCSI Errors
It can only mean 3 things
1) Disk is failing
2) Low timeout value
3) SCSI termination and connection.
You just have to go through the process of elimination to determne your actual root cause. Check for IO error using STM..
# cstm
cstm>map
cstm>sel dev
cstm>info
cstm>infolog
If you don't see any error, double check connection, cable, termination,etc. If that is ok, then is it likely to be that the timeout value of the disk needs to be increased. For example ..
# pvchange -t 180 /dev/dsk/c0td0
increases it to 180 secs. Check man page of pvchange for details.
Of course you got to determine which device is giving the error message, typically what Eric had mentioned (eg: dev:1f079000 would be c7t9d0)
1) Disk is failing
2) Low timeout value
3) SCSI termination and connection.
You just have to go through the process of elimination to determne your actual root cause. Check for IO error using STM..
# cstm
cstm>map
cstm>sel dev
cstm>info
cstm>infolog
If you don't see any error, double check connection, cable, termination,etc. If that is ok, then is it likely to be that the timeout value of the disk needs to be increased. For example ..
# pvchange -t 180 /dev/dsk/c0td0
increases it to 180 secs. Check man page of pvchange for details.
Of course you got to determine which device is giving the error message, typically what Eric had mentioned (eg: dev:1f079000 would be c7t9d0)
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP