EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

[maikebing]

• [ x] I have tried with the latest version of Docker Desktop
• [ x] I have tried disabling enabled experimental features
• [ x] I have uploaded Diagnostics
• Diagnostics ID:C4E02F92-AB70-47DA-AD62-E93F92F8A89B/20230328092922

Actual behavior

Every few minutes, restart again and again.

Expected behavior

Information

• Windows Version: Windows 11 22H2 22621.1413
• Docker Desktop Version: 4.17.1 (101757)
• WSL2 backend
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM:

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

[2023-03-28T09:24:55.399695200Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [ 10.710301] EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[WARN] DD0033: does the host have Internet access? unable to fetch http://docker.com/
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [ 10.710301] EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?

Please note the following 2 warnings:

1 : The check: does the host have Internet access?
Produced the following warning: unable to fetch http://docker.com/

If the host does not have Internet access then containers will also not have Internet access.

The lack of Internet access could be caused by

• physical disconnection: check your ethernet cable or Wifi network
• the local network firewall policy: check with your IT department if access to docker.com is expected to work
• a VPN (or lack of one): try again with or without the VPN running

2 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: [ 10.710301] EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
microsoft/WSL#5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

Please investigate the following 1 issue:

1 : The test: is the WSL 2 Linux filesystem corrupt?
Failed with: [ 10.710301] EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
microsoft/WSL#5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

Steps to reproduce the behavior

1. ...
2. ...

[artm]

I'm getting the same diagnotics.
Docker desktop crashes after start up with this error dialog:

An unexpected error occurred
A timeout occured while waiting for a WSL integration agent to become ready.

This can occur when starting after an abrupt termination. To work around the issue, please terminate WSL (wsl --shutdown) and start Docker Desktop again. If the issue persists please collect diagnostics and submit an issue (https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal).

Error details:
1 error occurred:

• starting WSL integration service: synchronising agents: starting added distros: 1 error occurred:
• waiting for WSL integration for wsl-admin: waiting for WSL distro integration to become ready in "wsl-admin": timeout

Suggestions from the error message and linked issues didn't help:

• executing wsl --shutdown
• unregistering docker-desktop / docker-desktop-data WSL
• reinstalling DD

I originally had this problem with DD 4.15.0 and currently (after an attempt to solve by reinstall) with 4.17.1.

[kwint]

Having the same issue here. Restarting wsl doesn't seem to work.

Docker desktop is hanging on "Docker Desktop Starting" splash screen.

Also, my diagnose.exe check hangs after this log output:

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [   20.306316] EXT4-fs error (device sde): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?

[megcredit]

same issue after trying to move the wsl files to a separate drive (not enough space on my C drive - this has been the most difficult process ever)

[maikebing]

Please investigate the following 2 issues:

1 : The test: is the VM time synchronized?
    Failed with: parsing time output: 2023-04-15T11:01:45+00:00: parsing time "2023-04-15T11:01:45+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".

2 : The test: is the WSL 2 Linux filesystem corrupt?
    Failed with: [   15.045125] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
https://github.com/microsoft/WSL/issues/5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

[Tofandel]

I had the same issue with docker desktop 4.21.1, I just did wsl --shutdown which fixed the fs issue and then fully restarting docker desktop and it started

[jtabox]

Hi,
I've been instructed to leave a comment here, I seem to be having the same issue, and shutting down and restarting WSL and Docker Desktop doesn't seem to fix it.

I had to produce diagnostics logs for another issue and noticed this in self-diagnose.json:

[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [    2.748394] EXT4-fs error (device sdc): ext4_put_super:1196: comm Xwayland: Couldn't clean up the journal

Checking dmesg in WSL I could find those lines:

[    2.741056] blk_update_request: I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[    2.746483] Buffer I/O error on dev sdc, logical block 134184960, lost sync page write
[    2.746920] JBD2: Error -5 detected when updating journal superblock for sdc-8.
[    2.747316] Aborting journal on device sdc-8.
[    2.747579] Buffer I/O error on dev sdc, logical block 134184960, lost sync page write
[    2.747971] JBD2: Error -5 detected when updating journal superblock for sdc-8.
[    2.748394] EXT4-fs error (device sdc): ext4_put_super:1196: comm Xwayland: Couldn't clean up the journal
[    2.748846] EXT4-fs (sdc): Remounting filesystem read-only

I shut down Docker Desktop, then wsl --shutdown, waited 10-15 seconds until all the distros stopped running and restarted Docker Desktop again, but the issue appeared again in dmesg:

[    2.104095] blk_update_request: I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[    2.105796] blk_update_request: I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[    2.106669] Buffer I/O error on dev sdc, logical block 134184960, lost sync page write
[    2.107254] JBD2: Error -5 detected when updating journal superblock for sdc-8.
[    2.107732] Aborting journal on device sdc-8.
[    2.108038] Buffer I/O error on dev sdc, logical block 134184960, lost sync page write
[    2.108577] JBD2: Error -5 detected when updating journal superblock for sdc-8.
[    2.109124] EXT4-fs error (device sdc): ext4_put_super:1196: comm Xwayland: Couldn't clean up the journal
[    2.109600] EXT4-fs (sdc): Remounting filesystem read-only

According to lsblk, device sdc is /mnt/wsl/docker-desktop/docker-desktop-user-distro.

In case it's of any help, here are the diagnostics logs. They were created for another issue as I said, but it was happening at the same time as this one:

Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/25CEB2BE-D79A-4F2B-ACB7-B6FAC9D4F447/20240206105236.zip
Diagnostics ID:      (uploaded)

[jtabox]

Just wanted to add that all the above logs are after a complete wipe (incl. docker folders in Local and Roaming AppData, Program Files, ProgramData and a .docker folder in my user home folder) and fresh reinstall of Docker Desktop.

[emack463]

Just noting that I had this issue reported in com.docker.docker-diagnose for Windows 10, Docker Desktop version 4.27.1. After container construction, containers would periodically crash. I eventually resolved (fingers crossed) by rolling back to Docker Desktop 4.27.0. So far diagnose is clear. Postscript; it just crashed again.

Post-postscript: Rolled back to DD 4.26.1, Switched distro from Debian to Ubuntu and so far the test container has been running for 12 hours and diagnose is clear (also upgraded NVIDIA drivers, just in case). I'd guess the rollback was the key bit.

[maikebing]

It may have something to do with the NVIDIA graphics card driver!My DD somehow returned to normal, I don't dare to reproduce it. Maybe someone can try to reproduce it.

[jtabox]

@maikebing How do you mean with NVIDIA drivers? How would you reproduce the issue?

[maikebing]

It may be because the NVIDIA driver was installed and then uninstalled. Anyway, after waiting for a few months, updating the new version of wsl, DD is normal.