Quote from: tverweij on June 21, 2026, 06:33:53 PMI use production - needed for backup.
But I also tried Standard - just made a standard snapshot by hand and removed it again.
Both production as standard snapshot causes the errors to be displayed in the OpnSense VM.
No difference that I can see.
Quote from: juicemain on June 20, 2026, 11:44:27 PMIf anyone has any clue as to what this could be at this point, anything would be much appreciated. I have no idea what to check next, and I highly doubt the ISP is going to be willing to help much. Thanks again for all the help already.Ask your ISP to replace the ONT with a different/better/updated model ?!
thomaslauer 2019-05-20 19:05:15 UTC
Hi, i have 120 PFSense VMs from 2.3.4 to 2.4.4-2 all Hyperv VMs with GEN2 and UFS.
and some vms with Hyperv GEN2 and UFS. All this VM has the same issue.
I have only one VM with GEN2 and ZFS. This VM has no SCSI Errors during the snapshot.
Nick 2019-05-31 16:53:28 UTC
I am having this problem with PFSense (2.4.4-RELEASE-p3) running on Hyper-V (Windows 2012 R2). In my case, replication might run fine for a while (hours, days) but at some point there is a SCSI Status Error during a WRITE operation and PFSense/FreeBSD will become locked up or partially working but eventually will not respond to network or UI requests. I would love a resolution to this. For the moment, I've disabled replication and it's been fine.
Perhaps useful, perhaps not: I've been running PFSense for years as a replicating VM on Hyper-V W2K2012R2 without issues. It was just this week when I started having problems. PFSense was previously running many different versions (2.2, 2.3, 2.4.3). When I started having problems this week I had not upgraded PFSsense or the hypervisor. As far as I can tell "nothing changed".
Nick