Unsolved
This post is more than 5 years old
3 Posts
0
420
March 22nd, 2017 21:00
PE 410 / PERC S300 - Unable to replace drive
PE410 w/ PERC S300 Controller
3 Drive (SAS) RAID5 Array
One of the three drives was in predicted failure. I removed the drive and installed a replacement drive. Upon doing so, I have the following symptoms:
1. When I go to the 'physical disks' under the controller section of OMA, it brings up a blank page. Prior to the replacement, this page would load fine
2. When I go to Virtual Disks, I have my now-degrated virtual disk (RAID5) AND a new Non-RAID disk. When I try to delete the non-RAID VD, it just goes to a blank page, similar to item 1 above. For what it's worth, both VDs show 0.01 GB in size which obviously isn't correct.
The server is running fine and fully functional
I have updated from OMA 8.3 to 8.5, no difference
S300 Firmware is on latest revision
What is my next step to try and get the new drive visible in OMA so I can assign it as hot-spare and allow the array rebuild to start?
-Ben
benjamin.rutter
3 Posts
0
March 24th, 2017 06:00
Hello Robert - I actually tried that first to no avail. I have also rebooted the server (which would have restarted that service) and also upgraded OMSA from 8.3 to 8.5 (which I assume also would have restarted that service). The problem persists.
Is there any merit to the idea that I may have better luck doing this through the RAID configuration utility during POST vs. the OMSA web interface?
-Ben
benjamin.rutter
3 Posts
0
March 24th, 2017 07:00
Quick update. I was able to delete the Non-RAID VD from the omconfig command line utility, however the system still doesn't see the new physical disk to be able to rebuild to or designate as a hot spare...
I tried restarting the Data Service after deleting that VD but still nothing. The Physical disks page still comes up as blank. I also tried to initiate a controller rescan via omconfig with but the command is apparently unsupported on this controller (S300)
Thoughts?
-Ben