Leaderboard

Popular Content

Showing content with the highest reputation since 04/13/24 in Report Comments

  1. I tested the bonding suggestion, and that worked for me. After a reboot the container got the correct IP, but my network setting maybe different from yours. Next I’ll attempt an upgrade to 6.12.10 and see if that also works with regards to the container network settings surviving. EDIT: Upgraded and the network settings is indeed still sticking, I'll keep monitoring for stability:
    1 point
  2. Sorry for the late reply, but I have some personal issues to deal with first. I can't test at the moment, but there are two ways to deal with your configuration. 1. Define eth0 as bonding interface as well (next to bond2). Then upgrade and see if all assignment are correctly processed. 2. If the above doesn't work, then (temporary) configure eth2 as regular interface (remove bonding)
    1 point
  3. I've ordered replacement processor, motherboard, and RAM. I'm currently testing, but it seems like it's actually the RAM, even though it didn't show any errors, and I tested each one separately, so both must be defective or both incompatible. Although i checked compatability before 🤔 ASUS ROG STRIX B760-I GAMING WIFI with Corsair Vengeance, DDR5-4800, CL40 - 32 GB Dual-Kit, black Now I have the Kingston FURY Beast Black DDR5 16GB (2x8GB) 5600MT/s DDR5 CL40 DIMM Desktop Gaming Memory Kit with 2 - KF556C40BBK2-16 and so far, Unraid is running without any error messages. I'll do another test later with the old RAM to double check it was the RAM, one module at a time.
    1 point
  4. Yep, at the end of format sync is used to make sure any pending writes are committed to the drive but that's system wide and preclear does a constant write that won't end until it's done. But you can pause preclear and it should go through, then resume.
    1 point
  5. Wait times are how long the system waits after starting the container before starting the next one. In your case it did wait 60 seconds (presumably that's what you had it set to) Jul 6 20:38:31 Liberty rc.docker: plex: started succesfully! Jul 6 20:38:31 Liberty rc.docker: plex: wait 60 seconds ... Jul 6 20:39:31 Liberty rc.docker: telegraf: started succesfully! Why not move plex to the bottom of the start order and the second last container enter in a wait time?
    1 point
  6. Directly executing scripts stored on the flash drive is no longer allowed due to security changes The easy workaround though is to change your go file to something akin to bash /boot/path/To/myScript.sh
    1 point