February 4, 20242 yr Hello, my cache drive seems to be corrupted out of nowhere. File system was btrfs. I tried running some commands that I found in another thread but I only got this as a response. Image of the drive: I have attached my diagnostics. Is the issue fixable without any data loss? Tower Diagnostics 20240204 2135.zip
February 5, 20242 yr Community Expert Solution It does have an issue with the log tree, but the command you used in not correct, try: btrfs rescue zero-log /dev/nvme0n1p1 Then re-start the array
April 22, 20242 yr THANK YOU!!! You saved my bacon as well, back in business now! (I had to do it on both of the nvme drives for anyone else wondering, since there were in a pool) Edited April 22, 20242 yr by abbzer0 screenshot
April 23, 20242 yr Community Expert 12 hours ago, abbzer0 said: (I had to do it on both of the nvme drives for anyone else wondering, since there were in a pool For the future, you just need to run the command in one of the pool devices, since it's the same filesystem.
May 10, 20242 yr Hello. Im having the exact same situation, and on the command btrfs rescue zero-log /dev/nvme0n1p1 i get this output root@Tower:~# btrfs rescue zero-log /dev/nvme0n1p1 Clearing log on /dev/nvme0n1p1, previous log_root 824766611456, level 0 ERROR: failed to write super block for devid 1: flush error: No data available ERROR: failed to write dev supers: No data available WARNING: fsync on device 1 failed: No data available Edited May 10, 20242 yr by neighboring-ferryman2976
May 10, 20242 yr Community Expert Please post the diagnostics, jut because it's unmountable, it doesn't mean it's the same issue.
May 10, 20242 yr Sure here it is! 7 hours ago, JorgeB said: Please post the diagnostics, jut because it's unmountable, it doesn't mean it's the same issue. tower-diagnostics-20240510-2043.zip
May 10, 20242 yr Community Expert 7 minutes ago, neighboring-ferryman2976 said: Sure here it is! The NVMe device failed and needs to be replaced: SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode If you don't have a backup see below for mounting the pool read-only, that may allow you to copy the data: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
May 11, 20242 yr 14 hours ago, JorgeB said: The NVMe device failed and needs to be replaced: SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode If you don't have a backup see below for mounting the pool read-only, that may allow you to copy the data: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 Thanks for the investigation. I would never thought that was the failed SSD, it has been less than a year installed, and it's a Samsung, and no real hard work for it has been seen. I've gone through some steps but didn't succeed, here is my Terminal LOG. Update: I've specified the wrong disk. I got a list of all btrfs drives by command: btrfs fi show and the correct command was btrfs restore -vi /dev/nvme0n1p1 /mnt/disk2/restore It was p1 that i was missing. Restore in process, i get some errors like is it normal? it is because of failed disk sectors? Can i try to repair it BTRFS check --repair (dangerous to use)? Or it will be in failed SMART mode forever? What are my option to get the Unraid working as before? i ordered a new nvme drive. Add it to the pool cache, copy files i recovered and its good to go? or its more complex issue Quote ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/3e/309d8568c418f32bd70852f96ab1a50b026b5fc742b0f14fd194754a81594f.file failed Error reading 762662383616, -1 ERROR: exhausted mirrors trying to read (2 > 1) ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/6f/839f60e0cf76fd7b9c48196d24a77762170917f9bf7e80cc32d73197d5b054.file failed Error reading 762662199296, -1 ERROR: exhausted mirrors trying to read (2 > 1) ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/0b/b19bcfdab08b21c18de938a7341012dbf6904251fa967cdd471a1474c19d49.file failed Error reading 764996014080, -1 ERROR: exhausted mirrors trying to read (2 > 1) ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/0b/4995c53318bba287759b2903529419933576a3d0bc3fc1b91b9881e7e01185.dirtree failed Short read for 762677981184, read 118784, read_len 208896 ERROR: exhausted mirrors trying to read (2 > 1) ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/a5/d84512a055f1934fb7b803566446ec11dd5a7129988e6a85152dcd89d382df.file failed Error reading 762671841280, -1 ERROR: exhausted mirrors trying to read (2 > 1) ERROR: copying data for /mnt/disk2/restore/appdata/steam-headless/.local/share/flatpak/repo/objects/7b/60afa6cf2410d186e64baa5a616784386e298ba3aed6e20aa93fd825d681b6.file failed Edited May 11, 20242 yr by neighboring-ferryman2976
May 11, 20242 yr Community Expert Did you try the mount read only option? That would be the best one option if it works.
May 11, 20242 yr 5 hours ago, JorgeB said: Did you try the mount read only option? That would be the best one option if it works. sorry, no, i got errors on first steps due to p1, and completed only the last. Yes it mounted, and i copied all the data. Thank you! What are my moves when i get new nvme drive. I eject the old one, insert the new one i add it as cache disk and copy all the files. my all dockers should start as usual?
May 12, 20242 yr Community Expert 14 hours ago, neighboring-ferryman2976 said: I eject the old one, insert the new one i add it as cache disk and copy all the files. my all dockers should start as usual? Basically yes, also note that the docker image can easily be recreated if there's a problem with the old one. https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
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.