In the process of doing raid data recovery, I found that there are many cases of abnormal situations. For example, in the following case, after the hard disk is replaced, the data is abnormal. Let us take a look.
The array of 11 disks used on the Sun minicomputer, due to the red light alarm of the hard disk, the file system fails after replacing the hard disk Rebuild. The following is the data recovery processing scheme:
Fault description and operation:
1. The array is composed of 11 250GB IDE hard disks. During normal operation, a disk is lit with a red light alarm. At this time, the array data can still be accessed and normal.
2. Without the shutdown, unplug the hard disk and the array is still normal. Then replaced with a new hard drive, the array automatically Rebuild, no human intervention.
3. When Rebuild is completed, the array partitions are not mounted under solaris, and some can be mounted, but the files and directories inside are not normal.
4. Unplug the newly replaced hard disk and the array is still faulty.
Analysis and solutions:
1. After unplugging the faulty disk, the new disk has not been replaced, and the array is still normal. This indicates that one disk is missing and the array data is still intact.
2, after replacing the new disk, the system automatically Rebuild, from the design of the array card itself, in theory, the target disk of Rebuild should be the newly replaced hard disk.
3. First check if there is any data in the disk array in the newly replaced hard disk. If there is data, compare it with the data volume of other data disks. If there is only a small amount of data, this means that the entire Rebuild has not been completed. If the data volume is the same as other hard disks, it is more troublesome. It is initially determined to be system level. The partition structure is wrong; if the new disk does not contain any data in the array, this means that Rebuild is not executed at all, or the target disk of Rebuild is not a newly replaced hard disk, but another hard disk.
4. Assuming that Rebuild is not completed, the recovery plan is: remove the newly replaced hard disk and reorganize the data with 10 disks.
5, assuming that Rebuild has been completed, Rebuild target disk is also right, trouble! From the solaris system level to repair the partition information.
6, assuming that Rebuild is not carried out, the recovery plan is the same as 4.
7, assuming that the Rebuild target disk is not a new hard disk, but also trouble, first find the disk of the wrong Rebuild, you also need the data of the disk that first alarmed, in order to reorganize the data.
8. All analysis and reorganization data are completed on the windows platform. After the reorganization, the data can be verified in the solaris environment.
9, the entire recovery time is relatively long, a total of 2.6TB of disk space, reorganization can take 24 hours or longer. The entire recovery process is 3-5 days, smooth.
Skin Care,Skin Care Series,Natural Skin Care,Skin Care Products
Shenzhen Sipimo Technology Co., Ltd , https://www.sipimotech.com