stavr0s13

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by stavr0s13

  1. I would specify a disk drive, would be easier! Thanks for your help!!
  2. In my case should be DropboxTest right? When i go to \\192.168.1.250\DropboxTest all i see is folders etc,var,root,home and more. but when i do ls /mnt/user/DropboxTest it gives me back the dropbox folders.. As for the status. inside the docker at /usr/local/bin there is the dropbox.py. normaly when you do dropbox.py status. it spits out the status. but not its says python3 no suchfile or dir. (i remember it was working in the past)
  3. Ok i'll write exactly what i'm doing to verify. The script i use is this. I've noticed you had a "#" in front of DROPBOXSIZE. Removed it. I've also delete /mnt/user/appdata/dropbox and delete Dropbox docker from previously installed apps on CA. /mnt/user/DropboxTest is not on share list and it doesn't exist now #!/bin/bash # Script (partially commented out) for moving dropbox to a loopback image file # This gets around the restriction of Dropbox now only supporting ext4 on Linux # (see https://popey.com/blog/posts/fixing-broken-dropbox-sync-support.html) # # we need to leave active the bit about mounting the image at array start # Location of the image which will contain the new ext4 partition # Typically this would be on the cache but this is not mandatory. DROPBOXDISK=/mnt/user/ DROPBOXFILE=$DROPBOXDISK/DropboxTest.img # Current location of my existing Dropbox folder # (using User Share means we do not need t/ know device currently used) DROPBOXHOME=/mnt/user/DropboxTest # 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="2500G" # Start by making sure the disk to be used is present if [ ! -e $DROPBOXDISK ]; then logger -s "ERROR: $DROPBOXDISK disk not present" exit -1 else # ...and that we have not already followed this process if [ -e $DROPBOXFILE ]; then logger -s "Found existing $DROPBOXFILE" else # 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. sudo dd if=/dev/zero of="$DROPBOXFILE" bs=1 count=0 seek="$DROPBOXSIZE" # Format it ext4, because Dropbox Inc. says so sudo mkfs.ext4 "$DROPBOXFILE" # Make a new Dropbox folder to replace the old one. This will be the mount point # under which the sparse image file will be mounted. We want to make sure it is # on the same device as the image file. sudo mkdir $DROPBOXDISK/`basename $DROPBOXHOME` # Set ownership and permissions on the new folder so Dropbox has access # (generic Linux case) # sudo chown $(id -un) "$DROPBOXHOME" # sudo chgrp $(id -gn) "$DROPBOXHOME" # (Unraid specific case) sudo chown nobody "$DROPBOXHOME" sudo chgrp users "$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' sudo chattr +i "$DROPBOXHOME" # Mount the sparse file at the dropbox mount point sudo mount -o loop "$DROPBOXFILE" "$DROPBOXHOME" # Let's unmount it as we normally want to use fstab entry sudo umount "$DROPBOXHOME" fi fi # Create a line in our /etc/fstab so this gets mounted on every boot up status=`grep -o "$DROPBOXHOME" /etc/fstab` if [ $? -eq 0 ]; then logger -s "Entry for $DROPBOXHOME already present in /etc/fstab" else echo "$DROPBOXFILE" "$DROPBOXHOME" ext4 loop,defaults,rw,relatime,exec,user_xattr 0 0 | sudo tee -a /etc/fstab logger -s "Entry for $DROPBOXHOME added to /etcfstab" fi # This will mount as per the fstab sudo mount -a logger -s "$DROPBOXFILE mounted at $DROPBOXHOME" exit 0 After running this script, DropboxTest folder created and DropboxTest.img file also created under /mnt/user/ Installing Dropbox Docker from CA now. /mnt/user/appdata/dropbox is the config folder /mnt/user/DropboxTest is the data folder Pulled image, go to log, copy link and allow access. Computer is now linked. After that i see the log and it looks like its restarting. twice. then i get a bunch of WARNING:tornado.access:404 HEAD /blocks/225260633/YgzjUPL0SS1U22ovWyju6qgqHYqJb1uNMuvRRotfWH4 (172.17.0.1) 11.81ms Ok, lets restart the docker. Now looks like its working fine. running du -sh /mnt/user/DropboxTest shows the size increasing. But after some minutes i get again this WARNINGs after restarting the docker by itself twice then sits there spitting WARNINGs, but file size still increasing. Now, how should i setup this folder so i can access it via SMB and how i can see the status of the dropbox syncing. I know there is the dropbox.py somewhere inside but i dont know how to use it. I tried to provide as more info as i could to help you instead of guessing! Thanks
  4. Just to be sure. You pointed your docker to /mnt/cache/Dropbox right? Does it working as it should? Or did you had any problems? And lastly. is it safe to remove the lines that does the move from old dropbox home to the new? Sorry for the maybe stupid questions but i'm fairly new to linux terminal ecosystem.
  5. Hey ken-ji , Are you stillworking on it or it is dropped? Is there any other alternatives for true 2 way sync between dropbox <-> unraid? How can i set a VM doing the sync? As i read somewhere someone done it. Thanks!!
  6. Thanks for your time, i give it one more shot and if i won't make it as i want.. i'll go with the "trick" option i wrote about that seems to work! Thanks again
  7. Hmm, no problem with that, i have one more question before i give up also on this and try to figure out how to make my windows pc dropbox app to point on a NAS drive (i found some method online that tricks it, dunno if it still works.EDIT: *http://www.rob-st.com/2016/11/17/setup-dropbox-nas-shared-network-drive/* this works.just did it, i think i'm gonna go with this solution i guess. My Computer stays on 24/7, but even a little donwtime would only have effect if i have new files added to DB and wont sync until i turn this on. but thats not a big deal) When i install db docker as nobody and have the share public i can read/write from other local computers. If i make the share private and i TRY to log in with a different user lets say UserA. I dont have permission. If i install the docker as UserA i CAN access it from another computer using UserA logins. The thing is that i want to have 2 or 3 users accessing the dropbox folder with different permissions each one. e.g Me - full permissions to read/write on all dropbox folder Media server - Read Only permissions to Music and tv shows folder inside dropbox My Mom - read/write to her folder inside dropbox I know that for the specific folder permission will have to make extra shares, thats ok But dropbox folder can be accessed only from the install user. Can you solve this for me? I guess i wont be turning on and off the NAS so frequenlty after i set it up Thanks
  8. Any fix for the relink after reboot problem?