detz
Members-
Posts
230 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
detz's Achievements
Explorer (4/14)
2
Reputation
-
This looks interesting, what do people use this for?
-
Thanks, I re-read that so many times because I thought I was crazy and missed something, turns out I was. 🙂 I did figure out from another one of your posts I can just make a new mount point in the container and use that instead of media so I just make one my bucket name and that works too. Edit: Oh, i didn't see the readme, I was looking at the FAQ and it's not mentioned there: https://github.com/binhex/documentation/blob/master/docker/faq/rclone.md
-
Is it possible to even use B2 with this setup as the buckets have to be unique? No matter what I set it's going to try and upload to b2:/media/.... and I can't make a media bucket as that's already take in b2. What am I missing here?
-
Own two license, can I easily move the pro key to my plus server?
detz replied to detz's topic in General Support
Thanks, so I think the best course of actions is Buy a new usb drive Setup the new drive, copy the config file from the Plus drive (the config/setup I want) Copy the key from the pro usb drive Start the array and have it reassign this key to the new usb drive. -
Own two license, can I easily move the pro key to my plus server?
detz replied to detz's topic in General Support
So I don't want to lose a license, I feel like if I transfer the Pro to the Plus drive I will lose the Plus license. Maybe I should just get a new usb drive and transfer the pro to that? The problem is the plus license is the one in my main machine now and it has the drive limit so to avoid a similar issue I want to just use my pro license instead. -
Because of this: I would like to use the pro license that I have, is there an easy way to do this to keep everything as it is on the server just upgrade the license to my pro license? I'd also like to use the plus usb drive as it's newer and larger so I would prefer to not just copy things over to the older pro device
-
After reboot, "Too many attached devices. Please consider upgrading your"
detz replied to detz's topic in General Support
Yes, I get that, but that's not my question. I was able to start the array multiple times with these 13 devices while I was home replacing the drive and it allowed it. Now it won't when I'm not physically there, why was this? Also, I would think a basic warning when stopping the array "You have too many devices connected, you will not be able to start the array...." would be shown to prevent this situation. Now my array is stopped with no way to start it again since I'm not physically at home so I have no way to get my files. The worst part is I have a pro license too, at home, not in use...I'm starting to wonder if it's time to look at other options. Besides paying for an extended license which I don't need is there any way to "remove" a device so I can start this array back up? -
So I had a issue where two drives "failed" and I had to rush to replace them I put a new drive in and put the old one attached as a usb drive so I could copy files over, reboot and eventually rebuilt the new drive with data. My parity drive was still broken though so I just stopped the array to start to pre-clear it and now I can't start it again. I get what the message is but I'm confused on WHY it let me start it about six times over the past weeks and now all of a sudden it won't. I'm physically away from the server for a week now and can't just unplug something, is there a way I can get this back online (I need to access these files) without physically being there? Why did this just happen, it's frustrating it let me stop the array knowing I couldn't start it back again without any changes!! cylon-diagnostics-20210828-1904.zip
-
The rebuild went fine and just like the emulated drive it was missing a lot of files. I used an external usb HD base to connect up the old drive and I've been copying files over for days now (so slow...). All the files appear to be fine on the old drive which makes this even more confusing but this approach does seem to be working. Is there anything we can do to protect against this? Is this common, seems odd it's this easy to lose data in a protected array
-
new drive is rebuilding and I mounted the old disk and it's ready for copying once the rebuild is done. I did have to change the UUID in the settings for the mount to work. I'll report back tomorrow when the rebuild is done. Is there a way to rsync easily to just copy everything over or is this going to be a slow single dir move process?
-
Stopped array again, changed to 'no device' in dropdown (didn't start array) and the drive was mounted in UD correctly. I can browse the drive fine in ssh. I copied some files around and scp'd one locally and it was fine. Again, not sure if everything is there but it appears to be working. I didn't mount it read-only but it doesn't appear to be re-built. cylon-diagnostics-20210818-0321.zip
-
I stopped the array and unassigned it (using the dropdown) I then mounted it in UD and browsed around in ssh (pushed the Mount button as it showed up down there when I unselected it above) I didn't start the array though. I then re-selected it back in the dropdown "added it back" and started the array Its unmountable