-
Notifications
You must be signed in to change notification settings - Fork 855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File or directory damaged or unreadable when launching linux distro #7433
Comments
Well... I reinstalled another distribution (Ubuntu 20) and got all my files back. I run the adviced fix "sudo e2fsck /dev/sdd -p", and it does find problems that it can "fix". But then the distrib doesn't even start with the error above (file or directory unreadable). So I guess the e2fsck command is doing more harm than good... I'm guessing this is all due to the recent Windows update I did as I never got these problems before (but I had others...)... I'm sorry but I'm sick of all these issues... I already lost several days of work because of them. I'm going back to VMWare... and I'll maybe come back to WSL 2 once the tech is more stable - for now... it just prevents me from working properly. |
@Kulgar, how did you get all your files back? I'm seeing the same error: The file or directory is corrupted and unreadable. [process exited with code 4294967295] Any advice is appreciated. Thanks. |
@mixxen I mounted the corrupted WSL 2 virtual disk on another fresh WSL 2 install and extracted the files from there... Do you know how to do that? |
@Kulgar, thanks for the advice. I see that my ext4.vhdx file is 0kb. I'm pretty sure that chkdsk corrupted the virtual disk file and everything is lost. I had to start from scratch...I'll be sure the backup the vhdx file regularly from now on. |
ow, shit... I didn't have this problem, my ext4 wasn't 0 Ko, it was more sth like 30 Go... |
Also the same. I notice that when Windows was starting it was fixing the C partition, so I think it saw somthing like ext4 and delete it. |
Same. Complete garbage sometimes. All my work project files that I didn't save into a repository are gone. Thankfully I put important stuff on the cloud. |
@Kulgar how to mount the corrupted WSL 2 virtual disk? |
@SBKK : It's been a long time so I don't recall exactly how I did it. I think I just followed some tutorial, like this one: https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk Also look at this : https://superuser.com/questions/1659218/is-there-a-way-to-access-files-from-one-wsl-2-distro-image-in-another-one |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Windows Build Number
Microsoft Windows [version 10.0.19043.1237]
WSL Version
Kernel Version
5.10.16
Distro Version
Ubuntu 18.04
Other Software
N.A.
Repro Steps
The launch of my Ubuntu 18.04 VM just stopped working.
It was working perfectly fine yesterday.
The error message I get is:
File or directory is damaged and unreadable
[process ended with code 4294967295]
I wonder if it stopped working because of a windows update I did recently.
Also, I really don't know what could have corrupted the vhdx file...
Expected Behavior
I just want the VM to launch again... thanks in advance if you have any idea on how I can repair my VM...
Actual Behavior
Getting the error message
File or directory is damaged and unreadable
[process ended with code 4294967295]
I am able to mount the ext4.vhdx file from another Ubuntu VM. I am actually extracting all the files I can to get my environment back... But I'd prefer being able to repair my existing VM.
Diagnostic Logs
Let me know if I can provide you with any relevant logs.
The text was updated successfully, but these errors were encountered: