paddi.a

Thank you so much. This seems to have solved the issue. Unraid is up and running on ZFS with containers and data restored. I have not had any issues so far when working with files on the pool device. I will report back if any errors occur, but for now this is solved.

Hi Jorge, thank you for taking a look at the files. I was having the feeling it could be filesystem related since it mostly occures when some I/O on the drive (cache in this specific case) happened. I had it 2 times yesterday when downloading kind of a lot zip files and extracting them onto the cache drive. When it crashed today, I was manually extracting a zip file, downloaded yesterday, via the SMB Share. What do you recommend to do, checking if its filesystem related? Also, what are my options if it actually is a fs-issue? The RAM is brand new. Im going to do a Memtest to check if these are faulty. Thanks in Advance!

Hello everyone, I'm pretty new to unraid platform - have been using synology nas devices for years and went to unraid a week ago. Set it up and got it running flawlessly with 2x 12TB HDD; 1TB SSD as a Cache drive on a i5-6500; 32GB Ram. Since yesterday, unraid keeps kind of crashing, leaving the docker services with no response. I just had it crash, when I was unzipping some files on the SMB Share. After the "crash" it is non responsive of the webUI actions. I cannot stop the array, I cannot shutdown the clean way, docker does not show as running neither do VMs. CLI works tho - but I have the same result on the powerdown -r and docker restart stuff - just not beeing executed. Weird thing is: The WebUI shows 2 Cores as 100% utilized. htop does not confirm this tho. The only way I can fix it is to power off the hard way and reboot. Anyone of you had something similar? Im clueless atm what could cause the issue and I'd really like to get it fixed since im running adguard as my home DNS which prevents the household from using the internet since its not responding on DNS Querys. unraid-diagnostics-20240228-1038.zip