dayzd Posted June 2, 2015 Posted June 2, 2015 Hi all. I've managed to get myself into a weird situation with the HP P400 raid controller that I have in my personal workstation at home. (I edit a fair amount of video, so I have a small array for working projects) Backstory I started off with a 4-disk RAID5. One of the disks failed, so I stopped using the array and replaced the affected disk. When adding the replacement disk, I DID NOT let the array start the disk recovery process at boot - I opted to skip this and use the Storage Controller app once the system had booted. Somewhere within the HP storage controller application, I got something wrong. I suspect what I managed to do was rebuild the whole array, not just the replaced disk - now I have a working array, but with many many missing files, and the ones that are left are all corrupted (if they're larger than the stripe size) because the restriping that I think happened has filled every 4th block with 0's from the new disk. Traditional RAID recovery tools have not helped when given all four disks, or just the three original working disks. But wait, there's more! The latest addition to this cautionary tale (which I've given a working title of "RAID is not backup - you should know better") is that I've managed to resurrect the original failing disk. The drive had fallen prey to the well known Seagate / Maxtor 7200.11 firmware bug, which I've now fixed. And you're saying all this because...? What I'd like to try now is to replace the brand new disk I've just put into the array with the original Seagate that went bad, then restripe the whole array, in the hope that this will rebuild the missing blocks (that should theoretically still be on the Seagate) and bring all my data back. My problem is the controller won't let me - because it restriped the array with the new disk, it wants to rebuild the re-added Seagate based on the disks it already has, and as such has queued a disk rebuild for it, which I can't clear. TL;DR Does anyone know of a way to get an HP P400 raid controller to cancel/ignore an outstanding disk rebuild in favour of doing a complete array rebuild? Footnote I've spent long enough with this that I've now written off the data I've lost. I have copies of the most important stuff and what I've lost I can recreate with a week or so of effort. I don't care what happens to these disks now. At this point I just want to see if it can be recovered - I've never been beaten by a disk failure before and it's a matter of pride that I try everything feasibly possible to win!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now