- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: help fixing botched drive replacement
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
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
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
01-02-2018 11:05 AM
01-02-2018 11:05 AM
help fixing botched drive replacement
We have a couple drives that were attempted to be replaced, incorrectly, a while back. I am attempting to bring the new drives online but have been unsuccessful. I am assuming I need to move chunklets and other commands but am not clear what steps to take, since proper procedure was not followed to start with.
Assuming an expert can determine what I need to do with the following info:
3par.lctn.org cli% servicemag status -d
Cage 0, magazine 0:
A servicemag resume command failed on this magazine.
The command completed at Tue Jan 2 11:56:32 2018.
The output of the servicemag resume was:
servicemag resume 0 0
... mag 0 0 already onlooped
... firmware is current on pd WWN [2000B45253744ED3] Id [ 0]
... firmware is current on pd WWN [2000B45253744FCB] Id [ 6]
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 0
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 0
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 0
... checking for valid disks...
Failed --
disk WWN [2000B45253744FCB] Id [ 6] is not normal. Please use showpd -s to see details of disk state
servicemag resume 0 0 -- Failed
Cage 0, magazine 6:
A servicemag resume command failed on this magazine.
The command completed at Wed Dec 20 08:14:51 2017.
The output of the servicemag resume was:
servicemag resume 0 6
... onlooping mag 0 6
Failed --
Unable to access drive magazine via one or more loops in cage cage0. No drive magazine is present or detected in that position.
Failed --
Unable to access drive magazine via one or more loops in cage cage0. No drive magazine is present or detected in that position.
servicemag resume 0 6 -- Failed
Cage 0, magazine 12:
A servicemag resume command failed on this magazine.
The command completed at Tue Jan 2 12:40:44 2018.
The output of the servicemag resume was:
servicemag resume 0 12
... mag 0 12 already onlooped
... firmware is current on pd WWN [2000B45253744ED3] Id [ 0]
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 12
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 12
... checking for valid disks...
... checking for valid disks...
... disks not normal yet..trying admit/onloop again
... onlooping mag 0 12
... checking for valid disks...
Failed --
disk WWN [2000B45253744ED3] Id [ 0] is not normal. Please use showpd -s to see details of disk state
servicemag resume 0 12 -- Failed
3par.lctn.org cli% showpd -s
Id CagePos Type -State- -------------------------------Detailed_State-------------------------------
0 0:12:0 FC failed vacated,notready,not_available_for_allocations,invalid_media,failed_hardware
1 0:3:0 NL normal normal
2 0:4:0 FC normal normal
3 0:7:0 NL normal normal
4 0:8:0 FC normal normal
5 0:11:0 NL normal normal
6 0:0:0 FC failed vacated,notready,invalid_media,servicing
7 0:15:0 NL normal normal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 02:45 AM
01-03-2018 02:45 AM
Re: help fixing botched drive replacement
Something went wrong. What means "incorrectly" - what exactly was done?
What 3PAR model is it?
0:0:0 and 0:12:0 are obviously failed and should be replaced.
There is probably no disk in 0:6:0
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
01-03-2018 05:48 AM
01-03-2018 05:48 AM
Re: help fixing botched drive replacement
Drives were replaced with new without going through proper steps.
Model F200
I believe the replacement drives are good. At least they show drive size, etc... and there are not any amber lights. I can run recommended commands to confirm.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 05:51 AM
01-03-2018 05:51 AM
Re: help fixing botched drive replacement
>> without going through proper steps.
What has been done?
Pulling the drives without running servicemag?
Please show
CLI% showpd -failed -degraded
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
01-03-2018 06:05 AM
01-03-2018 06:05 AM
Re: help fixing botched drive replacement
Correct. Servicmag was not run and old drives are no longer available.
showpd -failed -degraded
-Size(MB)-- ----Ports----
Id CagePos Type RPM State Total Free A B Capacity(GB)
0 0:12:0 FC 15 failed 285440 0 0:0:1* 1:0:1 300
6 0:0:0 FC 15 failed 285440 0 0:0:1 1:0:1* 300
I will need to order new drives if these are indeed bad.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 06:37 AM
01-03-2018 06:37 AM
Re: help fixing botched drive replacement
Please confirm - the original bad disks are pulled and the new disks inserted without running any command?
Please post the output of
cli% showcage -d cage0
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
01-03-2018 06:51 AM
01-03-2018 06:51 AM
Re: help fixing botched drive replacement
No commands were run.
showcage -d cage0
Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side
0 cage0 0:0:1 0 1:0:1 0 8 33-34 08 08 DC3 n/a
-----------Cage detail info for cage0 ---------
Position: bay9 D2
-----------Midplane Info------------
VendorId,ProductId 3PARdata,DC3
Assembly Serial_Num OPS69907C01C3C6
Node_WWN 20000050CC01C3C6
TempSensor_State OK
TempSensor_Value 35
OpsPanel_State OK
Audible_Alarm_State Muted
ID_Switch 1
Cage_State OK
Interface Board Info LoopA LoopB
Firmware_status Current Current
Product_Rev 08 08
IFC_State OK OK
ESH_State OK OK
Master_CPU Yes No
Loop_Map valid valid
Link_Speed 4Gbps 4Gbps
Port0_State OK OK
Port1_State No_SFP No_SFP
Port2_State No_SFP No_SFP
Port3_State No_SFP No_SFP
Power Supply Info State Fan State AC Assy_Part
ps0 OK MedSpeed OK --
ps1 OK MedSpeed OK --
--------------Drive Info--------------- ----LoopA----- ----LoopB-----
Drive NodeWWN State Temp(C) ALPA LoopState ALPA LoopState
0:0 2000b45253744fcb Degraded N/A 0xe1 OK 0xe1 OK
3:0 2210000a33015be8 Normal 33 0xda OK 0xda OK
4:0 2000b452537450d9 Normal 34 0xd9 OK 0xd9 OK
7:0 2210000a33015b5d Normal 34 0xd4 OK 0xd4 OK
8:0 2000b452537438ab Normal 34 0xd3 OK 0xd3 OK
11:0 2210000a33015b42 Normal 34 0xce OK 0xce OK
12:0 2000b45253744ed3 Degraded N/A 0xcd OK 0xcd OK
15:0 2210000a33015b1b Normal 34 0xca OK 0xca OK
3par.lctn.org cli%
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2018 06:58 AM
01-03-2018 06:58 AM
Re: help fixing botched drive replacement
Please try a
cli% admithw -checkonly
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
01-03-2018 08:03 AM
01-03-2018 08:03 AM
Re: help fixing botched drive replacement
admithw -checkonly
Checking for drive table upgrade packages
Checking nodes...
Checking volumes...
Checking system LDs...
After an upgrade from 2.2.4 or earlier, if sufficient space is present,
admithw will automatically remove and recreate the preserved data LDs
with a larger set size to improve their availability.
Checking ports...
Checking state of disks...
The following disks are NOT in an acceptable state:
Id CagePos Type -State- -------------------------------Detailed_State-------------------------------
0 0:12:0 FC failed vacated,notready,not_available_for_allocations,invalid_media,failed_hardware
6 0:0:0 FC failed vacated,notready,invalid_media,servicing
----------------------------------------------------------------------------------------------------
2 total
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2018 07:12 AM
01-05-2018 07:12 AM
Re: help fixing botched drive replacement
Bump