SideSh0wWilly

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SideSh0wWilly's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. I encountered this same issue after adding cache drives (pool of 2). I had to set the filesystem type on the primary drive to auto and then start the array. After that I had to format both drives as they still showed unmountable.
  2. Removed the runtime folder and it can't find it. I think that it is downloading the jre16 runtime and not the jdk. Doesn't appear to be a container issue but a mod pack dependency issue. Thanks for the help on this one. loving the repository. Edit: I know its a java issue... [16:26:46] [ERROR] Error while starting the server java.io.IOException: Cannot run program "java" (in directory "."): error=2, No such file or directory at java.base/java.lang.ProcessBuilder.start(Unknown Source) at java.base/java.lang.ProcessBuilder.start(Unknown Source) at atm.bloodworkxgaming.serverstarter.LoaderManager.startAndWaitForProcess(LoaderManager.kt:257) at atm.bloodworkxgaming.serverstarter.LoaderManager.startServer(LoaderManager.kt:240) at atm.bloodworkxgaming.serverstarter.LoaderManager.handleServer(LoaderManager.kt:43) at atm.bloodworkxgaming.serverstarter.ServerStarter.startLoading(ServerStarter.kt:190) at atm.bloodworkxgaming.serverstarter.ServerStarterKt.main(ServerStarter.kt:202) Caused by: java.io.IOException: error=2, No such file or directory at java.base/java.lang.ProcessImpl.forkAndExec(Native Method) at java.base/java.lang.ProcessImpl.<init>(Unknown Source) at java.base/java.lang.ProcessImpl.start(Unknown Source) If I figure a way to put the jdk in the runtime folder I will post back here with it.
  3. I believe with the 1.17 servers it needs the new JDK 16 not the JRE. It does run on windows now that the JDK is installed. I was reading on the runtime, but couldn't find anything on replacing what's in the container.
  4. Minecraft Basic Server Docker container continues to terminate on modpack installation. Container creation: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='MinecraftBasicServer' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'JAR_NAME'='serverstarter-2.0.1' -e 'GAME_V'='custom' -e 'GAME_PARAMS'='' -e 'EXTRA_JVM_PARAMS'='' -e 'XMS_SIZE'='4096' -e 'XMX_SIZE'='4096' -e 'ACCEPT_EULA'='true' -e 'RUNTIME_NAME'='jre16' -e 'UID'='99' -e 'GID'='100' -p '25565:25565/tcp' -p '25575:25575/tcp' -p '9011:8080/tcp' -v '/mnt/disk1/appdata/minecraft':'/serverdata/serverfiles':'rw' --restart=unless-stopped 'ich777/minecraftbasicserver' e53f6ae1f2824f0f24ca870dff83a2d88fc5d083492de8fff7e8fbc3f4a61b37 Set the jar file correctly and the version to custom. It starts and then terminates almost immediately. I can't tell if its the mod pack or the container settings killing the server. mcdocker.log
  5. To everyone that worked on this, Thank you. All drives are up and functioning as expected. Appreciate the hard work put into this to get those of us on the older hardware back in business.
  6. I can confirm that the NetApp PM80xx series cards do not work with the 0.1.40 driver on version 6.9 and above. I have just setup a new system with a DS4243 and the NetApp card. Could not see the drives at all. As soon as I downgraded to 6.8.3 all is back and visible.