johnodon Posted October 7, 2016 Share Posted October 7, 2016 Just started seeing the below messages a few minutes ago. I stopped the array since. Advice? Oct 7 13:35:38 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231476686848 wanted 1231262 found 1231051 Oct 7 13:35:43 unRAID emhttp: shcmd (120): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 40 |& logger Oct 7 13:35:43 unRAID kernel: BTRFS info (device loop0): disk space caching is enabled Oct 7 13:35:43 unRAID kernel: BTRFS: has skinny extents Oct 7 13:35:43 unRAID kernel: BTRFS error (device loop0): parent transid verify failed on 9903521792 wanted 135393 found 131733 Oct 7 13:35:43 unRAID kernel: BTRFS error (device loop0): parent transid verify failed on 9903521792 wanted 135393 found 131733 Oct 7 13:35:43 unRAID kernel: BTRFS: failed to read tree root on loop0 Oct 7 13:35:43 unRAID root: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Oct 7 13:35:43 unRAID root: missing codepage or helper program, or other error Oct 7 13:35:43 unRAID root: Oct 7 13:35:43 unRAID root: In some cases useful info is found in syslog - try Oct 7 13:35:43 unRAID root: dmesg | tail or so. Oct 7 13:35:43 unRAID kernel: BTRFS: open_ctree failed Oct 7 13:35:43 unRAID root: mount error Oct 7 13:35:43 unRAID emhttp: err: shcmd: shcmd (120): exit status: 1 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231497052160 wanted 1231273 found 1231052 Oct 7 13:35:51 unRAID kernel: repair_io_failure: 26 callbacks suppressed Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231497052160 (dev /dev/sdc1 sector 206007520) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231497056256 (dev /dev/sdc1 sector 206007528) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231497060352 (dev /dev/sdc1 sector 206007536) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231497064448 (dev /dev/sdc1 sector 206007544) Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231490596864 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490596864 (dev /dev/sdc1 sector 205994912) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490600960 (dev /dev/sdc1 sector 205994920) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490605056 (dev /dev/sdc1 sector 205994928) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490609152 (dev /dev/sdc1 sector 205994936) Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231490711552 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490711552 (dev /dev/sdc1 sector 205995136) Oct 7 13:35:51 unRAID kernel: BTRFS info (device sdd1): read error corrected: ino 1 off 1231490715648 (dev /dev/sdc1 sector 205995144) Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231486058496 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231486074880 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231497314304 wanted 1231273 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231497494528 wanted 1231273 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231494299648 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231490940928 wanted 1231272 found 1231052 Oct 7 13:35:51 unRAID kernel: BTRFS error (device sdd1): parent transid verify failed on 1231457779712 wanted 1231257 found 1231051 Quote Link to comment
JorgeB Posted October 7, 2016 Share Posted October 7, 2016 Possibly one of the cache disks dropped offline, diagnostics would help. Quote Link to comment
johnodon Posted October 7, 2016 Author Share Posted October 7, 2016 Ran a BTRFS scrub and corrected 600+ errors. Had to blow away the docker image but it also unfortunately it also corrupted two of my VMs. Oh well...all rebuildable. john Quote Link to comment
Recommended Posts
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.