Recent content by jhr

Oh, I understand now — I missed the beginning of his story, where he mentioned starting with a single-disk RAID1. Now it makes sense. I started getting worried about weird ZFS RAID1 behavior, but I did some tests with a regular two-disk ZFS RAID1 setup, and it worked exactly as expected. I...

That's what I'm talking about — he had a fully functional ZFS RAID1 setup, and then one of the two HDDs failed. So I think he should have been able to boot from the other one.

so you are missing those tools in your rescue iso ? did you tried Proxmox iso, Advanced and Rescue boot ? btw: I believe that if you have mirror, you have to be able to boot from both disks and if one of them is dead, you can always boot from the other one, or not ?

maybe wrong disk number lsblk -f

Oops, my bad — totally forgot I’d messed with some ZFS settings in /etc/modprobe.d/zfs.conf. That limited the ARC cache and slowed down all my backups. Sorry! It was nothing to do with update.

ZFS RAID1 should be a mirror, BUT not whole HDD, BUT only part3 (in my scenario, which I believe is default scenario). So you have mirrored data on part3, but to boot from a new drive, you have to clone other parts, which you did anf then you have to reactivate booting using something like this...

I'm seeing the same issue on my servers + backups are now taking roughly 3x longer than before the update. Is is safe to downgrade all packages ? sudo apt install libpve-network-api-perl=0.11.1 \ libpve-network-perl=0.11.1 \ proxmox-ve=8.3.0 \ proxmox-widget-toolkit=4.3.9 \ pve-docs=8.3.2 \...

I have a few servers with Proxmox and a couple of VMs and LXCs on each of it. When I did apt update && apt dist-upgrade, sometimes all my VMs and LXCs were automaticaly rebooted during an update process, perhaps due to update qemu or kvm or something like that. I guessed it is normal behaviour...

I am trying to find the best config for my Proxmox on ZFS rpool. I know that ZFS eats so many RAM for caching. When I am not limiting amount of arc in /sys/module/zfs/parameters/zfs_arc_max, sooner or later I have more than 90% of RAM used. I have for example 64GB physical RAM, my one only VM...

Some kind of steps are allowed only for root (update, USB passthrough, etc)

But I want the opposite, do not repeat missed. My server automaticaly runs jobs ASAP, even I did't check that settings (Run jobs as soon as possible if they couldn't start on schedule, for example, due to the node being offline.)

I have a Proxmox VE server with one VM on it. And I consider to setup a backup job to PBS every hour. But sometimes happen that the backup job is not finnished and a new backup job waits for end of previous backup and when it stops the new backup start immediately and then another backup job is...

I would like to report weird bahavior of free/used space in LXC too. my config: arch: amd64 cores: 2 description: revize 17.12.2024 features: fuse=1,nesting=1 hostname: myene99 memory: 2048 mp1: zfs-mirror:subvol-5099-disk-0,mp=/dsk1,backup=1,size=80G mp2: /dsk0/mybackup99,mp=/dsk0/mybackup99...

Here are Thank you for analysis.

Hi, here it is. It's one of many synced backups, this one is not so big. 2024-11-03T14:53:47+01:00: sync snapshot vm/110/2024-10-27T19:00:25Z 2024-11-03T14:53:47+01:00: sync archive qemu-server.conf.blob 2024-11-03T14:53:47+01:00: sync archive drive-virtio3.img.fidx 2024-11-03T15:04:54+01:00...