JonathanM

Moderators
  • Posts

    16084
  • Joined

  • Last visited

  • Days Won

    65

JonathanM last won the day on November 11 2023

JonathanM had the most liked content!

Retained

  • Member Title
    unAdvanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

JonathanM's Achievements

Grand Master

Grand Master (14/14)

2.3k

Reputation

202

Community Answers

  1. Did you get an auto reply? If not try sending again. Generally containers put their executables and other common program parts inside the docker.img file, and their customizable parts live in ./appdata/* and the templates are on the flash drive. Do you have any backups of the flash drive? If you only had a single parity drive in Parity1, then data drive order doesn't matter. If for some reason you had that parity drive in Parity2, then order does matter. The two parity slots use different calculations.
  2. Pick one app to work on, read the first post in that app's thread and follow the troubleshooting steps. When you have the appropriate log file, read through it and XXXX out any credentials then post it in that app's thread with a description of what you have done so far and where you are getting stuck. Since you say you have the same issue on multiple containers, I'm betting if you fix one, you can easily figure out how to deal with the rest.
  3. There are at least 5 different implementations of nextcloud, each with their own support areas. Please click on the nextcloud icon in the gui and select the support item, then read and post in that specific area.
  4. I don't know if the time being wrong will give that error, but try setting the BIOS time to GMT. You should be able to save the diagnostics zip file to the flash, shut down the machine, then attach the zip file to your next post here.
  5. According to your previous screenshot you aren't using that file.
  6. I don't understand what you think is wrong, everything looks good to me.
  7. Everything will only be files not in use, so to get "everything" moved you need to stop the docker and vm services in settings. You will know when the services are stopped because the docker and vm tabs will be missing from the GUI.
  8. Motherboard reported, may be accurate, maybe not. fixed allocation by Unraid It's the percentage of space used INSIDE the docker.img file. Not the free space on the drive holding the image file.
  9. Use the 6.12.10 files, overwrite everything on the USB except the config folder. Make sure you keep the config folder, make a backup of it before you do anything else.
  10. Pretty sure that didn't work like you thought it did, because those locations are the same. /mnt/user paths are the combined view of all the root paths on the array disks and the pools combined. user share and disk share should never be mixed in a file operation.
  11. It does, I use it extensively, each of my VM's runs apcupsd in slave mode, and is set to begin shutting down a minute or two after the host server reports a loss of power. Server shutdown is much smoother for me if the VM's are all shut down before the server itself starts the shutdown sequence.
  12. Block the entire 140.210.*.* network in your firewall.
  13. Ask your ISP if they put you on a CGNAT address. If so, ask if they can put you back on a direct internet address instead.