• Posts

  • Joined

  • Last visited

Recent Profile Visitors

1750 profile views

MowMdown's Achievements


Apprentice (3/14)



  1. just change --vfs-cache-mode full to --vfs-cache-mode off
  2. That is strange, Im not sure why it would write to the _vfs upstream if you have your local path listed first in the union when writing to the union... for the record you can export /mnt/disks/some_dir as a share through SMB example: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [some_dir] path = /mnt/disks/some_dir comment = browsable = yes # Public public = yes writeable = yes vfs object = You simply add this to the SMB extras under Settings > SMB
  3. when writing to the union mount directory “media” the non “vfs” one, shouldn’t be touching the cache because it should only write to the local drives your first upstream in the Union setup. Sounds like maybe you should check the spelling/case of that first path. you might need to add the flag -vv to the mount command so you can verbosely debug the issue further.
  4. @axeman, no, if you pay close attention to the path for that move command, im using "/mnt/user/media" not "/mnt/disks/media" (I don't mount to /user/) My rclone mount is under "/mnt/disks/media" so it does not interfere with the move. I'm essentiall moving the files from /mnt/user/media to the "crypt:media" mount but as far as the unraid is concerned the file isn't actually moving since no matter where I put the file it always shows up in /mnt/disks/media.
  5. I just run this nightly at 3am using user scripts, super simple. (obviously I don't have a folder named "files" but you can use your imagination) rclone move /mnt/user/media/files crypt:files -v --delete-empty-src-dirs --fast-list --drive-stop-on-upload-limit --order-by size,desc I have a single 500GB drive that I fill up with whatever I want to be moved to the cloud and that small script does it.
  6. Might be related to your mount command you're using. the ":nc" suffix is simply "No Create" and shouldn't really affect the reading of files so I assume the mount you're using to mount to "media_vfs" directory is possibly the culprit. Edit: No Plex/Emby would not be able to write unencrypted data to the mount since rclone is the one encrypting anything that gets written to it. I simply want to avoid writing NEW files to it to avoid corruption because writing to a mount is not best practice. you can also use the :ro suffix to essentially mount it "read only" however thats also not what I want because with :nc I am able to upgrade media using sonarr/radarr which requires those programs to be able to delete files. can't do that when it's read only. (Im not actually sure :nc or :ro is neccessay since we are using the "ff" policy which essentially only deals with the first listed upstream which is our local array drives) When those programs do upgrade the media, they actually delete them off the cloud mount, and then write the new file/data to the local array drives where my upload script will essentially write it back to the cloud. It's actually kinda clever the way I set it up.
  7. You don't need any physical unassigned devices, I don't have any. It's just where I mounted my cloud mounts. Post your "Union" rclone config like I did above. I'm not sure I understand where to do this. When using the /mnt/disks/ as your path in the docker configs for each docker, unraid will throw an warning that the path is not using the Slave options. If you edit the docker container config and you go to edit one of the path variables you will see "Access Mode" that will need to be changed from Read/Write to RW Slave. Super easy to change.
  8. I'm very time limited this week but here is a crude setup of what you need to do. Using rclone union instead of MergerFS setup (this setup will assume you already are familiar with rclone mounts and are using the latest version 1.53.2) For my mount script is pretty straight forward, I create two directories needed, the first one is needed to mount the cloud which will utilize rclone's VFS caching and the second mount will unionize the VFS mount with the local media. #!/bin/bash mkdir -p /mnt/disks/media_vfs mkdir -p /mnt/disks/media rclone mount --allow-other \ --dir-cache-time 100h \ --fast-list \ --poll-interval 15s \ --cache-dir=/mnt/user/system/rclone \ --vfs-cache-mode full \ --vfs-cache-max-size 500G \ --vfs-cache-max-age 168h \ --vfs-read-chunk-size 128M \ --vfs-read-chunk-size-limit off \ --vfs-read-ahead 128M \ crypt: /mnt/disks/media_vfs & rclone mount --allow-other union: /mnt/disks/media & In the first rclone mount command im using my "crypt:" rclone mount, you will need to replace --> crypt: <-- with your mount. You must edit the "--cache-dir=" variable to where you want rclone to cache your media on your local unraid machine as well as the "--vfs-cache-max-size" to the largest size you are willing to cache on your disk. All the other vfs flags should remain the same. Now the next step is using rclone to configure the "union" mount needed to union the VFS mount with the local media directory. Enter rclone config and select "n" for a new remote and name it union, then select the union option. It's going to ask for the "upstreams" you're going to first type the local path to your media, put in a space, and then you're going to put in the path to the mount location we just made /mnt/disks/media_vfs and then I personally add the :nc modifier to avoid accidentally creating files to the cloud mount. Next rclone will ask for the action_policy, enter ff Next will be the create_policy, enter ff Next will be the search policy, enter all Last will be the cache time, leave 120 default Once it's done it should look something like this: [union] type = union upstreams = /mnt/user/plexmedia/ /mnt/disks/media_vfs:nc action_policy = ff create_policy = ff search_policy = all cache_time = 120 Remember to replace /plexmedia/ with root of your media location. (your remote should follow the same directory structure or this may cause issues) Once you actually mount the mounts after union is created, you should be able to browse "/mnt/disks/media" (the non _vfs media) and see a compete list of all your media whether it be in the cloud or locally) One last thing, you will need to change your dockers paths from /mnt/user/etc/etc/etc/ to /mnt/disks/media/ so it can read from this mount. you will also need to change them from Read/Write to the R/W Slave. To unmount at array shutdown: #!/bin/bash fusermount -uz /mnt/disks/media fusermount -uz /mnt/disks/media_vfs
  9. Just giving an update to one of my comments from a month or so ago: I just wanted to say that the built in rclone union backend/mount is quite good and much less complicated than using the mergerFS setup. I found a way that allows you to use the rclone VFS caching w/ the cloud mount and using the local storage in tandem. Movies play instantly and it's wonderful. If anybody is interested let me know and I'll share my setup.
  10. I had no issues building my kernel while I was running the Nvidia Unraid from LISO.
  11. Or you can use @ich777's Unraid-Kernel-Helper docker to build the 6.8.3 kernel with the latest NVIDIA drivers or just download the pre-compiled 6.8.3 w/ them from the docker thread located: here!
  12. I just like to keep the first core free when running heavy CPU tasks.
  13. Got it. I assumed the variable followed the manual method of pinning cores to a docker. The documentation doesn't give an example for a specific number of cores except for "all", which is why I did what I did. I totally forgot I could do it this way... apparently I like doing things the difficult way. Needless to say I did get it working and it booted up 1st try. Woohoo!
  14. Quick Question/Possible Bug? I replaced the Compile CPU Count field with 1,2,3,5,6,7 from "all" and the build failed and threw a bunch of errors. Using "all" yields a positive result. Am I entering the cores wrong or is there something else at play? I noticed in the log that the "1" was missing and it looked like this: " ,2,3,5,6,7"