SkinnyV

I had a lot of issues like this, my advice might not be the best, but downgrading to 6.11.5 solved all my issues.

For the time that you are trying to diagnose this, writing the syslog to flash would be most likely an easier and better option than messing around with the syslog server. Plus, if the server start crashing, you might not get everything logged if it is affecting your share and that is where the logs get saved.

I’m willing to bet you started having these issues around the time you upgraded to unraid 12. If you search a bit, You’ll see many peoples seem to be experiencing these weird crash or server becoming unresponsive issues. I reverted to 11 for a while and it was rock solid again. Then I updated again to one of the newer 12.x build and started getting them again. At first it was supposed to be caused by docker’s networks settings, then it seem nobody knew whats causing theses things and the blame got shifted to mysterious hardwares issues or incompatibility that can’t really be verified. How can AMD suddenly not be recommended? I have been using AMD hardwares for years with unraid prior to these issues starting and seldomly ever had issue or crash that weren’t caused by a bad hard drive or something like that. It then started with the first time I upgraded to 12 within the firt 2 or 3 days. I personnaly will be moving back to 11 in the next few days as it doesn’t seem like this is going to be addressed.

I have replaced the cache hdd that was giving the error and replaced the power supply with a stronger one. I still get random crashes triggering regular parity check. I had another of these crash this morning between 8h45 and 9h15 am. Adding new logs, hopefully, someone can help out otherwise I will have to revert to unraid 11 and live with some plugin that no longer can be installed on that version. Thanks! unraid_crash.txt

Nothing else that could have to do with the random unaccessible web gui and crash?

Ever since I upgraded to 12.x, I get random intermittent crash. I reverted back to the last 11.x for a while and the server was very stable again. Then upgraded to 12.1.8 when I read about some crash issue being resolved but started getting crash again. I then went to 12.1.4 and it seemed to be ok but it still crashed, although less often. Hoping to have someone help me figure out the log before reverting back again to the last 11.x version. I did switch the network type to ipvlan like some post mentioned but same issue persist. I would like to avoid going back to the old version since some plugins now refuse to install unless you are on 12, but at this point I keep having the server becoming unaccessible randomly, not reboot properly and spend so much time with it redoing parity check. Attached is the syslog from the last 2 days and it crashed on the 25th sometime during the end of the day. Thank you syslog_24-25.txt

I had these kind of issues eversince upgrading to 12.x. I reverted back to the last 11 version and was stable again. Then upgraded again after reading reports that crash issues were resolved, but still have them. Now thinking of going back again as there really seem to be something off with 12.x.

Thanks for checking and for your suggestion, I tried it on a different power cable and its been rebuilding for a while without error until now. Would you think that power supply issue could cause this? My PSU should be able to handle my system, but I am wondering if I didn't overload one of its power lane by being forced to use power connector duplicator because of how few connector my PSU offer. Would you think that it could cause that kind of issues?

I have been having issue with my unraid server's gui suddenly becoming unaccessable lately. Last time it did that, I had to force shut down but the parity check stopped after a while due to error on one of my newer drive. I tried to rebuild the drive but it stop pretty quickly due to error, I did a quick smart test and it seem to have passed. Anyone could help me out figure out the issue with the diagnostics? The drive in question is pretty new so I am confused why it would give issue like this. Thank you! unraid-diagnostics-20230812-1050.zip

Yes, I saw your reply, thank you. But I would still prefer for the array not to auto-start after a disabled drive so I don’t keep using the array without noticing.

I understand, thank you for the explanation.

But what if the array is not auto-started if a disk is found missing/disabled? Wouldn’t the disabled disk still be in sync and could be re-enabled without a rebuild?

+1 for me. I had a drive that got disabled and I was trying to find a way to re-enable it without rebuilding. You are supposed to do that if nothing new was changed while hdd was in emulated mode and the array get re-starting at every reboot and tvwas frustrating not to be able to set it so it wouldn’t start with a missing drive.

I had to play inside my server this month and it happened twice that a cable got loose and one of my hdd got disabled by Unraid. I was surprised to find out that there is no straightforward way to re-enable a drive when you know it is good. I had to rebuild twice and it take ages. I found some way to do it while searching but it involved playing with reconfiguring the array and it was a bit scary to do. It would be nice to have an easily accessible way of re-enabling a disabled hdd straight from the GUI. Thanks!

+1 for me. One of the first thing I was looking for when I bought unraid and I was migrating data from others hard drive. I’m used to the file browser of QNAP and I am really missing the option. The current workaround of using docker is really clunky for me.