I have a hp 3par v400 with 2 magazine with disk alert in fault, for this perform the maintenance procedure servicemag and release the 2 magazine, make the replacement of the disk with failure in the magazine, but the servicemag tells me that the disk does not It is the correct one, but it shows me all normal discs, I will attach the commands with the storage information.
My query if you know what steps I need to follow so that the magazine recognizes me well ?? Thanks in advance
Model,InServ V400
OS Version,3.2.1 (MU5)
Controller Nodes,2
----------------------------------
cli% servicemag status
Cage 0, magazine 0:
A servicemag resume command failed on this magazine.
The command completed at Thu May 16 15:12:31 2019.
servicemag resume 0 0 -- Failed. Please run servicemag status -d for more detail
--------------------------------------------------------------------------------------
servicemag status -d
Cage 0, magazine 0:
A servicemag resume command failed on this magazine.
The command completed at Thu May 16 15:12:31 2019.
The output of the servicemag resume was:
servicemag resume 0 0
... mag 0 0 already onlooped
... firmware is current on pd WWN [2000B45253A90A79] Id [ 4]
... firmware is current on pd WWN [2000B452536BA909] Id [ 5]
... firmware is current on pd WWN [5000CCA0371E606C] Id [ 9]
... firmware is current on pd WWN [2000B452536BEA98] Id [10]
... checking for valid disks...
Failed --
A disk has been incorrectly replaced.
This disk was not specified in the servicemag start -pdid option.
Please put the original disk back.
servicemag resume 0 0 -- Failed
------------------------------------------------------------------------------------------
cli% showpd -c -p -devtype FC
-------- Normal Chunklets --------- ---- Spare Chunklets ----
- Used -- -------- Unused --------- - Used - ---- Unused ----
Id CagePos Type State Total OK Fail Free Uninit Unavail Fail OK Fail Free Uninit Fail
4 0:0:0 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
5 0:0:1 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
9 0:0:2 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
10 0:0:3 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
--------------------------------------------------------------------------------------------
cli% showpd -e -p -devtype FC
-Read Error- -Write Error-
Id CagePos Type State Corr UnCorr Corr UnCorr T(C) LifeLeft%
4 0:0:0 FC normal 0 0 0 0 35 N/A
5 0:0:1 FC normal 0 0 0 0 40 N/A
9 0:0:2 FC normal N/A 0 N/A 0 40 N/A
10 0:0:3 FC normal 0 0 0 0 35 N/A
--------------------------------------------------------------------------------------------
cli% showpd -i
Id CagePos State ----Node_WWN---- --MFR-- -----Model------ ----Serial---- -FW_Rev-- Protocol MediaType -----AdmissionTime------
4 0:0:0 normal 2000B45253A90A79 SEAGATE SEGLE0600GBFC15K 6SL7E98R 3P01 FC Magnetic 2019-05-16 14:51:05 CLT
5 0:0:1 normal 2000B452536BA909 SEAGATE SEGLE0600GBFC15K 6SL1QSX7 3P01 FC Magnetic 2019-05-16 14:51:05 CLT
9 0:0:2 normal 5000CCA0371E606C HITACHI HVIPC0600GBFC15K 2AVJPWKN 3P04 FC Magnetic 2019-05-16 14:51:05 CLT
10 0:0:3 normal 2000B452536BEA98 SEAGATE SEGLE0600GBFC15K 6SL1LSZF 3P01 FC Magnetic 2019-05-16 14:51:05 CLT
------------------------------------------------------------------------------------------------------------------------------
cli% showcage -d cage0
Id Name LoopA Pos.A LoopB Pos.B Drives Temp RevA RevB Model Side
0 cage0 0:6:1 0 1:6:1 0 20 15-40 2.64 2.64 DC4 n/a
-----------Cage detail info for cage0 ---------
Position: cabinet00 D0
Fibre Channel Info PortA0 PortB0 PortA1 PortB1
Link_Speed 4Gbps -- -- 4Gbps
----------------------------------SFP Info-----------------------------------
FCAL SFP -State- --Manufacturer-- MaxSpeed(Gbps) TXDisable TXFault RXLoss DDM
0 0 OK FINISAR CORP. 4.2 No No No Yes
1 1 OK FINISAR CORP. 4.2 No No No Yes
Interface Board Info FCAL0 FCAL1
Link A RXLEDs Green Off
Link A TXLEDs Green Off
Link B RXLEDs Off Green
Link B TXLEDs Off Green
LED(Loop_Split) Off Off
LEDS(system,hotplug) Green,Off Green,Off
-----------Midplane Info-----------
Firmware_status Current
Product_Rev 2.64
State Normal Op
Loop_Split 0
VendorId,ProductId 3PARdata,DC4
Unique_ID 106203000037FF00
Power Supply Info State Fan State AC Assy_Part
ps0 OK OK OK PO1
ps1 OK OK OK PO1
ps2 OK OK OK PO1
ps3 OK OK OK PO1
-----Magazine Info----- ---State---
Mag SysLED HplLED Disks LoopA LoopB
0 Green Off 4 Ready Ready
3 Green Off 4 Ready Ready
4 Green Off 4 Ready Ready
6 Green Off 4 Ready Ready
7 Green Off 4 Ready Ready
-------------Drive Info------------- ----LoopA----- ----LoopB-----
Drive NodeWWN LED Temp(C) ALPA LoopState ALPA LoopState
0:0 2000b45253a90a79 Green 35 0xe1 OK 0xe1 OK
0:1 2000b452536ba909 Green 40 0xe0 OK 0xe0 OK
0:2 5000cca0371e606c Green 40 0xdc OK 0xdc OK
0:3 2000b452536bea98 Green 35 0xda OK 0xda OK
------------------------------------------------------------------------------------------------------------------------
Hello Jpalma2001
A disk has been incorrectly replaced.
This disk was not specified in the servicemag start -pdid option.
Please put the original disk back.
servicemag resume 0 0 -- Failed
Normally, when the servicemag operation complains that the disk is not the correct one , it could be that one has replaced the incorrect slot disk in the magazine.
Note : Disk 0:0:0 is the farthest disk from the handle and disk 0:0:3 is closest to the handle.
What does the following commands say ?
showpd -failed -degraded -s
showpd -p -cg 0 -mg 0 -c
showpd -p -cg 0 -mg 0 -s
showpd -p -cg 0 -mg 0 -i
showpd -p -cg 0 -mg 0 -e
servicemag status -d
I'm an HPE Employee
Hello
Looks like the disk replacement was done on another mag and not this because the output of showpd -p -cg 0 -mg 0 -i clearly states that the disks in Cage 0 Mag 0 are all admitted on 2019-05-16 and not later.
A full output of showpd -i and showpd -c will tell us which disks were introduced / worked on Mon Jul 1 14:03:26 2019.
I suggest you log a case with HPE support and they should be able to fix after determining the actual replacement drive and OR if an incorrect servicemag command had been issued.
I'm an HPE Employee
Yes , this looks good !
However, we have no 'Used' chunklets in the drives on this mag; they need to be played back.
showpd -c
--------- Normal Chunklets --------- ---- Spare Chunklets ----
-- Used -- -------- Unused --------- - Used - ---- Unused ----
Id CagePos Type State Total OK Fail Free Uninit Unavail Fail OK Fail Free Uninit Fail
4 0:0:0 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
5 0:0:1 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
9 0:0:2 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
10 0:0:3 FC normal 546 0 0 0 0 546 0 0 0 0 0 0
Hence , we may need to run a 'servicemag resume 0 0' to repopulate the magazine.
I'm an HPE Employee
Hello Paul,
Change the scenario, when running servicemag could not finish correctly I got the following message, attached photos of the problem.
I would like to know how I can release the magazine to change?
cli% showpd -failed
--Size(MB)-- ----Ports----
Id CagePos Type RPM State Total Free A B Capacity(GB)
--- 0:0:1 FC 15 failed 0 0 0:6:1- 1:6:1- --
--- 0:0:2 FC 15 failed 0 0 0:6:1- 1:6:1- --
--- 0:0:3 FC 15 failed 0 0 0:6:1- 1:6:1- --
--- 0:0:0 FC 15 failed 559104 0 0:6:1* 1:6:1 600
Paul, I am attentive to your comments and commands that I can make, thanks
Hello
" When running servicemag could not finish correctly" - Would that be a 'servicemag start' OR 'servicemag resume' ?
'servicemag status -d'
Also, the output of showpd -p -cg 0 -mg 0 -c / showpd -p -cg 0 -mg 0 -s / showpd -p -cg 0 -mg 0 -e will help.
Removing a magazine after a failed servicemag operation should be dealt with carefully.
I'm an HPE Employee