Another RAID 5 Critical disk failed or not responding

Toggle sidebar Toggle sidebar
D

Dwakefield528

Commendable
Dec 31, 2016
2
0
1,510
I am having a similar problem as dalin300 had on January 5, 2010 10:56:34 PM with some differences in hardware and usage.

Motherboard is Gigabyte GA-880GA-UD3H
3x Western Digital Hard drives

2 drives are still recognized and assigned to LD 1

Third drive is listed as a Single drive in the Ctrl+F RAID option utility.

I have a new drive but have been getting the same issue. I cannot find instructions on how to get the third drive assigned to the LD. The system worked great for 5 years.

Just stopped working about 3 days ago.

Also, the system will not boot into Windows now. Gets to the Windows Start screen but the Windows logo never shows.

Is there a way to fix this RAID and if not is there a way to recover the files from the two good drives?
 
Solution
S
The RAID failed for a reason. Typically it is due to drive problems. Check the SMART health status of your drives with a tool like CrystalDiskInfo.

I would suggest you first recover the data then remake the RAID5 then restore the recovered data as attempting to "fix" the RAID can cause more damage.

Most will tell you best practice is to make images of the RAID member drives and perform recovery on the images using tools like R-Studio UFSexplorer DMDE etc.

The other option is to perform RAID recovery the Linux way which is the process I use as it is often possible to safely avoid the imaging step.
Sort by date Sort by votes
D

Dwakefield528

Commendable
Dec 31, 2016
2
0
1,510
WD5000AAKS - 00UU3A0 500GB
WD Caviar Blue

That is the type of all three original drives and they worked in the RAID5 configuration perfectly for the last 5 years.

The drive I got for replacement is WD Blue 1 TB.

All are SATA drives.
 
Upvote 0 Downvote
S

S Haran

Distinguished
Jul 12, 2013
219
0
18,910
The RAID failed for a reason. Typically it is due to drive problems. Check the SMART health status of your drives with a tool like CrystalDiskInfo.

I would suggest you first recover the data then remake the RAID5 then restore the recovered data as attempting to "fix" the RAID can cause more damage.

Most will tell you best practice is to make images of the RAID member drives and perform recovery on the images using tools like R-Studio UFSexplorer DMDE etc.

The other option is to perform RAID recovery the Linux way which is the process I use as it is often possible to safely avoid the imaging step.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom