Case intake and secure registration
We record the device, failure history, business priority, encryption status and required data before assigning a unique case reference.
Documented chain of custody and clear recovery objective.
Clear, controlled and evidence-led
Every case follows a documented workflow designed to protect the original media, reduce unnecessary risk and give you a clear decision before recovery work begins.
Why process matters
Storage failures can worsen when a device is repeatedly powered, rebuilt, formatted or scanned without first understanding the failure. Our workflow separates diagnosis, approval, acquisition, recovery and verification so each technical decision is made in the correct order.
That discipline is especially important for unstable hard drives, SSD firmware faults, degraded RAID arrays, encrypted volumes and virtual infrastructure.
From first contact to completion
Each stage has a defined purpose and a clear outcome, helping customers understand what is happening and why.
We record the device, failure history, business priority, encryption status and required data before assigning a unique case reference.
Documented chain of custody and clear recovery objective.
Engineers assess the device non-destructively to identify mechanical, electronic, firmware, logical, RAID, file-system or encryption-related failure.
Diagnosis, recovery approach, expected timescale and quotation.
Recovery work begins only after the customer approves the diagnosis and quotation. Where appropriate, urgent or priority handling can be arranged.
No recovery work proceeds without informed approval.
The original media is stabilised and imaged first. Recovery is then performed from controlled copies using hardware, firmware and software techniques selected for the failure.
Maximum preservation of the original device and recoverable evidence.
Recovered structures and priority files are checked for readability, completeness and consistency. Database, virtual machine and business data receive case-specific validation.
A verified recovery result rather than an untested file dump.
Approved data is transferred to suitable return media or a secure agreed method. Original devices and temporary working data are handled according to the case agreement.
Organised delivery, documented completion and privacy-conscious closure.
Prepare your case
Accurate history can prevent repeated work and help engineers choose the safest initial tests. Do not hide previous recovery attempts; they are technically important.
Open the case submission formDevice type, manufacturer, model and capacity
What happened immediately before the failure
Any repair, rebuild, format or recovery attempts already made
Required folders, databases, virtual machines or business files
Encryption passwords or recovery keys, where applicable
Operational deadline and priority level
Engineering and confidentiality controls
Recovery is designed around preserving the source device. We avoid unnecessary writes and work from controlled images whenever technically possible.
The diagnosis, quotation and expected recovery path are communicated before chargeable recovery work begins.
A clicking HDD, failed NVMe SSD, degraded RAID and corrupted VMFS datastore require different tools, sequencing and risk controls.
Customer data is accessed only for diagnosis, recovery and verification within the authorised scope of the case.
Realistic expectations
A healthy 8 TB drive with a logical issue may be easier than a severely unstable 500 GB drive. RAID layout, encryption, media degradation and replacement-part availability can materially affect the timeline.
For routine HDD, SSD and removable-media cases, subject to device condition.
RAID, NAS, servers, virtualisation and encrypted systems require architecture-specific analysis.
For operationally critical business cases where accelerated engineering is practical.
Before you submit the device
Do not initialise, format, rebuild, repair, clone with general-purpose tools or repeatedly power an unstable device. Record what happened and contact the laboratory before taking further action.
Common process questions
These answers explain the general workflow. Exact procedures may vary according to the device, failure and required data.
The initial assessment is designed to be non-destructive. Where a device requires opening, component work or another invasive procedure, the recovery path and associated risk are explained before proceeding.
The original device may need stabilisation, firmware access or controlled imaging. File-system analysis and recovery are then normally performed from an image or clone rather than repeatedly stressing the source media.
Where technically practical, a recovery result or representative file listing can be supplied so the customer can assess the outcome before final delivery. The exact verification method depends on the case type and confidentiality requirements.
Simple logical cases may be completed quickly, while mechanically damaged drives, unstable flash media, RAID arrays and encrypted enterprise systems may require substantially more time. A case-specific estimate follows diagnosis.
The result depends on the approved service terms and the technical condition of the media. Diagnosis is used to identify likely recoverability before the main recovery stage, and any change in prognosis is communicated.
Power the device off, avoid further recovery attempts, use anti-static protection where available, cushion it on all sides and place it in a rigid outer box. Do not ship a bare drive in an envelope.