Case:
RAID information is lost, and there are users in the array of SQL databases in the past year.
Solution:
During the analysis, it was found that there were many residual partitions and DBR information in the array, and the incorrect MFT positioning was positioned to the current MFT, and the size of the block was 512SEC.Next, the depressed situation appeared. In the mirror of 5 plates, I couldn’t find the verification block, because the 5 plates in the second block were normal MFT records (everyone knows that the raid of the strange number plate disk is raid.If there are four plates in a plate, then the school block must be garbled after XOR).At this time, I started to suspect that the array was not RAID5, and it was likely to be RAID0 (because the starting position of MFT was located in 786432 clusters/5).However, because the user is the administrator of the computer room and has certain experience, the patience is very affected. After 1 hour of confirmation, it is determined that the array is listed as RAID0, and everything is normal after Winhex reorganization.