bobbiewang

That's great! Thank you very much.

Excuse me, it's not a correcting scrub. I'm not sure whether there is a chance to damage data if "Repair corrupted blocks" is checked. So, I did scrub only before backup. I just finished data backup, and did a scrub with "Repair corrupted blocks" checked. Below is the result. Is my cache disk fine now? Shall I format the disk (sdf) to avoid the issue in future? Thanks.

Thank you, JorgeB. I ran scrub on cache disk and results was shown in page as following. I stopped and started Array for the 3rd time. Now, I'm able to start VM and Docker, but I'm not sure whether cache disk is fine or not...

JorgeB, appreciate your help. I searched "drop" in log files, but didn't get any useful information. Could you please let me know lines indicate devices dropped offline? I hope to analyze by myself in future. If I click cache disk to see details, I can see current "btrfs scrub status" is as following. Shall I manually run scrub with "Repair corrupted blocks" checked? Thanks.

I'm using Unraid 6.11.5. Currently, I'm able to start Array and enable VM/Docker services in Setting page. However, I'm NOT able to start any VM or Docker instances. It looks like something wrong with my cache disk, but I don't know how to analyze diagnostics logs. Could anyone help to read attached diagnostics log files, or tell me commands to check Btrfs? BTW, I'm using 2 Crucial MX500 1 TB SATA SSD disks as cache pool, and my NAS is HP Microserver Gen8. This is not the 1st time that I ran into issue. Last time, I reboot my NAS and the issue was gone (not same issue I think), but reboot doesn't work this time. Is there any known hardware compatibility issue with Unraid? Thank you in advance. tower-diagnostics-20230705-2311.zip