jotube Posted June 26, 2023 Share Posted June 26, 2023 hi community, this is my first post here so bear with me if I do anything wrong after updating to 6.12, I noticed that some of my Docker containers that were running on my cache (SSD) stopped working. After rebooting the server and starting the array, the cache now shows as "Unmountable: Unsupported or no file system". I have also backed up the flash but still get the message. It should be noted that I had set the setting for "appdata" to "Prefer", so of course the affected containers are not started. Now I'm wondering what happened here and how I can recover my data. zima-diagnostics-20230626-0702.zip Quote Link to comment
Solution JorgeB Posted June 26, 2023 Solution Share Posted June 26, 2023 If the only issue is the log tree this may help, don't stop the array and type: btrfs rescue zero-log /dev/mapper/sdb1 Then re-start array and post new dags 1 Quote Link to comment
jotube Posted June 26, 2023 Author Share Posted June 26, 2023 you are the best! it is running again. but here are the diag again. zima-diagnostics-20230626-1939.zip 1 Quote Link to comment
JorgeB Posted June 26, 2023 Share Posted June 26, 2023 Looks good so far, take the opportunity to update your backups if needed. Quote Link to comment
jotube Posted June 27, 2023 Author Share Posted June 27, 2023 On 6/26/2023 at 7:48 PM, JorgeB said: Looks good so far, take the opportunity to update your backups if needed. I am currently creating backups of the cache, using the mover. However, it has already been more than 10 hours for 30 GB. Before that, I set all folders in the share to "yes". As a test, I tried copying a folder from the cache to an unassigned device using "sudo MC". At the same time, I checked the logs and received the following message: Jun 27 21:35:26 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:26 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: verify_parent_transid: 11671 callbacks suppressed Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:31 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:36 Zima kernel: verify_parent_transid: 11810 callbacks suppressed Jun 27 21:35:36 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Jun 27 21:35:36 Zima kernel: BTRFS error (device dm-1: state EA): parent transid verify failed on 1471459033088 wanted 96486 found 95971 Does this mean that my hard drive is broken or just the format? thanks in advance. zima-diagnostics-20230627-2133.zip Quote Link to comment
trurl Posted June 27, 2023 Share Posted June 27, 2023 Not related to your btrfs errors, but why do you have Docker enabled in Settings if you're not ready to run it yet? Quote Link to comment
JorgeB Posted June 28, 2023 Share Posted June 28, 2023 11 hours ago, jotube said: wanted 96486 found 95971 This means some writes were lost, usually due to a bad firmware/controller, you will need to backup what you can and re-format the pool. Quote Link to comment
jotube Posted June 30, 2023 Author Share Posted June 30, 2023 Ok thanks. I have already imported an old backup but will be a lesson to me. I will run backups more often. Thanks for the quick answers! 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.