Hey guys,
I have an Asus M5A99FX Pro R2.0 motherboard with AMD RAIDXpert. I set up a 1000GB RAID1 array on it. This was about 8 years ago. Every once in a while, a power outage or something would knock one drive offline and degrade the array. After a reboot the drive would be back online and it would rebuild just fine.
Recently, a drive dropped offline and the array became degraded. I figured it was no big deal and rebooted then set it to rebuild overnight. The next morning I took a look and both drives had dropped offline at 70% rebuild. Uh oh.
I rebooted and tried rebuilding a few more times but one of the drives kept going offline. Figured it must be bad so I swapped another in and started rebuilding to it. The rebuild was almost complete when the other drive went offline.
I am currently cloning the last drive to a good drive as it does not seem likely that it will do a successful rebuild. And yes, I know RAID is not a backup. I have several backups of the drive. I am just cloning it to save me the trouble of reinstalling some programs that I didn't have at the time of the last backup.
I tossed the first failed disk in another PC while the other one was cloning to take a look at the SMART data. 7120 bad sectors. Ouch. No wonder it wouldn't rebuild.
This leads to my question. Why on earth would the RAID controller never alert me to such an unhealthy disk? This disk has obviously been going out for a long time and it was just after the second disk started going bad that I found the problem. Trying to view the SMART data on the PC when the drive is in RAID just gives "not supported".
I have another way older PC with a RAID controller that I just use as a server for some video games. I am using a hard drive with bad sectors since I really don't care if it dies abruptly. However, every time I boot that PC, it beeps and complains that one of my RAID disks are failing.
Is there something that I am doing wrong with the AMD AMD RAIDXpert that I can't see the SMART data from the OS, and that the RAID controller never complains even when there is a disk that has both feet in the grave? It seems to defeat the purpose of the RAID array... Having one disk go bad and then just swapping a new one in isn't an option when the controller waits until both disks are bad to alert me to the problem...
Let me know your thoughts.
I have an Asus M5A99FX Pro R2.0 motherboard with AMD RAIDXpert. I set up a 1000GB RAID1 array on it. This was about 8 years ago. Every once in a while, a power outage or something would knock one drive offline and degrade the array. After a reboot the drive would be back online and it would rebuild just fine.
Recently, a drive dropped offline and the array became degraded. I figured it was no big deal and rebooted then set it to rebuild overnight. The next morning I took a look and both drives had dropped offline at 70% rebuild. Uh oh.
I rebooted and tried rebuilding a few more times but one of the drives kept going offline. Figured it must be bad so I swapped another in and started rebuilding to it. The rebuild was almost complete when the other drive went offline.
I am currently cloning the last drive to a good drive as it does not seem likely that it will do a successful rebuild. And yes, I know RAID is not a backup. I have several backups of the drive. I am just cloning it to save me the trouble of reinstalling some programs that I didn't have at the time of the last backup.
I tossed the first failed disk in another PC while the other one was cloning to take a look at the SMART data. 7120 bad sectors. Ouch. No wonder it wouldn't rebuild.
This leads to my question. Why on earth would the RAID controller never alert me to such an unhealthy disk? This disk has obviously been going out for a long time and it was just after the second disk started going bad that I found the problem. Trying to view the SMART data on the PC when the drive is in RAID just gives "not supported".
I have another way older PC with a RAID controller that I just use as a server for some video games. I am using a hard drive with bad sectors since I really don't care if it dies abruptly. However, every time I boot that PC, it beeps and complains that one of my RAID disks are failing.
Is there something that I am doing wrong with the AMD AMD RAIDXpert that I can't see the SMART data from the OS, and that the RAID controller never complains even when there is a disk that has both feet in the grave? It seems to defeat the purpose of the RAID array... Having one disk go bad and then just swapping a new one in isn't an option when the controller waits until both disks are bad to alert me to the problem...
Let me know your thoughts.
Comment