Gets stuck analyzing D drive

[shedunraid]

I have tried a few different things..

If i have "/mnt/user/" as the D Drive.. on install BackBlaze will get totally stuck on Analyzing (at arround 99%)

If i delete the container, reinstall and set "/mnt/user/SOME FOLDER" it will work fine.

If I do option 2, then change back to "/mnt/user/" re-start the container, add the D drive in BB settings... it will try to analyze but get stuck again at almost done...

Any ideas what might be causing this?

Thanks :)

[lnxd]

Strange, I was checking as I was experiencing the exact same thing, but I worked out the cause in my situation. Those directories suggest you're likely using this with Unraid, if so, try the following:

1. SSH into Unraid
2. Run lsof -r 1 -w /mnt/user | grep drive_d
3. Let it run for at least a minute or so, if you start to see output it's still scanning.

The bz scanner doesn't seem to like processing thousands of little files, and unfortunately even though I've excluded those directories manually, it scans them anyway.

#24
#10

[shedunraid]

thanks for that, really helped. I checked and it was still analyzing files, i left it for ages.. and i mean like 8 hours.. and it eventually finished analysing.

I have had a few "bad_bzdata_permissions" pop ups, but have used the following method to deal with:
1 - Goto settings in BackBlaze
2 - Check the issues tab
3 - Exlude the files / folders that have been marked in "issues"
4 - restarted the container - no more issues.

One question i have, could any point me in the direction to be able to change which version of backblaze is installed,

I wanted to give the BETA a go as it seems it may have patched a few of the issues I am having, just unsure how to change which version is installed in wine.

Thanks :) - @JonathanTreffler thanks so much for your time on this project!!

[JonathanTreffler]

One question i have, could any point me in the direction to be able to change which version of backblaze is installed,

You can download a specific version of the Backblaze Client as described here: #7 (comment)

Installing newer versions or downgrading the version is done by downloading the installer into a location the docker has access to (or downloading it using curl or wget from the docker terminal) and running it using the following command in the docker terminal with the path replaced:
wine64 "/path/from/inside/docker/container/<filename>.exe"

Then follow the steps of the installer instructions like on the first install.

[smccloud]

I ran into this issue as well, I gave up and map my cache and each drive as their own volume. My current startup command (as posted by UNRAID when I update) is as follows
docker run -d --name='backblaze_personal_backup' --net='mybridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="BB-8" -e HOST_CONTAINERNAME="backblaze_personal_backup" -e 'SECURE_CONNECTION'='0' -e 'TZ'='America/Chicago' -e 'DISPLAY_WIDTH'='1024' -e 'DISPLAY_HEIGHT'='800' -e 'VNC_PASSWORD'='' -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'FORCE_LATEST_UPDATE'='True' -e 'X11VNC_EXTRA_OPTS'='' -e 'ENABLE_CJK_FONT'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5800]/' -l net.unraid.docker.icon='https://assets-global.website-files.com/63d32de856f6323a43a277f2/64b1ab4aa5aef8291e9291ab_Favicon.png' -p '7820:5800/tcp' -p '7920:5900/tcp' -v '/mnt/cache/':'/drive_d/':'rw' -v '/mnt/cache/appdata/backblaze_personal_backup':'/config':'rw' -v '/mnt/disk1/':'/drive_e/':'rw' -v '/mnt/disk2/':'/drive_f/':'rw' -v '/mnt/disk3/':'/drive_g/':'rw' -v '/mnt/disk4/':'/drive_h/':'rw' -v '/mnt/disk5/':'/drive_i/':'rw' -v '/mnt/disk6/':'/drive_j/':'rw' -v '/mnt/disk7/':'/drive_k/':'rw' -v '/mnt/disk8/':'/drive_l/':'rw' -v '/mnt/disk9/':'/drive_m/':'rw' -v '/dev/shm/cache-bzvol':'/drive_d/.bzvol':'rw' --init 'tessypowder/backblaze-personal-wine'
You'll notice I mount /drive_d/.bzvol in /dev/shm as well to save SSD writes.