wgstarks

Members
  • Posts

    4569
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by wgstarks

  1. For what it’s worth my M1 mini is working with both this docker and unRAID on Ventura. Of course, it was working on Monterey and Big Sur as well.
  2. And you ran the command sudo chown -R <UID>:<GID> /mnt/user/<nameofshare>/ right?
  3. @Joseph Also want to be sure you haven’t altered the destination share created by this docker? No changes to permissions, smb share settings, etc. This is really just a shot in the dark but I know you posted something earlier about changing permissions. All you should need to do is run the sudo command on that share.
  4. Might try posting on the GitHub project page with that log entry. https://github.com/mbentley/docker-timemachine
  5. Those settings aren't affected. You shouldn't notice any change at all.
  6. Open the docker configuration (click the docker name) and in the repository field type a colon and tag number (no spaces). Click “apply” at the bottom of the page. You can get the tag number from dockerhub. See the link in the first post.
  7. A re-install is implemented differently from an update but from a users perspective it's exactly the same except that it may take slightly longer. All files are being updated rather than just the changed files.
  8. You might also try just using an unraid share for TM backups.
  9. I had similar issues at one point and corrected them by re-installing macOS. This apparently doesn't work for everyone though. It's a simple process, roughly equivalent to installing an update, if you want to give it a try.
  10. I just use one share with multiple folders but I believe either would work.
  11. This is really just a shot in the dark but the first thing I would try is deleting everything on the share you’re backing up to and then just connect the Big Sur machine (remove this location from the Ventura machine) and see if it works properly then. If so, you should probably setup separate shares for the two machines. https://forums.unraid.net/topic/123985-timemachine-application-support-thread/?do=findComment&comment=1134386 FYI, if you click this (or any) docker run link it shows you how to get the data.
  12. Or just wait a few days and see what problems other users are reporting.
  13. There isn’t an option for *all. You just need to click ignore for each one though.
  14. I’ve never seen anything like that. Another option would be to check the trackers used by the private indexer or save yourself some trouble and let all torrents seed to the minimum time/ratio.
  15. You can request this feature in their forums but I don’t think it exists yet. https://qbforums.shiki.hu/viewforum.php?f=10&sid=7f4005cb04884a786f508294be14ea29 Probably the best way to prevent this would be to set the torrent to delete after seeding for a specific time. I believe two weeks is standard to keep from getting labeled as a leech.
  16. I can't answer any of your questions but I can suggest settings that are working fairly well for me. Stop your array and edit boot/config/smb-fruit.conf to match these- # global parameters are defined in /etc/rc.d/rc.samba # current per-share Unraid OS defaults vfs objects = catia fruit streams_xattr #fruit:resource = file fruit:metadata = stream #fruit:locking = none fruit:encoding = native #fruit:veto_appledouble = yes fruit:posix_rename = yes #readdir_attr:aapl_rsize = yes #readdir_attr:aapl_finder_info = yes #readdir_attr:aapl_max_access = yes #fruit:wipe_intentionally_left_blank_rfork = no #fruit:delete_empty_adfiles = no #fruit:zero_file_id = no # these are added automatically if TimeMachine enabled for a share: #fruit:time machine #fruit:time machine max size = SIZE #spotlight settings spotlight = yes In your smb extra configuration add this- #spotlight settings [global] spotlight backend = tracker #end spotlight settings Start the array. I’m getting fair transfer speeds and Finder searches are working great. No spotlight indexing though. This is with macOS Ventura (13.0.1) and unRAID 6.11.4. Your results may vary.
  17. Cache>min free space setting should have a note beside the setting that the setting can only be adjusted when array is stopped. This would be in keeping with other settings with similar requirements. This info should also be included in the "Help" menu.
  18. I would suggest posting this in the TDARR support thread. https://forums.unraid.net/topic/84070-support-haveagitgat-tdarr-audiovideo-library-analytics-transcode-automation/
  19. You can run the Frigate docker in either one. I think a lot of people run it on unRAID just because that machine has more horsepower. No. You can also use CPU for detection (that’s the default) but it’s my understanding it’s a real hog,
  20. Thanks. Looks like it only supports UEFI boot mode anyway.
  21. How would you install and run it on the flash? Is it just a matter of replacing /boot/memtest?
  22. I’m sure I’m not the person to help with this but I would recommend you post your diagnostics from right after a reboot with the array set to auto start.
  23. I think most people probably only use one path in qbit and then sub folders for complete, incomplete etc but if your config is working then no point in fixing it.
  24. 2 paths may cause issues if you are using any of the *arrs suite. Are you?