Hello,
I replaced a failed disk in a out of maintenance 3PAR 7200, but after completing all steps, the new disk still showing amber light.
There is no running servicemag command nor is the system showing any error. System tuning has been completed, GUI and CLI showing status ok.
I couldn't find a solution here or web either
Is there a way to fix this issue?
Best Regards!
3par – new disk showing amber LED
Re: 3par – new disk showing amber LED
dratmti wrote:Hello,
I replaced a failed disk in a out of maintenance 3PAR 7200, but after completing all steps, the new disk still showing amber light.
There is no running servicemag command nor is the system showing any error. System tuning has been completed, GUI and CLI showing status ok.
I couldn't find a solution here or web either
Is there a way to fix this issue?
Best Regards!
Are you sure you installed a supported drive?
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.
Re: 3par – new disk showing amber LED
MammaGutt wrote:dratmti wrote:Hello,
I replaced a failed disk in a out of maintenance 3PAR 7200, but after completing all steps, the new disk still showing amber light.
There is no running servicemag command nor is the system showing any error. System tuning has been completed, GUI and CLI showing status ok.
I couldn't find a solution here or web either
Is there a way to fix this issue?
Best Regards!
Are you sure you installed a supported drive?
-
- Posts: 3
- Joined: Tue Apr 30, 2024 11:11 am
Re: 3par – new disk showing amber LED
I've had this same issue on a 7400c, showpd all looked OK, no other issues from checkhealth and the same model numbers and FW version after upgrade as the rest of the disks in the system.
The only thing thats cleared it for me was a full shutdown and power on of the 3par (upon moving it to a different location) so I'd just assumed it was a bug with 3.3.1 MU3.
The only thing thats cleared it for me was a full shutdown and power on of the 3par (upon moving it to a different location) so I'd just assumed it was a bug with 3.3.1 MU3.