Click on each image to view.
|
|
|
 |
| Desktop PC drive, belonging to a school office, which was gutted by fire. School rolls, accounts and payroll records were all stored on this drive. The smoke and heat damaged all of the drive electronics and the drive's spindle / ball-bearings mechanism. The smoke particles were cleaned off the drive platters. The drive's electronics and heat-damaged spindle were replaced. Recovery was 100 per cent successful. |
|
 |
| A PCB board badly damaged by heat and smoke. |
|
 |
| Failed drive heads. Owner needed 4 and a half years of .jpeg (photo) files extracted from this drive, as well as his Excel, Word and .PDF documents. Recovery was successful. |
|
 |
| This drive along with 3 others of the same type was part of a failed RAID 5 array. The RAID array belonged to an accountancy practice who stored a substantial amount of their client’s financial data on the server. We determined the parity and striping of the RAID array and performed a complete recovery for them, saving them a significant amount of potentially lost labour hours (and their reputation). |
|
 |
| This drive would spin up but was invisible to the host system's BIOS. Using our diagnostic utilities we found the NVRAM chip on the controller board of this drive had gone corrupt. The user needed to recover one 4GB .PST file containing 2 years worth of emails and all his business contacts. Recovery was successful. |
|
 |
| This drive, along with 3 others of identical type and size was part of a RAID 5 array. The business in question was only performing sporadic backups. They needed Word and Excel files, Crystal Reports files, Quickbooks and Thesauras payroll data retrieved. Recovery was successful. |
|
 |
| Failed drive heads. User needed to recover several hundred Autocad files along with Word, Excel, Outlook and TAS books files. The Autocad files contained architectural drawings and plans that would have taken months to recreate. Recovery was successful. |
|
 |
| This drive's firmware had failed. The drive belonged to the vice-president of a semi-state body, and contained important data which had not been backed up to the organisation's server. The in-house I.T team tried to recover the data but were only partially successful (they recovered about 10-15%). Drive Rescue Data Recovery recovered all the data within 72 hours. |
|
 |
| Desktop PC drive which experienced a power surge during an electrical storm, the electrical surge caused drive stiction and electronic damage. |
|
 |
| Problem: Seized Ball Bearings. The owner was a corporate user who had erroneously believed his laptop's backup system to the company's server was working. His whole customer database of the user was stored on this drive. The ball bearings were replaced and his complete customer database of the user was retrieved and returned to him on a DVD. |
|
 |
| This drive would power up but make no noise except a barely audible ticking noise. The problem was caused by a failed drive heads. As the exact part was not available in Europe or the US, new donor heads had to be ordered from a specialist components supplier in Asia. The donor heads worked and enabled a perfect read of the platters again. |
|
 |
| This drive, which was inside a family computer, was accidentally formatted by an enthusiastic (but well-intentioned) brother-in-law trying to repair the system. He ended up performing a complete format of the drive and then proceeded to install a fresh copy Windows. The family thought they had lost years of photos, legal documents, school and college projects. Recovery was successful. |
|
 |
| This drive was sent to us by a laptop user who discovered while his drive would power up it would not spin. We opened up the drive in our clean-room and discovered the problem was caused by the drive heads after stubbornly "parking" on the drive platters (otherwise known as stiction). The user needed all his Sage 50 accounts information, 600 contact details stored in Sage ACT and Photoshop files extracted. All of the files were recovered. |
|
| |