Jump to content

BRiT

Members
  • Posts

    6,575
  • Joined

  • Days Won

    8

Everything posted by BRiT

  1. Revert to base RC3 and post your experience with that.
  2. There was quick patches to 4.11.1 on the 18th. https://www.samba.org/samba/history/samba-4.11.1.html
  3. I suspect something in this area. But since you provided nothing (no Diagnostis attached), no one can help you.
  4. If you added this via your GO file then change this to be this: cp /boot/custom/docker-shell /usr/local/bin cp /boot/custom/docker-shell /usr/local/bin chmod 755 /usr/local/bin/docker-shell
  5. If your script is stored on your Flash drive or under /boot/ then you need to invoke it with "bash " first. This is covered in the release notes and threads for the 6.8 series. Or copy it to /tmp and then chmod 755 (to make it +x executable) then invoke it.
  6. BRiT

    Uptime

    For a cumulative uptime since, do the following: ls -al /boot/config/*.key ๐Ÿคฃ
  7. I certainly hope this isn't a HeisenBug. I was getting that feeling when reading all the progress posts that were not corrupting. ๐Ÿ˜Ÿ
  8. Has anyone tried it keeping the Scheduler set to the default? Does that still cause corruption? The reason I ask is that kernel discussion thread is a bit dense with info and seems like sometimes conflicting info, so for me the one part where they talked about the Scheduler didn't seem as straightforward as it should have. It was tough to see a consensus on scheduler being set to any value versus being set to "none".
  9. BRiT

    Uptime

    What's accumulative uptime? Is it registered to particular hardware or merely tied to the USB Flash Drive? If you change enough hardware of the system does the accumulative uptime start over at 0 again?
  10. Just wanted to say thanks for the links to the Kernel driver discussions and patches.
  11. Misconfigured dockers. One or more of them are writing inside the image. Go back through and make sure the docker only writes to locations you have mapped in the config. Check for typos or wrong case.
  12. Read the link and follow the thread instructions. It doesnt enforce it when you are on the middle or higher options.
  13. Did you start off with an entirely new/fresh database? Or was it restored from an earlier backup?
  14. As typical, @Squid is correct. No good reason to duplicate a well supported plugin.
  15. What else would you be doing over the holidays? ๐Ÿฌ ๐Ÿฆƒ ๐Ÿ•ฏ๏ธ ๐Ÿ•Ž ๐ŸŽ… ๐ŸŽ†
  16. The 6.8-RC notes states they upgraded to FUSE-3, so maybe rclone needs to be recompiled for this new target?
  17. Was your system performance changed much through changes in these tunables on the older versions? My system performance wasn't drastically changed on older versions, just minor improvements so I suppose I'll be alright. But seeing how vastly different other systems are I would think the new unraid would require some sort of knobs to tune.
  18. That isn't a fix. While it may be an acceptable workaround for some, it's not for others.
  19. So this is something to report to Limetech and they will have to make the changes required in order to get solid performance on wider variety of hardware?
  20. Try with using different drives for all your reads -- 2 of your reads are from the same drive, disk 9.
  21. Give it some time. It takes hours of work to get each new version ready for distribution.
  22. Looks like the 6.8 series will present a new set of challenges on tuning... In particular:
  23. As stated earlier, new and current info is available at the active thread:
ร—
ร—
  • Create New...