Symptoms

Partition lost. Prompt for formatting the partition. Partition data lost or garbled. The hard disk turns to only one partition after reinstalling the operating system. Prompt for damage of the structure when open a partition or file.

Probable Reasons

Destroyed by virus. Bad tracks. Incorrectly format partition or deleted files. The power is unstable or data line connects incorrectly. Misuse of Ghost, or be interrupted when using a partitioning software like Pqmagic.

Solutions

Analyze the underlying data storage structure, restore the damaged logic parameters, and regenerate files by using the professional data recovery software.

Time & Success Rate

General need 2 hours to complete.
The data are very likely to be recovered, unless they've been covered completely.

Symptoms

Can not boot the operating system. The hard disk partition is not completely identified. The hard disk doesn't work when power on. The hard disk has abnormal sound when power on. The board of hard disk has a short-circuit.

Probable Reasons

Head damage. Bad tracks. Motor damage. Fire ware damage. Zero track damage. Board short-circuit, or BIOS damage. The power is unstable, or data line connects incorrectly.

Solutions

Recover according to the damaged condition of hardware.
1. In the track, fire ware, or board damaged condition, the data can be recovered by external-fixed.
2. In the head or motor damaged condition, the data can be recovered by internal-fixed in the Class 100 Clean Room.

Time & Success Rate

General it takes 2 hours if it doesn't need to open the hard disk. It will take 5 hours if it need to open the hard disk.
Please cut-off the power supply when you heard abnormal sound. And if you don't, it will damage the hard disk surface, as a result, your data probably can not be recovered.

Symptoms

Can not attach the database. Database suspect. SQL system table page garbled. Can not attach the SQL database. Database capacity becomes 0 bytes. Can not start the ORACLE database.

Probable Reasons

System table damage. MDF files damage. Accidentally deleted and write data again. Many bad pages are existed in the database file. The length of DATARUN is too long that it's perhaps broken.

Solutions

1. Fix error pages and page links, export data tables.
2. Update the length of DATARUN, restore the broken page links, and export data tables.
3. In data cover situation, we analyze the table structure, extract, integrate, and recombine the fragments so that we can recover the database.

Time & Success Rate

At least 3 hours.
If you deleted the database accidentally, you can't write data into the same path any more, besides, you can't rebuild a file with the same name to cover it.

Symptoms

RAID crash. RAID information lost. RAID offline. RAID data volume failure. RAID starting failure.

Probable Reasons

RAID card damage. Rebuild RAID in a wrong way. RAID information garbled. Accidentally format partition. Hard disk physical damage (bad tracks or head damage).

Solutions

1. Analyze configure information, build a virtual RAID, and recombine the data.
2. Update dynamic database, restore structure catalog and reload the RAID.
3. In the bad tracks or head damage condition, the physical damage need to be fixed first, then rebuild the RAID based on a image file.

Time & Success

At least 3 hours.
If you have important data, please don't rebuild the RAID or format the partition in it.

1. Free consultation and check, data recovery after quotation.
2. Efficiency comes first.
3. Process following the principle of recoverability, to keep clients' hard disk in safe.
4. Confidentiality agreement and prevent data leakage.
5. Free data backup for 2 workdays to avoid accident.