Close to having rclone setup and runing but having a few issues....
I pretty much followed SpaceInvader's Video to the T.
So I can transfer from /mnt/disks/secure --> /mnt/disks/gdrive fine.. and /mnt/disks/gdrive matches what's on my gdrive account...
my path: \MARS\secure-cloud matches what's in /mnt/disks/secure
the Issue is when I try and transfer to the mounted cloud path from my desktop. I can transfer from the mounted cloud path TO my desktop but not vice versa.
It stalls for a couple minutes in the transfer window, then says
Now if I transfer (from windows) Test.mp4 from my desktop --> gdrive (X:) and then Go on Krusader and transfer Test.mp4 from /mnt/disks/gdrive --> /mnt/disks/secure it works fine. Just an extra step involved is all. Like so: https://i.imgur.com/I7sZgQo.png
Googling 0x8007003B....:
- "It seems the problem is not the SMB, i have mounted now the share over NFS and i get the same error. "
- "You have Intel & Realtek NIC in bonding bridge, pls try remove Intel from the bridge and plug LAN cable in Realtek only."
- "This did solve it for me. I bonded the onboard Intel with a Realtek card. Both 1gb ports.
I set them up with 802.3ad and made the adjustments on the unifi US8 switch. All seemed good and I was pulling down multiple files from the server faster than before.
Then tried to upload a 5gb file and the 0x0error started. Found this thread, dropped the bonding and now I can copy up. "
- I have managed to solve this I think and for anyone else with the same issue, this seems to have been a setting in Windows 10 that needed to be disabled in order to stop this,
"netsh interface tcp set global chimney=disabled"
"I updated the virtIO network fixed my 0x8007003B error." I re-downloaded the virtio drivers iso and did a driver update and now seems to be working."
The only two things that are failing are:
1. Transferring Test.mp4 from desktop to //MARS/Secure-Cloud
2. Transferring Test.mp4 from gdrive (X:) Mount to //MARS/Secure-cloud
Here's a screenshot of my setup now
Also when Mounting the disks drives... if they aren't empty the logs show this:
2019/12/22 13:21:15 Fatal error: Directory is not empty: /mnt/disks/gdrive If you want to mount it anyway use: --allow-non-empty option
2019/12/22 13:21:16 Fatal error: Directory is not empty: /mnt/disks/secure If you want to mount it anyway use: --allow-non-empty option
But if you try and add that flag to the script, it produces another error since --allow-non-empty' currently doesn't support fusermount which doesn't support the FUSE option apparently.