- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- I/O error
Disk Enclosures
1752860
Members
3779
Online
108790
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
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
тАО07-27-2001 02:11 AM
тАО07-27-2001 02:11 AM
I/O error
hi all..i have got a 12H disk array with two K-360 servers in a cluster.suddenly one volume showed I/O error when bdf is typed.then momentarily the node2 in the cluster gave the error"x controller failed" and it told couldnt access a disk at a specified address.here i have attached the dmesg output.this is an SOS.kindly suggest the possible problem.the dmesg output is of node 2.node1 dmesg output i didnt get.awaiting reply.
thanks in advance.
viks
thanks in advance.
viks
regard
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2001 03:50 AM
тАО07-27-2001 03:50 AM
Re: I/O error
Hi,
It looks as if one of the controllers of the autoraid failed. Because you have Alternate paths to your luns configured the kernel switches to that alternate patchs when the primary patch fails (that's why you see the switch messages). You can check the autoraid with the following commands:
/opt/hparray/bin/arraydsp -i
this will give the serial number which is needed with the next commands:
arraydsp -a [serialnr] # for all info
arraydsp -c [serialnr] # for controller info
Check the status of the controllers. Also, if possible, check the display on the 12H itself.
If there are problems contact HP ...
It looks as if one of the controllers of the autoraid failed. Because you have Alternate paths to your luns configured the kernel switches to that alternate patchs when the primary patch fails (that's why you see the switch messages). You can check the autoraid with the following commands:
/opt/hparray/bin/arraydsp -i
this will give the serial number which is needed with the next commands:
arraydsp -a [serialnr] # for all info
arraydsp -c [serialnr] # for controller info
Check the status of the controllers. Also, if possible, check the display on the 12H itself.
If there are problems contact HP ...
The surest sign that life exists elsewhere in the universe is that none of it has tried to contact us
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2001 04:22 AM
тАО07-27-2001 04:22 AM
Re: I/O error
Did you take a look at the front panel on HP AutoRAID ?
Did it show nothing ?
"Dmesg output" explained that there is a failure in the hardware path for /dev/dsk/c2t1d5 so the ownership of the LUN automatically switches to the alternate path for /dev/dsk/c3t0d5 because alternate links are configured.
For some reason, the problem has been disappeared naturally so the ownership of the LUN for /dev/dsk/c3t0d5 switches to the primary path again.
Dmesg shows this procedure over and over which means that there must be something wrong on AutoRAID.
Check out controller and host bus adaptor !
It's a good idea to issue ARM (Array Management) commands to get a clue as follows:
# arraydsp -i ( To get a serial number )
# arraydsp -a
# logprint -a
Hope this helps.
Did it show nothing ?
"Dmesg output" explained that there is a failure in the hardware path for /dev/dsk/c2t1d5 so the ownership of the LUN automatically switches to the alternate path for /dev/dsk/c3t0d5 because alternate links are configured.
For some reason, the problem has been disappeared naturally so the ownership of the LUN for /dev/dsk/c3t0d5 switches to the primary path again.
Dmesg shows this procedure over and over which means that there must be something wrong on AutoRAID.
Check out controller and host bus adaptor !
It's a good idea to issue ARM (Array Management) commands to get a clue as follows:
# arraydsp -i ( To get a serial number )
# arraydsp -a
# logprint -a
Hope this helps.
Never say "no" first.
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