anethema

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About anethema

  • Rank
    Newbie
  1. Awesome I also still cannot run docker containers on br0 either. It will start causing macvlan errors in syslog and eventually kernel panic. The problem also followed me from my R510 to my R720 if that helps at all.
  2. Well just reporting back that mounting as rclone works MUCH better. Restores at full speed. The checking files and anything folder related is pretty slow, but the transfer itself is fast. So it seems like its a problem with cloudberry itself, in their B2 implementation.
  3. I'm not holding out hope for it to be much faster, as just the repository sync is on track to take two full days. I will see about the restore once the sync is done, but it really does seem like something is broken with cloudberry itself. Maybe some setting or something, but it DOES transfer for me, just horribly slowly, and I've now verified on the unraid machine itself that it works very quickly in unraid itself.
  4. I'm actually trying another route now. I have my B2 bucket mounted as a folder in unraid using rclone. I can copy files out of the FUSE folder at full line speed of my network, so it is def not backblaze being slow. The folder structure is just synchronizing now in cloudberry so we will see how a restore works with that.
  5. Maybe but it is taking like 5mins to download a 100kb .png file. It really seems to be just going very slow.
  6. Thanks for the help I will give it a shot. I am on unifi also. I think I can probably just move unifi controller to a bridge mode and get rid of pihole. Does this also happen with VMs though? I really need my blue iris VM to have an IP heh.
  7. It does not even create a VM for me. I get this from the helper script after I got the notification it was ready: It does not create any VM for me. EDIT: Removing the entire macinabox appdata, app, and the /mnt/user/system/custom_ovmf folder fixed this for me.
  8. How does this actually work in practice though. If Pihole etc is on a different network VLAN how do your computers on your network see it ? Also do you know if this problem occurs if you set the network of the container to br0 but then leave it to grab an IP via DHCP ? If so I could just put an entry in the DHCP table instead.
  9. My server also crashing. The same nf_conntrack_core.c macvlan errors. It will usually handle a couple of them then kernel panic. I will try disabling all custom IPs, but is it really expected that we cannot set a static IP or the server will crash every 4-6 hours? This bug continues for my in 6.9RC2. Not sure how having the containers on a separate VLAN will help since I set them as a static IP because they need to be accessible to my normal network (unifi controller, pihole, etc)
  10. I'm having absolutely abysmal speeds using cloudberry to pull from B2. Tried a download of files from the backblaze website myself and it goes full line speed of my internet. 2kb/s Anyone have any idea why this would be happening? Lost my plex folder but it will be a long long time restoring at this pace heh.
  11. Just wondering if the steamcache is using an odd region? I am only getting 3-4MB/sec rather than the normal 16 on the first download(to SSD). My Steam is set to Canada - Edmonton on the downloading machine. When I download for the first time through the steamcache i get: 10.3.3.171 / - - - [14/Nov/2019:15:25:49 -0700] "GET /depot/583952/chunk/6fe88c8bc485c906703424d6dc8be0f20168823b HTTP/1.1" 200 103152 "-" "Valve/Steam HTTP Client 1.0" "MISS" "cache1-sea1.steamcontent.com" "-" So using a seattle server rather than the one I have set in steam?
  12. My filebot has also long ago stopped scanning for folder changes. Is there any way to fix this?
  13. I tried installing it with no luck. The following error happened: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='telegraf' --net='host' --privileged=true -e TZ="America/Phoenix" -e HOST_OS="Unraid" -e 'HOST_PROC'='/rootfs/proc/' -e 'HOST_SYS'='/rootfs/sys/' -e 'HOST_ETC'='/rootfs/etc/' -e 'HOST_MOUNT_PREFIX'='/rootfs/' -v '/var/run/utmp':'/var/run/utmp':'ro' -v '/var/run/docker.sock':'/var/run/docker.sock':'ro' -v '/':'/rootfs':'ro' -v '/sys/':'/rootfs/sys':'ro' -v '/etc/':'/rootfs/etc':'ro' -v '/proc/':'/rootfs/proc':'ro' -v '/m
  14. Ya it just sits there. Nothing I can do seems to make it actually detect folder changes to run again. [2018-09-22 19:35:44] FileBot: Finished running command. Exit code was 0 [2018-09-22 19:35:44] FileBot: Waiting for new change