WSL not running after performing Virtual Hard Disk Expansion

[leventidis]

Windows Version

Microsoft Windows [Version 10.0.19045.2965]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 18.04

Other Software

No response

Repro Steps

My disk space I was using for my WSL Ubuntu-18.04 was running low, so I increased it from 264GB to 400GB using the instruction at: https://learn.microsoft.com/en-us/windows/wsl/disk-space#how-to-expand-the-size-of-your-wsl-2-virtual-hard-disk

The virtual disk space seems to have grown successfully but I am no longer able to access my WSL Ubuntu-18.04

Have I have corrupted my virtual hard disk. Any way I can recover files from it (through WSL or any other way that can access the ext4.vhdx file)?

Expected Behavior

Ability to access my WSL after expanding the virtual disk size

Actual Behavior

No longer able to access WSL.

The instance appears to have been stopped:

I tried various solutions from: #5836 but they don't seem to have helped. WSL is still not launching. I am also unable to access my WSL files from windows explorer using \\$WSL

I also tried moving my ext4.vhdx file into another machine and performing wsl --import-in-place but it also didn't work, showing the WSL instance as stopped and unable to access it via WSL terminal or powershell.

Diagnostic Logs

No response

[Baryczka]

Hey there! Have you tried to run wsl with debug console enabled to see at what point something is wrong?

C:\Users<user>.wslconfig

[wsl2]
debugConsole=true

[leventidis]

I didn't have such a file under my Users directory so I created one and initialize as you specified.

I currently don't see any new debug messages when trying to run wsl.exe from powershell or when trying to open the WSL terminal. Are debug message generated in some log file somewhere, if so where (I won't have access if they are generated in the WSL parititon).

My current error message when running wsl.exe from powershell or from the WSL terminal is the following:

The operation timed out because a response was not received from the virtual machine or container.
Error code: Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT

[process exited with code 4294967295 (0xffffffff)]

[Xthkeer]

Same issue, please delete this guide to prevent more people from ruining their own wsl
https://learn.microsoft.com/en-us/windows/wsl/disk-space#how-to-expand-the-size-of-your-wsl-2-virtual-hard-disk
@msftgits
same issue here: #9443

[Immortalin]

Same issue, also followed the guide

[Immortalin]

I have tracked down a few related issues:

https://www.spinics.net/lists/linux-ext4/msg86785.html
https://gitlab.com/qemu-project/qemu/-/issues/727
https://christopherkibble.com/posts/wsl-vhdx-recovery/
#5895

[ele7enxxh]

Do you have any solutions? I have encountered the same problem. This is really too bad, according to the official documentation, the expansion operation could have caused such a serious problem.

[microsoft-github-policy-service]

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!