[Help] F4-424 Max: Volume 1 / Volume Corrupted [SOLVED]

[cassio]

Hello,

Mind to extend some help? I do have a F4 424Max with dual disks of 12TB and 2xnvme as cache - using a BTRFS volume. Since a reboot, the volume 1 shows as corrupted. smartctl and dmesg dont shows any errors, I dont miss any files, and dont see any errors at mdadm. I dont want to format/backup everything, because it just doesnt make any sense to reformat a unit with 7 months of usage - and still trusting on the platform

What am I missing? Any clues?

Thanks!

[cassio]

[TMbuddy]

Hello! You may attempt filesystem repair by following this guide: [Insert Article Link]. Alternatively, contact our Live Chat support on the official website to schedule remote assistance with a technical engineer.
viewtopic.php?t=2575

[cassio]

Hello! You may attempt filesystem repair by following this guide: [Insert Article Link]. Alternatively, contact our Live Chat support on the official website to schedule remote assistance with a technical engineer.
viewtopic.php?t=2575

Hello... thanks for the answer. Thats my initial idea - but with dmesg returining clean, I'm not sure if really theres a problem with Volume1 at all. It works perfectly. Looks like the Interface is buggy and missing a "push" to get the properties that the web code requires to show all good.
Support is a good idea. Hard to believe that a new system does have this kind of issue. Shameful.

[TMtina]

Hello! You may attempt filesystem repair by following this guide: [Insert Article Link]. Alternatively, contact our Live Chat support on the official website to schedule remote assistance with a technical engineer.
viewtopic.php?t=2575

Hello... thanks for the answer. Thats my initial idea - but with dmesg returining clean, I'm not sure if really theres a problem with Volume1 at all. It works perfectly. Looks like the Interface is buggy and missing a "push" to get the properties that the web code requires to show all good.
Support is a good idea. Hard to believe that a new system does have this kind of issue. Shameful.

Hello! To resolve this issue more efficiently, we recommend contacting our official online support. Our engineers can schedule a remote session to thoroughly inspect your system configuration and identify the root cause. Thank you for your cooperation!

[cassio]

Just to close the topic correctly, a full reinstall of the TOS fixed the issue.