Search results

Hi, We do have that setup for a non profit, using dropbear to unlock / with SSH. It works fine, including on a cluster and a shared iSCSI VG using LUKS (this is not obvious, but doesn't apply to your setup). It has been running since Proxmox ~7, and now on 9.1.. It's fine.

Maybe add a network packet dump.. that feels a bit weird..

This feels like a hardware issue.. or maybe the software watchdog kicking in, but you'd have logs.. what does dmesg(or dmesg -Tw) say? What's the status on RAM when the backup happen?

I'd use ZFS, but you sure can do RAID 10.. for 10 disks of 6 TB, raid6 is still reasonnable though, but yeah..

Your actual problem is systemd going to rescue.. plymouth shouldn't be installed on proxmox, I think, maybe it came with a dependency from someone installed.. What state is your proxmox install? does it drop to a root shell? Can you try to boot the former kernel (might not work..) from GRUB?

I somehow really wonder who on Earth would require a java lib in 2026, but hey, you do you, nice work! Maybe that can be useful on Android though..

vm-101-disk-0 is the only LV appearing, I guess that's the one you want.. what you should do is create another VM to attach that disk, or you could even get its conf from the former PVE node, if you have it (/etc/pve/qemu-server/101.conf) and put it on the new node you show there.. either move...

tu as un peu court-circuité un autre sujet.. ça serait plus fin de créer ton propre thread dans le forum.. pour ton problème, tu as du malencontreusement attacher des disques de VM et non juste des sauvegardes sur le stockage en question..

Haha. This is an old thread, but.. On Proxmox 9.1, a rather active Debian 13 VM fully froze just around receiving fsfreeze during a backup task. Investigating..

I missed the reply, but.. I was indeed pinpointing the issue that could happen without the stretch mode enabled, as it was suggested as a workaround.. But yeah.

ah, just read @ https://docs.ceph.com/en/latest/rados/operations/stretch-mode/#individual-stretch-pools that netsplit cause IO block with individual stretch pool, so, not exactly the good usecase..

Hi, Has anyone experimented with ceph stretch pools that seem to have appeared in squid? (not stretched clusters) It seems rather new, but rather interesting, as it may not require the whole cluster to be set to stretched, while still dealing with the guarantee of OSDs and monitors being on...

Hmm.. what would your pools settings be then? 4/2 for the stretched one? Problem would be that you might end up with only one replica at the other DC there (so IO block until recovery?), unless you actually set it down to 4/1... Also, I may be wrong, but in that scenario, you could have...

I guess you have enough RAM on the host to fulfill that RAM need? And that virtio_balloon is loaded on TrueNAS? (lsmod | grep virtio_balloon) Also, I'd give the VM a bit of swap, in case balloon deflation doesn't happen fast enough for process to get enough RAM... The "precise" number of 8G...

The linked articles suggests using zfs import as readonly to work around the bug/issue, maybe that can save you… It's a bit too precise / specific from this point for me to help you further…

Well, technically, it's a LV, yes, but it's not directly a mountable partition, it's a raw device, that has its own partition table and all (unless you used it directly as a filesystem, without a label nor a partition there…). So you *could* mount it, but it's not that simple. Also, it's...

Is there anything classy you guys don't do hahah! That is impressive, I think one of you mentioned it @ FOSDEM now that I think of it..

Do you see the disk as having the good size in Proxmox GUI? (or using pvesm list VM-Import | grep ' 105$' ), What does the subvolume tell you, from the host? (zfs list testzfs/subvol-105-disk-0) It's indeed not normal for the container to not have been resized by the GUI process, it might be a...

Setup a VM with a live ISO to boot and inspect all disks, and if it's the same OS as your VM, you can even install grub from there. Say it's Ubuntu, boot it (or boot it live using netboot.xyz for even more fun! ;)), then check what lsblk has to say, then try mounting partitions in /mnt to find...

It's a good suggestion, maybe open a feature request on bugzilla?