April 1, 20233 yr Hi, I'm newbie to use unraid, i use unraid with 1x Parity 2x Array disk (4TB). i was build with new array configuration before (because removed ssd from existing array, of course i use unbalance), i haven't got any problem but; now; i see errors on main tab. what should i do for fixing errors? tower-diagnostics-20230401-1532.zip mdstatus.txt Edited April 1, 20233 yr by Shavell added mdstatus
April 1, 20233 yr Author Additionally, root@Tower:/dev# btrfs check -p /dev/md1 Opening filesystem to check... Checking filesystem on /dev/md1 UUID: 904fbb78-8c15-41a6-8d3a-7ec90c032db1 [1/7] checking root items (0:00:07 elapsed, 378497 items checked) [2/7] checking extents (0:00:51 elapsed, 232141 items checked) [3/7] checking free space tree (0:00:00 elapsed, 3111 items checked) [4/7] checking fs roots (0:00:02 elapsed, 7861 items checked) [5/7] checking csums (without verifying data) (0:00:00 elapsed, 296244 items checked) [6/7] checking root refs (0:00:00 elapsed, 3 items checked) [7/7] checking quota groups skipped (not enabled on this FS) found 3336852819968 bytes used, no error found total csum bytes: 3231620568 total tree bytes: 3803250688 total fs tree bytes: 129318912 total extent tree bytes: 30244864 btree space waste bytes: 401565494 file data blocks allocated: 4681315549184 referenced 3331709378560 root@Tower:/dev# btrfs check -p /dev/md2 Opening filesystem to check... Checking filesystem on /dev/md2 UUID: d64bbca3-0e01-4a99-931c-0408c8dcfaaa [1/7] checking root items (0:00:00 elapsed, 8752 items checked) [2/7] checking extents (0:00:01 elapsed, 3719 items checked) [3/7] checking free space tree (0:00:00 elapsed, 52 items checked) [4/7] checking fs roots (0:00:00 elapsed, 304 items checked) [5/7] checking csums (without verifying data) (0:00:00 elapsed, 4779 items checked) [6/7] checking root refs (0:00:00 elapsed, 3 items checked) [7/7] checking quota groups skipped (not enabled on this FS) found 51722932224 bytes used, no error found total csum bytes: 50451316 total tree bytes: 60784640 total fs tree bytes: 4997120 total extent tree bytes: 655360 btree space waste bytes: 5075954 file data blocks allocated: 51662147584 referenced 51662147584
April 1, 20233 yr Community Expert Solution Those are sync errors, and unrelated to the filesystem, you had a 3 device array, then did a new config without the SSD and checked "parity is already valid", that's not true unless the device was cleared before removing, so some sync errors after that are normal.
April 1, 20233 yr Author 2 minutes ago, JorgeB said: Those are sync errors, and unrelated to the filesystem, you had a 3 device array, then did a new config without the SSD and checked "parity is already valid", that's not true unless the device was cleared before removing, so some sync errors after that are normal. what are you recommend to remove disk from array policy for use? may i did wrong attempt? ty.
April 1, 20233 yr Community Expert We usually recommend removing the disk and then re-syncing parity, both options are described here: https://wiki.unraid.net/Shrink_array
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.