Search results

Not just that. Grub also fails to boot if any encrypted dataset is present in the pool. See here

For anyone that could encounter the same problem: turns out the problem was that I had created a zfs dataset (in addition to the ones created by the PBS installer) without specifying the dnodesize=legacy option. When grub encounters a dataset with dnodesize=auto (the default), it fails to boot...

Is it possible to build from source the backup client for Ubuntu ARM64 (i.e. raspberry pi 4)?

Today, I started my Proxmox Backup server, and grub fails to boot. The server is a repurposed old machine with two 4TB HDD with ZFS RAID 1. This kind of failure happened to me in the past with PVE, when I was trying to have ZFS disks connected to a Dell PERC controller (an unhealthy idea that...

It also seems that this procedure corrupts the zfs cache files (the system works, but there is a FAILED message at boot). To rebuild it: zpool set cachefile=/etc/zfs/zpool.cache rpool update-initramfs -k all -u reboot

I found out the missing step: at the (initramfs) prompt, force the pool to be imported even if it was last accessed on a different machine: zfs import -f rpool zfs export rpool (the final export step is probably unneccessary, but just in case...) Shut down the machine, remove the temporary...

update: I have realized that I did not backup the boot partition. So for backup I did dd if=/dev/sda2 of=partition-sda2 dd if=/dev/sdb2 of=partition-sdb2 dd if=/dev/sdc2 of=partition-sdc2 and to restore (from removable media) dd if=partition-sda2 of=/dev/sdb2 dd if=partition-sdb2 of=/dev/sdc2...

I have a single machine with proxmox on ZFS with a single pool containing a three-disk mirror. Backups aside, I would like to implement a simple disaster recovery strategy. The idea is to save the partition scheme of the disks on removeble media, and then dump the pool to LTO tape, so to be able...

I have a proxmox installation with two bootable disks in a ZFS mirror (set up from the Proxmox installer): sda, sdb. I have removed a faulted disk ("zfs detach rpool sdb2") and now I want to replace with a new one. I understand that I have to use the "zfs attach" command. However, with which...

I have no experience with hp microservers, but this is how I solved for my case: 1) no swap on ZFS (I don't remember if it was related to this particular failure, but still, don't do it; newer proxmox installers do not do it either). 2) no ZFS disk connected to any kind of pseudo-smart...

Ok, maybe this is a stupid question, but I was wondering... pve-zsync syncs a snapshot of the zvol containing the VM virtual disk. But since this is done while the VM is running (unlike what vzdump does), isn't it possible that the guest filesystem is "frozen" while it is in some inconsistent...

For the record: apparently not only it works with push method, but will pull too. Just use different names for each job (--name option of pve-zsync).

Well, as I wrote above I had very bad experiences with ZFS on the H310, and finally I gave up and settled for the onboard SATA; this way I had no more problems. However, at least on R220 the I/O is not great with this setup. As always, YMMV.

Nine years later I am resuming this old thread to note that the info message is still very uninformative: "only 1 backup(s) allowed - please consider to remove old backup files" I also thought for a long time it was some kind of technical limitation, not a simple proxmox setting. Maybe it...

@mailinglists: Okay, if swap on zfs is known to be unstable there is really no point in doing in-depth tests as @czechsys recommended. I'll get rid of that swap and consider some alternative. Thanks. btw: 1) If the current Proxmox installer does not create swap on ZFS anymore, does it allow to...

You mean an additional physical disk (ie. not the ones where proxmox is installed) and put the VM there?

so, basically, dropping the caches does not work

I've tried this, without disabling the swap: 1. rebooted the host 2. started the guest 3. "sync; echo 3 > /proc/sys/vm/drop_caches" on both the guest and the host 4. started the infamous rsync on the guest 5. after a while, the host rebooted: [ 823.461934] perf: interrupt took too long (2504...

This is not a cluster. They are three separate, almost identical machines carrying different VMs; their only relationship is that they use pve-zsync for backup (not related to this issue, the problem never manifest during that operation). I am showing you all three machines just to underline...

How often? Yes, from one of the three affected machines (see below). They have different specs: machine1: 16 GB RAM, 8 GB swap, total pool size 4TB (mostly unused) machine2: 32 GB RAM, 8 GB swap, total pool size 4TB (mostly unused) machine3: 7 GB RAM, 6 GB swap, total pool size 250GB...