daddygrant Posted June 26, 2018 Share Posted June 26, 2018 My UnRaid cache went offline overnight. Rebooting or reseating the drive doesn't help. I'm getting Unmountable file system. Can anyone add some insight? Jun 26 17:32:28 Level2 kernel: nvme0n1: p1Jun 26 17:32:28 Level2 kernel: BTRFS: device fsid e5c6c962-9832-4b71-b271-74aadb623225 devid 1 transid 93580 /dev/nvme0n1p1Jun 26 17:32:56 Level2 emhttpd: INTEL_SSDPEDMX012T7_CVPF7185000Y1P2JGN (nvme0n1) 512 2344225968Jun 26 17:33:40 Level2 emhttpd: INTEL_SSDPEDMX012T7_CVPF7185000Y1P2JGN (nvme0n1) 512 2344225968Jun 26 17:33:40 Level2 emhttpd: import 30 cache device: (nvme0n1) INTEL_SSDPEDMX012T7_CVPF7185000Y1P2JGNJun 26 17:33:58 Level2 emhttpd: shcmd (139): mount -t btrfs -o noatime,nodiratime /dev/nvme0n1p1 /mnt/cacheJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): disk space caching is enabledJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): has skinny extentsJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizationsJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): the free space cache file (246982639616) is invalid, skip itJun 26 17:33:58 Level2 kernel: BTRFS critical (device nvme0n1p1): corrupt leaf, slot offset bad: block=188066988032, root=1, slot=129Jun 26 17:33:58 Level2 kernel: BTRFS critical (device nvme0n1p1): corrupt leaf, slot offset bad: block=188066988032, root=1, slot=129Jun 26 17:33:58 Level2 kernel: BTRFS: error (device nvme0n1p1) in btrfs_run_delayed_refs:3089: errno=-5 IO failureJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): delayed_refs has NO entryJun 26 17:33:58 Level2 kernel: BTRFS: error (device nvme0n1p1) in btrfs_replay_log:2476: errno=-5 IO failure (Failed to recover log tree)Jun 26 17:33:58 Level2 kernel: BTRFS error (device nvme0n1p1): cleaner transaction attach returned -30Jun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): space_info 1 has 4316372992 free, is not fullJun 26 17:33:58 Level2 kernel: BTRFS info (device nvme0n1p1): space_info total=744111472640, used=739794771968, pinned=0, reserved=262144, may_use=0, readonly=65536Jun 26 17:33:58 Level2 root: mount: /mnt/cache: can't read superblock on /dev/nvme0n1p1.Jun 26 17:33:58 Level2 kernel: BTRFS error (device nvme0n1p1): open_ctree failedJun 26 17:37:28 Level2 emhttpd: shcmd (191): /usr/sbin/hdparm -y /dev/nvme0n1Jun 26 17:37:28 Level2 root: /dev/nvme0n1:Jun 26 17:37:31 Level2 emhttpd: shcmd (192): /usr/sbin/hdparm -S0 /dev/nvme0n1Jun 26 17:37:31 Level2 root: /dev/nvme0n1: Link to comment
daddygrant Posted June 26, 2018 Author Share Posted June 26, 2018 I'm checking the status now I'm getting the following checking extents incorrect offsets 9393 134227121 bad block 188066988032 ERROR: errors found in extent allocation tree or chunk allocation checking free space cache checking fs roots checking csums incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258214674432-258214723584 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258214969344-258214977536 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258215268352-258215272448 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258215464960-258215501824 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258215534592-258216222720 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258216493056-258216505344 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258216603648-258216951808 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258217000960-258217066496 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258217099264-258217955328 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258217988096-258218106880 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258218135552-258219134976 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258219167744-258219331584 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258219335680-258220089344 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258220318720-258220400640 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258220404736-258220904448 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258221137920-258221953024 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258222190592-258222215168 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258222465024-258222477312 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258222731264-258222776320 but there is no extent record incorrect offsets 9393 134227121 Error looking up extent record -1 csum exists for 258222809088-258222956544 but there is no extent record ERROR: errors found in csum tree Checking filesystem on /dev/nvme1n1p1 UUID: e5c6c962-9832-4b71-b271-74aadb623225 found 275468541952 bytes used, error(s) found total csum bytes: 0 total tree bytes: 170672128 total fs tree bytes: 0 total extent tree bytes: 170295296 btree space waste bytes: 25007386 file data blocks allocated: 182976512 Link to comment
daddygrant Posted June 27, 2018 Author Share Posted June 27, 2018 Good news. I was able to do a btrfs repair and get my server back online. I needed to redownload the docker img file. One odd this is when I ran the scrub it detected an " uncorrectable error" .. hmm scrub status for e5c6c962-9832-4b71-b271-74aadb623225 scrub started at Tue Jun 26 20:24:35 2018, running for 00:05:41 total bytes scrubbed: 520.07GiB with 1 errors error details: csum=1 corrected errors: 0, uncorrectable errors: 1, unverified errors: 0 Link to comment
JorgeB Posted June 27, 2018 Share Posted June 27, 2018 6 hours ago, daddygrant said: One odd this is when I ran the scrub it detected an " uncorrectable error" .. hmm If it's a file with a bad checksum it will be identified in the syslog, delete or replace that file. Also, and though it's getting better all the time, btrfs repair often can't fix the problem 100%, most times it's recommended to backup cache, reformat and restore the data to avoid issues again in the near future. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.