July 10, 2025Jul 10 On 6/28/2025 at 8:08 PM, gurulee said:I am seriously considering upgrading from 6.12.15 > 7.1.4. But before I do so, I wanted to see if anyone else had an identical upgrade path that went smoothly?I currently rely on Macvlan and custom bri networks for dockers with static IP's.Also, anything out of the ordinary to call out before I move forward with upgrade?Have you made the jump yet?
July 11, 2025Jul 11 I'm still sitting on 6.12.15 too. I don't yet have full confidence in the 7.x series based on the threads I've seen.
July 11, 2025Jul 11 I’m still on 6.12.15. Best upgrade path to 7.1.4?6.12.15->7.1.4?6.12.15->7.0->7.1.4?Other?No ZFS in use. Currently have 9 data +1 parity xfs array and 2 SSD btrfs pool cache.Thanks for any guidance!
July 11, 2025Jul 11 11 minutes ago, splerman said:I’m still on 6.12.15. Best upgrade path to 7.1.4?Should be fine going directly to 7.1.4, but it's always good to create a flash drive backup in case something goes wrong to allow an easy revert.Also read the release notes from the major releases, 7.0.0 and 7.1.0
July 13, 2025Jul 13 On 7/11/2025 at 11:34 AM, splerman said:I’m still on 6.12.15. Best upgrade path to 7.1.4?6.12.15->7.1.4?6.12.15->7.0->7.1.4?Other?No ZFS in use. Currently have 9 data +1 parity xfs array and 2 SSD btrfs pool cache.Thanks for any guidance!I have a very similar setup and current version, look forward to your after install input if you decide to update to 7.1.4
July 15, 2025Jul 15 What! my trusty usb stick of 10 years of 4GB is not longer capable, this needs to be fixes.but for real, never have gotten this message, there is only 675MB free what can I delete safely to make space?
July 15, 2025Jul 15 59 minutes ago, ijuarez said:but for real, never have gotten this message, there is only 675MB free what can I delete safely to make space?You can probably start by deleting your "previous" folder.Maybe diagnostics in "logs".
July 15, 2025Jul 15 Probably a bunch of old logs or other things, shouldn't be much more than 2GB used even with previous.
July 16, 2025Jul 16 9 hours ago, ijuarez said:What! my trusty usb stick of 10 years of 4GB is not longer capable, this needs to be fixes.but for real, never have gotten this message, there is only 675MB free what can I delete safely to make space?I was using 1GB sticks until this update, for sure you have a lot of stuff you can delete! Maybe a lot of old logs and old plugins you don't need.
July 16, 2025Jul 16 2 days before the 1 month mark since release, I decided to pull the trigger and updated from 7.0.1 to 7.1.4.Everything went very smoothly, no problem after reboot. I use ZFS, many docker containers (some with custom networks), SMB, NFS, various plugins (user scripts, auto fan, ZFS master, ITE I87 driver...), etc.As far as I can tell 7.1.4 is totally fine. Edited July 16, 2025Jul 16 by googleg
July 17, 2025Jul 17 I'm curious to know if Limetech are working on a 7.1.5 release or whether they're done and now they're moving on to 7.2, etc, etc.It seems there's still a few rough edges for a number of folks with the 7.1.x series. It'd be really good to see if some of those could be further refined and cleaned up before moving on.
July 22, 2025Jul 22 upgraded from the 7 beta to 7.1.4having some issues where now every time i have to log into the web ui - it isn't seeming to store cookies with saved password. i guess i'll try delete the cookies and try againwhats more concerning is that i got a kernel panicJul 21 21:04:39 192.168.1.3 kernel: ata15.00: exception Emask 0x10 SAct 0x106c0 SErr 0x0 action 0x6 frozen Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: irq_stat 0x08000000, interface fatal error Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: cmd 60/c8:30:b8:b7:5f/01:00:77:00:00/40 tag 6 ncq dma 233472 in Jul 21 21:04:39 192.168.1.3 kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: status: { DRDY } Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: cmd 60/00:38:80:b9:5f/04:00:77:00:00/40 tag 7 ncq dma 524288 in Jul 21 21:04:39 192.168.1.3 kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: status: { DRDY } Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: cmd 60/20:48:20:14:0c/00:00:84:00:00/40 tag 9 ncq dma 16384 in Jul 21 21:04:39 192.168.1.3 kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: status: { DRDY } Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: cmd 60/10:50:70:87:64/00:00:7e:00:00/40 tag 10 ncq dma 8192 in Jul 21 21:04:39 192.168.1.3 kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: status: { DRDY } Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: cmd 60/80:80:00:49:ab/00:00:88:00:00/40 tag 16 ncq dma 65536 in Jul 21 21:04:39 192.168.1.3 kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jul 21 21:04:39 192.168.1.3 kernel: ata15.00: status: { DRDY } Jul 21 21:04:39 192.168.1.3 kernel: ata15: hard resetting link Jul 21 21:04:40 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:40 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:41 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:41 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:42 192.168.1.3 kernel: ata15: failed to resume link (SControl FFFFFFFF) Jul 21 21:04:42 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:42 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:44 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:44 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:44 192.168.1.3 kernel: ata15: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jul 21 21:04:45 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:45 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:46 192.168.1.3 kernel: mpt3sas_cm0: SAS host is non-operational !!!! Jul 21 21:04:46 192.168.1.3 kernel: mpt3sas_cm0: _base_fault_reset_work: Running mpt3sas_dead_ioc thread success !!!! Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449376 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449384 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449392 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449400 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449408 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449416 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449424 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449432 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449440 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449448 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449456 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449464 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449472 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449480 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449488 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449496 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449504 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449512 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449520 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449528 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449536 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449544 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449552 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449560 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449568 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449576 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449584 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449592 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449600 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449608 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449616 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=15798449624 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976912 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976920 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976928 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976936 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976944 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976952 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976960 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976968 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976976 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976984 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743976992 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977000 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977008 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977016 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977024 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977032 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977040 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977048 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977056 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977064 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977072 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977080 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977088 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977096 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977104 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977112 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977120 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977128 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977136 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977144 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977152 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=8743977160 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729824 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729832 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729840 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729848 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729856 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729864 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729872 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729880 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729888 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729896 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729904 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729912 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729920 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729928 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729936 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729944 Jul 21 21:04:46 192.168.1.3 kernel: md: disk10 read error, sector=13575729952 Jul 21 21:04:46 192.168.1.3 kernel: mpt3sas_cm1: SAS host is non-operational !!!! Jul 21 21:04:46 192.168.1.3 kernel: mpt3sas_cm1: _base_fault_reset_work: Running mpt3sas_dead_ioc thread success !!!! Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449376 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449384 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449392 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449400 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449408 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449416 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449424 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449432 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449440 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449448 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449456 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449464 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449472 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449480 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449488 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449496 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449504 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449512 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449520 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449528 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449536 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449544 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449552 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449560 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449568 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449576 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449584 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449592 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449600 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449608 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449616 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=15798449624 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188032 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188040 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188048 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188056 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188064 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188072 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188080 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188088 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188096 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188104 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188112 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188120 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188128 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188136 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188144 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188152 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188160 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188168 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188176 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188184 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188192 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188200 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188208 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188216 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188224 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188232 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188240 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188248 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188256 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188264 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188272 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=22087188280 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976912 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976920 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976928 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976936 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976944 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976952 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976960 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976968 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976976 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976984 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743976992 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977000 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977008 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977016 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977024 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977032 Jul 21 21:04:46 192.168.1.3 kernel: md: disk12 read error, sector=8743977040the disks themselves seem fine, so not really sure where to go from here
July 22, 2025Jul 22 5 hours ago, mrpops2ko said:whats more concerning is that i got a kernel panicI see disk errors, but no kernel panic in your extract from the log.In any case, as stated in the first post, you should create a new thread in the General Support section and attach your diagnostics.
August 5, 2025Aug 5 Anyone else having issues with PCIe passthrough to a VM?At my parents I have a HP Gen 8 Mincroserver with an Intel Xeon E3-1230 V2 running 7.0.1 and I'm able to passthrough a PCIe network card just fine.However, when I upgraded to 7.1.4 I started getting this error:2025-08-02 17:16:36.612+0000: 12559: error : qemuProcessReportLogError:1953 : internal error: QEMU unexpectedly closed the monitor (vm='pfSense'): 2025-08-02T17:16:36.605906Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:07:00.0","id":"hostdev0","bus":"pci.3","addr":"0x0"}: vfio 0000:07:00.0: failed to setup container for group 1: Failed to set group container: Invalid argumentI tried recreating the VM from scratch but it still has the same error. The card is a quad Intel 82580 and all four are vfio bound. Unless I missed it, I couldn't see anything in the changelogs.
August 6, 2025Aug 6 Author This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic under General Support. Be sure to include your diagnostics.zip
August 6, 2025Aug 6 10 hours ago, ljm42 said:This announce post is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic under General Support. Be sure to include your diagnostics.zipThanks, I just thought I'd ask here first in case it was a known issue with a quick fix.
August 7, 2025Aug 7 On 8/6/2025 at 6:54 AM, tech3475 said:Thanks, I just thought I'd ask here first in case it was a known issue with a quick fix.Yes had almost exact issue going from 7.0.1 > 7.1.2 but with an i226 nic. Rolled back to 7.0.1 and haven't looked back.
August 11, 2025Aug 11 Somehow I have upgraded from version 7 to the latest version without any issues.It would be useful to have a hardware index and, when upgrading, could give a confidence level based on our current setup of how well things will (or not) go.
August 11, 2025Aug 11 2 minutes ago, Goldmaster said:It would be useful to have a hardware index and, when upgrading, could give a confidence level based on our current setup of how well things will (or not) go.In my experience, issues after upgrading are more often related to the specific settings and apps users are using than the hardware itself, so I'm not sure how useful that would be.
August 11, 2025Aug 11 7 minutes ago, JorgeB said:In my experience, issues after upgrading are more often related to the specific settings and apps users are using than the hardware itselfAh! Interesting. The reason for that was that i have to swap my m.2 drives that i had between cache and Windows 11 vm. after 6.9 the drive i was using caused windows not to start downgrade and windows worked fine. It was the same for linux as well. Swapped it for cache use and used the cache drive which was larger for windows install and the issue was sorted.
August 19, 2025Aug 19 Did the update from 6.12.15 to 7.1.4 without issues so far.This was my update checklist- [x] update plugins and dockers- [x] backup appdata VM USB- [x] shutdown VMs- [x] backups to cloud- [x] stop array- [x] update OS- [x] check for plugin update errors if exist- [x] reboot- [x] pray
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.