Solved!
Go to SolutionI
ianjenkins
3 Posts
0
39936
April 8th, 2010 06:00
Degraded
I have a PE1800, with a SCSI hotplug backplane and a 3 disk RAID5. Recently it came up with one disk showing degraded. Perhaps unwisely (having read many posts on the internet which suggest a quick unplug and plugin might of solved it!), I replaced the disk this morning. Everything went fine, it has rebuilt, server is up and happy, however the disk in question still shows up degraded.
The virtual disks shows happy in Openmanage, just the physical disk that shows degraded.
Any ideas?
SBS 2003 if that makes a difference
2035
0
Posted April 8th, 2010 08:00
Many thanks for the response.
I actually marked it as offline in OM first, then removed it. Still worth trying the rescan option?
2035
0
Posted April 8th, 2010 08:00
Rescan worked a treat. Thank you very much.
2035
0
Posted April 8th, 2010 08:00
I'm guessing that the drive was "degraded" - showing Predictive Failure - but was still Online when you removed it? Try a RESCAN on the controller. In OpenManage Server Administrator, go to Storage>PERC>Information/Configuration (link at the top of page), then RESCAN from drop down menu of available controller tasks. In Array Manager, right-click on the PERC and choose RESCAN.
2035
0
Posted July 20th, 2011 06:00
Strange - I have the same problem, but I don't see the option for rescan in my PERC 5/E Adapter Info/Conf page. Has it been renamed in OMSA 6.5?
2035
0
Posted July 20th, 2011 07:00
PERC 5/6 do not have a rescan. Have you run a Consistency Check recently?
theflash1932
11 Legend
•
16255 Posts
2035
1
Posted April 8th, 2010 08:00
Yes, especially if firmware hasn't been updated and/or there wasn't at least 30 seconds between drive changes. There is no harm in a RESCAN ... it simply forces the controller to re-evaluate the devices it manages.
You will receive a warning that you must click on the NAME of the server in OMSA AFTER the rescan completes but before the changes will be visible. Once the rescan completes (let the page finish loading), then close and restart OMSA.