Search results

Tried apt autoclean - ok apt autoremove - BAD A guess: updates don't support kdump-tools? I'll try removing that next...

On the LAN side, each accessible LAN interface requires both: * A shared CARP IP, that switches back and forth (I use *.1) * A unique IP for that interface (I use *.2 for primary and *.3 for secondary) Since pfSense supplies DHCP and local DNS, that's pretty easy. On the WAN side, a) it's...

Follow the pfSense CARP cookbook carefully. The MOST important thing by far: all network devices must be in the exact same order internally to pfSense, as that is the assumption for sync. If that's a problem, there's a workaround using LAGGs. If you end up having to reconfigure network...

I provided the update log above. From that log, it looks like the autoupdate (initiated in the GUI) *tries* to remove old versions... but it didn't do anything? ALSO: I find no documented way to examine nor discover the status of the /EFI partition? Here's my proxmox-boot-tool info:

I just attempted an update, which failed pretty miserably. I note that a LOT of old versions are still hanging around... is that an issue? End of errors: Below: - pveversion -v Attached: - captured live errors - mount - cat /proc/mounts Anything else? pveversion -v [See attached for...

I'm using HA CARP which is built into pfSense... in my case on 2 proxmox VM's. This has some advantages over vm migration. Most particularly: CARP maintains a live backup of all connections. Rather nice when a cutover maintains all connections. Do you have 2+ WAN connections? If so, it's...

I have a functioning ProxMox cluster, including: * Two hosts plus a QDevice * pfSense routers on each (synced CARP primary and backup/mirror) * plus some VM's on each Each box has a dedicated port for the host, using my primary subnet. To date, the hosts know nothing about VLANs. Each box has...

I've got a 2-node Proxmox cluster + QDevice (on a tiny raspberri pi ;) ) All is working well. pvecm status correctly shows everything I can't find anything in the GUI to hint that a QDevice exists or is present Am I missing something, or is this simply missing from the GUI? I'm thinking it...

Oops. I'm not the OP on this thread. I apologize!

SOLVED.... what a relief! I had already run memtest, and the RAM had passed. Yet... memtest86 has been radically strengthened since I last made my bootable copy. Using the latest version? Bad RAM. Pull that RAM (still have 8GB, enough for now) and all is wonderfully well. H/T @kalasnikov for...

Will do. FWIW, there are a number of new distracting error messages-on-boot-or-crash that appear to be just that: distractions not worth focus... ...no irq handler for vector ...BIOS has corrupted hw-PMU resources (MSR 38d... ...DMA failed to allocate 128 KiB GFP_KERNEL [GFP_DMA pool for atomic...

Unfortunately, fixing my filesystem did not fix the original crash-on-backup issue. Not only that, I saw on the console some disturbing messages fly by, about kdump not supporting the current kernel, so the dump wasn't complete... (...and another error saying something about a BIOS bug...

@oguz, The good news: fixing zfs filesystem error took care of crash-on-gzip. (There is bad news in another message :confused:) The following info is not currently listed in Proxmox documentation that I can see... So I wrote it up :) Current HowTo: Managing filesystem issues with ZFS on Proxmox...

Thanks! (I updated the instructions with a more general crashkernel param, and a link to some documentation. Have not found ubuntu-specific info, nor any details of what actually affects the reserved RAM size. This works for me...) I know how to handle disk issues; not used to reading Oops...

Done! First, the dmesg.* lines... A) Some early lines showing some kind of (minor?) issues [ 136.170773] audit: type=1400 audit(1643760906.256:20): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" na me="lxc-402_</var/lib/lxc>" pid=7260 comm="apparmor_parser" [...

Current instructions for enabling kdump-tools in proxmox with zfs (NOTE: apt update etc are NOT currently supported with kdump-tools installed. See below for uninstall instructions for when done testing!) # apt install kdump-tools Select no for kexec reboots Select yes for enabling kdump-tools...

Hmmm... looks like kdump-tools and zfs-root are not quite happy together, although there are patches. Working on it.

*ping*... Anybody have a pointer on how to capture a hard host crash? I'm getting reliable crashes *every* time I attempt a backup on this host... or when proxmox attempts to update (presumably due to trying to backup.) Right now I can watch a huge amount of console log stuff spin by, but it is...

"not documented" -- as in, from the GUI level. I think what surprised me about this was that the GUI supports serial ports, so I assumed what the GUI had was the extent of my options.

I just wasted hours trying to get a serial port to work in a VM, when the real issue was ProxMox misconfig (by default). The ProxMox gui configures serial ports as sockets. I don't know where it DOES work, but it does NOT work if a VM needs to access a device on a serial port (UPS, modem...