backblaze-personal-wine-container
backblaze-personal-wine-container copied to clipboard
JonathanTreffler
Bug: bzdata permissions error
I am constantly getting a dialog coming up with a Learn More / Close button. The dialog says ERR_NotificationDialog_bad_bzdata_permissions. It doesn't seem to be causing any issues with the backup running, but it keeps popping up
.
bzdata is a folder created on every storage media Backblaze backs up. Does the docker have read and write permissions on your storage path or just read ? Both is required.
I'm getting the same error message, clean install I used this image in unraid, https://hub.docker.com/r/tessypowder/backblaze-personal-wine
Permissions look as expected:
# docker exec --user app Backblaze_Personal_Backup ls -la /config/wine/dosdevices/
total 0
drwxr-xr-x 1 app app 26 Feb 10 04:17 .
drwxr-xr-x 1 app app 146 Feb 10 04:40 ..
lrwxrwxrwx 1 app app 10 Feb 10 04:17 c: -> ../drive_c
lrwxrwxrwx 1 app app 1 Feb 10 04:17 z: -> /
any thoughts?
This is what the .bzvol folder looks like on my d: drive: root@c05259643506:/drive_d/.bzvol# ls -lga total 12 drwxrwxrwx 1 users 0 Feb 10 10:29 . drwxrwxrwx 1 users 22 Jan 29 15:19 .. drwxrwxrwx 1 users 36 Jan 29 15:19 bzscratch -rw-rw-rw- 1 users 256 Jan 29 15:19 bzvol_id.xml -rwxrwxrwx 1 app 2584 Feb 10 10:29 ping_20220210_0067.log -rw-rw-rw- 1 users 268 Jan 29 15:19 README.txt root@c05259643506:/drive_d/.bzvol#
rwxr-xr-x 1 app 12 Jan 29 15:17 . drwxr-xr-x 1 app 168 Feb 9 18:20 .. lrwxrwxrwx 1 app 10 Jan 29 14:53 c: -> ../drive_c lrwxrwxrwx 1 app 9 Jan 29 15:17 d: -> /drive_d/ lrwxrwxrwx 1 app 1 Jan 29 14:53 z: -> / root@c05259643506:/config/wine/dosdevices#
From the container console, I can create files and remove them on D: so it seems to have access.
I'm getting the same error message, clean install I used this image in unraid, https://hub.docker.com/r/tessypowder/backblaze-personal-wine
Permissions look as expected:
# docker exec --user app Backblaze_Personal_Backup ls -la /config/wine/dosdevices/ total 0 drwxr-xr-x 1 app app 26 Feb 10 04:17 . drwxr-xr-x 1 app app 146 Feb 10 04:40 .. lrwxrwxrwx 1 app app 10 Feb 10 04:17 c: -> ../drive_c lrwxrwxrwx 1 app app 1 Feb 10 04:17 z: -> /any thoughts?
Did you follow all installation steps in the Installation section of the README ? You don't seem to have configured the d drive at all.
I did and I did have a D: drive.
On Feb 16, 2022, at 2:05 PM, Jonathan Treffler @.***> wrote:
Did you follow all installation steps in the Installation section of the README ? You don't seem to have configured the d drive at all.
Sorry @monteroman, I meant @hkrob I edited my comment immediately after commenting to include a quote, but since you seem to be reading this via mail, you never saw that change.
rwxr-xr-x 1 app 12 Jan 29 15:17 . drwxr-xr-x 1 app 168 Feb 9 18:20 .. lrwxrwxrwx 1 app 10 Jan 29 14:53 c: -> ../drive_c lrwxrwxrwx 1 app 9 Jan 29 15:17 d: -> /drive_d/ lrwxrwxrwx 1 app 1 Jan 29 14:53 z: -> / root@c05259643506:/config/wine/dosdevices#
Your d drive setup is correct.
From the container console, I can create files and remove them on D: so it seems to have access.
In case you are using Unraid:
With which user are you logged into the console? If you are using the built-in Unraid Console for the docker, you are probably root. Try logging into the console through the general unraid system console and logging into the docker console from there using:
docker exec --user app -it backblaze_personal_backup bash
Then test the permissions again.
I’m using Unraid so it’s running as a Docker container.
On Feb 16, 2022, at 2:11 PM, Jonathan Treffler @.***> wrote:
@monteroman https://github.com/monteroman Which OS are you using?
— Reply to this email directly, view it on GitHub https://github.com/JonathanTreffler/backblaze-personal-wine-container/issues/6#issuecomment-1042055745, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJS2IRET3NF6WXTOX6NZM3U3PZFPANCNFSM5N6Q5BNQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.
Hi, Yes I followed the README.
Maybe this helps?
`
root@Corsair:~# docker exec --user app -it Backblaze_Personal_Backup bash
bash: /dev/null/.bashrc: Not a directory
app@d22396fd813c:/tmp$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop2 83886080 45836588 35694996 57% /
tmpfs 65536 0 65536 0% /dev
tmpfs 16413284 0 16413284 0% /sys/fs/cgroup
shm 65536 0 65536 0% /dev/shm
rootfs 16338576 1587032 14751544 10% /usr/sbin/docker-init
shfs 1220362952 730452156 489910796 60% /config
/dev/loop2 83886080 45836588 35694996 57% /etc/hosts
tmpfs 16413284 0 16413284 0% /proc/acpi
tmpfs 16413284 0 16413284 0% /sys/firmware
app@d22396fd813c:/config$ ls -la /config/wine/dosdevices
total 0
drwxr-xr-x 1 app app 56 Feb 10 08:04 .
drwxr-xr-x 1 app app 146 Feb 16 20:06 ..
lrwxrwxrwx 1 app app 10 Feb 10 04:17 c: -> ../drive_c
lrwxrwxrwx 1 app app 9 Feb 10 07:53 d: -> /drive_d/
lrwxrwxrwx 1 app app 9 Feb 10 08:04 e: -> /drive_e/
lrwxrwxrwx 1 app app 9 Feb 10 08:04 f: -> /drive_f/
lrwxrwxrwx 1 app app 1 Feb 10 04:17 z: -> /
`
I've been wondering about this too. I assume it's referring to this bzdata folder:
drwxr-xr-x 1 app app 456 Feb 19 20:08 bzdata
root@b4089400642d:/config/wine/drive_c/ProgramData/Backblaze#
I increased the permissions using chmod -R 777 and am waiting to see if the error still happens.
UPDATE: Error still happens. Haven't yet found which (if any) of the many, many Backblaze log files might shed more light on this error...
Hi, Yes I followed the README.
Maybe this helps?
`
root@Corsair:~# docker exec --user app -it Backblaze_Personal_Backup bash bash: /dev/null/.bashrc: Not a directory app@d22396fd813c:/tmp$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/loop2 83886080 45836588 35694996 57% / tmpfs 65536 0 65536 0% /dev tmpfs 16413284 0 16413284 0% /sys/fs/cgroup shm 65536 0 65536 0% /dev/shm rootfs 16338576 1587032 14751544 10% /usr/sbin/docker-init shfs 1220362952 730452156 489910796 60% /config /dev/loop2 83886080 45836588 35694996 57% /etc/hosts tmpfs 16413284 0 16413284 0% /proc/acpi tmpfs 16413284 0 16413284 0% /sys/firmware app@d22396fd813c:/config$ ls -la /config/wine/dosdevices total 0 drwxr-xr-x 1 app app 56 Feb 10 08:04 . drwxr-xr-x 1 app app 146 Feb 16 20:06 .. lrwxrwxrwx 1 app app 10 Feb 10 04:17 c: -> ../drive_c lrwxrwxrwx 1 app app 9 Feb 10 07:53 d: -> /drive_d/ lrwxrwxrwx 1 app app 9 Feb 10 08:04 e: -> /drive_e/ lrwxrwxrwx 1 app app 9 Feb 10 08:04 f: -> /drive_f/ lrwxrwxrwx 1 app app 1 Feb 10 04:17 z: -> /`
This time your drive setup looks correct.
@monteroman Unfortunately I don't have an idea why this happens, especially since we both use unraid so our folder permissions should be very similar. Currently, I have no way of reproducing the error and therefore can't debug it. If you find a solution it would be great if could share it in this issue so I can add it to the Readme. Good luck debugging :)
FYI I have the same issue and backups appear to be happening correctly.
I am having this error too. You say that it's supposed to create the bzvol on all drives that are being backed up?
When I check my array, only 6 out of the 15 drives have bzvol's on them. I have all my drives being backed up. I wonder if this is related. I wouldn't even know how to get them created though, unless copy/pasting them to the other drives would work?
Anyone else look at your drives, and see if it shows when you browse your array via disk# with something like Krusader if you have some disks with bzvol's not on them. (Drive 14 in this case has 34GBs of freespace left.)
I am having this error too. You say that it's supposed to create the bzvol on all drives that are being backed up?
When I check my array, only 6 out of the 15 drives have bzvol's on them. I have all my drives being backed up. I wonder if this is related. I wouldn't even know how to get them created though, unless copy/pasting them to the other drives would work?
Anyone else look at your drives, and see if it shows when you browse your array via disk# with something like Krusader if you have some disks with bzvol's not on them. (Drive 14 in this case has 34GBs of freespace left.)
Backblaze does not see the individual disks, it sees the Unraid Array as one disk. bzvol being only on some disks is just how unraid works and is not the problem.
Hi, I have the same issue. The d: drive is working fine and also has a .bzvol folder with files in it.
But the c: drive does not have a .bzvol folder - is it possible that this causes the error message?
But the c: drive does not have a .bzvol folder - is it possible that this causes the error message?
That could very well be, but I cannot test this right now: Have you tried disabling the backup of the C: drive? (Can you even do that ?)
I am having this issue as well (Also using Unraid). I can't see anyone posting the permissions of the filesystem that they are backing up from outside the container. When I checked mine, all 4 drives had a .bzvol directory with only r-x in Krusader (I didn't drop back in to the CLI). I couldn't change the permissions in Krusader however the New Permissions tool made them all rwx. I will let you know how it goes.
I tried excluding the backblaze app folder from backups. Didn’t work.
Here is what I did to solve this for Unraid installations (not all the steps are relevant to fixing this, but just wanted to fully list what I did)
- Delete container and image
- In the main Unraid CLI, run
rm -rf /mnt/user/appdata/backblaze_personal_backup/ - Prepare to install this docker again
- In settings, change name from "Backblaze_Personal_Backup" to "backblaze_personal_backup"
- Change the dimensions of the VNC to 600 x 600 (I saw a warning in the logs about the display dimensions needing to be divisible by 4)
- Make sure your timezone matches with your Unraid timezone
- Run all of the steps in the readme
- IMPORTANT - Before logging in for the first time to Backblaze, make sure to run Steps 9 and 10 in the readme (I don't have proof, but my guess is Backblaze maps the available drives for backup on first login and never again, so if you skip ahead and then try running Steps 9 and 10, it won't work)
- Let Backblaze analyze the available files (your drive should now be "visible" to Backblaze)
- Profit
So steps 8, 9 (and of course 10 :wink:) are the mandatory steps for the fix ?
@JonathanTreffler Yes, the issue for me was order of operations. The ERR_NotificationDialog_bad_bzdata_permissions popup still appears for me, but I am able to back up my drives with no issue
@JonathanTreffler Yes, the issue for me was order of operations. The ERR_NotificationDialog_bad_bzdata_permissions popup still appears for me, but I am able to back up my drives with no issue
Ok, so now we know why the popup broke the backup functionality for some and didn't for others. We still don't exactly know why the popup appears for some users, but it is not very critical as the rest works. Are there any tweaks to the installation guide you would propose or does it cover the fix already as long as the steps are run in the order as they are written?
@JonathanTreffler I would say your guide works as you say as long as it is followed in order (you make this clear enough imo; I just jumped ahead).
Maybe adding a suggestion for Unraid users to start from scratch by doing:
- Delete container and image
- In the main Unraid CLI, run rm -rf /mnt/user/appdata/backblaze_personal_backup/
might help some. I can prepare a minor PR to add to the readme if you'd like
Here is what I did to solve this for Unraid installations (not all the steps are relevant to fixing this, but just wanted to fully list what I did)
1. Delete container and image 2. In the main Unraid CLI, run `rm -rf /mnt/user/appdata/backblaze_personal_backup/` 3. Prepare to install this docker again 4. In settings, change name from "Backblaze_Personal_Backup" to "backblaze_personal_backup" 5. Change the dimensions of the VNC to 600 x 600 (I saw a warning in the logs about the display dimensions needing to be divisible by 4) 6. Make sure your timezone matches with your Unraid timezone 7. Run all of the steps in the readme 8. IMPORTANT - Before logging in for the first time to Backblaze, make sure to run Steps 9 and 10 in the readme (I don't have proof, but my guess is Backblaze maps the available drives for backup on first login and never again, so if you skip ahead and then try running Steps 9 and 10, it won't work) 9. Let Backblaze analyze the available files (your drive should now be "visible" to Backblaze) 10. Profit
I can confirm I have the error message as well, running in Unraid. Did a complete reinstall following the above instruction, and the error message still appears. My way of handling it is to restart the container every day, running good so far.
So my initial install I had to use winecfg as root and was able to map the drive. Before I couldn't access the unraid array to be backed up. I am reading this new issue here. I just manually created the .bzvol through the console on the drive c through config/wine/drive_c then chown 777 .bzvol I am waiting to see if that fixes that error message. My other concern. Why in god's green earth is this using so much ram. It is up to 9 gigs now. I am about to restart the docker.
