hybridtracer

I'm specifying a vdisk manually. I actually fixed it with a reboot. I just hadn't tried rebooting yet because I had some balancing processes running.

Where do I choose that? I have the qcow2 for hassIO on the share and i select it under "Primary vDisk Location" are you saying I have to specify somewhere else that i'm using qcow2?

I'm trying to create a VM for HassIO and I keep getting an error. operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd I followed this guide here. https://community.home-assistant.io/t/hassio-on-unraid/59959 The file is there so I don't really know what's happening as this is my first VM. HVM: Enabled The above is enabled since I've seen that asked before. I found this in the libvirt log 2020-09-30 16:06:30.183+0000: 4371: info : libvirt version: 5.10.0 2020-09-30 16:06:30.183+0000: 4371: info : hostname: NAS 2020-09-30 16:06:30.183+0000: 4371: warning : qemuDomainObjTaint:9301 : Domain id=1 name='HassIO' uuid=aeeb767f-4f63-90fd-a7b9-13b38f477428 is tainted: high-privileges 2020-09-30 16:06:30.184+0000: 4371: warning : qemuDomainObjTaint:9301 : Domain id=1 name='HassIO' uuid=aeeb767f-4f63-90fd-a7b9-13b38f477428 is tainted: host-cpu 2020-09-30 16:06:30.826+0000: 4374: error : virFileRewrite:525 : cannot sync file '/etc/libvirt/qemu/HassIO.xml.new': Input/output error 2020-09-30 16:09:51.021+0000: 4373: error : virNetClientProgramDispatchError:172 : Cannot open log file: '/var/log/libvirt/qemu/HassIO.log': Device or resource busy 2020-09-30 16:51:34.423+0000: 4370: error : qemuPrepareNVRAM:4420 : operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd 2020-09-30 16:51:34.436+0000: 4370: warning : virHostdevReAttachUSBDevices:1822 : Unable to find device 000.000 in list of active USB devices 2020-09-30 16:51:49.953+0000: 4372: error : qemuPrepareNVRAM:4420 : operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd 2020-09-30 16:51:49.968+0000: 4372: warning : virHostdevReAttachUSBDevices:1822 : Unable to find device 000.000 in list of active USB devices

I'm trying to create a VM for HassIO and I keep getting an error. operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd I followed this guide here. https://community.home-assistant.io/t/hassio-on-unraid/59959 The file is there so I don't really know what's happening as this is my first VM. HVM: Enabled The above is enabled since I've seen that asked before. I found this in the libvirt log 2020-09-30 16:06:30.183+0000: 4371: info : libvirt version: 5.10.0 2020-09-30 16:06:30.183+0000: 4371: info : hostname: NAS 2020-09-30 16:06:30.183+0000: 4371: warning : qemuDomainObjTaint:9301 : Domain id=1 name='HassIO' uuid=aeeb767f-4f63-90fd-a7b9-13b38f477428 is tainted: high-privileges 2020-09-30 16:06:30.184+0000: 4371: warning : qemuDomainObjTaint:9301 : Domain id=1 name='HassIO' uuid=aeeb767f-4f63-90fd-a7b9-13b38f477428 is tainted: host-cpu 2020-09-30 16:06:30.826+0000: 4374: error : virFileRewrite:525 : cannot sync file '/etc/libvirt/qemu/HassIO.xml.new': Input/output error 2020-09-30 16:09:51.021+0000: 4373: error : virNetClientProgramDispatchError:172 : Cannot open log file: '/var/log/libvirt/qemu/HassIO.log': Device or resource busy 2020-09-30 16:51:34.423+0000: 4370: error : qemuPrepareNVRAM:4420 : operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd 2020-09-30 16:51:34.436+0000: 4370: warning : virHostdevReAttachUSBDevices:1822 : Unable to find device 000.000 in list of active USB devices 2020-09-30 16:51:49.953+0000: 4372: error : qemuPrepareNVRAM:4420 : operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd 2020-09-30 16:51:49.968+0000: 4372: warning : virHostdevReAttachUSBDevices:1822 : Unable to find device 000.000 in list of active USB devices

Any thoughts on what may cause this? It is the second time it has happened.

I did a check an repair on disk 2. After reboot, the cache came up as unmountable. nas-diagnostics-20200106-1326.zip

It seems like my cache is read only. Everything was fine but I can't access any of my Docker WebUIs anymore. I did some searching but I don't think I have the normal issue I've been seeing. There are no errors that I can tell. root@NAS:~# btrfs balance start -dusage=75 /mnt/cache ERROR: error during balancing '/mnt/cache': Read-only file system There may be more info in syslog - try dmesg | tail root@NAS:~# btrfs balance start -dusage=25 /mnt/cache ERROR: error during balancing '/mnt/cache': Read-only file system There may be more info in syslog - try dmesg | tail root@NAS:~# btrfs dev stats -z /mnt/cache [/dev/nvme0n1p1].write_io_errs 0 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 0 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 root@NAS:~# btrfs fi show /mnt/cache Label: none uuid: 3bdd2a6c-a527-4a33-838d-200712723d0c Total devices 1 FS bytes used 140.43GiB devid 1 size 465.76GiB used 163.02GiB path /dev/nvme0n1p1 Anyone have any ideas on what to try? This happened to me once before and I reformatted the cache. I'm hoping there is a better way without having to resetup my dockers. nas-diagnostics-20200106-0253.zip

Hi, I was wondering if anyone has insight on installing mods to the terraria server container. Any guidance is greatly appreciated.