So i am not sure where to start with this. I am new to unRAID in general so not sure what info is needed or how to get it. This has happened to me twice in the last 5 days and has me a bit worried for the future. So after gracefully shutting down the Windows 10 VM i have (only VM created), the whole unRAID server becomes unresponsive. I can ping it and that's it. No webinterface, putty, or console. I have to hard power down or reset. When things come back up my cache drive is empty and i need to readd drives to it. I use the cache pool as my location for my VM. Any thoughts on how to get logs out of a unresponsive system?

So i am not sure where to start with this. I am new to unRAID in general so not sure what info is needed or how to get it. This has happened to me twice in the last 5 days and has me a bit worried for the future. So after gracefully shutting down the Windows 10 VM i have (only VM created), the whole unRAID server becomes unresponsive. I can ping it and that's it. No webinterface, putty, or console. I have to hard power down or reset. When things come back up my cache drive is empty and i need to readd drives to it. I use the cache pool as my location for my VM. Any thoughts on how to get logs out of a unresponsive system?

Needing to re-add the drives after reboot was a bug on 6.3.0.  Update to 6.3.1

 

To get logs out of an unresponsive system, install the Fix Common Problems plugin, go to its settings and put it into Troubleshooting Mode

 

After the system is unresponsive, reboot the system, and within the Logs folder there will be a number of dated Diagnostics files and FCPsyslog_tail.txt  Upload the last Diagnostics and the FCPsyslog_tail file here.