- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: rp3440 , ID the source of scsi 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
тАО09-09-2013 06:52 AM - last edited on тАО09-09-2013 07:33 PM by Liuqing
тАО09-09-2013 06:52 AM - last edited on тАО09-09-2013 07:33 PM by Liuqing
I have an RP3440 with scsi errors showing in dmesg. All disks show CLAIMED in ioscan -fnkC disk, all disks return data from diskinfo -V. An excerpt from dmesg:
blkno: 14390055, sectno: 28780110, offset: 1850514432, bcount: 2048.
SCSI: Async write error -- dev: b 31 0x032000, errno: 126, resid: 4096,
blkno: 14123968, sectno: 28247936, offset: 1578041344, bcount: 4096.
is there a way to identify the disk generating errors with the data from dmesg?
On sun, we could use iostat -e to display errors for specific disks. Is there a
similar command on HP?
P.S. This thread has been moved fromServers > HP 9000 to HP-UX > sysadmin.
-HP Forum Moderator
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2013 07:22 AM
тАО09-09-2013 07:22 AM
Re: rp3440 , ID the source of scsi errors
Hi,
the following part of the message is pointing to the device "dev: b 31 0x032000", and it decodes to "c3t2d0".
So please check your ioscan -fn output for this device file.
You may check the device with diskinfo command and Online Diagnostics (Support Tools Manager).
# diskinfo -v /dev/rdsk/c3t2d0
# mstm (menu driven version of Support Tools Manager)
Kind Regards
Holger
Was this post useful? - You may click the KUDOS! Star.
- Tags:
- diskinfo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2013 07:24 AM
тАО09-09-2013 07:24 AM
SolutionIn the dmesg error message, the string after "dev:" is the key.
b 31 0x032000
- "b" means it is a block device.
- 31 is the major device number. Looking at the "Block" column of the "lsdev" output, we'll find that the driver for that major number is "sdisk", so it is a SCSI disk device (= not a tape device or any other type of SCSI device)
- 0x032000 is the minor device number. As we already know this is a block device for a disk, we can just run "ll /dev/dsk | grep 0x032000" to find the device. Alternatively, we could split the hexadecimal number into components: 0x is just the indicator that the number is hexadecimal, 03 is the controller number, 2 is the SCSI target ID and the next number is the LUN number.
So the device that is producing the errors would seem to be /dev/dsk/c3t2d0. In a default installation with no external storage devices, that could be the top-most disk slot in the server's front panel (it's the only one with the target ID #2), but you should verify the hardware path of the disk with "ioscan -fnCdisk" to be sure.
In a rp3440, the hardware paths are:
- disk slot 0: 0/1/1/0.0.0 (= device c2t0d0 in a default installation)
- disk slot 1: 0/1/1/0.1.0 (= device c2t1d0 in a default installation)
- disk slot 2: 0/1/1/1.2.0 (= device c3t2d0 in a default installation)
- DVD drive: 0/0/2/0.0.0.0 (= device c0t0d0 in a default installation)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2013 09:17 AM
тАО09-09-2013 09:17 AM
Re: rp3440 , ID the source of scsi errors
TYVM. That's exactly the info I needed!