by Alt » Wed Apr 18, 2012 4:28 am
There may be several reasons for that. One, for example, is corrupted RAID service information.
When a RAID controller creates a RAID out of the disks, it writes some service information on it like the disk order, block size, etc. When such information becomes corrupted for some reasons, the controller cannot assemble the RAID anymore, or does that incorrectly. Therefore, Windows cannot access file system information and treats the RAID as an unformatted volume. But the data on the disks remains uncorrupted and can be recovered.
When you create a virtual RAID in R-Studio, you specify those parameters manually, the RAID is assembled correctly, and the data may be retrieved.
Just notice - this is only one reason, there may be others, and it's impossible to determine which one without seeing the actual data on the disks.
There may be several reasons for that. One, for example, is corrupted RAID service information.
When a RAID controller creates a RAID out of the disks, it writes some service information on it like the disk order, block size, etc. When such information becomes corrupted for some reasons, the controller cannot assemble the RAID anymore, or does that incorrectly. Therefore, Windows cannot access file system information and treats the RAID as an unformatted volume. But the data on the disks remains uncorrupted and can be recovered.
When you create a virtual RAID in R-Studio, you specify those parameters manually, the RAID is assembled correctly, and the data may be retrieved.
Just notice - this is only one reason, there may be others, and it's impossible to determine which one without seeing the actual data on the disks.