Rudde

I'm also experiencing this exact issues, also on new MB, RAM, CPU, and USB. I made this thread about it: Did you ever fix this?

Now it crashed again, but it is not responsive, it's on and display the error, but I can't connect to it with SSH or access the WebUI to get another diagnostics. While this error is not one of the those I've have managed to screenshot, it is an error I've gotten before, it's "nf_nat_setup_info" this happen after I started to stress-test my rTorrent docker, as I have suspected it's related to docker in some way. I started adding a few torrents, one after another and it very quickly crashed. I tried to move things away from the SSD when I got this error message last time because I didn't want the SSD to be involved with the docker instances as I was afraid it had depleted sectors, so I moved the data to make sure that wasn't whats wrong.

Yes. Here is a completely fresh one I took just now, after a fresh boot, after having not turned it on since the last crash. No errors have yet occurred on monitor during this boot prior to taking the diagostics. I will let it run, and see if an error occur on screen, and take another one before it become completely useless and I have to hard-rest it. tower-diagnostics-20190531-0916.zip

There was no errors in it, it was the standard output. These issues also occurred way before that error popped up, also feel like this is the most irrelevant error to the symptoms experienced. Why would a completely corrupt storage-disk even crash unRAID?

I've managed to run xfs_repair on the device in question. It have had absolutely on effect on any of the issues described in this thread. I have no idea what to do next. Is there anything indicating anything wrong in the diagnostics files?

The memtest was done in the same time area. The server hasn't really been used since the diagnosis because of the problems descibed here being a prior for a long time prior to it. Okey. Thanks. Do they count from Disk 1 -> md1, Disk 2 -> md2 and such? Where does cache and parity 1 and 2 land in this scheme?

I've added the diagnostic dump to my OP. I've rebooted it now, but my trail has expired among with my two extensions and I can't access the WebUI anymore. And it doesn't seem like /dev/md3 exist either. I suspect this is what unraid have named their pool, and that it's not a reference to one of my disks. I have ran parity check several times where it completed without any issues.

Hello! I've decided I wanted to try unRAID for a new NAS build, so I've installed it and had in running for a few months. But I'm experiencing severe issues where I can't consider this build complete. I randomly get errors and it wasn't as bad in the beginning, but I never really hammered the NAS very much. I get a whole bunch of different errors. Attached you see some of the ones I've screenshotted from my BNC. I have obtained a diagnostic dump after I've confirmed one error got on the screen but didn't make the unraid unresponsive yet. But it always happens. I also suspect it can be related to docker, which I currently only run a rtorrent docker, I've attempted to heavily limit the number of files it allowed to keep open at once and limited it's ability to create connection, but it had no effect on unraid just crashing completely. I've kept my server in a good state longer if I don't start any dockers, and when I start rtorrent. The problems always start occurring within two days or so with uptime. I've rand memtest86 on my hardware to check it, but it's found nothing. tower-diagnostics-20190506-2015.zip