microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.46k stars 822 forks source link

The file or directory is corrupted and unreadable #7991

Open veqryn opened 2 years ago

veqryn commented 2 years ago

Version

Microsoft Windows [Version 10.0.19043.1466]

WSL Version

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

Was running an I/O heavy process inside WSL2. It wasn't doing anything crazy, just reading from files, writing to temporary files, calculating and transforming data in memory. At some point, my laptop had a blue screen of death. I rebooted, and WSL2 now doesn't start, and gives me the error message: The file or directory is corrupted and unreadable I have run checkdisk, as well as memory checks, and is fine with no problems discovered. Docker for Windows still starts ok, just my Ubuntu doesn't anymore.

Expected Behavior

The virtual disk for ubuntu shouldn't get corrupted so easily. There should be ways to recover.

Actual Behavior

The file or directory is corrupted and unreadable. Press any key to continue...

### Diagnostic Logs I followed the steps to submit the issue with a link to here, in the Feedback Hub.
ohmer commented 2 years ago

Just hit the same issue. BSOD while doing a rm inside Ubuntu 20.04. Disk was almost full and I was removing quite a large volume of file (200GB). Found this in the event log:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8036eaf12e6, 0xffffdb83a2e7f458, 0xffffdb83a2e7ec70). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fe835643-f31c-4081-bf9d-6a5167c3a962.

ohmer commented 2 years ago

image

Antonia-Chalka commented 2 years ago

Had the same issue with @ohmer. Was removing a large amount of files (~600GB), had a BSOD with IRQL_NOT_LESS_OR_EQUAL. Ran sfc/scannow just in case and though it outputted that it detected and repaired corrupt files, wsl is throwing me the same error message as above

DanPinGF commented 2 years ago

You might have to reinstall WSL. Damage done from a Stop screen can be extremely unpredictable.

DanPinGF commented 2 years ago

Was removing a large amount of files (~600GB), had a BSOD with IRQL_NOT_LESS_OR_EQUAL.

@Antonia-Chalka, in that case I would have brought up your situation here: #7335

Benhawkins18 commented 1 year ago

Same issue here. Disk was full, removed 200g of data and got a blue screen of death. wsl The file or directory is corrupted and unreadable.

danieledagnelli commented 1 year ago

Same issue here. Was deleting a 200G folder, BSOD, same error.

Nekto89 commented 1 year ago

same issue, got BSOD while doing rm -rf on large build folder. Now I can't launch Debian Bullseye anymore "The file or directory is corrupted and unreadable." image

oemaix commented 9 months ago

the same issue was encountered after I deleted 200GB inside Ubuntu.

ericblade commented 8 months ago

Was building an OS image with Yocto, and the final step, building the image, was taking an extremely significant amount of time longer than normal. I was unable to open another WSL shell, with it simply hanging on a black screen, so I did a wsl --shutdown, which i let run for about 15 minutes (!!) and then I restarted the PC.

When I came back to it, the WSL instance Ih ad been working in gave this error

Failed to attach disk 'D:\WSL\LuneOS-Build\ext4.vhdx' to WSL2: The file or directory is corrupted and unreadable.
Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x80070570

[process exited with code 4294967295 (0xffffffff)]

complete chkdsk did not fix

11philip22 commented 4 months ago

I have the same problem

PS C:\Users\philip> wsl
The file or directory is corrupted and unreadable.

I tried check chkdsk, I disabled to optional feature and enabled it again, did the same with dism restarted 10000's of times and tried reinstalling again trough the store or appx package. And nothing works. No I am not gonna reinstall windows because this piece of trash doesnt work. My time has been wasted enough

OBorce commented 1 month ago

Same issue, does anyone know if there is a way to recover data from the Ubuntu disc?