April 12, 20242 yr every 2 days i have this problem - docker service failed to start...and i have to restore a backup of usb key... how can i solve? thanks here last rows from sys log Apr 12 09:42:02 LordbyeNas emhttpd: shcmd (996586): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 50 Apr 12 09:42:02 LordbyeNas kernel: loop4: detected capacity change from 0 to 104857600 Apr 12 09:42:02 LordbyeNas root: mount: /var/lib/docker: mount(2) system call failed: File exists. Apr 12 09:42:02 LordbyeNas root: dmesg(1) may have more information after failed mount system call. Apr 12 09:42:02 LordbyeNas kernel: BTRFS warning: duplicate device /dev/loop4 devid 1 generation 262288 scanned by mount (20622) Apr 12 09:42:02 LordbyeNas root: mount error Apr 12 09:42:02 LordbyeNas emhttpd: shcmd (996586): exit status: 1 Apr 12 09:42:03 LordbyeNas avahi-daemon[20484]: Service "LordbyeNas" (/services/ssh.service) successfully established. Apr 12 09:42:03 LordbyeNas avahi-daemon[20484]: Service "LordbyeNas" (/services/smb.service) successfully established. Apr 12 09:42:03 LordbyeNas avahi-daemon[20484]: Service "LordbyeNas" (/services/sftp-ssh.service) successfully established. Apr 12 09:42:24 LordbyeNas nmbd[20328]: [2024/04/12 09:42:24.433402, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Apr 12 09:42:24 LordbyeNas nmbd[20328]: ***** Apr 12 09:42:24 LordbyeNas nmbd[20328]: Apr 12 09:42:24 LordbyeNas nmbd[20328]: Samba name server LORDBYENAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.10 Apr 12 09:42:24 LordbyeNas nmbd[20328]: Apr 12 09:42:24 LordbyeNas nmbd[20328]: ***** Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:47:26 LordbyeNas emhttpd: spinning down /dev/sdc Apr 12 09:48:50 LordbyeNas emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/Riavvio docker/script Apr 12 09:48:51 LordbyeNas kernel: docker0: port 2(veth0e80741) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 9(vethe5a4021) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 8(vethccab7aa) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 7(veth4a016e4) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 6(veth507bce7) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 5(vethebe6137) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 4(vethf5ac7b1) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 3(veth6e4d6ea) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: docker0: port 1(vethebcaa70) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device veth0e80741 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 2(veth0e80741) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device vethe5a4021 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 9(vethe5a4021) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device vethccab7aa left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 8(vethccab7aa) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device veth4a016e4 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 7(veth4a016e4) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device veth507bce7 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 6(veth507bce7) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device vethebe6137 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 5(vethebe6137) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device vethf5ac7b1 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 4(vethf5ac7b1) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device veth6e4d6ea left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 3(veth6e4d6ea) entered disabled state Apr 12 09:48:51 LordbyeNas kernel: device vethebcaa70 left promiscuous mode Apr 12 09:48:51 LordbyeNas kernel: docker0: port 1(vethebcaa70) entered disabled state Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:07 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:20 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:20 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:20 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:20 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:21 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:21 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:21 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:49:21 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:49:31 LordbyeNas flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:52:12 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Edited April 12, 20242 yr by Lordbye
April 12, 20242 yr Community Expert Solution 2 hours ago, Lordbye said: Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 12 09:43:17 LordbyeNas kernel: SQUASHFS error: Failed to read block 0x28885fc: -5 These usually mean a flash drive problem.
April 12, 20242 yr Author ouch..again? i have to change usb key every 6/8 months ok i'll try to buy another usb key and reload thanks
April 12, 20242 yr Author there is some command line that i can use to fix the situation while waiting for a new key
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.