Invisible Even to Linux

The decode

The Linux live USB test is genuinely good diagnosis, and it localises the fault. Booting a Linux live environment tests the drive independently of Windows and its installation — a lower-level look that a great many people would not think to try. That Linux also cannot see the drive rules out a Windows-specific or software problem: the drive is not presenting itself to any system at all. His test correctly establishes that the fault is in the drive itself, at the hardware level.

Undetected at the hardware level means the drive isn't identifying itself, which has several recoverable causes. A drive invisible even to Linux is not communicating its basic identity to the system — and the reasons are drive-side: a controller-board fault, a firmware problem in the drive's own internal systems, or a mechanical failure that stops it initialising. None of these is a software issue, and importantly, none necessarily means the data is damaged. The fault is in reaching the drive, not in what it holds.

His pessimism is understandable but premature, because these faults are addressable. "Not much to do" is the natural conclusion when a drive shows up nowhere — but a laboratory works precisely at this level. A firmware fault is addressed in the drive's service mode to restore detection; a controller-board fault is repaired or the board's calibration transferred to a donor; a mechanical fault is addressed in clean air. What looks like a dead end to normal systems is often a routine drive-side recovery, and the data is frequently intact behind the fault.

The drive's age raises fragility, not impossibility. A 12-year-old drive is more delicate — components aged, lubricants settled — so it is handled gently, with imaging that assumes each read could be among its last. But age does not change the diagnosis or rule out recovery; it means careful first handling and, for some faults, more effort sourcing a compatible donor. The fault is standard; the years are why the approach is cautious.

The honest prognosis depends on which drive-side fault it is, established at assessment. A firmware or controller fault with intact platters typically recovers well once detection is restored; a mechanical fault depends on the platters' condition. Which applies is determined on professional equipment at the outset, and the prognosis stated plainly before any charge — but his careful test describes a recoverable class of fault, not the dead end he fears.

On the bench

The drive was assessed on PC-3000 UDMA for detection, firmware state and responsiveness, and its power draw profiled on a current-monitored bench supply while listening for spin-up and mechanical behaviour. Its firmware was addressed in service mode where the drive's own systems had faulted, or the mechanism opened in clean air under laminar flow for a head or motor fault. Once detection was restored, the drive was imaged on DeepSpar Disk Imager and the data validated.

The outcome

The drive-side fault identified and addressed, detection restored, and the data imaged and validated. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; opening a drive is invasive work, so 50% of the quote is payable upfront to cover donor parts and lab time, with the rest owed only if the data comes back. The decode: invisible even to Linux means the drive isn't identifying itself — a hardware-level fault, not a software one, and one a laboratory can often address. Your test was exactly right, but "nothing to do" is premature: reached at the drive level, your data behind the fault comes back.

Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.