He was in the middle of copying music from a USB stick that "plays fine" to a microSD card for his MP3 player when the stick's doors closed: "the stick will not open up to see the files on it", on the same Surface laptop he "always" uses. He has an older backup stick, but it holds "only 80% of the files", so he would rather not fall back on it and re-rip all his CDs. A stick which will play music but can't show you its file list has a logical fault, not a dead one; and since the backup is incomplete, recovering this stick is the only way to get back the missing 20% without the discs.
| Media | USB flash drive containing music files; the drive won't open to show its contents (but the contents still play); an older backup drive holds approximately 80% of the collection |
| Reported situation | Music on the stick reportedly still plays · cannot open the list of files on the drive · same trusted laptop used as always · a backup stick that contains about 80% of the collection · reluctance to rebuild the missing files by re-ripping CDs · prefers to recover all files currently stored on the stick |
| Fault class | Corruption of the file system or directory structures on flash media; the file structure is damaged enough that the listing won't open, while most of the music data is still intact behind these corrupted structures; card health to be confirmed |
| Equipment used | Drive imaged with a hardware write-blocker before analysing it · file system and directory structures extracted from the image with R-Studio, and FAT/exFAT backups compared · audio files no longer referenced by the damaged directory carved in PhotoRec · controller and flash health bench-tested · recovered music verified by playback and compared to the existing backup to confirm the missing 20% has been captured |
A drive which cannot open its file list generally has structural damage rather than damage to the data. The file listing comes from reading the directory entries within the filesystem. When these directory entries become corrupted, the drive will fail to open, yet the actual files remain unaltered in their locations in the data area. That the music on the stick reportedly still plays in some contexts is consistent with the data remaining intact while the catalogue indexing it is damaged: the files exist, but the catalogue describing them is broken.
The failure to open the stick on the same laptop he always uses points the fault at the stick itself. The Surface normally opens it without issue, which rules out a sudden change in software or drivers on his side and eliminates compatibility issues. It is the stick's own structures that have gone wrong.
The incomplete backup is what makes the recovery of this stick truly important. An 80 percent complete backup leaves 20 percent of his collection stored only on the now defective stick. Those files could otherwise only be recreated by re-ripping CDs, exactly the work he wishes to avoid. A good backup is not making recovery optional here: the stick holds the only current copy of a fifth of his music, so it is worth recovering properly.
Two routes cover the recovery, and his backup helps verify it. Where the directory structures can be rebuilt from their backup copies, he gets back all of his music in its folders again; where they cannot, the audio files are carved cleanly out of the data area by signature. And because an incomplete backup is available, the recovered set can be compared with it to confirm that the missing 20% has indeed been captured, verifying that the recovery has genuinely closed the gap.
All processes occur on the image, protecting a stick in an uncertain state. The reason for creating an image before attempting any kind of recovery is that you don't want to make any changes to a flash drive while trying to repair or restore anything. Since the recovery tools run on the image (not the actual stick), no repair attempt writes to a device whose structures are already damaged. Also, if the stick is physically failing rather than just logically corrupt, making an image captures what is readable before it deteriorates any further.
The stick's health is checked, and whatever that assessment shows guides the advice that follows. Most problems like this are purely logical, but a failing stick can corrupt in the same way, so it makes sense to check whether the device is healthy. Either way, the fully recovered music library deserves to live somewhere more durable than a single flash stick, and keeping a complete copy in more than one place fixes the 80% problem for good.
The stick was imaged under a hardware write-blocker before anything interpreted it. All filesystem and directory structures were then parsed from that image in R-Studio, with the FAT/exFAT backup copies compared, and PhotoRec carving was run for audio files the damaged directory no longer referenced. The controller and flash health were tested on the bench, after which the recovered music was confirmed through playback and matched against the incomplete backup to confirm that the missing 20% was recovered.
The stick was imaged, the filesystem and directory structures rebuilt and the data area carved, and all the music recovered and cross-checked with the incomplete backup. The assessment is free and the quote is a single fixed figure plus VAT; you have nothing to pay should we fail to recover your data. The decode: your stick not opening does not mean your music is lost; it simply means your directory is damaged. Since your backup contains only 80% of your music library, this stick is now your only copy of the remaining songs. Recovered and compared against your existing backup, the missing fifth comes back without you having to touch your CDs.
Stop writing data to the stick and do not run file system or disk repair utilities on it: typically a drive which will not open has damaged directories but still holds the files behind them, and repair operations write new information to the very device you are trying to save. Keep your partial backup; it can be used to verify that the recovery captured the files the backup missed. Recover from an image rather than the stick itself, and once you have the full set back, keep a complete copy in more than one place.
Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, 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, and in most cases you only pay if we recover your data. Start now or call the freephone.