remotevisitor
-
Posts
412 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by remotevisitor
-
-
You are correct, just remove the "-R" option when using the "mv" command.
-
The command you want to add to the script is:
cp -R /mnt/disks/DELUGETorrents/Seedbox_Downloads/* /mnt/disks/DELUGETorrents/Sonarr_Pickup/When you want to move the files rather than copy them change the "cp" to "mv".
-
User Scripts plugin is probably the easiest way ... it supports running commands on a schedule.
-
38 minutes ago, meep said:
UnRAID counts drives in the array, cache and parity towards license. USB key and unassigned devices are not counted.
That’s incorrect.
All connected drives, other than the USB boot drive, count towards the license count. This limit is checked when the data array is started.
However once the array is started additional drives can be added to be used as unassigned drives. If the system is rebooted, these additional drives will count towards the limit so may need to be temporarily removed in order to get below the limit in order to start the data array
-
2
-
-
Click on the SMART status entry on the dashboard for the disk in question and select the Acknowledge option.
CRC entries are never actually reset back to zero, but if the value changes again you will be warned.
if you are already doing this, then you may have some issue saving the saved state back to the flash drive.
-
How about:
find /mnt/user/yourfolder -type f -mtime -0 -print
-
The issue is rather subtle so I’m not surprised if you find it difficult to grasp what is exactly going on.
I have the cache setting on the shares on my system which hold all my TV and films set YES even though 99% of the time I am reading from them, so unless you have a specific reason on why you must set it to NO then this is the easiest solution.
For the other solution, no you do not need to create a second user. What you will find when your array has been started is that your shares appear under the directories /mnt/user and /mnt/user0. The difference is the /mnt/user ones include files that are on your cache + data drives, while the /mnt/user0 ones just include the files that are on your data disks.
The /mnt/user0 directory is really a hangover from the old way that mover used to be implemented to copy files from the cache disk to the array. It has since been replaced with a dedicated mover program which understands how to move the files to/from the cache disk without using it. Tom has dropped hints that he would like to get ride of /mnt/user0, but some people have indicated they do have uses for it; so it may or may not disappear in a future release.
-
1
-
-
I think the problem that a file has been created on a share which uses the cache disk, so the file is created on the cache disk.
The file is then moved to the Media share, and rather surprisingly you find it is still on the cache disk in the Media share, even though the Media share is set to cache NO. This is actually expected behaviour and the reason is rather subtle.
The caches setting on a share only affects the creation of new files and not files which already exist on a disk. Now as the file already exists on the cache disk and the cache disk is included in the Media share the cache setting does not apply so the file is moved into a directory in the Media share on the cache disk.
There are 2 possible solutions:
- Change the Media share to cache YES so the mover will move file to the data disks when it runs.
- Move files to /mnt/user0/Media rather than /mnt/user/Media as that does not include the cache disk so the move is forced to do a copy & delete farther than just a rename.
-
1
-
-
You are right .... I didn’t notice the additional directory before the .local .
-
Names beginning with . are not displayed by ls unless you add the -a option.
-
Install the "nerd pack" plugin using Community Applications.
Then in Settings there should be a new Nerd Pack setting which allows you to select additional commands, and bc is in the list.
-
Current version is English only.
However it is expected that 6.9 will have support for additional languages, although I expect the actual translations will probably need to be community supplied.
Don’t know about foreign keyboard support.
-
If it isn’t already there, a check for this in the Fix Common Problems sounds like a good idea as I suspect there are likely to be a number of people having this cache pool issue and being unaware their cache pool is not redundant ( @Squid )
-
Most likely causes:
- network cable has broken wire in it ... solution: try a different cable.
- cable connection is poor .... solution: check both ends of the network cable is fully plugged into the sockets. If either end has a broken clip on the connector, replace cable.
- port in hub is going wonky .... solution: try another port.
- hub is going wonky .... solution: replace hub.
- network port in Unraid server is going ... solution: use a cheap plugin network card, intel based ones are usually pretty compatible with Unraid.
-
1
-
This is expected behaviour .... but the reason is rather subtle.
The cache setting on a share is used when a file is created on a disk. So when you use Syncthing to copy the files to your system it is creating new files on your system so it honours the cache setting and creates the files on the cache disk.
When you then move the files to your Media share it is just renaming the files (not creating new files) so the cache setting is not used and the files will remain on the cache disk. As the Media share cache setting is "No", mover does not move files from the cache disk.
So you currently have 2 possibilities:
- Change the cache setting on your Media share to “Yes" so that mover will copy files from cache disk to data disks.
- Copy the files to /mnt/user0/Media rather than /mnt/user/Media; this will ensure the moved files are moved to the data disks rather than remain on the cache disk. (Note however Tom is thinking about removing /mnt/user0 in a future version).
-
-
Probably one of the plug-ins was replacing a library used by the system with an old version not compatible with the new UnRaid system; deleting all the plugins will have prevented this happening.
-
If you boot in safe mode does the gui work ok?
If so then most likely a plug-in that is incompatible with the version of Unraid is being loaded.
-
Is your unRaid system running? If so then it should be displayed at the top right in the gui in the registration field.
-
I suggest contacting Limetech support directly via email.
i know that Tom has previously mentioned that some of the early license keys didn’t get added to the current database, so I suspect yours could be one of those. If so I’m sure support will be able to sort out your problem.
-
Not knowing what all your shares are for and how you manage adding new files it is difficult to know 100% what is the best solution for you.
Personally I would just set your main shares which are fed from your download shares to Use Cache Yes, and then set mover to run at a schedule that suits your usage (or manually run mover if you want). Then you don’t need to keep doing anything special and the system will just do the necessary stuff for you without you needing to take any additional actions.
-
1
-
-
As a work-around to the feature you might want to consider renaming the files to /mnt/user0/<sharename> rather than /mnt/user/<sharename> as user0 specifically excludes the cache disk which forces a move/rename to not be on the cache disk, so it will do the copy/delete method.
-
I think this is down to the way the mv (rename) interacts with the Use Cache setting.
The Use Cache setting affects where new files are located.
Now consider the case where one of your downloaders downloads a file which uses the Use Cache setting to place the file on the cache drive. All as expected.
Now you run some program to move/rename the file to some other share. Now if possible Linux will just move the file to the destination on the same disk (which is not creating a new file but moving an existing one so the Use Cache setting has no effect) and only if that fails will it do a copy (which does create a new file so uses the Use Cache setting) and delete the original file.
So if the file to be moved is on the cache disk in the downloads share it will end up still on the cache disk after it has been moved to a share which has Use Cache set to No ..... unexpected, but a feature on the way the system works.
-
If you cannot open the files I don’t understand how you can copy them, as the copy process would need to open the files in order to do the copy.
Are the original and the copy on the same data disk, or do they end up on different disks?
-
Possibly this issue ....
[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation
in Docker Containers
Posted
Have a read of this issue (towards the end there is a mention of a possible workaround) ...