An older office machine left them with a drive that half-cooperates. A Seagate Barracuda from a Dell Optiplex gives an "Error code 7" under a Dell recovery disk, and connected by SATA-to-USB to a laptop it "does shows as a disk, does not allow to see the files" They need the data. A drive that appears as a disk but won't show its files has a fault between being detected and being readable — it gets far enough to be seen but not far enough to present its data, which points at a drive-side condition to assess before more attempts wear it further.
| Media | Seagate Barracuda drive from a Dell Optiplex desktop — an "Error code 7" under a Dell recovery disk, and over SATA-to-USB it shows as a disk but its files are inaccessible; data recovery required. |
| Reported situation | Older Dell desktop, drive giving Error code 7 under the recovery disk · drive connected by SATA-to-USB to a laptop · shows as a disk but files not viewable · data recovery needed · aged drive and system. |
| Fault class | A drive detected but not readable — from filesystem or structure damage to a developing drive fault degrading reads; the data behind it to be assessed, further access attempts the hazard on an aged drive. |
| Equipment used | Drive health assessed on PC-3000 UDMA, read behaviour and any weak or failing areas profiled, since it is detected but unreadable · imaged under a hardware write-blocker on DeepSpar Disk Imager with retry limits, securing readable data first · filesystem structures parsed from the image in R-Studio, rebuilt where damaged · signature carving for anything the structures no longer reference · recovered data validated. |
Detected but not readable places the fault between two stages, which is informative. A drive showing as a disk means it is detected — it powers, communicates, and identifies itself. Not being able to see the files means it cannot present its data — either because the filesystem structures are damaged, or because the drive is struggling to read the areas holding the file information. It gets past detection but not to readable data, and that gap is where the fault sits.
The fault could be logical or a developing drive problem, and the distinction sets the method. "Shows as a disk, no files" fits two situations. The structures describing the files may be damaged — a logical fault with the data intact behind it. Or the drive may be failing to read reliably, an early hardware fault degrading access to the file information. The two need different handling — filesystem rebuilding versus careful imaging of a struggling drive — so which it is is established first, by assessing the drive's read behaviour.
Error code 7 and the age together suggest not assuming a purely logical fault. An error under the recovery disk, on a drive of this generation in an older system, means the drive's health cannot be taken for granted. It may be logical, but an aged drive that reads poorly is a real possibility — and that matters, because a struggling drive should be imaged with retry limits to secure what is readable before repeated access wears it further. Treating it cautiously is the safe assumption until health is confirmed.
Repeated access attempts are the risk on an aged drive, and imaging comes first. If the drive is failing, each attempt to read the files — through the recovery disk, through the SATA-to-USB connection — spends its remaining life and can worsen weak areas. So the first laboratory step is a health assessment, then a retry-limited image that captures readable data in one careful pass, rather than more attempts to browse the files directly. Recovery then works from that image.
The honest prognosis depends on the fault, established at assessment. If the fault is logical, rebuilding the structures from the image returns the data well. If the drive is failing, the outcome depends on how much images cleanly before weak areas defeat reading — captured as fully as the drive allows and reported honestly. Which applies is determined on professional equipment at the outset, with the recoverable extent confirmed before any charge.
The drive's health was assessed on PC-3000 UDMA, its read behaviour and any weak or failing areas profiled. It was imaged under a hardware write-blocker on DeepSpar Disk Imager with retry limits to secure readable data first, and the filesystem structures parsed from the image in R-Studio and rebuilt where damaged. Signature carving recovered anything the structures no longer referenced, and the recovered data validated.
Drive health assessed, a retry-limited image secured, and the data rebuilt or carved from it. 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: showing as a disk but not its files is a fault between detection and readability — logical, or a drive beginning to fail. Assessed and imaged carefully rather than browsed repeatedly, your data comes back as fully as the drive allows.
Stop trying to browse the files repeatedly — a drive detected but not readable may be beginning to fail, and each attempt through a recovery disk or USB adapter spends its remaining life. It's either damaged structures with the data intact, or a struggling drive, and telling them apart needs a health assessment first. Don't run repair tools that write to it or let anything reformat it. Set the drive aside and have it imaged, so the data can be recovered from a copy rather than the failing original.
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.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.