Latest activity
-
Ppringlestuffs reacted to rgreen83's post in the thread ProxMox 9.1.2 on MS-01 cannot make i226-V come up with
Like.
There is a lot of issues with i226-V and latest versions of proxmox, but not limited to proxmox, it seems to be affecting many linux and freebsd systems. My solution was to update the nic firmware, see here for many others doing the same... -
Ppringlestuffs reacted to mkrijtenberg's post in the thread Unstable Ethernet negotiation on Intel i226-V rev 4 (Aoostar WTR Pro, Ryzen 7 5825U) with Like.
I've experienced the same issues. Thanks to your post I found the solution. My WTR Pro kept dying when I was transferring my data from another NAS to this one. Turns out the Intel NIC has some kind of power saving feature which interferes while...
-
Ppringlestuffs replied to the thread [SOLVED] Very high latency with Intel i226-v NICs.This is the same as disabling IOMMU, correct? Which won't be an acceptable workaround for many users. Yet another trash NIC from Intel who have been releasing terrible buggy NICs in the consumer segment for many years at this point :( Is there...
-
AAlegzander replied to the thread Opt-in Linux 7.0 Kernel for Proxmox VE 9 available on test and no-subscription.Has anyone tested SR-IOV functionality for iGPUs like the one in Alder Lake CPUs ? I'd be curious to know. Haven't switched my system to 7.0 yet as I need it for work, but if anyone's tested it, I'd be curious about your results. Thanks !
-
GAfter being a bit inspired by the awesome Nimble Plugin that was released I decided to use a little of my downtime on Vacation to try and give the same thing a go, but using Synology/DSM as the storage backend. This will allow you to use iSCSI...
-
JJohannes S reacted to chrcoluk's post in the thread [TUTORIAL] Understanding QCOW2 Risks with QEMU cache=none in Proxmox with Like.
To be fair to Proxmox it is documented that cache=none does not fully disable write caching here. For that you need 'writethrough' or 'directsync', but expect absolutely horrific write performance on non enterprise SSDs and all spindles...
-
SSgingold replied to the thread Reboot stuck on GRUB and reinstall attempt doesn't get past Install screen.I agree, it's definitely an issue with the Minisforum. I just cleared the BIOS by removing the CMOS battery per your suggestion, also reseated the RAM. No luck. I think this pc is just hosed.
-
JJohannes S replied to the thread PVE 8 to 9 In-place Upgrade.apt/dpkg actually have an mechanism to take care that config files are not overwritten by a config update. The package maintainer needs to build the package accordingly though.
-
JIdeally APT needs something like mergemaster, I have never seen such a good tool anywhere else, ironically mergemaster got discontinued on FreeBSD and replaced with something inferior.
-
RRianKellyIT replied to the thread IPv6 forwarding enabled by default on one interface.The root cause is the Proxmox firewall service (pve-firewall). When it starts, it sets net.ipv6.conf.all.forwarding=1 globally because VMs and containers need IPv6 packet forwarding to work. This happens even if the firewall is technically...
-
Ssteves replied to the thread TASK ERROR: activating LV 'pve/data' failed: Check of pool pve/data failed (status:64). Manual repair required!.@fiona here is the output of "lvconvert -v --repair pve/data" when run from an 8.4 iso.
-
Ddiverk replied to the thread [SOLVED] Unable to update PVE from 7.3.3.Thank You for the response! I set the DNS options in the GUI under network>DNS. Okay, so I found the problem. I changed my network router over a year ago, and it's at a different IP address. I could manually ping it (SSH'd into pve), but...
-
CCycloneB replied to the thread [SOLVED] DegradedArray alert day after upgrading pve8 to 9.And the spinners look good too, if I'm reading this right. When I spin up the VM again, I get these messages: Apr 05 18:22:36 <node> kernel: md/raid1:md126: Disk failure on sda1, disabling device.md/raid1:md126: Operation continuing on 2...
-
CCycloneB replied to the thread [SOLVED] DegradedArray alert day after upgrading pve8 to 9.
-
CCycloneB replied to the thread [SOLVED] DegradedArray alert day after upgrading pve8 to 9.I removed the startup option on TrueNAS, rebooted the host, and ran smartctl to check for things: nvme0n1 is the boot SSD, so ignoring that drive. So the NVMe look good, right? Spinners in the next post due to character limits.
-
Jjanus57 replied to the thread 3 nodes without cluster sharing a subnet?.Hi, yes, see REF1918 for completeness Yes, if your router can do a static route But at this point the question will be more "Why would you do this" instead of putting it all in the same subnet ? Best regards,
-
OOnslow replied to the thread [SOLVED] Unable to update PVE from 7.3.3.Welcome, @diverk ! Where have you set it? Please post the real config (not a relation :cool: ) in CODE blocks (using that "</>" icon in the composing menu).
-
JJohannes S reacted to bbgeek17's post in the thread [TUTORIAL] Understanding QCOW2 Risks with QEMU cache=none in Proxmox with Like.
Happy New Year! Sorry for the delay on this... we wanted to do a proper analysis. Both cache=direct and cache=writethrough provide substantially stronger consistency guarantees than cache=none. If you are using QCOW/LVM and consistency is a...
-
JJohannes S reacted to RolandK's post in the thread [TUTORIAL] Understanding QCOW2 Risks with QEMU cache=none in Proxmox with Like.
doesn't this bold statement need correction ? https://wiki.qemu.org/Features/Qcow2DataIntegrity Summary The qcow2 image format driver has known data integrity issues which need to be addressed. Note: This page is out of date and no longer...
-
JJohannes S replied to the thread [TUTORIAL] Understanding QCOW2 Risks with QEMU cache=none in Proxmox.That question should propably asked at the qemu developers, especially the one mentioned as owner in the wiki page.