ZimaOS WebUI not working, disconnecting from NAS

hiimoost1 · July 7, 2026, 12:13am

I use ZimaOS as my media server and have it connected to my NAS. I’ve changed the fstab to make sure it connects on boot, but occasionally while downloading and unpacking a file it Sabnzbd it completely locks up everything. Nothing out of the norm on the display, just can’t connect to the WebUI and all my apps are down. I’m not the most savvy when it comes to Linux so bear with me on everything. I used

journalctl -b -1 -p 3

as suggested by another user (with a different but similar issue) to get logs and this is what came up. I’m just assuming it has to do with losing connection to my NAS but not entirely sure. Tried hardwired straight to NAS through a switch and wireless both with same results. Will work for a while and then randomly just quit on me. Any help is appreciated. Logs below.

Jul 07 00:44:35 ZimaOS systemd[1]: multi-user.target: Job getty.target/start deleted to break ordering cycle starting with multi-user.target/start

Jul 07 00:44:39 ZimaOS kernel: Bluetooth: hci0: Reading supported features failed (-16)

Jul 07 00:44:41 ZimaOS blkmapd[631]: open pipe file /run/nfs/rpc_pipefs/nfs/blocklayout failed: No such file or directory

Jul 07 00:44:42 ZimaOS auditctl[637]: audit rules file /etc/audit/audit.rules doesn’t exist

Jul 07 00:44:42 ZimaOS systemd[1]: virtproxyd.socket: Socket service virtproxyd.service not loaded, refusing.

Jul 07 00:44:42 ZimaOS systemd[1]: Failed to listen on libvirt proxy daemon socket.

Jul 07 00:44:42 ZimaOS bluetoothd[648]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled

Jul 07 00:44:42 ZimaOS bluetoothd[648]: bap: Operation not supported (95)

Jul 07 00:44:43 ZimaOS avahi-daemon[792]: chroot.c: open() failed: No such file or directory

Jul 07 00:44:51 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:44:52 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2905904: comm du: iget: checksum invalid

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: [2026/07/07 00:44:53.726567, 0] ../../source3/passdb/pdb_smbpasswd.c:266(startsmbfilepwent)

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: startsmbfilepwent_internal: unable to lock file /etc/samba/smbpasswd. Error was Permission denied

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: [2026/07/07 00:44:53.726663, 0] ../../source3/passdb/pdb_smbpasswd.c:1378(smbpasswd_getsampwsid)

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: Unable to open passdb database.

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: [2026/07/07 00:44:53.726828, 0] ../../source3/passdb/pdb_smbpasswd.c:266(startsmbfilepwent)

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: startsmbfilepwent_internal: unable to lock file /etc/samba/smbpasswd. Error was Permission denied

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: [2026/07/07 00:44:53.726876, 0] ../../source3/passdb/pdb_smbpasswd.c:1378(smbpasswd_getsampwsid)

Jul 07 00:44:53 ZimaOS rpcd_lsad[1477]: Unable to open passdb database.

Jul 07 00:44:53 ZimaOS kernel: EXT4-fs error (device sda8): htree_dirblock_to_tree:1083: inode #3147530: comm du: Directory block failed checksum

Jul 07 00:44:58 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2629974: comm du: iget: checksum invalid

Jul 07 00:44:58 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2629974: comm dockerd: iget: checksum invalid

Jul 07 00:44:58 ZimaOS kernel: overlayfs: failed to resolve ‘/var/lib/docker/overlay2/l/ETLMEDEHKCOC7JPEULRDCZXJM4’: -74

Jul 07 00:44:59 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2905904: comm du: iget: checksum invalid

Jul 07 00:44:59 ZimaOS kernel: EXT4-fs error (device sda8): htree_dirblock_to_tree:1083: inode #3147530: comm du: Directory block failed checksum

Jul 07 00:45:00 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2629972: comm du: iget: checksum invalid

Jul 07 00:45:00 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2629973: comm du: iget: checksum invalid

Jul 07 00:45:00 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:06 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:11 ZimaOS kernel: EXT4-fs error (device sda8): ext4_lookup:1813: inode #2629974: comm dockerd: iget: checksum invalid

Jul 07 00:45:11 ZimaOS kernel: overlayfs: failed to resolve ‘/var/lib/docker/overlay2/l/ETLMEDEHKCOC7JPEULRDCZXJM4’: -74

Jul 07 00:45:13 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:19 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:25 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:31 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:32 ZimaOS nmbd[1269]: [2026/07/07 00:45:32.924600, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)

Jul 07 00:45:32 ZimaOS nmbd[1269]: dump_workgroups()

Jul 07 00:45:32 ZimaOS nmbd[1269]: dump workgroup on subnet 192.168.0.130: netmask= 255.255.255.0:

Jul 07 00:45:32 ZimaOS nmbd[1269]: WORKGROUP(1) current master browser = ZIMAOS

Jul 07 00:45:32 ZimaOS nmbd[1269]: ZIMAOS 40849a03 (Samba 4.21.9)

Jul 07 00:45:32 ZimaOS nmbd[1269]: OOSTNAS 40809a03 (OostNas)

Jul 07 00:45:32 ZimaOS nmbd[1269]: UGREEN 40809a03 (OostNas)

Jul 07 00:45:32 ZimaOS nmbd[1269]: [2026/07/07 00:45:32.925554, 0] ../../source3/nmbd/nmbd_workgroupdb.c:279(dump_workgroups)

Jul 07 00:45:32 ZimaOS nmbd[1269]: dump_workgroups()

Jul 07 00:45:32 ZimaOS nmbd[1269]: dump workgroup on subnet 192.168.122.1: netmask= 255.255.255.0:

Jul 07 00:45:32 ZimaOS nmbd[1269]: WORKGROUP(1) current master browser = ZIMAOS

Jul 07 00:45:32 ZimaOS nmbd[1269]: ZIMAOS 40849a03 (Samba 4.21.9)

Jul 07 00:45:32 ZimaOS nmbd[1269]: [2026/07/07 00:45:32.925820, 0] ../../source3/nmbd/nmbd_namelistdb.c:658(dump_all_namelists)

Jul 07 00:45:32 ZimaOS nmbd[1269]: dump_all_namelists: Can’t open file /var/lock/samba/namelist.debug: Permission denied

Jul 07 00:45:37 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:38 ZimaOS kernel: xhci_hcd 0000:39:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13

Jul 07 00:45:43 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:49 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:45:55 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:01 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:04 ZimaOS kernel: CIFS: VFS: \\192.168.0.30 sends on sock 0000000038999299 stuck for 15 seconds

Jul 07 00:46:07 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:13 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:19 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:25 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:31 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:37 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:43 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:49 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:46:55 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:01 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:07 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:13 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:19 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:25 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:31 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:37 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:43 ZimaOS systemd[1]: Failed to start IceWhale Files Service.

Jul 07 00:47:49 ZimaOS systemd[1]: var.mount: Job DATA.mount/stop deleted to break ordering cycle starting with var.mount/stop

Jul 07 00:47:49 ZimaOS blkmapd[631]: exit on signal(15)

Jul 07 00:47:49 ZimaOS dbus-broker-launch[643]: Activation request for ‘org.freedesktop.Avahi’ failed.

Jul 07 00:47:49 ZimaOS dbus-broker-launch[643]: Activation request for ‘org.freedesktop.nm_dispatcher’ failed.

Jul 07 00:47:49 ZimaOS winbindd[1296]: [2026/07/07 00:47:49.576383, 0, traceid=1] ../../source3/winbindd/winbindd_dual.c:1986(winbindd_sig_term_handler)

Jul 07 00:47:49 ZimaOS winbindd[1296]: Got sig[15] terminate (is_parent=1)

Jul 07 00:47:49 ZimaOS winbindd[1481]: [2026/07/07 00:47:49.576145, 0] ../../source3/winbindd/winbindd_dual.c:1986(winbindd_sig_term_handler)

Jul 07 00:47:49 ZimaOS winbindd[1481]: Got sig[15] terminate (is_parent=0)

Jul 07 00:47:49 ZimaOS winbindd[1343]: [2026/07/07 00:47:49.589340, 0] ../../source3/winbindd/winbindd_dual.c:1986(winbindd_sig_term_handler)

Jul 07 00:47:49 ZimaOS winbindd[1343]: Got sig[15] terminate (is_parent=0)

standard input lines 56-108/108 100%

gelbuilding · July 7, 2026, 10:13am

From those logs, I would not treat this as only a NAS connection issue yet.

The main red flag is this part:

EXT4-fs error (device sda8)
checksum invalid
Directory block failed checksum
overlayfs: failed to resolve /var/lib/docker/overlay2/...

That suggests the local ZimaOS disk/filesystem used by Docker may have errors. If Docker’s overlay storage is affected, that can explain why the WebUI and apps all stop responding.

The NAS/CIFS issue also appears here:

CIFS: VFS: \\192.168.0.30 sends on sock ... stuck for 15 seconds

But that appears after the local EXT4/Docker errors, so I would first verify the local disk and Docker storage health before blaming the NAS only.

Can you please run these after a reboot, before starting SABnzbd again?

lsblk -f

df -hT /DATA /var/lib/docker

dmesg -T | grep -iE 'ext4|i/o error|checksum|overlayfs|cifs|sda8' | tail -80

Also, please confirm whether SABnzbd is downloading/unpacking directly to the NAS mount, or whether it downloads to local storage first and only moves completed files to the NAS.

If SABnzbd is unpacking directly over CIFS/SMB, I would suggest testing with a local incomplete/download folder first, then move completed files to the NAS after unpacking. But the EXT4 errors need checking first because they may indicate local filesystem corruption or a failing disk.

hiimoost1 · July 10, 2026, 1:58am

lsblk -f

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS

loop0 squashfs 4.0

loop1 squashfs 4.0

loop2 squashfs 4.0

loop3 squashfs 4.0

loop4 squashfs 4.0

loop5 squashfs 4.0

sda

├─sda1 vfat FAT16 casaos-boot DEF8-7803 31.2M 2% /mnt/boot

├─sda2 squashfs 4.0

├─sda3 squashfs 4.0 0 100% /

├─sda4

├─sda5

├─sda6

├─sda7 ext4 1.0 casaos-overlay 63195bc2-9470-4d17-80b7-763f091fbeaa 77.5M 0% /var/lib/zerotier-one

│ /var/lib/rauc

│ /mnt/overlay

└─sda8 ext4 1.0 casaos-data 0be65118-7509-4a70-b576-62bab24171d7 67G 31% /var/log
                                                                                     /var/lib/libvirt

                                                                                     /var/lib/icewhale

                                                                                     /var/lib/docker

                                                                                     /var/lib/extensions

                                                                                     /var/lib/bluetooth

                                                                                     /var/lib/casaos

                                                                                     /opt

                                                                                     /media

                                                                                     /DATA

                                                                                     /var/lib/casaos_data
nbd0

nbd1

nbd2

nbd3

nbd4

nbd5

nbd6

nbd7

zram0 [SWAP]

zram1

zram2

nbd8

nbd9

nbd10

nbd11

nbd12

nbd13

nbd14

nbd15

df -hT /DATA /var/lib/docker

Filesystem Type Size Used Avail Use% Mounted on

/dev/sda8 ext4 98G 31G 68G 32% /DATA

/dev/sda8 ext4 98G 31G 68G 32% /var/lib/docker

dmesg -T | grep -iE ‘ext4|i/o error|checksum|overlayfs|cifs|sda8’ | tail -80

[Fri Jul 10 02:52:14 2026] ACPI: Early table checksum verification disabled

[Fri Jul 10 02:52:14 2026] xor: automatically using best checksumming function avx

[Fri Jul 10 02:52:15 2026] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8

[Fri Jul 10 02:52:15 2026] EXT4-fs (sda7): mounted filesystem 63195bc2-9470-4d17-80b7-763f091fbeaa r/w with ordered data mode. Quota mode: none.

[Fri Jul 10 02:52:23 2026] EXT4-fs (sda8): mounted filesystem 0be65118-7509-4a70-b576-62bab24171d7 r/w with ordered data mode. Quota mode: none.

[Fri Jul 10 02:52:23 2026] EXT4-fs (sda8): resizing filesystem from 26112113 to 26112113 blocks

[Fri Jul 10 02:52:34 2026] EXT4-fs error (device sda8): htree_dirblock_to_tree:1083: inode #2900116: comm du: Directory block failed checksum

[Fri Jul 10 02:52:34 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625005: comm du: iget: checksum invalid

[Fri Jul 10 02:52:34 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625008: comm du: iget: checksum invalid

[Fri Jul 10 02:52:34 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625007: comm du: iget: checksum invalid

[Fri Jul 10 02:52:34 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625006: comm du: iget: checksum invalid

[Fri Jul 10 02:52:35 2026] Key type cifs.idmap registered

[Fri Jul 10 02:52:35 2026] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.

[Fri Jul 10 02:52:35 2026] CIFS: Attempting to mount //192.168.0.30/media

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625008: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625008: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625007: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625007: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625008: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625008: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625007: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:46 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625007: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:47 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625006: comm .NET TP Worker: iget: checksum invalid

[Fri Jul 10 02:52:47 2026] EXT4-fs error (device sda8): ext4_lookup:1813: inode #2625006: comm .NET TP Worker: iget: checksum invalid

These are the results of running those. It is downloading and unpacking straight to the NAS to keep much faster transfer speeds via hardlinks with the Arr stack. If possible I’d like to keep it that way so copying movies won’t take so long to finish up, but if its causing that much of an issue I suppose I could just deal with it.

gelbuilding · July 12, 2026, 7:20am

Thanks for posting the results.

This confirms the main issue is not just the NAS connection.

Your /DATA and Docker storage are both on:

/dev/sda8

And this is the important part of the log:

EXT4-fs error (device sda8): Directory block failed checksum
EXT4-fs error (device sda8): iget: checksum invalid

That means the local ZimaOS data partition has filesystem errors/corruption. Since /DATA, /var/lib/docker, /var/log, /media, IceWhale services, and Docker all sit on that same partition, this can explain why the WebUI and all apps lock up.

The NAS/CIFS mount may still be involved, especially because SABnzbd is downloading and unpacking directly to the NAS, but I would not blame the NAS first while sda8 is throwing EXT4 checksum errors.

At this point I would stop SABnzbd and avoid heavy writes until the local disk/filesystem is checked, because continuing to write to a damaged filesystem can make things worse.

Can you please run:

mount | grep 'sda8'

journalctl -k -b | grep -iE 'sda8|ext4|i/o error|checksum|ata|smart|nvme' | tail -120

Also, what physical drive is sda? Is ZimaOS installed on an internal SSD, SATA SSD, USB drive, or something else?

For the SABnzbd setup: hardlinks only work within the same filesystem/mount. If SABnzbd and the Arr stack are all using the same NAS share path, keeping downloads and completed media on the NAS makes sense. But first the local sda8 corruption needs to be dealt with, because Docker itself depends on it.

hiimoost1 · July 14, 2026, 11:43pm

Sorry, personal life been a little crazy completely forgot to respond.

mount | grep 'sda8'

returns this

/dev/sda8 on /var/lib/casaos_data type ext4 (rw,relatime,commit=30)
/dev/sda8 on /opt type ext4 (rw,relatime,commit=30)
/dev/sda8 on /DATA type ext4 (rw,relatime,commit=30)
/dev/sda8 on /media type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/bluetooth type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/casaos type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/docker type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/extensions type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/icewhale type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/lib/libvirt type ext4 (rw,relatime,commit=30)
/dev/sda8 on /var/log type ext4 (rw,relatime,commit=30)

And

journalctl -k -b | grep -iE 'sda8|ext4|i/o error|checksum|ata|smart|nvme' | tail -120

Returns this

Jul 14 15:45:34 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:37 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:37 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:37 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:37 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:40 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:40 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:40 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:40 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:44 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:44 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:44 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:44 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:47 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:47 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:47 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:47 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:50 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:50 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:50 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:50 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:53 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:53 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:53 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:53 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:56 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:56 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:56 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:45:56 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:00 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:00 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:00 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:00 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:09 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:09 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:09 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:09 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:12 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:12 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:12 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:12 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:16 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:16 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:16 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:16 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:19 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:19 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:19 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:19 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:22 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:22 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:22 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:22 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:25 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:25 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:25 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:25 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:28 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:28 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:29 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:29 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:32 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:32 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:32 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:32 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:35 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:35 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:35 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:35 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:38 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:38 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:38 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:38 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:41 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:41 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:41 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:41 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:45 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:45 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:45 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:45 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:48 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:48 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:48 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:48 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:51 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:51 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:51 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:51 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:54 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:54 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:54 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:54 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:57 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:57 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:57 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:46:57 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:01 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:01 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:01 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:01 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:04 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 15:47:04 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c305f2c]
Jul 14 22:14:03 ZimaOS kernel: SQUASHFS error: lz4 decompression failed, data probably corrupt
Jul 14 22:14:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:03 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]
Jul 14 22:14:06 ZimaOS kernel: SQUASHFS error: Unable to read metadata cache entry [4c31558e]

ZimaOS is installed on an internal Kingston NVMe installed from a decent brand name USB drive with no issues originally. NAS is a DH2300 with a WD Red 8 TB drive in it. WD was bought brand new and hasn’t given me any issues or signs of failing since I bought it a few months ago.

gelbuilding · July 15, 2026, 9:15am

Thanks for the update.

This now looks bigger than the NAS mount.

Your /dev/sda8 is mounted to all the important ZimaOS data paths:

/DATA
/var/lib/docker
/var/lib/icewhale
/var/log
/media
/opt

So when sda8 has checksum errors, Docker, apps, logs, Files, and the WebUI can all be affected.

But the new log also shows repeated SQUASHFS errors:

SQUASHFS error: Unable to read metadata cache entry
SQUASHFS error: lz4 decompression failed, data probably corrupt

That is a major red flag. ZimaOS uses SquashFS for the read-only system image, so this is not pointing at the NAS first. Together with the earlier EXT4 errors on sda8, I would treat the internal Kingston NVMe / ZimaOS install as suspect.

I would avoid heavy downloading/unpacking for now until the local drive is checked.

Please run these two checks:

smartctl -a /dev/sda

journalctl -k -b | grep -iE 'squashfs|sda|ata|nvme|i/o error|read error|medium error|reset|timeout|checksum|ext4' | tail -200

If smartctl is not available on your install, please say so.

At this stage I would also make sure anything important under /DATA is backed up before doing repairs or reinstalling. The NAS may still be involved as a workload trigger, but these logs point to the local ZimaOS drive/install path first.