RAID5 recovery

[MONTEGOD7SS]

Had a Perc controller get it's config hosed and after a reconfigure everything is up and showing in Windows. I did not rebuild the array (just reinitialized) or format the drive and when running ZAR it did show all of the data as being recoverable but froze at 100% saying "idle". This was done by trying it as a broken array, and now I am trying it with the intact array option so that it looks more like a Windows Defrag window. Should I have just let it sit at 100% until it was done, even though it sat that way for 12hr or so? Attached is a screen shot of the progress so far, is it looking good?

[Alexey V. Gubin]

You verify it if is stuck by checking the Task Manager. If CPU usage is low, and ZAR does not indicate any disk activity, and you cannot actually hear disks seeking, for about ten minutes, then its stuck.

Your screenshot is looking good - it is just doing its disk scan, at a reasonably good speed (see bottom of the window - reading 12.3 Mbyte/sec @ 75% CPU usage).

[MONTEGOD7SS]

It is at 47% complete now and between 25-45% CPU usage. Was there something that should have been selected/deselected for the broken array scan that might have caused it to not go past 100% and give me the Next button? Can I assume that the blue boxes in this scan are the file structure since the array was never rebuilt, just reinitialized?

[Alexey V. Gubin]

Was there something that should have been selected/deselected for the broken array scan that might have caused it to not go past 100% and give me the Next button?


No. It is either a bug (likely), or something malfunctioned in hardware (less likely). Regardless of settings, it should either complete the run, or bail out but give some reasonable error message. Just a lock up with no indication whatsoever is bad.


Can I assume that the blue boxes in this scan are the file structure since the array was never rebuilt, just reinitialized?

Yes.