strike

Then go for it :)

Chinese sellers are notoriously known for selling fake LSI controllers, which is why they're always cheaper. That being said, a fake card can work just as good, but they can be manufactured with poor component quality. Another reason for them being cheaper is that almost everything in electronics from China ships for free. But as long as you buy from a seller with a high score, you should be good.

The array refers to the traditional way of storing files in Unraid. Before cache and pools, there was only the array. Each drive in the array (except parity) has its own individual file system and operates independently with real-time parity updates and no striping. Then cache was introduced as a way to leverage the higher write speed, so the files would first go to the cache drive, then be offloaded to the array, typically during nighttime when the server is idle. Then the ability to add cache drives to a pool became available. The cache is now essentially a pool of either single or multiple drives. If multiple drives, it has to be in either the BTRFS or ZFS file system, which then forms a RAID. So the two ways of storing files are now boiling down to a couple of things: 1. Array is for slow writes and a different parity protection system. If more than 2 (max) drives fail at the same time, you lose only data on those drives and not the rest of the array. And of course, mixing of drives with different sizes. 2. The pool(s) are for faster write speed and a parity protection system, where if more than 3 (max) drives fail at the same time, you lose not only the data on those drives but ALL your data. So it's essentially 2 different use cases. The allocation method is just a set of rules for the way you want to fill up your drives in the ARRAY. As they are individual drives with an independent file system, they can be written to in different ways. Either balanced (high water), write to the drive with the most free space, or simply just fill up one drive at a time until your most free space setting is reached before it moves to the next drive. In a pool, all files are striped over all drives and will fill up the same, so the allocation method doesn't apply; it only applies to drives in the array. Hope this makes sense :)

Same for me

New version is out, be sure to check out the new settings. It now supports "Other Library Paths", where you can basically put any folder(s) you like. Multiple sorting orders are available, as well as the ability to set the priority for which library is moved. I've been testing it for the last couple of days, and everything appears to be working as expected.

Got it. I'll see what I can come up with without making it too complicated.

What should the configurable options be? Just, smallest folders and random folders? Alphabetically? Other sorting orders? Should be doable. This is an excellent idea, btw. I can see if I can take a look at your suggestion next week, as I have some free time then.

That's something I haven't seen before. But I think this happens because of a caching delay in the OS, The script is reading the disk's free space immediately after moving the files, and the system often hasn't updated its records yet, leading to a stale (and in this case, incorrect) reading of 0. I've added a sync command to the script. This command forces the system to write all cached data to the disk, ensuring that any subsequent reads of the disk's free space are accurate. A new update is ready shortly.

Awesome. Yeah, I broke the cron schedule a while back. Fixed it, but the setting needed to be reapplied like you just did. You mean other than movies and tv shows? If you can tell me what the logic should be, I can probably figure something out. I could add a third category for "Other Paths" that would have the lowest priority. This means the script would only move files from your "other" paths if it couldn't free up enough space by moving movies or TV shows first. The new logic would be: Movies > TV Shows > Other Files. Like movies, the items in the "other" paths would just be folders that the script would move one by one. Maybe starting with the smallest folder first? Or did you have anything else in mind? New update is out btw, with the new notification and some small changes. @Nonoss

Are you on the latest version? Try to enable dry run and change the schedule to run a minute after you have done that, to check if it fires off. If it works just disable dry run and set the schedule back to what you want. There was an issue with the cron job in an earlier version, but it was fixed.

So I had some time after work to look at this, but I got a question for you. And for anyone else, too, for that matter. I'm not able to get it exactly how I want it, so I want to ask you guys what you think. The issue is with Unraid's notify system. Anything I put in the description will be displayed in the web UI, and it will also be automatically sent to any notification agents. The problem is that the unraid notification is formatted in html, and the message sent to the agents is not. So I can put a detailed notification summary pop-up like this: But then the message in the agents (or at least email) will be like this, improperly formatted: Here I have also added the correct formatting in the message itself. That's why it's duplicated. And the log is missing from this example, but it's in the end. Event: Disk Space Management Subject: Run Summary Description: Run finished. Total moved: 192.00GB in 13 items.. . <b>DRY RUN: No files were actually moved.</b>. . Start: 2025-08-24 22:01:59. End: 2025-08-24 22:02:02. . <b>--- Disk Summary ---</b>. - Moved 94.00GB from disk9 to disk5. New free space on disk9 is ~151GB.. - Moved 12.00GB from disk1 to disk5. New free space on disk1 is ~66GB.. - Moved 4.00GB from disk17 to disk5. New free space on disk17 is ~60GB.. - Moved 14.00GB from disk10 to disk5. New free space on disk10 is ~72GB.. - Moved 19.00GB from disk14 to disk5. New free space on disk14 is ~70GB.. - Moved 18.00GB from disk13 to disk5. New free space on disk13 is ~68GB.. - Moved 18.00GB from disk12 to disk5. New free space on disk12 is ~77GB.. - Moved 13.00GB from disk11 to disk5. New free space on disk11 is ~63GB.. Importance: normal DRY RUN: No files were actually moved. Start: 2025-08-24 22:01:59 End: 2025-08-24 22:02:02 --- Disk Summary --- - Moved 94.00GB from disk9 to disk5. New free space on disk9 is ~151GB. - Moved 12.00GB from disk1 to disk5. New free space on disk1 is ~66GB. - Moved 4.00GB from disk17 to disk5. New free space on disk17 is ~60GB. - Moved 14.00GB from disk10 to disk5. New free space on disk10 is ~72GB. - Moved 19.00GB from disk14 to disk5. New free space on disk14 is ~70GB. - Moved 18.00GB from disk13 to disk5. New free space on disk13 is ~68GB. - Moved 18.00GB from disk12 to disk5. New free space on disk12 is ~77GB. - Moved 13.00GB from disk11 to disk5. New free space on disk11 is ~63GB. --- Log From Current Run (Last 200 Lines) --- Or I can put a very short notification like this in the webUI: Then the message to the agents will look like this: Event: Disk Space Management Subject: Run Summary Description: Run finished. Total moved: 192.00GB in 13 items. DRY RUN. Importance: normal DRY RUN: No files were actually moved. Start: 2025-08-24 22:32:55 End: 2025-08-24 22:32:58 --- Disk Summary --- - Moved 94.00GB from disk9 to disk5. New free space on disk9 is ~151GB. - Moved 12.00GB from disk1 to disk5. New free space on disk1 is ~66GB. - Moved 4.00GB from disk17 to disk5. New free space on disk17 is ~60GB. - Moved 14.00GB from disk10 to disk5. New free space on disk10 is ~72GB. - Moved 19.00GB from disk14 to disk5. New free space on disk14 is ~70GB. - Moved 18.00GB from disk13 to disk5. New free space on disk13 is ~68GB. - Moved 18.00GB from disk12 to disk5. New free space on disk12 is ~77GB. - Moved 13.00GB from disk11 to disk5. New free space on disk11 is ~63GB. --- Log From Current Run (Last 200 Lines) --- I personally like the notification from option one, but really dislike the duplicate and improper formatting in the message to the agents. I can, of course, remove the duplicate, but then only the improper formatting will be left. It seems I can't get it exactly perfect the way that I want it. But what do you guys think, which is better? I need to make some sort of compromise here.

I'm glad you find it usefull. Sure, I can add that in the next version. ☺️ A summary is probably best instead of the entire log. In case there's a lot to move, the notification would be long. Or just add the log to the email being sent. Or whatever notification agent the user have.

Awesome, then you're good.

Oh, I forgot one thing. You also need to update the config mappings in your container templates, where the appdata for the containers is since they are now on the array. And any download loactions for your downloaders/*arrs.

Ah, I see :)

When you do a new config, you can choose to Preserve current assignments. You probably did not do that, and then all slots are empty. And you need to reassign each drive. Try it again and preserve current assignments. And unassign the drives you want to remove.

Go to settings->Docker and delete the docker.img file. If mover won't move the files off the cache drive, do it manually from the file manager in the web ui or use Midnight Commander (mc) in the terminal. I personally prefer mc. Overwrite any existing files. When everything is moved, go to settings->Docker again and start the docker service, it will recreate the docke.img file. If you want it on the array you need to change the location first. Go to Apps -> Previous Apps and reinstall all your containers. But why do you want your docker containers running on the array anyway? Performance will suffer, it's highly recommended to have it on the cache drive.

Glad you like it. The correct way to exclude disks is a comma-separated list of full disk paths like this: /mnt/disk1,/mnt/disk2 I just realized that I could try to implement this better by listing all the disks and just adding a check box that the user can check to exclude each disk. I'll work on that for the next version.

Thanks for the feedback. Yeah,linux is case sensitive so getting the case right is important. I'll add a note in the help text about it and maybe see if I can add case checking.

This plugin is for those who don't use split any directory as required. Since you use that I suspect that you maybe have shows spread across multiple drives. If you want to consolidate your shows to individual drives you'll have to do some manual moving first,then change to the split level you want as split level only applies to new files. If you want to split at show level or season level is really a personal preference. I like to split at show level. It looks like you have the paths set up correctly. What is your threshold setting at in GB? And did you have any drives below that level when testing the dry run? If no disks are below the threshold it wont move anything and the script finishes without doing nothing. For testing you can put a higher threshold, anything higher then what you have as available space on one or more drives. Then do a dry run to see what it will do.

You can have multiple libraries in both movies and tv libraries, comma separated. E.g: share/Movies,share/Anime-Movies And share/TV,share/Anime-TV

I've fixed the issue now, so the logfile is created correctly. Please update the plugin :) The issue was that when you click the "Run Script Now" button in the UI, the script's output is sent directly to the iframe on the web page so you can see the progress. However, there is no redirection to the log file in this case. As a result, the log file is only ever created and written to when the scheduled cron job runs for the first time, not when you trigger it manually. The script is now modified to do its own logging to ensure the log file is created the first time when run manually as well.

Weird,it was created in my tests. Did you use the default path or did you use your own path? I'll look into it when I get home in a few hours.

The plugin is now available in CA :)

The plugin is now available in CA. Anyone using the script is encouraged to install the plugin as the script will no longer get updated.