Search results

so, after monitoring the environment for a while - i can confirm, that the issue has been fixed by moving the zfs-swap area on rpool to a non-zfs (ext4) file system. Thanks guys for help & support. I do appreciate a lot. Cheers Mike

ok - gents - so far - no crashes anymore So, i think re-swap to non-zfs (rpool) partition (ext4) solved the issue. i'll track the behave some more weeks .. then i think i could close the case. So far - thanks to all involved/helped on this topic :)

yes, mgabriel .. i read about it. i did: unpin kernel (previous action: Set kernel '6.5.13-5-pve' in /etc/kernel/proxmox-boot-pin) destroy rpool/swap create a new ext4 partition (20G) activating swap on this ext4 partition (20G) Let's see, if it works.

yes, that's right .. i also read, there could be some threats regarding swap on top of zfs. My config : ~# zfs list rpool/swap NAME USED AVAIL REFER MOUNTPOINT rpool/swap 31.6G 385G 11.0G -

did it : Set kernel '6.5.13-5-pve' in /etc/kernel/proxmox-boot-pin. let's see the results.

have got automatic crash monitoring/reporting - today got: !!! ATTENTION: PROXMOX CRASHED !!! - so numa: 0 did not help

just did it: numa: 0 let's see, if it's help & thanks

proxmox: description: SERVER product: P5K-E width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 RAM: 8GB configuration: boot=normal chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=xxxxxxx description: BIOS vendor: American Megatrends Inc. version: 1305...

Virtual Environment 8.2.2 RAM: 8GB pve-manager/8.2.2/ (running kernel: 6.8.4-3-pve) Linux prox 6.8.4-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) x86_64 GNU/Linux BOOT_IMAGE=/vmlinuz-6.8.4-3-pve root=ZFS=/ROOT/pve-1 ro root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet...

Excellent post-work Kyle. I will rework/revise upon your recommendations (good points about alignements).

Great Job, Kyle - you gave me a guideline for the drawings :) check it out .. the are mines -->

and of course step 7 at the end of all: 7. Run “proxmox-boot-tool” ----------------------- proxmox-boot-tool format /dev/sda2 proxmox-boot-tool format /dev/sdb2 proxmox-boot-tool init /dev/sda2 proxmox-boot-tool init /dev/sdb2

Thanks very much for this fantastic work, Kyle ! In the meantime i did successfully did the migration just - (i think at least) with another approach. During the Migration the whole system was up no downtime was needed: Prereq: we have a (ZFS ZPOOL) rpool (mirrored) with two disks: /dev/sda2...

Thx Fabian for your excellent explanation.

Thx Fabian, ok understood. What is the advantage having more than one ESP ? To have the chance/possibility to boot the systems from any of the ESP Partitions and so to get some kind of redundancy (if one of the ESP would fail) ?

ZFS: Switch Legacy-Boot to Proxmox Boot Tool https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool#3._Finding_potential_ESPs currently i'm running: pve-manager/6.4-13/9f411e79 (running kernel: 5.4.166-1-pve) To be best prepared to upgrade to v7.1 i want/need to switch from...

i'v attached three ZFS(zvol) Disks to the VM (two of them over virtio, one of them over scsi)

After taken a ZFS Snapshot with the GUI (Proxmox 6.2-11), the GUI is writing, that the Snapshot was taken successfully. After clicking again to the GUI Snapshot context, the snapshot is not visible. But on CLI by entering "zfs list -t snapshot" the Snapshot for all the attached Disks into the...