The customer needed Microsoft Exchange databases (.edb files) from a NetGear NAS/SAN crashed due to hardware failures on multiple drives.

The storage system failed to boot properly. The customer needs only a small set of data whose backup is either corrupt or not available.

The customer could not find 1000s of family photos and Microsoft Word documents on his NAS.

The customer needs a way to bypass all virtuallization layers and restore the data directly.

A share was deleted from a FreeNAS server. The customer needed to get back his digital photos.

A thin provisioning volume on a RAID was unmountable. The customer seeked help after trying many commercial recovery softwares.

A customer has an encrypted NAS. The shared volume was no longer accessible.

A customer has a FreeNAS with 4x3TB drives. The connections to the drives were lost, and afterward the zpool could not be imported.

A customer has a RAID 0 that contains two partitions on the same physical hard drive.

A customer has a partially corrupted sparse bundle disk image holding an HFS+ volume.

A customer has a NAS with 8x3TB drives holding two thin-provisioned ext4 volumes. For unknown reasons the volumes became corrupted and inaccessible.

A ReadyNAS device is no longer accessible. It uses the new Linux file system BtrFS.

While creating a new VHD file on an iSCSI device, the customer accidentally deleted existing VHD files.

The NAS failed with one drive damaged beyond repair. The customer failed to determine the RAID settings.

The drives had some bad sectors causing data to be inaccessible. Standard RAID/NAS data recovery methods yielded just around 50% recovery rate.

The NAS was working fine but movies were accidentally deleted.

An HP SAN with 8x1TB hard drives failed. It contained 4 logical volumes and was configured with thin provisioning.

The NAS initially displayed error code E13 and E26 and data became inaccessible. After the customer applied a firmware update in order to fix the problem, the NAS displayed error code E30 (drive malfunctioning).

A failed Lacie NAS consisted of 5x500 GB hard drives with two drives having damaged sectors. The customer was able to clone the drives to disk image files but had problems reconstructing the data.

A customer had a zpool on a RAIDZ consisting of 3x2TB drives. One drive went bad forcing the RAID to operate in degraded mode. A technician tried to replace the bad drive, but he replaced a good drive by mistake. The RAID rebuild failed and the RAID went down. The customer tried unsuccessfully to import and scrub the zpool.

A customer needed to recover data from a rebuilt RAID. The customer was able to reconstruct the RAID and the HFS+ volume it contained. However only small files were recovered. All large files were corrupted.

Read more

A customer had an Iomega StorCenter ix4-200d NAS that rebooted continuously with the error message "insufficient disks for RAID 5".

A customer needed help with an 8x750GB RAID 5. The drives were from a server with a failed controller card. Information about the controller card was not available. The RAID was believed to hold two HFS+ partitions.

The NAS went offline. After forcing the device back online, the customer could not find the shared folder holding his data. He tried to recover the data using File Scavenger®, but most recovered files lost the original name and could not be opened.