GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Interim Recovery Mode and bad disk
ProLiant Servers (ML,DL,SL)
1847254
Members
4578
Online
110263
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
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
09-07-2010 02:06 AM
09-07-2010 02:06 AM
Interim Recovery Mode and bad disk
hello,
DL380-G5, fw from 2009, redHat 5.4.
I have setup an 0+1 array of 6 disks a while ago.
One of these disk failed (between sunday and monday), an it seems that disk report an error, turning filesystems readonly. (And of course we need to reboot host).
Shouldn't array stuff prevent us from seeing the error ?
Jean-Yves Picard
cma's report:
Sep 6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status OK to Physical Drive Not Properly Connected
Sep 6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Physical Drive Not Properly Connected to Interim Recovery
Sep 6 16:14:28 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Interim Recovery.
Sep 6 16:14:28 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now Failed.
Sep 7 11:18:55 redhat54 cmaeventd[7661]: Hot-plug drive inserted: Port 2I Box 1 Bay 2 of Array Controller in slot 1.
Sep 7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Interim Recovery to Ready For Rebuild
Sep 7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Ready For Rebuild to Rebuilding
Sep 7 11:19:05 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Rebuilding.
Sep 7 11:19:05 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now OK.
Sep 7 11:54:00 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Rebuilding to OK
Sep 7 11:54:07 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now OK.
DL380-G5, fw from 2009, redHat 5.4.
I have setup an 0+1 array of 6 disks a while ago.
One of these disk failed (between sunday and monday), an it seems that disk report an error, turning filesystems readonly. (And of course we need to reboot host).
Shouldn't array stuff prevent us from seeing the error ?
Jean-Yves Picard
cma's report:
Sep 6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status OK to Physical Drive Not Properly Connected
Sep 6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Physical Drive Not Properly Connected to Interim Recovery
Sep 6 16:14:28 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Interim Recovery.
Sep 6 16:14:28 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now Failed.
Sep 7 11:18:55 redhat54 cmaeventd[7661]: Hot-plug drive inserted: Port 2I Box 1 Bay 2 of Array Controller in slot 1.
Sep 7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Interim Recovery to Ready For Rebuild
Sep 7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Ready For Rebuild to Rebuilding
Sep 7 11:19:05 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Rebuilding.
Sep 7 11:19:05 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now OK.
Sep 7 11:54:00 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Rebuilding to OK
Sep 7 11:54:07 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now OK.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2010 02:15 AM
09-07-2010 02:15 AM
Re: Interim Recovery Mode and bad disk
You are right; normally this is transparent to the OS. The log you sent looks normal. There must be a problem anywhere else (maybe controller firmware, cabling, another bad disk, etc ...)
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2010 02:26 AM
09-07-2010 02:26 AM
Re: Interim Recovery Mode and bad disk
Seem perfectly well to me :)
I know absolutely nothing aboute Linux.
You would see the same events in Windows, when you have the insight agents running.
My gues is that you got the insight agents installed.
You should see these as a service messages to the system administrator.
It tell you, a disk has faile.
Wich physical and logical disk.
It report, that it has discovered a disk change.
And that rebuild has startet.
And best of all, that it has finished.
You should be Happy :)
BR
/jag
I know absolutely nothing aboute Linux.
You would see the same events in Windows, when you have the insight agents running.
My gues is that you got the insight agents installed.
You should see these as a service messages to the system administrator.
It tell you, a disk has faile.
Wich physical and logical disk.
It report, that it has discovered a disk change.
And that rebuild has startet.
And best of all, that it has finished.
You should be Happy :)
BR
/jag

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 2026 Hewlett Packard Enterprise Development LP