July 7, 20196 yr Hi all, I am a somewhat seasoned vet when it comes to unRAID but this is the first time I've had major issues that I cannot fix without wanting to lose my data, so please help! We lost power unexpectedly a few days ago, the tower obviously shutdown uncleanly. I have tried to boot it and pull diagnostics from it with no avail. I have tried to delete the docker image via cli but it just hangs. I am at a loss; entirely confused. Everything I do, the OS just hangs. I am running 6.7.2. I will attach what logs I have, any sort of input will be appreciated. Thank you! tower-syslog-20190707-0201.zip tower-diagnostics-20190707-0149.zip Edited July 7, 20196 yr by kgwozdz adding diagnostics
July 7, 20196 yr Does IP have change so you can't access \\tower - Pls check in local console, there are the actual IP show after Unraid boot up You have BTRFS file system error, may be try set Unraid don't auto start the array, and you can enter GUI. In USB stick, /config/disk.cfg, change ' startArray="no" ', then save. Jul 6 21:42:37 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:42:47 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:42:57 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:07 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:18 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:28 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:38 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:48 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:58 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Edited July 7, 20196 yr by Benson
July 7, 20196 yr The docker image is definately pooched. Jul 6 21:42:25 Tower emhttpd: shcmd (114): /usr/local/sbin/mount_image '/mnt/cache/appdata/docker.img' /var/lib/docker 50 Jul 6 21:44:59 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 /dev/loop2 776T 12G 776T 1% /var/lib/docker Most interesting is that you have a 50G docker image file (twice as large as 99% of the rest of the users, but so be it -> not a problem by itself), but after mounted, it thinks that it is a 776TB image. It is easiest to simply delete the image, and recreate it. But, Jul 6 21:42:22 Tower emhttpd: shcmd (92): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/sdm1 /mnt/cache While half your drives are formatted as reiserfs, array drives tend to be basically static whereas the cache drive tends to always be changing. I would never let the cache drive be rfs. Switch it to XFS for less problems.
July 7, 20196 yr Author 17 hours ago, Benson said: Does IP have change so you can't access \\tower - Pls check in local console, there are the actual IP show after Unraid boot up You have BTRFS file system error, may be try set Unraid don't auto start the array, and you can enter GUI. In USB stick, /config/disk.cfg, change ' startArray="no" ', then save. Jul 6 21:42:37 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:42:47 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:42:57 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:07 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:18 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:28 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:38 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:48 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Jul 6 21:43:58 Tower kernel: BTRFS warning (device loop2): csum failed root 5 ino 3059 off 237568 csum 0x98f94189 expected csum 0x80789b56 mirror 1 Thanks for the reply. After I set it to not start the array, What do I need to do to fix the BTRFS errors? Edited July 7, 20196 yr by kgwozdz had set twice instead of start; incomplete sentence
Archived
This topic is now archived and is closed to further replies.