![]() However, only the files which are smaller than (N-1)*(block size) can be recovered. Having data from the rest of the member disks you can try to recover files. Since RAID 0 arrays are non-redundant, then if one of the member disks fails, then data that was on the failed disk is lost forever. Since the data is not that important to you, rebuilding the RAID configuration from scratch shouldn't bother you so much. However, you would most probably need to re-configure the whole array afterwards, and format both drives in the process. If you right-click in Disk Management on the missing drive, you should have the option to Reactivate Disk which should mark it as Online like the other. If the same controller has more SATA ports available try swapping the location of that HDD as well. I'd advise you to check the connections to it and also swap the SATA cable that is connecting it. ![]() This means that it's either corrupted or disconnected. Well, you could try running the DOS version of WD's Data LifeGuard as well then, it will allow to perform the QUICK and EXTENDED tests on the both drives without booting into Windows and it might also help you check their SMART attributes, however, the SATA mode needs to be either AHCI or IDE for this to happen.Īccording to your Disk Management screenshot, it seems like one of the HDD has gone missing. ![]() The data is not valuable enough to me that I would consider pursuing recovery through a professional company, but if there is a way I can fix this myself through Windows or DOS I would be willing to invest the time to do so Not to mention I have not seen anything abnormal in the performance of the drive in recent days and was able to play large 30 GB+ video files off the drive with normal loading times and no problems at all even on the day of the crash. test on either drive due to the drives being set up in RAID). Also two days before it crashed, I ran an extended Western Digital Lifeguard tool test on the drive and it passed determining no issues (I was unable to run a S.M.A.R.T. This is totally out of the realm though of anything I've seen before so I'm hoping someone who is familiar with what Disk Management is telling me can walk me through a few steps because I'd rather be safe than sorry.Īs mentioned before, I ran an HDTune Surface Test of both drives turning up no issues after the crash occurred. I have had RAID drives stop working in the past and I've gotten them working by various simple fixes in the BIOS or elsewhere. I appreciate the response, but I really don't believe that this is an issue with physical drive failure but rather the configuration of these RAID drives having gotten out of whack and can be corrected either through Windows or DOS by taking a series of simple steps. The only thing I've done so far to try to remedy the situation is switch the configuration in BIOS for the drives from RAID to AHCI and then back to RAID as that's fixed previous RAID arrays that have stopped working, but as that has not worked I'm a bit out of my comfort zone and I'd like some advice before proceeding with any troubleshooting. Not sure what has happened that's caused them to be listed as basically three disks when there are only two physical disks in the system comprising the RAID, hopefully someone can shed some light on that. Just so it's clear, other than the main SSD C: drive, I have two 4TB Western Digital Black Caviar drives that are supposed to be comprising the X: drive. This is what it looks like in Disk Management currently: Hoping someone can help me, my RAID 0 configuration on my desktop recently crashed and I'm hoping it can still be recovered (All of the data is already backed up on my NAS, but I'd like to get the drives up and running again if possible).
0 Comments
Leave a Reply. |