xyseer

However, this parity is so sucks and I'm not considering use this raw backup method again. It's so unreliable! Unraid is so that worse than Raid! I trusted in Unraid so much and it treated my data like that inversely.

OK, Thanks for your answer and solutions. I'll try ddrescue to bring data.

So, you mean that if 'btrfs restore' cannot bring the files back, then all my data will be lost? (Since I've tried restore yesterday however it cannot restore anything. Even using btrfs-find-root together with btrfs restore in order to manually recover some data has failed😭)

Here's the diagnostics from my Unraid xynas-diagnostics-20230831-1023.zip

The disk1 reported below when check status of btrfs: Couldn't read tree root Could not open root, trying backup super parent transid verify failed on 240418816 wanted 33573 found 33543 parent transid verify failed on 240418816 wanted 33573 found 33543 parent transid verify failed on 240418816 wanted 33573 found 33543 Ignoring transid failure ERROR: root [1 0] level 2 does not match 0

I have only one parity and 2 disks in my system. Recently one of my disk(disk1) had read errors and the system disabled that disk. I have no choice but to replace that bad disk with a new one. As many topics have said. Just replace disk in the array slot and the system will automatically rebuild data with out any other procedures. While tragedy happened here. When the rebuilding finished. A notice that "Unmountable: no or wrong filesystem." was on the disk. While I used the btrfs in the former disk so I tried to run "btrfs check" to see whether there was a filesystem error. Unfortunately, the tools shows that "cannot read chunk-tree". I tried lots of things including btrfs rescue but nothing happened. It was stiil unmountable. Is there any way to bring my data back? There was no valuable logs since I've reboot systems for lots of times.