xamindar
-
Posts
442 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by xamindar
-
-
+1! Would love to have this feature.
-
So I just upgraded one of my servers from a 5.0.5 server with a plus key to 6b14 using same key.
I performed a stop array today and noticed I can select a drive for all 20 something slots.
My plus key was only for 7 total.
I don't have any drive to add nor do I currently need to. Which is the reason I never went to Pro yet.
I'm gonna go out on a limb and assume that if I add an 8th or N'th drive it'll have a data cap placed on it until I upgrade my key?
As of beta 14, we upped plus to 8 drives instead of 7. You'll see far more slots than your license allows, but if you assign more than 8 on plus, the array won't start.
Wouldn't it be better to only list the slots your license allows? Why the regression? Does it at least tell you why the array wont start and the actual amount of slots you are allowed?
-
Your understanding of "fill up" is correct, but as noted, they're filled in order.
You MAY not have to actually swap the disk assignments -- try listing them in the order you want them to be used in the list of Included disks ... i.e. change your "Included" list to "disk4, disk1". I'm not sure if UnRAID parses this list in order, or simply sets tatus bits r.e. the included disks. If it "looks" at the list, just listing them in the order you want them used should resolve this.
Yeah I think that's how it worked in previous unRAID versions. But in 6, I don't have the option of manually editing that field. How can I test this in unRAID 6?
-
What is it about disk4 that makes you want to prefer it over disk1?
You could just swap them in the array with New Config / Trust Parity.
Your question does not help my problem in any way but I'll answer it anyway.
Disk4 is for the shares that usually get updated daily (btsync, dropbox, developement files, etc), Disk1 is my "backup" share wich is updated rarely and has extra space, disk2 and disk3 are for all my multimedia files (movies, tv shows, music, photos, etc).
There, now you know my layout. The point is I want the array to only need to spin up disk4 and parity when these disk4 shares are used. The other three disks are used far less.
My understanding of the "Fill-up" mode was that it would continue putting new files on to the disk that has the share, and then expand to another disk when the original is full. It doesn't appear to be doing this.
-
I would like one of my shares confined to disk4 until it is nearly full and then move on to disk1. But every time the mover moves the new additions off the cache drive it recreates the share on disk1 and moves it there.
My settings for the share are; Fill-up, min free=5GB, included disks=disk1,disk4.
Is there no way to have it this way? I guess the workaround would be to remove disk1 as an included disk and just make sure disk4 never gets full?
-
Thanks for the replies and info.
Since you responded, gfjardim, I am wanting to back up your btsync container before upgrading in case it upgrades to sync 2.0. Sync 2.0 is incompatible with the old 1.4 clients which all my other devices run.
Which version does it update to?
BTSync 2.0.82
Crap ok, thanks for the answer
Save me the trouble of updating to find out it doesn't work with anything anymore. -
Thanks for the replies and info.
Since you responded, gfjardim, I am wanting to back up your btsync container before upgrading in case it upgrades to sync 2.0. Sync 2.0 is incompatible with the old 1.4 clients which all my other devices run.
Which version does it update to?
-
Is it possible to back up my existing docker before updating it? As it runs on btrfs, can I just snapshot it somehow?
-
I am just curious why there is an included and an excluded disk list in share options. Isn't having both of these redundant?
It seems if I include certain disks then it should mean the remaining are excluded should it not?
Just curious as having these two redundant options really confuses me. Is there something I am missing?
-
Received an error email last night:
Subject:
cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null
Body:
gzip: stdout: No space left on device
error: failed to compress log /var/log/libvirt/libvirtd.log.1
Any thoughts on what is happening?
Something ran out of space......Is your flash drive full?
-
Is your Dropbox staying linked on restart? I have to go to the dropbox website and allow access to my unraid server every time I restart the dropbox docker. How can I fix this?
Also, the plugin version of dropbox will tell you whether it is indexing/syncing/idle, how do you find this out with the docker?
-
That is an awesome post WeeboTech, you should sticky that somewhere with best practices for moving files between disks.
-
docker
as time passes plugins will get less and less
I would hope they do not remove plugin support in favor of docker. Both have their uses. Some things are better as a plugin and some are better as a docker.
What are some things that are better as plugins rather than dockers? There's probably something but I'm willing to bet over 90% of stuff would be better in a docker.
Really? You can't come up with this yourself? Any of the webgui addons.
-
docker
as time passes plugins will get less and less
I would hope they do not remove plugin support in favor of docker. Both have their uses. Some things are better as a plugin and some are better as a docker.
-
Too bad, the web gui dieing and everything else still working has been a problem since way back in the 4.0 days. It is still an issue on 6.0b14.
There needs to be a way to restart it as everything else remains working just fine (ssh, samba, etc).
-
I have had a lot more problems with dockers. Only tried two so far: btsync and dropbox.
-btsync will randomly turn off upnp in it's options and the docker has ports mapped that I did not set.
-dropbox requires me to "authorize" it on the dropbox website every time I restart the docker. Unacceptable.
Both in plugin forms work perfectly!
-
I would recommend against using "--remove-source-files" as you will be formatting the drive at the end anyway. No need to delete the originating drive. That way you can compare the sizes of the two drives just before you format it to make sure sizes are about the same. That's the way I'm doing it but I am using this command:
rsync -ac --progress /mnt/user/disk/* /mnt/user/disk2/
-
Yea once in out of the hospital and back home I'll check the URL, likely it just changed so should be a quick fix so long as the dependencies haven't changed.
Haha I get it, because House is your avatar. lol.
-
-
Actually mine doesn't show correctly either. This is what I see:
Memory: 8192 MB (max. installable capacity 4 GB)
I only have 4GB installed - the numbers seem reversed.
-
Cant you just use these links, I would expect that they should always pull the latest version. The problem is you don,t know what the that version is. You could put a button on the plugin that the user pushes to download the latest file. The plugin then downloads and installs it. That way it is on the user to decide when to update. For the initial install you would want to grab the latest and install.
As an alternative, create a sub-directory that the user downloads the appropriate version to. Then the plugin garbs it if it exist, installs it and then moves it to the plugin folder.
https://download-cdn.getsyncapp.com/stable/linux-i386/BitTorrent-Sync_i386.tar.gz
https://download-cdn.getsyncapp.com/stable/linux-x64/BitTorrent-Sync_x64.tar.gz
That's a good idea considering the app tells you when there is a newer version out anyway.
-
Every time I launch this Dropbox docker I have to reconnect it to my dropbox account.
-
I am trying to get btsync working but have a few questions.
I first tried the one from the hurricane repository. Certain settings such as enabling upnp would not stay on. BTSync would just disable that option again - I assume it is broken in his build?
Then I tried gfjardim's which seems to work a little better. The upnp setting stays on. I had set it up in host networking mode but it still lists port mappings on the docker page. Why is it doing this when that is not the way I set it up? Any way to remove these port mappings and put it in host mode?
Also, both were telling me the btsync app is outdated. How can I tell it to update btsync when a new version is out?
EDIT: Just learned they went pay on this app. Guess people will stop using it.
-
Quick question, how do I prevent the mover from moving my docker.img off the cache drive? Does it still ignore .files? Should I create a specific file name or folder for the image?
Also, why store all the config files on a user share? Wouldn't that prevent your drives from spinning down?
I'm new to this docker thing so forgive me if I missed something.
Save me the trouble of updating to find out it doesn't work with anything anymore.
Additional Drives Opened Up?
in General Support
Posted
Can you explain what you mean? So if I have a plus key that allows 8 slots you want it to still show 26 so that I can assign one to slot 25 and one to slot 2? What does it matter as I will still only be allowed a total of 8 slots? I don't think "slots" apply to any particular port so it doesn't really matter if I assign a disk to slot 8 or slot 25, might as well show the correct amount of slots allowed by the license.