iilied Posted July 24, 2022 Share Posted July 24, 2022 (edited) hello, was rebuilding a disk and cache 1 dropped offline then went online again, and since the log is listing errors: Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031746809856 (dev /dev/sdc1 sector 6058872) Jul 24 06:24:00 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 1031702478848 wanted 24394769 found 24380501 Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702478848 (dev /dev/sdc1 sector 5972288) Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702482944 (dev /dev/sdc1 sector 5972296) Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702487040 (dev /dev/sdc1 sector 5972304) Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702491136 (dev /dev/sdc1 sector 5972312) Jul 24 06:24:00 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 1031746781184 wanted 24394898 found 24380677 Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031746781184 (dev /dev/sdc1 sector 6058816) Jul 24 06:24:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031746785280 (dev /dev/sdc1 sector 6058824) Jul 24 06:24:00 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 29528623 off 70361088 csum 0x06a1d7ca expected csum 0x71a37def mirror 2 Jul 24 06:24:00 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 1031236435968 wanted 24393467 found 24378723 Jul 24 06:25:00 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 1031702462464 wanted 24394769 found 24380501 Jul 24 06:25:00 Tower kernel: repair_io_failure: 7 callbacks suppressed Jul 24 06:25:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702462464 (dev /dev/sdc1 sector 5972256) Jul 24 06:25:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702466560 (dev /dev/sdc1 sector 5972264) Jul 24 06:25:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702470656 (dev /dev/sdc1 sector 5972272) Jul 24 06:25:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 0 off 1031702474752 (dev /dev/sdc1 sector 5972280) Jul 24 06:25:03 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 33750182 off 8265728 csum 0x98f94189 expected csum 0x7ca57398 mirror 2 Jul 24 06:25:03 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 33750182 off 8265728 (dev /dev/sdc1 sector 132894080) Jul 24 06:25:03 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 33750182 off 8503296 csum 0x98f94189 expected csum 0x78909ff8 mirror 2 Jul 24 06:25:03 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 33750182 off 8503296 (dev /dev/sdc1 sector 132894544) Jul 24 06:25:18 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 33750182 off 8282112 csum 0x98f94189 expected csum 0x190b460d mirror 2 Jul 24 06:25:18 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 33750182 off 8282112 (dev /dev/sdc1 sector 132894112) Jul 24 06:26:00 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 29528623 off 39731200 csum 0xb74044e9 expected csum 0xae6e14c9 mirror 2 Jul 24 06:26:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 29528623 off 39731200 (dev /dev/sdc1 sector 92317816) Jul 24 06:28:00 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 29528623 off 26374144 csum 0x98f94189 expected csum 0x42f382f4 mirror 2 Jul 24 06:28:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 29528623 off 26374144 (dev /dev/sdc1 sector 175102552) Jul 24 06:28:00 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 29528623 off 1466368 csum 0x31453955 expected csum 0x0a8d7f8c mirror 2 Jul 24 06:28:00 Tower kernel: BTRFS info (device sdc1): read error corrected: ino 29528623 off 1466368 (dev /dev/sdc1 sector 174960776) how to go about this? thanks tower-diagnostics-20220724-0626.zip Edited July 26, 2022 by iilied Quote Link to comment
Solution JorgeB Posted July 25, 2022 Solution Share Posted July 25, 2022 On 7/24/2022 at 4:31 AM, iilied said: how to go about this? Run a scrub, then check that in the output all errors were corrected. 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.