jowi

I've installed this using the excellent video i can get into the webui etc, everything seems to work. I gave it an ip address of 192.168.1.10, and i'm using the cloudflare dns (1.1.1.1 / 1.0.0.1). Now, if i change my router's DNS (Netgear WNDR3700) to use 192.168.1.10, i can't browse to any sites... it just won't work. If i return the router to 1.1.1.1/1.0.0.1 and configure my mac maually so it uses pihole as it's DNS server, i can browse perfectly, and i can see in pihole's query log everything is also logged etc. so it does work... But why won't it work if i configure it on my router? I did not give pihole a static ip adress IN the router, is that mandatory? I had problems doing that; i have to enter the mac address, which is the same as unraid server itself... it won't allow me to do that. What am i missing?

Tried it again... now Dropbox thought i deleted all contents and it was removing everything on all my synced devices.... luckily i had a backup... Not gonna try this again unless someone makes a good foolproof tutorial on this that actually works. Back to the ext4 usb stick for me.

So if i understand correctly, the .dropbox.img file (sparsefile, formatted as ext4) is an actual file that persists somewhere on the array or ssd in another location then were Dropbox archive is. Lets say it is /mnt/disk1/temp/.dropbox.img Then we have a 2nd location, the actual location you enter in Dropbox, where Dropbox will sync its files to, lets say this is /mnt/cache/Dropbox And the .dropbox.img file is then mounted at /mnt/cache/Dropbox? So that /mnt/cache/Dropbox folder will basically show the contents of the .img file? (or the other way around) So Dropbox reads and writes to and from /mnt/cache/Dropbox but actually it is the .img file that will contain the data?

I did use the shebang line after the first attempt, and i did save it using np++. Not sure about the Linux line endings, np++ just shows CRLF. I also think the instructions (!) are too complicated; why make a backup and rsync back ets. Just stop Dropbox, remove the contents, create the image/loopback and let Dropbox sync itself to it on startup, would be simpler.

Depends on where you currently have stored Dropbox... mine was on a unassigned device. Also depends on where you want the dropbox to be afterwards. In my case, on my /mnt/cache in a Dropbox folder. And yes, commands placed after each other in a file, is called a script.

Jeezes what a f$E^&%^&* mess this... it did not work, but now i got a .dropbox.img file i can not delete. Help? *edit* after 3.5 heart attacks i found that the folder the .img was in, had it's 'i' attribute set... removed that, and now it's gone... *wipes sweat of face* I'm gonna use the usb stick. That is something i understand

Entering the commands by hand one by one seems to do the trick...

I can't get that script to work at all. I put it in a .sh file, but it crashes on the empty lines, if i remove these, i get errors like: dd: invalid number: ‘10G\r\r’ etc... How do you run this? # Location of the image which will contain the new ext4 partition DROPBOXFILE=/mnt/cache/Dropbox/.dropbox.img # Current location of my Dropbox folder DROPBOXHOME=/mnt/disks/SanDisk32GUSB/Dropbox # Where we will copy the folder to. If you have little space, you could make this # a folder on a USB drive DROPBOXBACKUP=/mnt/cache/Temp/old_Dropbox # What size is the Dropbox image file going to be. It makes sense to set this # to whatever the capacity of your Dropbox account is, or a little more. DROPBOXSIZE="10G" # Create a 'sparse' file which will start out small and grow to the maximum # size defined above. So we don't eat all that space immediately. dd if=/dev/zero of="$DROPBOXFILE" bs=1 count=0 seek="$DROPBOXSIZE" # Format it ext4, because Dropbox Inc. says so mkfs.ext4 "$DROPBOXFILE" # Move the current Dropbox folder to the backup location mv "$DROPBOXHOME" "$DROPBOXBACKUP" # Make a new Dropbox folder to replace the old one. This will be the mount point # under which the sparse file will be mounted mkdir "$DROPBOXHOME" # Make sure the mount point can't be written to if for some reason the partition # doesn't get mounted. We don't want dropbox to see an empty folder and think 'yay, let's delete # all his files because this folder is empty, that must be what they want' chattr +i "$DROPBOXHOME" # Mount the sparse file at the dropbox mount point mount -o loop "$DROPBOXFILE" "$DROPBOXHOME" # Copy the files from the existing dropbox folder to the new one, which will put them # inside the sparse file. You should see the file grow as this runs. rsync -a "$DROPBOXBACKUP"/ "$DROPBOXHOME"/ # Create a line in our /etc/fstab so this gets mounted on every boot up echo "$DROPBOXFILE" "$DROPBOXHOME" ext4 loop,defaults,rw,relatime,exec,user_xattr 0 0 | sudo tee -a /etc/fstab # Let's unmount it so we can make sure the above line worked umount "$DROPBOXHOME" # This will mount as per the fstab mount -a # Set ownership and permissions on the new folder so Dropbox has access chown $(id -un) "$DROPBOXHOME" chgrp $(id -gn) "$DROPBOXHOME" ./convert_dropbox.sh: line 1: #: command not found ./convert_dropbox.sh: line 2: $'\r': command not found ./convert_dropbox.sh: line 3: $'\r': command not found ./convert_dropbox.sh: line 4: $'\r': command not found ./convert_dropbox.sh: line 6: $'\r': command not found ./convert_dropbox.sh: line 7: $'\r': command not found ./convert_dropbox.sh: line 8: $'\r': command not found ./convert_dropbox.sh: line 10: $'\r': command not found ./convert_dropbox.sh: line 12: $'\r': command not found ./convert_dropbox.sh: line 13: $'\r': command not found ./convert_dropbox.sh: line 14: $'\r': command not found ./convert_dropbox.sh: line 16: $'\r': command not found dd: invalid number: ‘’ ./convert_dropbox.sh: line 18: $'\r': command not found ./convert_dropbox.sh: line 20: $'\r': command not found mke2fs 1.44.0 (7-Mar-2018) ' on device ''alid blocks ' ./convert_dropbox.sh: line 22: $'\r': command not found ./convert_dropbox.sh: line 24: $'\r': command not found mv: target ''$'\r' is not a directory ./convert_dropbox.sh: line 26: $'\r': command not found ./convert_dropbox.sh: line 28: $'\r': command not found mkdir: cannot create directory ‘’: No such file or directory ./convert_dropbox.sh: line 30: $'\r': command not found ./convert_dropbox.sh: line 32: $'\r': command not found chattr: No such file or directory while trying to stat ./convert_dropbox.sh: line 34: $'\r': command not found ./convert_dropbox.sh: line 36: $'\r': command not found mount: bad usage Try 'mount --help' for more information. ./convert_dropbox.sh: line 38: $'\r': command not found ./convert_dropbox.sh: line 40: $'\r': command not found rsync: failed to set times on "/mnt/cache/Temp/\#015/.": Operation not permitted (1) rsync: symlink "/mnt/cache/Temp/\#015/init" -> "/sbin/init" failed: Operation not permitted (1) rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/bin" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/boot" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/dev" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: mkstemp "/mnt/cache/Temp/\#015/.wget-hsts.ZE4WcX" failed: Operation not permitted (1) rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/etc" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/home" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/lib" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/lib64" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/mnt/cache/Temp/\#015/mnt" failed: Operation not permitted (1) *** Skipping any contents from this failed directory ***

I assume you changed the DROPBOXFILE="$HOME"/.dropbox.img etc to some other location?

Yes, i've read about that construction as well, but my unix knowledge is not very good... but that would be an even better solution please post a step-by-step instruction if you get it working!

I've added a USB stick using the unassigned devices plugin, formatted it as EXT4, pointed the docker to it and voila, dropbox is now running Since Dropbox is constantly synced between all different devices, i don't need it to persists on the array anyway, but it is nice to have acces to it from within UNRAID.

Thanks! I know these serverboards can be picky regarding memory, cpu's etc. so it's good to know this shouldn't be a problem, before i order it

I've been using a 250GB SATA SSD for some time now, and now i'm upgrading my UNRAID server with a Xeon CPU (in stead of an core-i3) and 16GB in stead of 4GB memory, so i can run some VM's as well. Now i do i want to get a bigger SSD/cache drive to run the VM's (and dockers etc) from, so i was thinking of getting a 1TB SSD. I understand that the M.2 interface is the way to go these days, so i was thinking of getting an M.2 SSD, using a PCIe to M.2 adapter, since the X9SCM doesn't have M.2 slots on the motherboard natively. Has anyone used this in a X9SCM? Will it work without any problems? I don't have to boot from it, it is just ment as SSD/cache in UNRAID.

Is it possible to (re)format my SSD to ext4 in UNRAID? That would solve it i assume?

Thanks, i'll try that. Another thing i noticed; i'm using a python postprocessing script in sabnzbd that renames the downloaded file, adds some info from thetvdb, and moves it to the right place in the array, refreshes sonarr's history so sonarr knows the new name i gave it, and last but not least, i'm sending myself an email that episode x from series y is downloaded. Everything seems to work, except for sending the email... it looks like it gets sent without errors or exceptions, using smtp, ssl (port 587, with correct credentials etc) but it is not getting delivered, i never get the email? Is there something i need to change in my code now i'm sending from inside this vpn? *edit* seems to be a provider issue... i've been using a fake email adres as sender, e.g. [email protected]. I think the ISP changed something so you can't do that anymore; if i'm using my actual, real email address it works... probably an anti spam countermeasure or something.

Thanks. I tried the method of checking the ip address under Q2, if i do this for the sabnzbd-vpn docker, i get the ip address my VPN provider gave me, so that seems ok. But if i do the same for the Sonarr docker, where i've setup sonarr to use the sabnzbd-vpn as proxy, it gives me the ip adress of my original ISP... or is this correct?

I've set this up using a custom VPN provider, and after some minor issues it looks like it is working. VPN is enabled, i can see in the logging the VPN is set up, and sabnzbd is actually downloading... i'm also using the VPN created here for e.g. sonarr, by setting sonarr's proxy to vpn's ip:8118. Sonarr works as well as it seems. But is there a way to make sure it i actually working as it should? No dns leaking etc? Other tests? i mean sab is downloading, but i can't really tell if it is actually doing it over the vpn or not?

Funny thing is, i had it working on XFS just a few days ago, after updating libc... but now it complains about the filesystem again.

Just rebooted the server, and now dropbox is again complaining about the diskformat (my ssd is xfs) which is weird, it updated everything 2 days ago and was syncing as well. It won't sync now...

I followed the install howto in the link. So just downloaded the package and then upgradepkg --install-new glibc-2.23-x86_64-4_slack14.2.txz.

I've installed the Dropbox folder on a XFS formatted SSD, and manually upgraded the glibc in the docker to 2.23 using https://slackware.pkgs.org/14.2/slackware-patches-x86_64/glibc-2.23-x86_64-4_slack14.2.txz.html since Dropbox logging was also complaining that it needed a glibc version >2.19 (docker has 2.17) and now it is working again.

O, so the safest thing to do is uninstall nerdpack, upgrade unraid, and re-install nerdpack so nerdpack will be updated as well?

Possibly a stupid question; but i'm running unraid 6.5.3 and i've read that upgrading to 6.6.3 will break the nerdpack, is that correct? The advice on the upgrade topic is to remove nerdpack, but i need nerdpack for several things, git, python, perl, etc... So does this mean i can not upgrade to unraid 6.6.3?

Got a reaction back from MyMedia: "This definitely could be possible but is not implemented yet. We could trigger IFTTT actions on key track actions from MyMedia. We will have a think and get back to you"

No, it;s not expensive at all, on the contrary i'll see if i can contact support.