- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI: write error - explained
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
тАО10-02-2005 03:54 PM
тАО10-02-2005 03:54 PM
Do you get these errors ? And how to correct ?
details and concerns
----------------------------------------------
what does Error message tell me ?
errno: 126 ?
resid: 4096 ?
grep SCSI: /var/adm/syslog/syslog.log:
Sep 22 09:39:51 MYSERVERNAME vmunix: SCSI: Async write error -- dev: b 31 0x043300, errno: 126, resid: 4096,
kernel's fprintf() format might be this:
# pwd
/stand
# grep SCSI: vmunix | grep -i 'write'
SCSI: Async write error -- dev: %s %d 0x%06x, errno: %d, resid: %d,
I can find the 'dev:' from ls -l /dev/dsk.. and match to the actual special disk device.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 04:02 PM
тАО10-02-2005 04:02 PM
Solutionb 31 - it is disk device. You may have disk problem.
ll /dev/dsk/* | grep 0x043300
This shold be disk c4t3d3
Check that disk - pvdisplay, diskinfo and dd test
dd if=/dev/rdsk/c4t3d3 of=/dev/null bs=1k
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 04:06 PM
тАО10-02-2005 04:06 PM
Re: SCSI: write error - explained
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 04:09 PM
тАО10-02-2005 04:09 PM
Re: SCSI: write error - explained
The device that have a problem is c4t3d3, check with 'ioscan -nfC disk' whether the status become NO_HW or missing or else.
Run the disk exercise with dd command :
# dd if=dev/rdsk/c4t3d3 of=/dev/null bs=1024
Check also with :
# pvdisplay -v /dev/dsk/c4t3d3
# diskinfo -v /dev/rdsk/c4t3d3
Hope this information can help you.
Cheers,
AW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 04:12 PM
тАО10-02-2005 04:12 PM
Re: SCSI: write error - explained
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=849572
You might have a corrupted disk, try RAC's method # dd if=/dev/rdsk/c4t3d3 of=/dev/null bs=1k
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2005 09:41 PM
тАО10-02-2005 09:41 PM
Re: SCSI: write error - explained
For example if the I/O routines were trying to write, say, 8k of data to the disk and only half was transferred then the resid would be 8192 (i.e. 8k) - 4096 (number of bytes actually transferred) = 4096.
Or, say the I/O routines were trying to transfer 4k to the disk, and none of it was successfully transferred then the resid would be 4096 (attempted) - 0 (successfully transferred) = 4096 (resid).
You would normally expect the resid to be zero. The errno is an indication of why the data transfer could not be completed. It would be 7E in hex and is a vendor specific SCSI error indicator.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2005 08:07 AM
тАО10-03-2005 08:07 AM
Re: SCSI: write error - explained
Mugilvannan, can you send that link again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2005 01:48 PM
тАО10-03-2005 01:48 PM
Re: SCSI: write error - explained
errno = 126 (EPOWERF) means the SCSI driver could not complete the read/write requests within specified timeouts.
The errors listed above are occurring in the syslog indicating timeouts have occurred but there are no vg[#]: pvnum=# (dev_t=##) is powerfailed as normally seen.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2005 07:35 PM
тАО10-03-2005 07:35 PM
Re: SCSI: write error - explained
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2005 02:13 PM
тАО10-07-2005 02:13 PM
Re: SCSI: write error - explained
http://www.santools.com/smart/SMARTMONUX-Manual.pdf
1.19 Storage Area Network (SAN) Device Ping
This function can be equated with a standard TCP/IP ping. It is used to both determine connectivity to a device, and
to report the amount of milliseconds it takes for a packet of data to get to the device and be acknowledged by it.
Syntax
smartmon-ux -fcping PortWWN LUN_Number [Attempts]
The LUN_Number would typically be zero for standard disks and tapes. It is quite common to be non-zero for logical
disks created by external RAID subsystems.
The PortWWN corresponds to the fibre channel port WWN for the selected device. This information can be obtained
by a variety of methods, including:
├В┬╖ Running smartmon-ux -fc which will dump all port and WWN info for the devices it can see
├В┬╖ Your HBA management software
├В┬╖ Your operating system's registry or boot logs (i.e, /vary/log/messages or dmesg)
The optional attempts field is used to tell the program how many attempts it should make. If you enter zero, then it
will send data indefinitely, or until you abort or kill the program.
Example
D:\TEST>smartmon-ux -fcping 22:00:00:20:37:E6:0A:38 0
SMARTMon-ux [Release 1.23, Build 07-DEC-2003] - Copyright 2003 SANtools, Inc.
http://www.SANtools.com
Port 22:00:00:20:37:E6:0A:38 replies in 0.010s as SEAGATE ST336605FC
Port 22:00:00:20:37:E6:0A:38 replies in 0.000s as SEAGATE ST336605FC
Port 22:00:00:20:37:E6:0A:38 replies in 0.000s as SEAGATE ST336605FC
59