April 23, 20206 yr hi all had my 2nd unraid crash today.upon restart none of the dockers would start.i suspect it is something to do with the Cache where the appdata is held but i can see the Cache and all the files on it.it is doing a parity check at the moment so i am waiting for it to finish before i start pulling stuff about.The log has these entrys in it- pr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS info (device loop2): checking UUID tree Apr 22 20:31:11 unraid root: Resize '/var/lib/docker' of 'max' Apr 22 20:31:11 unraid kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480 Apr 22 20:31:11 unraid emhttpd: shcmd (76): /etc/rc.d/rc.docker start Apr 22 20:31:11 unraid root: starting dockerd ... Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS critical (device loop2): corrupt leaf: root=7 block=6846775296 slot=68, unexpected item end, have 3398973883 expect 14779 Apr 22 20:31:11 unraid kernel: BTRFS: error (device loop2) in btrfs_finish_ordered_io:3107: errno=-5 IO failure Apr 22 20:31:11 unraid kernel: BTRFS info (device loop2): forced readonly Apr 22 20:31:11 unraid kernel: BTRFS error (device loop2): pending csums is 69632 Apr 22 20:31:27 unraid emhttpd: shcmd (78): umount /var/lib/docker Apr 22 20:31:27 unraid kernel: mdcmd (41): check nocorrect Apr 22 20:31:27 unraid kernel: md: recovery thread: check P ... Apr 22 20:31:29 unraid unassigned.devices: Mounting 'Auto Mount' Remote Shares... Apr 22 20:31:31 unraid unassigned.devices: Remote SMB/NFS server '10.0.0.2' is offline and share '//10.0.0.2/unraid backup' cannot be mounted. Apr 22 20:31:31 unraid emhttpd: shcmd (81): /etc/rc.d/rc.php-fpm start Apr 22 20:31:31 unraid root: Starting php-fpm done Apr 22 20:31:31 unraid emhttpd: shcmd (82): /etc/rc.d/rc.nginx start Apr 22 20:31:31 unraid root: Starting Nginx server daemon... Apr 22 20:31:35 unraid webGUI: Successful login user root from 10.1.1.45 The Cache is 2 SanDisk_SDSSDH3_1T00's any ideas? cheers...
April 23, 20206 yr You need to attach diagnostics (Tools -> Diagnostics -> attach the full zip file).
April 23, 20206 yr Community Expert Your docker image is corrupt. You will have to delete and recreate it. You can get your dockers back just as they were using the Previous Apps feature on the Apps page. Other than that diagnostics look OK and your configuration looks OK. No details about your dockers in diagnostics though. Have you had any problems filling docker image? The 20G you have should be plenty if you don't have an misconfigured application writing into it. That by itself shouldn't cause a crash, depending on how you define crash. I assume you mean nothing is working and you are forced to hard reboot, since you got an unclean shutdown parity check. Diagnostics only has syslog since the reboot. Setup syslog server so you can save syslogs where you can retrieve them if it happens again.
April 23, 20206 yr Author cheers that seems to have done the trick. the system stopped and i had to do a hard reboot. i have set up the systog server to see if it happens again. cheers for all your help
Archived
This topic is now archived and is closed to further replies.