RAID Data Recovery Cases | JiWang Data Recovery

Diagnostic testing confirmed no physical damage, allowing data recovery to proceed. Engineers used specialized equipment to reconstruct the data...

2019-07-04

JiWang Data Recovery engineers diagnosed the issue using professional equipment and found that offline server hard drives caused the server failure. To address this...

2019-04-06

1. JiWang Data Recovery engineers inspected the storage enclosure and found a failed drive in the 3559RUS3 unit, causing it to go offline...

2018-06-21

A BMX3850 server with two 300GB SAS drives had an unknown RAID level. Analysis after removing the drives revealed that data on both disks...

2017-03-19

Engineers imaged all four drives over seven hours, analyzed the original RAID 5 parameters, and successfully reconstructed the array virtually to recover the data.

2016-11-29

Initial diagnostics of the two drives showed firmware issues on Drive 0, which were repaired using specialized equipment. Drive 1 had PCB issues, which were addressed by...

2016-11-11

Engineers imaged each drive, analyzed filesystem structures to determine RAID parameters, excluded the failed drive, and built a virtual RAID array for recovery.

2016-10-30

1. RAID controller log analysis showed Drive 4 went offline 10 days prior and Drive 1 failed last, making repair of Drive 1 essential for recovery.

2016-10-17

JiWang engineers connected the drives to a dedicated workstation for testing. Drive 1 had minor bad sectors and was treated accordingly; the other drives...

2016-10-09

The administrator reported the server had been running for years on Windows 2000, but the RAID level was unknown. In this situation...

2016-09-26

Engineers imaged the storage to a 2TB drive, extracted the database, and mounted it on a Linux Oracle environment for verification.

2016-09-19

Diagnostics revealed head damage on Drive 2 and extensive bad sectors on Drive 0 among the five server drives. Engineers first used a PC-3000 in a cleanroom to...

2016-09-12

JiWang engineers first guided the client to image the storage to a 2TB drive. The database was then extracted and mounted for verification.

2016-09-05

JiWang Data Recovery engineers connected the drives to a specialized workstation for inspection. Drives 2 and 3 had minor bad sectors, and all drives were imaged.

2016-08-30

JiWang Data Recovery engineers imaged all four drives individually. By analyzing data storage patterns and parameters, the RAID 5 array data was successfully reconstructed.

2016-08-12

Upon inspection, JiWang Data Recovery engineers found that the last functional drive contained only zeros at the low level, indicating total data loss.

2016-07-29

Using specialized equipment, JiWang Data Recovery engineers determined that Drive 0 had head damage requiring cleanroom recovery, while Drive 1 had physical bad sectors.

2016-07-18

Our engineers removed and labeled the drives in order. Inspection revealed physical damage on Drive 4 and extensive physical bad sectors on Drive 3.

2016-07-10

JiWang Data Recovery engineers guided the client in imaging the storage to a 2TB drive. The database was then extracted and mounted.

2016-06-18

JiWang Data Recovery engineers removed the original drive trays, installed specialized adapters for the recovery workstation, and connected the server drives for analysis.

2016-06-03

Inspection by JiWang Data Recovery revealed that Drive 3 had been offline for six months. Drive 5, which failed later, had head damage.

2016-05-23

Upon arrival, JiWang Data Recovery engineers found the drive order had been altered and the RAID rebuilt. The Fibre Channel drives were then imaged.

2016-05-14

After analysis, JiWang Data Recovery engineers determined the issue was minor and the data could be recovered. The process was completed in one hour.

2016-05-07

The client submitted only the four drives after business hours without the server. JiWang Data Recovery engineers proceeded with analysis.

2016-04-30

Through inspection and virtual RAID technology, JiWang Data Recovery engineers successfully analyzed the array parameters and recovered the data.

2016-04-24
Search
WhatsApp