He moved a drive between worlds and it went wrong at the border. An external he had "only ever used before with an Ubuntu machine" was connected to Windows to copy files; on disconnecting, Ubuntu "would no longer mount it and the Windows laptop reported it as corrupted". He then "ran chkdsk F: \f on it from Windows and now both machines can mount it but show it as empty". It held many MP3s. Windows misreading a Linux filesystem, followed by chkdsk, is a specific and recoverable sequence — chkdsk applied to a filesystem it does not understand damaged the structures, but the MP3 data is very likely still present behind the emptied index.
| Media | External hard drive formatted with a Linux filesystem, used with Ubuntu — reported corrupt by Windows, then subjected to chkdsk, now mounting on both systems but showing empty; a large MP3 collection the target. |
| Reported situation | Drive used exclusively with Linux, occasionally a Mac · connected to Windows to copy files · Ubuntu then unable to mount it, Windows reporting corruption · chkdsk run from Windows · both systems now mounting the drive but showing it empty · recovery not urgent. |
| Fault class | Filesystem damage from chkdsk run against a non-native Linux filesystem — the directory structures altered so the volume appears empty, with the file data intact in the data area behind them. |
| Equipment used | Drive imaged under a hardware write-blocker before anything, and used unwritten from now on · the original Linux filesystem structures analysed on the image in R-Studio and UFS Explorer, chkdsk's changes assessed · the file data located directly and structures reconstructed where possible · signature carving in PhotoRec for the MP3 collection where structures were destroyed · recovered audio validated by playback. |
Windows reporting the drive corrupt was a misunderstanding, not necessarily a real fault. Windows does not natively read Linux filesystems, so a healthy Linux-formatted drive connected to Windows commonly appears corrupted or unformatted — Windows simply cannot parse the structures. At that first point, the drive was very likely fine; Windows was reporting its own inability to read the format, not genuine damage.
chkdsk on a filesystem it does not understand is where the damage came from, and this is the key point. chkdsk is a repair tool for Windows filesystems. Run against a Linux filesystem it does not recognise, it does not "fix" anything — it can misinterpret the structures and write changes that corrupt them. That both machines now mount the drive but show it empty is the signature: chkdsk altered the structures enough to make the volume appear as an empty, mountable disk, when moments before it held a full collection. The tool created the problem it appeared to solve.
"Empty" almost certainly does not mean erased. chkdsk damaging the directory structures makes the drive look empty because the index describing the files is broken — but the MP3 data itself sits untouched in the data area. This is the same principle as any structural damage: the catalogue is broken, the contents remain. An emptied listing is a very different thing from overwritten data, and the distinction is what makes recovery realistic.
The disconnect between Linux and Windows explains the initial mount failure too. Disconnecting the drive from Windows may not have unmounted it cleanly, and combined with the format mismatch, that is why Ubuntu then refused it. All of this is logical — a tangle of filesystem misreads and one destructive repair — with no indication of physical drive damage, which keeps the prognosis in the recoverable range.
Recovery works the original Linux filesystem, not Windows' view of it. The drive is read with tools that understand Linux filesystems, analysing what chkdsk altered and reconstructing the original structures where possible to return the MP3s with their names and folders. Where chkdsk destroyed structures beyond rebuilding, the audio is carved from the data area by signature — MP3s carry strong signatures and carve cleanly — and validated by playback.
His stopping is what preserves the outcome, and the honest note is small. That recovery is "not urgent" is fine so long as the drive is not used further — every write risks landing on the recoverable data. The one honest caveat is that chkdsk's changes occasionally cost some structure permanently, so a portion may return carved without original filenames; the recoverable extent is confirmed at assessment before any charge.
The drive was imaged under a hardware write-blocker before anything and used unwritten thereafter. The original Linux filesystem structures were analysed on the image in R-Studio and UFS Explorer, chkdsk's changes assessed, and the file data located directly with structures reconstructed where possible. Signature carving in PhotoRec recovered the MP3 collection where structures were destroyed, and the recovered audio was validated by playback.
Drive imaged, the Linux filesystem analysed and rebuilt where chkdsk had altered it, and the MP3 collection recovered. 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; if the data can't be brought back, no charge is made. The decode: Windows called a healthy Linux drive corrupt because it couldn't read the format, and chkdsk then damaged the structures — but "empty" means a broken index, not erased music. Read as the Linux filesystem it is, your MP3s come back.
Never run chkdsk on a drive formatted for another system — Windows can't read Linux or, fully, Mac filesystems, so it reports them as corrupt, and chkdsk then damages structures it doesn't understand, which is how a full drive comes to look empty. If Windows offers to fix or format a drive it can't read, decline. An "empty" drive after chkdsk usually still holds its data behind a broken index. Stop using it and have it read with tools built for its actual filesystem.
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.