- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- read i/o error
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
Forums
Discussions
Discussions
Discussions
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
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
07-17-2003 05:00 AM
07-17-2003 05:00 AM
We have an import running, which was stuck(hung), in dmesg output read i/o error was reported due to POWERFAILURE on SCSI device.
I checked syslog, and same error message is continueing.
Error message :
Jul 17 06:36:48 eagle vmunix:SCSI: read error -- dev b: 31 0x042000, errno:126, resid:2048
blkno:8, sectno:16, offset:8192, bcount: 2048,
LVM:vg[2]:pvnum=0 (dev_t=0x1f042000) is POWERFAILED
LVM:Recovered Path (device 0x1f042000) to PV 0 in VG 2.
LVM:Restored PV 0 to VG 2.
I have still not checked device is plugged correctly or not but this is new refurbished N-CLASS HP server we've received and I have started configuring.
Could somebody shed some light of experience on this problem ?
Thanks in advance for your help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:06 AM
07-17-2003 05:06 AM
Re: read i/o error
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:08 AM
07-17-2003 05:08 AM
Solutionll /dev/dsk | grep 042000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:09 AM
07-17-2003 05:09 AM
Re: read i/o error
What happened here is that one of the disk in the Volume group 2 lost connectivity to the power supply and after sometime the connectivity was restored. It could be due to loose connection or bad disk. The disk is also giving you I/O errors and there may be bad blocks in the disk. If these errors are comming frequently then you need to change the disk.
HTH,
Piyush
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:14 AM
07-17-2003 05:14 AM
Re: read i/o error
If you have a service contract, call HP and have them replace the disk.
Regards,
Dario
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:18 AM
07-17-2003 05:18 AM
Re: read i/o error
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:20 AM
07-17-2003 05:20 AM
Re: read i/o error
vgdisplay -v vg02 ( to see if all disks are "available");
diskinfo /dev/rdsk/c4t2d0 - if it returns valid information;
If any of the above fails - replace the disk.
You should run some additional commands to replace LVM drive.
Elena.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:23 AM
07-17-2003 05:23 AM
Re: read i/o error
if you have an high disk activity should be that the disk in the question was in time-out.
You can try to change the IO_timeout parameter with the pvchange command.
See man pvchange option -t.
A good value is 120 sec.
I know the default is 60 sec.
Enrico.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:47 AM
07-17-2003 05:47 AM
Re: read i/o error
I just wanted to chim in & show you how you could come to the above conclusions yourself
Jul 17 06:36:48 eagle vmunix:SCSI: read error -- dev b: 31 0x042000
This means device with major number 31 & mimor number 0x042000. is failing (SCSI error).
You can track the major number to a device/driver by doing lsdev | egrep 31. I think this is a disk devcice, dsk or rdsk. so cd /dev/dsk (or maybe /dev/rdsk) & do ls -l, track down device with minor number 0x042000. This is the device that is failing.
Also the LVM:... messages are also a give away
Regards
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:53 AM
07-17-2003 05:53 AM
Re: read i/o error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 05:54 AM
07-17-2003 05:54 AM
Re: read i/o error
I think it's not internal drive (as soon as bus is 4 and VG is 2).
Please check if there're more disks/devices on this SCSI bus (beginning with c4tXdY). Check if everything is connected securely. Check if there're such events for other connected disks. Check disk's readability with dd:
dd if=/dev/rdsk/c4t2d0 of=/dev/null bs=1024k
if finally it will return 'I/O error' then disk could be defective
Eugeny