Walker843

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Walker843

  1. Ok, I followed the instructions in the link and deleted the /mnt/cache/system/docker folder. I changed the option to docker.img and found that I was unable to start the docker service after that, which was not totally unexpected given that I had just deleted the entire folder. After a reboot, the docker service started and I was able to reinstall all of my containers. I am back to using a docker.img, and everything appears to be running great! Thank you for the help, @JorgeB!
  2. So it's ok to have Unraid completely remove /mnt/cache/system/docker and all the various folders that are in it?
  3. Hello, Quite some time ago, I switched from using docker.img to docker folders. Over time, the directory has gotten to be quite large and I assume this to be remnants of the many containers I've installed, tried out, and removed over that period. I'd like to just nuke it and start over, going back to docker.img but I'm not sure what's safe to delete. When I switched to folders, in Docker settings I used the folder /mnt/cache/system/docker instead of the /mnt/user/system/docker/docker that Unraid defaulted to. There are a lot of other directories in the docker folder and I'm not sure it's safe for me to just delete the entire /mnt/cache/system/docker folder using the delete folder option in Docker settings. Folder names like btrfs, network, trust, unraid, volumes, all sound like things that should not be removed. Can I completely remove /mnt/cache/system/docker, or would that be a really bad idea? If it is a bad idea, which folders in there should I remove to completely wipe out the docker folder structure so I can go back to using docker.img? Thanks!
  4. Ok, sounds good! I'll go ahead and set Fix Common Problems to ignore. I also noticed it had an MCE that has come up in other forum threads a few times and the general consensus is that it too can be safely ignored: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Thank you for taking a look, much appreciated!
  5. Hello, My server crashed at about 16:35 yesterday, and when it came back up the fix common problem plugin reported I had a machine check error event. I would appreciate help in finding out what caused it as I assumed whatever it was is the same problem that caused the server to crash. I've attached my diagnostics, and I also have the syslog if that would be helpful. The crash also caused a parity check, which is expected, and several of my docker containers became corrupted and had to be reinstalled. Still working through that part as the parity check continues for about another day yet. Thank you for any help! punisher-diagnostics-20221120-0957.zip
  6. It's been awhile since I did a forge 1.18 server, I've since switched to paper. If I recall correctly you set the jar file like normal, and basically put the contents of the run.bat or run.sh file into the "Additional Java arguments" box. So you'd paste the part that looks similar to "@user_jvm_args.txt @libraries/net/minecraftforge/forge/1.18.1-39.0.85/unix_args.txt" into it. I don't know if it's necessary, but I would also copy the jar file from the forge directory into the main server directory. I'm thinking that was the only way I could get it to show up in the "change runnable jar to:" box.