CorneliousJD

CP actually sent out an email a few weeks or a month or so ago stating that this will be a new thing moving forward - so this is normal as of now.

Hey Jim, I think the best thing to do here IMO would be to use the CA Appdata backup/restore to also backup your flash, and then use Crashplan to backup the backed-up file. I have mine setup to backup to /mnt/user/backups/unRAID/flash/ I then keep that whole "backups" folder backed up by CrashPlan so it's always accessible and uploaded whenever the auto-backups get generated.

Awesome - Just one question, where do I find this feature at? I've tried taking a look and I just don't see it, and I'm sure I'm overlooking something but I figured I'd ask EDIT: Nevermind I found it! Size divider for mini layout - thanks!!!

I had to end up upping mine to 1,500,000 and now it seems to be working properly finally. I am backing up about 850GB give or take, and have 128GB of RAM.

Sounds great, thank you for the consideration! This beats the pants off the excel sheet I kept before.

Gottcha, the layout display is what's used on the dashboard when you enable that though, would be nice (but low priority) to have an option to size both of them differently I guess. The default sizing looks perfect on the the "Devices" page but is too small IMO for the dashboard widget that you add.

I am using this to show my drive locations on the dashboard, works great, but I want them to be a nice sized with, like this 800x140 for example, the problem is, with this set at this size, it makes the info page HUGE Can we make these two values separated somewhere, or unrelated? Right now they appear linked somehow.

Thanks! I had mine set to 750,000 already, but I upped it to 1,048,576 We'll see if that makes a difference and if I need to I can go higher, I have 128GB of RAM so I have plenty to spare!

I'm recently seeing this error when I open the container to check on something, relating to the inotify watch limit. I know the instructions are here to fix that: https://support.code42.com/CrashPlan/6/Troubleshooting/Linux_real-time_file_watching_errors However I don't know where these instructions need to be completed at. If I do them in-container wont restarting the contianer wipe those changes out? Or updating it?

Used Catalina both times but it's downloading Mojave still - looks like someone else is now having the same problem, weird. I wont push too hard on it for now. If the container is just grabbing the recovery.img from a URL and that can be posted I can do a manual download and replace of my .img, if not I can wait it out, no real rush here, just something fun to mess with from the server. I really only want this up as an easy way to take how-to screenshots on a fresh mac.

Ok, so when I tried this a few days ago I got stuck, but now I'm booting to the installer just fine. However this time I picked Catalina, and it looks like it downloaded the Mojave recovery media, as it tells me it's going to install Mojave even though I picked Catalina. My old .img file for Catalina-install.img was 2,095.724KB, this new one that says Mojave in the actual installer (filename is still Catalina-install.img) is 2,085.568KB I've put the old file in it's place but it doesn't boot, it starts to load the 2nd bar under the Apple logo and doesn't go any further than that. Any advice? Is it against rules to share a direct download link to the Catalina-install.img?

I was able to roll back to :3.10.5 and get logged in, even tho cameras showed offline. Do a backup, and then run a clean install of the container. It took about 4-5 minutes to "Boot" the container, at which point on the first wizard screen I could restore from the backup I just took. Was able to login again, re-adopt my NVR to my UniFi account, and also analyze the recording database and restore past recordings. Back up and running on 3.10.10 now and all is well, thanks everyone!

Ah whoops, that must have gotten overwritten somehow when I was tweaking stuff via the GUI, good catch! Updated and it seems to be displaying better but still getting stuck here:

Ok so mostly smooth so far but I don't keep my VMs in /mnt/user/domains so i had to do some tweaking. I'm sure I've mucked something up now in the works but cannot figure it out. Anyone care to take a look? This is where it gets stuck now... And my XML is as follows <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacOS Catalina</name> <uuid>427e2dee-2768-4ceb-90d7-29da86721f8d</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="/mnt/user/vms/MacOS Catalina/icon/catalina.png" os="Catalina"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='14'/> <vcpupin vcpu='1' cpuset='30'/> <vcpupin vcpu='2' cpuset='15'/> <vcpupin vcpu='3' cpuset='31'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/427e2dee-2768-4ceb-90d7-29da86721f8d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'/> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/vms/MacOS Catalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vms/MacOS Catalina/Catalina-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vms/MacOS Catalina/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:29:4e:b9'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=redacted'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>

Thanks... haha this was by FAR the easiest solution. Worked great. Can confirm the newly generated default site conf looks like it has the fixes in place! EDIT: Although after doing this now I'm getting one small error on the security check page. The "Referrer-Policy" HTTP header is not set to "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" or "same-origin". But as H2O_King89 noted above, this is an easy fix. I just commented out line #21 on the newly generated config!