BTRFS filesys unmounted

My Rockstor setup has been giving me ctree errors

btrfs check gives me
BTRfs check errors found in extent allocation tree

would my best options to be perform a btrfs restore to a new disk, if so does that disk need to be BTRFS as well?

or should i try a repair or both? thoughts?

[root@host ~]# btrfs check --readonly /dev/sdd
Opening filesystem to check…
Checking filesystem on /dev/sdd
UUID: cad74c1c-dee1-470a-9b29-c66e3b02a54f
[1/7] checking root items
[2/7] checking extents
leaf parent key incorrect 11905083211776
bad block 11905083211776
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6400691458048-6400691466240 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6400691470336-6400892633088 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6400892665856-6401102372864 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401102381056-6401252388864 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401252397056-6401252446208 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401252450304-6401336623104 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401336659968-6401336668160 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401336672256-6401397280768 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401397293056-6401461456896 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401461477376-6401461510144 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401461514240-6401544380416 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401544413184-6401659756544 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401659764736-6401710186496 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401710190592-6401710215168 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401710219264-6401794052096 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401794056192-6401794109440 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401794113536-6401919492096 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401919496192-6401919610880 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6401919614976-6402020196352 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402020200448-6402121461760 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402121465856-6402194391040 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402194395136-6402194468864 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402194472960-6402194534400 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402194538496-6402229907456 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402229911552-6402265591808 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402265595904-6402265636864 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402265640960-6402409107456 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402409111552-6402455277568 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402455289856-6402455302144 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402455330816-6402455347200 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402455351296-6402502856704 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402502877184-6402538266624 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402538270720-6402574561280 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402574569472-6402574630912 but there is no extent record
leaf parent key incorrect 11905083211776
Error looking up extent record -1
csum exists for 6402574647296-6402610356224 but there is no extent record
ERROR: errors found in csum tree
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 5267514257408 bytes used, error(s) found
total csum bytes: 0
total tree bytes: 62521344
total fs tree bytes: 0
total extent tree bytes: 61734912
btree space waste bytes: 16604435
file data blocks allocated: 1437335552
referenced 1437335552
[root@host ~]# btrfs fi show
Label: ‘rockstor_rockstor’ uuid: 2e34fb77-7712-4356-9582-1cc853a2b830
Total devices 1 FS bytes used 9.15GiB
devid 1 size 66.59GiB used 38.05GiB path /dev/sdh3

Label: ‘externalwork’ uuid: c29e2829-cde6-4ce5-9920-56edf398b908
Total devices 1 FS bytes used 5.12GiB
devid 1 size 465.76GiB used 13.02GiB path /dev/sdg

Label: ‘Primary’ uuid: cad74c1c-dee1-470a-9b29-c66e3b02a54f
Total devices 6 FS bytes used 5.30TiB
devid 1 size 1.82TiB used 1.08TiB path /dev/sdd
devid 2 size 1.82TiB used 1.08TiB path /dev/sde
devid 3 size 1.82TiB used 1.08TiB path /dev/sdf
devid 4 size 1.82TiB used 1.08TiB path /dev/sda
devid 5 size 1.82TiB used 1.08TiB path /dev/sdc
devid 6 size 1.82TiB used 1.08TiB path /dev/sdb

So i have completed all steps on https://en.opensuse.org/SDB:BTRFS except for btrfs check --repair /dev/sda1 with no luck, (data is currently dumping to backups before i do that)

I got it to mount for a bit after btrfs rescue zero-log /dev/sda1 but scrubs just aborted and eventually it went back to being unmounted

At this point however i’m just not sure if i should just blow the data away and start doing indepth disk/mem testing. and then rebuild or just run the repair, since i’m not sure what would of caused the extent record errors