JP

Members
  • Posts

    422
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

JP's Achievements

Enthusiast

Enthusiast (6/14)

3

Reputation

  1. Some success! Once I made the change you recommended and started up the server I noticed some things I didn't really expect. That is, all the folders I had residing on the cache now became user shares. I guess by default these are now flagged to eventually be moved to the array so this is why UNRAID made the shares for them. For these folders that I only want on the cache and to never be moved, I suspect I need to change the USER CACHE POOL to ONLY. I think that is right. Also, to get files to move at all to the cache I had to stop the array and then go into cache settings and change MINIMUM FREE SPACE from some number that was in there to 0. They do appear to go directly to the cache when the number is 0, but if I followed the directions it didn't seem to work. When you click on the question mark near this field it states: This defines a "floor" for the amount of free space remaining in the volume. If the free space becomes less than this value, then new files written via user shares will fail with "not enough space" error. Enter a numeric value with one of these suffixes: KB = 1,000 MB = 1,000,000 GB = 1,000,000,000 TB = 1,000,000,000,000 K = 1,024 (ie, 2^10) M = 1,048,576 (ie, 2^20) G = 1,073,741,824 (ie, 2^30) T = 1,099,511,627,776 (ie, 2^40) If no suffix, a count of 1024-byte blocks is assumed. I tried reflecting 30 GB as my "floor" and writing out the zeros didn't seem to work so I tried just reflecting "30 GB" and that did seem to take. I guess that is accurate for what I'm trying to reflect. So I guess all that is left for me to do is update the settings on all these new shares that popped up. If I just want to continue having them on the CACHE then I can change USE CACHE POOL to ONLY and that should keep them only on the cache. Once I feel a bit more comfortable with the settings, I'll then change some of my larger shares (like Movies or TV Shows) over to USE CACHE POOL: YES. This should take any new files or folders that are created on the share to first be put to the cache drive and then later brought over to the array once MOVER runs. I my logic is right here.
  2. I'm pretty sure I am. Here is all I am really doing. I'm creating the user share with the criteria I listed before. I give it a unique name like TEST or TESTING. Then I go to File Explorer in Windows and type in \\{ip address of TOWER} and all my disk shares (DISK 1, DISK 2, etc.), user shares (including the one I just created called TEST), flash and cache drive, show up. I then just take a file and copy it to the newly created user share (i.e. TEST) and watch the UNRAID GUI for activity. The file(s) always go directly to the array and never the cache drive. I've done these tests repetitively, changing the criteria and user share name and there is nothing I can seem to do to get any size file to be saved to the cache first from a user share. I can of course save to the cache just fine by saving a file directly there. I have done multiple server reboots as well just to give myself a clean slate. Very confusing.
  3. Thanks for letting me know Squid. Done. If anyone else can think of why files won't go to my cache drive even though I tell the Share to do so, please let me know. This one has me stumped since I think I followed the directions perfectly.
  4. Just copying in Windows from the desktop to the TEST folder / share. I’ve tried 4 Gig files and small files. They all just save to the array. I’ve tried deleting the share and recreating it as well as multiple reboots on the server. The issue remains. Weird.
  5. Thank you. They are attached. tower-diagnostics-20210612-0534.zip
  6. I'm completely new to using Mover and thought I understood, but something doesn't appear right. To test Mover I decided to create a new share called, "Test." I changed "Use Cache Pool" to YES and "Select cache pool" to CACHE. I changed "Minimum Free Space" to 50 GB. There is 450 GB free on the cache drive. I left everything else at default. I thought this would tell UNRAID to put everything I copy into the TEST share onto the Cache drive first. However, it doesn't appear to have done that. The file I copy with is still getting put on the array when I attempt to put it in the TEST share. Any thoughts on what I'm doing wrong?
  7. Thanks John. I actually did that, but I still didn't see an option to format the drive. I needed to start the array. Once I did that the option to format the drive came available. This all seems to have worked, which is awesome. The Previous Apps option and having your settings retained was so nice. Thanks again.
  8. I finally got around to doing this and so far everything seems to have gone ok. I'm at step 6. in my list where I need to format the newly installed cache drive. However, there was no check box available for me to format it. I think the problem is that I was using this drive in another PC and it was already an NTFS disk. I did a little research and installed the UNASSIGNED DEVICES PLUS plugin because I thought I might need DESTRUCTIVE MODE enabled, but having that enabled still does not reflect a way to format the drive in Unassigned Devices so it can be used as a cache drive. Any guidance here? Should I possibly remove both of the partitions listed under the drive? Again, I don't need any of the data on this drive. I'm just looking to set it up as a cache drive and then have it rebuild the docker.img on it as I had on my previous cache drive.
  9. I could have sworn I read something in years past where people were choosing specific driver letters to copy files to for some kind of added benefit. But based on what your saying, it sound like there is no added benefit by doing so....correct?
  10. I've had an unRaid server for some time so its little embarrassing having to ask what I think is a pretty basic question, but I don't know so here goes. I have some 4K family videos that can get pretty big, some are 10, 20, 30 GBs. When I move these files from my video editing PC across the network to my unRaid server, what is the best process to do so? Traditionally, I've just copied it through a share path. I do NOT have mover enabled. This writes to the parity drive and provides some protection once it is finished. However, I've often that of just pointing to a specific drive with the folder path I'm looking for and copy it there. Doesn't that force it to be copied to that single drive? I'm not sure whether it builds parity during or after the file has been copied, but it seems like this would be a better process. I'm guessing because when the file is then accessed, it only needs to spin up one drive. If the files are large like these, couldn't unRaid span the file across two drives if I used the first method (via a share)?
  11. Thanks Squid. I did check the system log and I'm not seeing anything that stands out for the specific app that I think could have been the culprit. Out of curiosity, the Recycle Bin wouldn't help me recover those files now since it has already been deleted...correct?
  12. This isn't the end of the world since I maintain backups and my data is recoverable, but recently I had two folders full of files disappear. I don't see that I could have done it, but maybe I did. Another family member might have accidentally done it through an application (which I'm locking down now), but again, I would think it is unlikely. I looked through the log, but nothing stood out and I'm not savvy enough to really understand what I'm looking at. Ultimately, does UNRIAD keep some kind of log around when a file is deleted and provide some kind of source data that accomplished the deletion?
  13. Can anyone confirm the steps above are accurate? If possible, I would just like to confirm before attempting it. Thanks for any help.
  14. Thanks for the help. Sadly, I would have screwed this up had not thought to ask all these questions. If there is one thing I've learned before upgrading items like this is to be sure you know exactly what you are doing, before you do it. I've made some small assumptions in the past and they've bitten me. So with this in mind, I think I understand exactly what I need to do now to upgrade my cache drive and return everything to the same state it is now. Please let me know if anything here seems out of place: 1. Shut down all dockers 2. Disable docker 3. Click on the Advanced slider, select the option to delete docker.img and delete docker.img. 3. I don’t have VM, MOVER, or any shares on the cache drive so nothing to do there. 4. Copy the two folders I have from the cache (basically everything on the cache) somewhere to the array via Midnight Commander. 5. Once complete, shut down the server, remove my current cache drive and replace it with the new one. 6. Turn on the server, assign the new cache drive and check off the box to format it. Start the array. 7. Once the format is complete, move the two folders I saved on the array to the new cache drive. 8. Re-enable docker and have docker.img rebuilt in the same location with the same settings and size (they should have been saved...correct?). I should just have to click APPLY and DONE. 9. Go to PREVIOUS APPS under APPS and install all the same docker apps you had before. Little work should be done here since all the previous settings are saved here as well. 10. Start all the same dockers again that I was using before. These steps should return me to the exact same state I had before, only now my cache drive is upgraded to something much bigger (120 GB --> 500 GB). Does this sound accurate?
  15. Thanks for this. The light bulb went off a little bit because now I see where MOVER might help if it is able to easily move the docker.img file to the array and back for you. And I mostly understand what they are saying to recreate the docker.img file. I guess it sort of goes like this: 1. Disable Docker 2. Switch to the Advanced View and check off the box to Delete Docker.img and delete it. 3. Power down server and replace cache drive with new one. 4. Power up server, assign new cache drive, and format it. 5. Enable docker, which should recreate the docker.img file in the same location if I didn't change the path....correct? 6. Then it says in Squid's directions, to re-add the templates. Are the templates the Docker Containers themselves with all my port mappings and volume mappings? Will all those still be there and I simply need to enable the docker containers as I normally would to have them run? This is the part that sort of concerns me because I wouldn't want to have to re-create all this from scratch again.