- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Smart Array E200 interim recovery mode
Disk Enclosures
1753706
Members
4781
Online
108799
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
тАО10-11-2009 09:24 AM
тАО10-11-2009 09:24 AM
Smart Array E200 interim recovery mode
Dear all
We have a DL140 with E200 in interim recovery mode [1].
Working drive is: Port:box:bay=1I:1:1
Unfortunately we cannot rebuild the array because the controller is trying to use a drive in a bay that is not existing (2I:1:1) while it should use (1I:1:2).
Please see acucli output [2].
I tried to remove the wrong drive from the array and add the correct one (to be used for rebuilding) using the commands:
ctrl slot=4 array A remove drives=2I:1:1
ctrl slot=4 array A add drives=1I:1:2
But I get the error [3].
Can anyone help?
[1]
# arrayprobe
CRITICAL Arrayprobe Logical drive 0 on /dev/cciss/c0d0: Logical drive is using interim recovery mode
[2]
=> ctrl slot=4 pd all show detail
Smart Array E200 in Slot 4
array A (Failed)
physicaldrive 1I:1:1
Port: 1I
Box: 1
Bay: 1
Status: OK
Drive Type: Data Drive
Interface Type: SATA
Size: 250 GB
Firmware Revision: HPG6
Serial Number: 9SF10BW6
Model: ATA GB0250EAFJF
SATA NCQ Capable: False
PHY Count: 1
PHY Transfer Rate: 1.5GBPS
physicaldrive 2I:1:1
Port: 2I
Box: 1
Bay: 1
Status: Failed
Drive Type: Data Drive
Interface Type: SATA
Size: 0 MB
SATA NCQ Capable: False
unassigned
physicaldrive 1I:1:2
Port: 1I
Box: 1
Bay: 2
Status: OK
Drive Type: Unassigned Drive
Interface Type: SATA
Size: 250 GB
Firmware Revision: HPG6
Serial Number: 9SF10BVG
Model: ATA GB0250EAFJF
SATA NCQ Capable: False
PHY Count: 1
PHY Transfer Rate: 1.5GBPS
[3]
Error: This operation is not supported with the current configuration. Use the
"show" command on devices to show additional details about the
configuration.
We have a DL140 with E200 in interim recovery mode [1].
Working drive is: Port:box:bay=1I:1:1
Unfortunately we cannot rebuild the array because the controller is trying to use a drive in a bay that is not existing (2I:1:1) while it should use (1I:1:2).
Please see acucli output [2].
I tried to remove the wrong drive from the array and add the correct one (to be used for rebuilding) using the commands:
ctrl slot=4 array A remove drives=2I:1:1
ctrl slot=4 array A add drives=1I:1:2
But I get the error [3].
Can anyone help?
[1]
# arrayprobe
CRITICAL Arrayprobe Logical drive 0 on /dev/cciss/c0d0: Logical drive is using interim recovery mode
[2]
=> ctrl slot=4 pd all show detail
Smart Array E200 in Slot 4
array A (Failed)
physicaldrive 1I:1:1
Port: 1I
Box: 1
Bay: 1
Status: OK
Drive Type: Data Drive
Interface Type: SATA
Size: 250 GB
Firmware Revision: HPG6
Serial Number: 9SF10BW6
Model: ATA GB0250EAFJF
SATA NCQ Capable: False
PHY Count: 1
PHY Transfer Rate: 1.5GBPS
physicaldrive 2I:1:1
Port: 2I
Box: 1
Bay: 1
Status: Failed
Drive Type: Data Drive
Interface Type: SATA
Size: 0 MB
SATA NCQ Capable: False
unassigned
physicaldrive 1I:1:2
Port: 1I
Box: 1
Bay: 2
Status: OK
Drive Type: Unassigned Drive
Interface Type: SATA
Size: 250 GB
Firmware Revision: HPG6
Serial Number: 9SF10BVG
Model: ATA GB0250EAFJF
SATA NCQ Capable: False
PHY Count: 1
PHY Transfer Rate: 1.5GBPS
[3]
Error: This operation is not supported with the current configuration. Use the
"show" command on devices to show additional details about the
configuration.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2009 07:44 AM
тАО10-14-2009 07:44 AM
Re: Smart Array E200 interim recovery mode
Hi,
Just try Unplugging the Cable that connects the Array to the Controller and Plug it back in again.
Was there an MSA Down issue earlier?
Just try Unplugging the Cable that connects the Array to the Controller and Plug it back in again.
Was there an MSA Down issue earlier?
I am an HP employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2010 01:17 AM
тАО02-11-2010 01:17 AM
Re: Smart Array E200 interim recovery mode
Hi there,
we are suffering from the same problem, but we are not using hardware array facilities.
logs say it is critical, but we do not understand which is the problem.
OS is debian lenny with backports enabled.
Please CC to:
babel-adm@babel.ls.fi.upm.es
email error:
Subject: [Babel-adm] Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
Date: Thu, 11 Feb 2010 06:25:56 +0100
From: root@babel.ls.fi.upm.es (Cron Daemon)
To: root@babel.ls.fi.upm.es
/etc/cron.daily/arrayprobe:
CRITICAL Arrayprobe Logical drive 0 on /dev/cciss/c0d0: Logical drive is using interim recovery mode
run-parts: /etc/cron.daily/arrayprobe exited with return code 2
_______________________________________________
Babel-adm mailing list
we are suffering from the same problem, but we are not using hardware array facilities.
logs say it is critical, but we do not understand which is the problem.
OS is debian lenny with backports enabled.
Please CC to:
babel-adm@babel.ls.fi.upm.es
email error:
Subject: [Babel-adm] Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
Date: Thu, 11 Feb 2010 06:25:56 +0100
From: root@babel.ls.fi.upm.es (Cron Daemon)
To: root@babel.ls.fi.upm.es
/etc/cron.daily/arrayprobe:
CRITICAL Arrayprobe Logical drive 0 on /dev/cciss/c0d0: Logical drive is using interim recovery mode
run-parts: /etc/cron.daily/arrayprobe exited with return code 2
_______________________________________________
Babel-adm mailing list
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2010 01:21 AM
тАО02-11-2010 01:21 AM
Re: Smart Array E200 interim recovery mode
Ups, I forget to gice information ... sorry
We have an HP Proliant DL385 G2
* 2 x Opteron 2200
* 8 Gb de RAM
* 145Gb x 5 discos SAS 2.5
Thanks,
Victor.
We have an HP Proliant DL385 G2
* 2 x Opteron 2200
* 8 Gb de RAM
* 145Gb x 5 discos SAS 2.5
Thanks,
Victor.
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