ItsNotNick

If it's not too much to ask could I recommend/request Pixelmon? I use your SF3 server a few times a week and it's given me the least grief by far.

Okay, so I had this server running for a few days with a couple game settings changes. Then I go to change a couple other game settings and reboot, like I've done before and the server crashes. I reverted the changes I can remember, but it's still doing this. When I first setup the server, it was doing this, so I just removed the docker and reinstalled and that seemed to work. I don't know which of these files are required...so you can have them all. configstore_log.txt connection_log.txt connection_log_9876.txt service_log.txt stats_log.txt systemmanager.txt VRisingServer.log

So, after some time, I went from connecting every drive directly to the motherboard to using an HBA Card. And after doing that my parity check went from 17 errors to 16. My system hasn't crashed at all, which is good (?), although I don't know what I did exactly to fix that. I have 2 questions: 1: Does the decrease in parity checks (assuming it's not a fluke) suggest it's the cables? Since I did reconnect every single cable once, at least. 2: Is 16 parity checks a real issue or am I overreacting and it is something I could just ignore?

I am planning to switch motherboard out for one with a couple more PCIe slots, I could do that now, but I feel like it would be better not to change too much at once. Also worth mentioning that this only happens when running a parity check, I ran the server all week without a single crash, then turned on parity only for it to crash within a couple hours like I said.

Ok, after dealing with some other things I finally was able to start another parity check syslogand it crashed about an hour and a half in. After looking at the file I can see that there is data from after the crash, so I feel I should mention that I restarted the server before remembering about the syslog. Sorry if that make it harder.

Oh, I'm stupid. So it didn't log to the folder I set it to. I started another parity check and set it to log to flash, so I should get one soon. My bad.

My server has crashed 3 times now, increasing in frequency each time. I thought the issue may have been a couple new drives I added for parity, as they've put out parity errors while doing the latest check. I removed one of them and started a parity check only for it to crash in about an hour. I did some due diligence and enabled syslog (although it's not allowing me to upload them here for some reason) So here's a link to it. Also, I have no idea if it's related or just a random occurrence, but, my docker.img tripled in size randomly, so I had to go through that whole process of fixing it. Idk if that's helpful, just thought I'd mention it in case it was.

So, I'm most familiar with windows, so I used file explorer to move the world into saves. Which is the exact thing I did with your Satisfactory docker. Here is what I changed: These are the only things I changed with this entire server. And when I just deleted everything to start anew, I only changed the server name after the first boot/connect and both my friends and I were able to connect both times. But once I did what is in the first picture, it stops working, everytime. Here is what the save file is called: And here is what the name of the folder inside of 'Kubixe County' is named:

So, just to preface, I think I might just be stupid. This is for a 7D2D server. Every time I try and change the server config to use a save that I started a couple days prior to using a dedicated server it doesn't work. Sometimes it will enter a sort of update loop, but most of the time it will show that everything is fine and should be functioning, but I'm unable to connect to the server. I just don't know what I'm doing wrong. To make things worse, I'm brand new to Unraid and really don't know what I'm doing.