Tuesday 27 February 2018

Raid 1 degraded on file server - how to fix

tl;dr Windows server degraded non OS hardware raid 1 after disconnecting them. Disks are healthy. Looking on tips on how to proceed to fix this.

Hello.

I've never really worked with Raid much aside from creating software striped raids in Windows 7 to test how it works.

Now I've got a Windows server 2008 file server that has a dedicated raid controller card.

It was really old and in need of a clean up and potential upgrade, so I turned it off, cleaned it up, removed all drives and wrote down their models, capacities, how they are configured and which sata ports they are connected to. Then reassembled it back just as it was before and turned it on.

Thing is, I didn't use a physical monitor for it at first, it never had one, just used RDP. After about two minutes of being unable to ping it I connected a monitor and saw a huge amount of lines flying around the screen, saying "Deleting corrupt attribute record (128, "") from file record segment 234123." GIF: https://i.imgur.com/5F8LxFP.gifv (ignore the compression artifacts)

None of those words sounded friendly in the situation so I panicked and hard shut down the PC holding the power button.

After plugging in a keyboard I started it up again and it booted successfully. But in disk management it shows up two separate mirrored drives where a single raid array used to be. I can access both individually and they aren't mirroring anymore.

When rebooting I used ctrl+A hotkey to get into the raid card configuration screen. At first when it starts up it says both drives are healthy and connected. Manage drives option tells me the array is degraded and one of the drives is missing. When browsing other menus both drives still appear.

Pics:

https://i.imgur.com/y6KnOzE.jpg

https://i.imgur.com/dVAureI.jpg

https://i.imgur.com/ZCs4qHE.jpg

What would be the correct and safe procedure to fix this and rebuild the array without losing data?

Thanks!



Submitted February 27, 2018 at 04:31PM by ntech2 http://ift.tt/2CoQJNO

No comments:

Post a Comment