CellDweller Posted July 13, 2023 Share Posted July 13, 2023 (edited) After some years of stable unraid usage i ran into trouble last week. Some docker containers stopped responding and were acting weird. Did check to log and saw the cache ssd was giving errors. In this configuration i had a Samsung 850 Evo as cache drive on btrfs After this i turned the server down, reconnected the sata cable and did try again. Unraid was giving no smart errors so i thought lets give it a try. I got the same errors, turned the system down, did place the sata cable in another port and turned it on with one last try. Disk was seen but could not even be mounted anymore... I went ahead and put the ssd in my computer to took a look at this with the Samsung Magician Software and Hard Disk Sentinel. Samsung Magician was saying the drive was "good", Hard Disk Sentinel however told me it was acceptable. Seeing how this drive got a 150TBW in it's official specs and had written +288TB i decided to replace the disk at once with a Crucial MX500 (and even bought 2 to place them in raid 1) I used "Macrium Reflect 8" on windows to clone the old Samsung SSD to a new Crucial, and started to work with this. This drive is also un-mountable, but i am hoping to learn something by trying to recover the data. Also some of the appdata i did not backup recently (stupid, i know), and i was wondering if i could recover this. The old SSD is not completely dead, so i have some hope. However, did some digging and trying, but i am stuck at this moment and could use some advice. I included some stuff i did try beneath. root@Tower:/dev# btrfs check --readonly --force sdf1 Opening filesystem to check... checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root ERROR: cannot open file system root@Tower:/dev# btrfs-find-root sdf1 WARNING: cannot read chunk root, continue anyway Superblock thinks the generation is 36640635 Superblock thinks the level is 1 root@Tower:/dev# btrfs rescue super-recover -v sdf1 All Devices: Device: id = 1, name = sdf1 Before Recovering: [All good supers]: device name = sdf1 superblock bytenr = 65536 device name = sdf1 superblock bytenr = 67108864 device name = sdf1 superblock bytenr = 274877906944 [All bad supers]: All supers are valid, no need to recover root@Tower:/dev# btrfs rescue chunk-recover sdf1 Scanning: DONE in dev0 corrupt node: root=1 block=1128005632 slot=0, corrupt node: root=1 block=1128005632, nritems too large, have 12 expect range [1,0] Couldn't read tree root open with broken chunk error root@Tower:/# btrfs restore --dry-run -d /dev/sdf1 /home checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 checksum verify failed on 2169503744 wanted 0x00000000 found 0xb6bde3e4 bad tree block 2169503744, bytenr mismatch, want=2169503744, have=0 ERROR: cannot read chunk root Could not open root, trying backup super Is this a totally lost cause, or is there some hope here? Many thanks in advance! tower-diagnostics-20230713-2006.zip Edited July 13, 2023 by CellDweller Quote Link to comment
JorgeB Posted July 14, 2023 Share Posted July 14, 2023 That doesn't look recoverable to me, extent tree is missing data for both metadata copies. Quote Link to comment
CellDweller Posted July 18, 2023 Author Share Posted July 18, 2023 After some more searching and trying i did give up, bit disappointing but it is what it is. Did go for ZFS in mirror with the 2 MX500 ssd's, and setup my backups better this time. Thanks @JorgeB for your answer 1 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.