Unraid Crash + Possible to get diagnostics?

[bobokun]

I woke up this morning and noticed my whole unraid server wasn't responding, I checked the router and although it's connected through ethernet directly to my router it's not even showing up anymore on my router. I can't SSH to it or access unraid GUI/dockers. When I connect through IPMI to see what is going on I see these errors. Is there any way I can still get access to the logs before rebooting the server?

[bobokun]

Even sending it a soft shutdown command has it hanging so I ended up restarting the PC. When I started up the array again after reboot I noticed it was still getting a lot of the messages seen in the original post screenshot. Attached are the diagnostics.

unnas-diagnostics-20180630-0947.zip

[Squid]

They are corruption on your cache drive. Since it's btrfs, best to wait for @johnnie.black. Personally, I'm not a fan of btrfs on a single cache drive unless you have plans to shortly upgrade to a cache pool

Sent via Tapatalk because I'm either at work or enjoying the summer

[JorgeB]

When there's filesystem corruption with btrfs it's best to backup the data, reformat and restore, you can use this if you need help with the backup/restore.

[bobokun]

Thanks. After formatting the drive and restoring I stopped getting the error. However this morning I got an error that my server had call traces. I've attached diagnostics for that 

unnas-diagnostics-20180701-0843.zip

[Squid]

Are you assigning any dedicated IP addresses to a docker container?  There have been reports of when that happens a trace winds up being issued, in which case it can safely be ignored.

[bobokun]

Yes, I do have one dedicated IP address only for the pihole docker container

[JorgeB]

More info about that call trace here: