search

microsoft / WSL

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

Error code: Wsl/Service/CreateInstance/WSL_E_DISK_CORRUPTED when opening Ubuntu from apps #11400

Closed wcardosodev closed 6 months ago

wcardosodev commented 6 months ago

Windows Version

Microsoft Windows [Version 10.0.22631.3374]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

Kernel Version

Default Distribution: Ubuntu Default Version: 2

Distro Version

Ubuntu

Other Software

No response

Repro Steps

From windows search menu

Expected Behavior

Ubuntu would start

Actual Behavior

Get error message:

The distribution failed to start because its virtual disk is corrupted. Error code: Wsl/Service/CreateInstance/WSL_E_DISK_CORRUPTED Press any key to continue...

Diagnostic Logs

WslLogs-2024-03-30_21-25-56.zip

github-actions[bot] commented 6 months ago

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information 
Detected appx version: 2.1.5.0
Detected user visible error: Wsl/Service/CreateInstance/WSL_E_DISK_CORRUPTED

OneBlue commented 6 months ago

Thank you @wcardosodev. Looking at the logs it indeed looks like the disk is corrupted:

[ 55.269209] EXT4-fs (sdc): VFS: Can't find ext4 filesystem

You can try these instructions to recover the files but unfortunately you'll probably to unregister the distribution with wsl --unregister <distro> and register it again.

wcardosodev commented 6 months ago

@OneBlue thanks for the response, I already unregistered + reregistered as I needed it for work stuff. Do the logs give any indication of what may have caused the corruption as when I noticed it was corrupted I hadn't done any work related stuff in a week or so, just want to prevent this happening again in future

OneBlue commented 6 months ago

Unfortunately not. It could be hardware issue, bug or abrupt shutdown, but there's no easy way to tell after the fact.