Search results

IIRC the error on the screen at the time was systemd-journald.service failed to start or something like that. I'll have to check logs more thoroughly when I have some time and report back.

It's usually the result of a drive failing or beginning to fail. In this latest case there is an IO failure on the backup drive that was logged. SMART shows OK though and rerunning the backups worked fine. I suspect that the drive will flat out fail in the next few weeks or months so I am going...

Proxmox has been quite reliable for me but I have had issues from time to time. It's seems the most common issue I have is a backup failing for some reason. In some cases the backup fails because of a drive problem, and in other cases the issue is unknown. My latest failure I reboot and rerun...

Try manually importing the cert into the keychain and setting it to always trusted. It fixed it for me in Safari. I think my server updated it's cert or something recently and Safari wouldn't automatically trust the new certificate. I don't think this would be an issue with a non-self signed cert.

I believe my server updated it's ssl cert. Bypassing the warning and viewing the site anyway was apparently not enough to get Safari to allow the shell and console connections. I tried manually updating the certs on the server based on another thread but that didn't fix the issue either. After...

I just started getting this on one of my test servers, but not the other. I think it has something to do with the SSL certs, but running the update command I found from elsewhere on this forum did not help. I experience the message in Safari, but not Firefox. Not sure what is causing it yet.

I have not had any problems with my opnsense or freenas VMs other than the failure to boot as described in this thread and the problem with the qemu update and the q35 machine type. I'm now running i440fx with pci passthrough instead of pcie and everything is back to working fine as far as I can...

Ran the updates today which included the 5.3 kernel and it did indeed fix the issue for me as well.

Ditto. Just ran an update tonight and both my FreeBSD machines would hang on boot. kernel 5.0.21-5-pve and pve-qemu-kvm 4.1.1-1 I was able to get them to boot again by changing from host cpu type to kvm64. They both seem to be working now, but it remains to be seen if performance is affected...

I was under the impression that PCIE passthrough had to use q35 and it wouldn't work with i440fx.

I also could benefit from an ignore disk in the VM config so I could take a snapshot of a boot volume. I currently also exclude my passthrough disk from backup as it is itself a backup disk inside the VM. Luckily my boot volume is small and it's not that big of a deal to back it up before trying...

Apparently this is still a problem even after the update to QEMU 4.0.1. I had to update the machine option in my VM configs to get my PCI passthrough working on my two FreeBSD VMs. And unfortunately I also have a verification error due to the machine arguments as well. I guess I will wait to...

Ran into this today when I tried to upgrade to 6 again. Two of my VMs wouldn't work properly after the upgrade. I thought QEMU 4.0.1 fixed the issue, but apparently it didn't. After fixing the machine line in my VM configs I now have this error on my summary page: "Error Result verification...

I figured out what was going on. It's mentioned in other threads, but many of them recommend the solution without mentioning this issue. The problem is that proxmox will create the mount directory before the zfs mount happens and that ends up blocking the zfs mount. There is an option you can...

I've tried this and what ends up happening is that proxmox thinks the size of the backup directory is the same as the local directory. So if local is small then the backups will fail because it thinks it's filling up the location even though there is plenty of space. Has anybody got this...

I found a thread discussing a breaking change in qemu that might be related as well. It looks like they plan to revert the change in an update and take a different approach on reintroducing it in a later version. I'm not sure how this will all shake out, but it looks like these are related in...

I tried upgrading my main server this morning and had two freebsd vms using pcie passthrough that quit working after the upgrade. One VM was passing through a network card and the other a SATA controller. Everything looked fine based on how it worked under v5. Unfortunately I didn't happen to...

It comes and goes for me. Sometimes it will be weeks before I get a failure, and sometimes I get failures several nights in a row.

Well, the past week everything had been working well with no backup failures, and then this morning I get the email from the backup tool and 3 out of 4 of my VMs failed with the no such volume error. This is the first time in a long time that more than one backup failed, and I'm pretty sure I've...

The past 3 nights the same VM out of the 4 I have on my server has given me this error. I backed it up manually this morning with no problems. Not sure what to do to troubleshoot this, but it doesn't seem to be getting better, and there doesn't appear to be any issues with the VM. Also I've...