Siggz

@GoobarooI've been loving using your ATM9 server but, recently it started crashing a lot more, pretty sure it's on my server end and just need to adjust some BIOS settings to fix it. But, I was wondering if there was a way to add an automatic restart on crash functionality to the server? The docker container usually isn't crashing, just the minecraft server process and I would like it to just restart on minecraft server crash. I've used the extra parameters part of the docker template to do --restart unless-stopped but, it only restarts if the entire docker container crashes. Not completely sure if that is the correct way to do it but, it was something I found.

Yup, it looks like it was RAM setting in the BIOS, cleared CMOS and it started working properly. Though there is a weird issue of 1.10.3 of direwolf 1.18 not installing on the server side, despite it saying it's 1.10.3, it's actually 1.10.2.

Seems to be working now, don't know what changed. I'll let you know if the issue happens again. Edit: Was working fine for about 30 minutes then it died with the same error. hs_err_pid14.log

@Goobaroo Sorry for the late reply, been a hectic few weeks. It seems to still be giving me issues even when starting fresh. I've attached the error log again. I've also updated to the latest version of your docker container. hs_err_pid153.log

I'm using Unraid 6.11.1. Sorry for the late reply. hs_err_pid160.log

Hi Goobaroo, I've tried completely reinstalling the server but I am still getting the following error. Anything else that I can try?

Nevermind, I was able to find the firmware upgrade and it is now working. Though thank you for saying firmware, I wouldn't have thought about updating it/cross-flashing it. https://wiki.unraid.net/Firmware_upgrades V/R Siggz

It does not seem to be. Any guides on how to update the firmware?

Hi, I am having an issue of the array not being able to start due to the names of the hard drives being slightly different after installing the below SAS/SATA Controller. IBM Serveraid M1015 SAS/SATA Controller 46M0831 https://a.co/e2Ibqzj Previously the disks were mounted using the SATA ports on the motherboard while I waited for the controller to arrive. Attached is a picture of the devices not wanting to mount. It looks like the names changed just Is there a way to resolve the issue or do I just need to get a different controller? V/R Siggz

Sorry about that, I've attached a screenshot from my phone of the logs. Don't currently have access to anything else to grab the logs at the moment.

@Goobaroo The plexiglass one seems to be having permission issues, even after giving the folder 755 permissions. V/R Siggz

Hi Goobaroo, The DW20 pack is working great! I was just wondering if you could do the FTB Plexiglass Mountain pack, as I wanted to show minecraft modding to new players but, the DW20 pack is a bit too hard. V/R Siggz

@Goobaroo Thank you, that seems to have fixed the issue.

Hello again, After the fix it worked great for a day but, after shutting down the server to install a UPS, it is now unable to run giving the following logs on attempts to start the docker. I have made sure that run.sh is in the file directory and ran the new permissions command on the appdata folder, so it should have permission. Very sorry to bother you again. V/R Siggz + ID=95 + VER=2132 + cd /data + [[ true = \f\a\l\s\e ]] + echo eula=true + [[ -f serverinstall_95_2132 ]] + [[ -n FTB Presents Direwolf20 1.18 v1.3.1 Server Powered by Docker ]] + sed -i '/motd\s*=/ c motd=FTB Presents Direwolf20 1.18 v1.3.1 Server Powered by Docker' /data/server.properties + [[ -n world ]] + sed -i '/level-name\s*=/ c level-name=world' /data/server.properties + [[ -n rsmrules05 ]] + echo rsmrules05 + awk -v RS=, '{print}' + [[ -f run.sh ]] + [[ -f user_jvm_args.txt ]] + echo -Xms4096m -Xmx6144m + [[ -f run.sh ]] + ./run.sh /launch.sh: line 38: ./run.sh: Permission denied + ./start.sh /launch.sh: line 38: ./start.sh: No such file or directory ** Press ANY KEY to close this window **

Hello good sir, I appear to be having an issue of the docker not being able to find/open/create server.properties and the forge jar, I have tried a few things such as making sure the permissions are set correctly as well as giving the folder 777 privileges temporarily in order to try installing. I have also tried adding the files in manually as well and then giving the 777 privilege to the files/folders again. I have also tried uninstalling and reinstalling the docker, I was wondering if there is anything else that I can try, I am also a noob to unraid currently. V/R Siggz + [[ -n FTB Presents Direwolf20 1.18 v1.3.1 Server Powered by Docker ]] + sed -i '/motd\s*=/ c motd=FTB Presents Direwolf20 1.18 v1.3.1 Server Powered by Docker' /data/server.properties + [[ -n world ]] + sed -i '/level-name\s*=/ c level-name=world' /data/server.properties + [[ -n rsmrules05 ]] + awk -v RS=, '{print}' + echo rsmrules05 + [[ -f run.sh ]] ++ ls 'forge-*.jar' ls: cannot access 'forge-*.jar': No such file or directory + FORGE_JAR= + curl -Lo log4j2_112-116.xml https://launcher.mojang.com/v1/objects/02937d122c86ce73319ef9975b58896fc1b491d1/log4j2_112-116.xml % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1131 100 1131 0 0 12428 0 --:--:-- --:--:-- --:--:-- 12428 + java -server -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions -Dfml.queryResult=confirm -Dlog4j.configurationFile=log4j2_112-116.xml -Xms4096m -Xmx6144m -jar nogui Error: Unable to access jarfile nogui ** Press ANY KEY to close this window **