ervicemag start command failed

qingchuan — Tue, 27 Sep 2022 03:33:53 GMT

I have an storage (3PAR7200),，it has 2 harddrive failed，after we replace drive ，servicemag start command is failed，there is error log

1633442 cli% servicemag status -d Cage 0, magazine 3: A servicemag start command failed on this magazine. The command completed at Sun Sep 25 03:48:39 2022. The output of the servicemag start was: Failed -- Unable to run servicemag Start command. Servicemag is either active or has failed for this cage and magazine. Please rectify any error conditions and issue "servicemag unmark" before retrying. servicemag start -wait -pdid 9 -- Failed Cage 1, magazine 12: A servicemag resume command failed on this magazine. The command completed at Fri Sep 23 10:54:31 2022. The output of the servicemag resume was: servicemag resume 1 12 ... mag 1 12 already onlooped Wait for system to get drive device type... ... upgrading firmware on pd WWN [5000CCA0164C9DB7]... ... firmware is current on pd WWN [5000CCA07104D15B] Id [32] ... checking for valid disks... ... checking for valid disks... ... disks not normal yet..trying admit/onloop again ... onlooping mag 1 12 ... checking for valid disks... ... checking for valid disks... ... disks in mag : 1 12 ... normal disks: WWN [5000CCA0164C9DB7] Id [ 3] diskpos [0] ... not normal disks: WWN [5000CCA07104D15B] Id [32] ... verifying spare space for disks 32 and 3 ... playback chunklets from pd WWN [5000CCA0164C9DB7] Id [ 3] ... All chunklets played back / relocated. ... cleared logging mode for cage 1 mag 12 ... relocating chunklets from spare space ... chunklet 0:773 - move_error,move_failed, failed move ... chunklet 0:774 - move_error,move_failed, failed move ... chunklet 0:775 - move_error,move_failed, failed move . . . ... chunklet 42:812 - move_error,move_failed, failed move ... chunklet 43:777 - move_error,move_failed, failed move ... chunklet 43:778 - move_error,move_failed, failed move ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space ... Chunklets not in proper state for relocation, will wait 30 seconds and try again ... Retrying... relocating chunklets from spare space Failed -- PD 3 is not valid

，how to fix it？I am glad and gratitude for your suggestion

Re: ervicemag start command failed

Satish04 — Mon, 26 Sep 2022 09:48:10 GMT

Hi qingchuan,

Hope you are doing good.

Procedure to replace the failed drive:

1. To check if you have any failed or degraded disks in the system. Take note of the disk ID and cage position and run the command "showpd -failed -degraded".
2. Check if the disk sevicemag command is running on the drive, run the command "servicemag status".The servicemag command is used to inform the system to evacuate all the chunklets from a drive so that it is ready for service.
3. We can double check there is no data left on the drive by running "showpd –space PDID".
4. Now, we can replace the failed drive.
5. Once the drive is replaced run the command "admitpd"
6. Next, run the command "servicemag status".
7. To check the drive status run the command "showpd -state PDID".

When you are replacing the failed drive, need to check new drive FW will comaptible with system FW.
If the drive FW not compatible with system FW, need to upgrade the drive FW and then try admitting the PD.

Hope this helps.!

Regards,
Satish

topic Re: ervicemag start command failed in HPE 3PAR StoreServ Storage

ervicemag start command failed

Re: ervicemag start command failed