dboonthego

Members
  • Posts

    265
  • Joined

  • Last visited

  • Days Won

    1

dboonthego last won the day on October 6 2023

dboonthego had the most liked content!

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

dboonthego's Achievements

Contributor

Contributor (5/14)

51

Reputation

9

Community Answers

  1. I haven't experimented much with split leveling, but it sounds like you want to use top two directories as required. That should ensure all files within "newmovie" are written to the same disk under data/media/movies/newmovie Someone can correct me if I'm wrong. https://docs.unraid.net/unraid-os/manual/shares/user-shares/
  2. Most people set the appdata share to Primary-->Cache; Secondary-->None and as mentioned use the Apdata.Backup plugin for backups to the array.
  3. Precisely why I wish I could connect as a limited user, but I get your point and understand why it's not supported; I just wish it was. I believe I can switch from SFTP to Nextcloud and accomplish my goal so I'll try that first since I already have the Nextcloud docker. A dedicated SFTP docker to transfer this one file isn't appealing, but I'll keep it in mind for the future. Thanks for your input!
  4. Other than because I'm connecting as root, why not? Just to be clear, it's a local lan connection, not public.
  5. Will it ever be a thing? It pains me to use the root user for things that don't require root. I need to use SFTP instead of SMB to transfer a file between mobile and Unraid and the only user that can accomplish this is root. The owner, group, and file permissions are reset to root root 644 which creates problems accessing over SMB on Windows machines. I could set a cronjob to periodically set the permissions, but that's a hack. Is there a better way? -rw-r--r-- 1 root root 23998 Dec 7 23:51 myfile.txt
  6. Yes, but it's not a 1:1 copy of your photos. Originals are saved to the "Storage Path" which is typically an array share. The thumbnails are stored inside the "Data Dir" path which is where the container lives. Most likely /mnt/cache/appdata/photoprism/cache/thumbnails.
  7. We think we understand your layout. In this config, it looks like you'll have an array with a 12tb parity disk and a 10tb data disk giving you a total array capacity of 10tb. Then outside the array, you have a 2tb cache disk and a 10tb unassigned device disk (Project Data). The unassigned device is not in the array and therefore is not covered with parity protection. If all data here will truly be backups of stuff stored elsewhere, then this isn't a bad config. There's no built-in feature to handle backups. Various dockers are out there that can help with this though. Lucky backup is popular. Getting yourself familiar with rsync will help you perform manual file operations. The mover is there to manage files between your cache and array disks according to your share settings. You can review here: https://docs.unraid.net/legacy/FAQ/cache-disk/#the-mover
  8. You're better off writing to the array first (drives 1 & 2)(technically parity and data disk1) and then backing up to project data (disk3). Disk3 would be outisde the array and therefore unprotected. Doing it the other way would mean new files would be susceptible to data loss until disk3 is backed up to array. Keep in mind your backup is still in the same physical system. Consider storing backups off-site also. A single parity disk provides fault tollerance due to physical disk failure of up to one disk at a time. From user perspective, this allows the system to operate normally until a replacement disk can be installed and rebuilt. As said, parity is not a backup. It won't save you from theft, disasters, filesystem corruption, or accidental mistakes like writing a script to move thousands of files and forgetting the trailing slash/ in the destination. Yeah, I did that and it wasn't fun. Luckily I had good backups. Parity protection has performance overhead because every array write must also be written to parity. Using a cache disk allows you to initially write to the cache disk at faster speeds. Those files will be moved to the array off hours through a mover script. Dockers and virtual machines are also typically strictly stored on cache. You can add a 2nd cache disk for redundancy. You mentioned cache as main disk. Not sure what you meant by that.
  9. Is there a precedence to the retention setting? If I backup monthly, will I have THREE backups or ONE after the 4th month?
  10. Having duplicate files on both the cache and array would spin up parity. Check to make sure there are no files having the same name that exist in the same path on different disks.
  11. The share settings dictate how unraid will choose a disk for writing. If you set included disks, only those disks will be considered for writing of new files. If you set excluded, all other disks are considered. If you don't specify anything, then drives allowed under Settings > Global Share settings are allowed. So if you want all new files to be written to your new disk (say that's disk2) then set the share to include disk2. It's personal preference really with perhaps some performance considerations, but nothing wrong with doing it. Unraid will still read files that exist on any included/excluded disks if the share exists on them.
  12. Yep. Do the new config again by checking the yes box and apply. Assign your disks again without #6 and start the array. A parity sync will begin. You will see reads on all data disks and writes to parity with overall progress at the bottom of main tab. During sync, you may still see alerts ⚠️ that array is unprotected. That's normal until a successful parity sync. You will also want to review your default disk settings (spin down, filesystem, etc) and set them accordingly. The new config resets these settings to defaults. If you had disk shares enabled, those would need to be enabled again too.
  13. Where do you see this? Disk6 looks unassigned/not missing to me. Yes, but I don't think you need to do it. It looks like Disk6 is unassigned to me too. After doing the new config and starting the array, a parity sync begins and is calculated against all your array disks. It's normal to see a ln icon or status showing your system isn't protected while this is in progress. Once the sync is successful, that should go away. What does your main tab look like? What does it say for parity at the botom?
  14. Instead of checking the box "Yes, I want to do this" and clicking Apply, is it possible, you simply clicked "Done" and proceeded to unassign your disk? The checkbox is very easy to miss because it's hidden behind the preserve assignment drop down. "Apply" is greyed out until you check the box leaving you with "Done" being your only option. A reasonable person would assume they're "Done" making changes and click the button thinking it works similarly to how OK vs. Apply works in a Windows environment, but it seems "Done" doesn't actually do anything but kick you back to the Tools menu. What I'm thinking you did. What needs to be done.
  15. I don't understand this. Unraid supports one user (root) with SSH access.