Recent content by proxwolfe

Not exactly sure what my issue was. I had a container that would start. Then I updated Debian inside and afterwards it wouldn't start anymore. But it was not the Debian 13.1 issue mentioned above because I checked and it still said Debian 13.0. Anyway, updating PVE (including pvecontainer from...

So I tried this and the conversion worked (as per mbr2gpt). But now, when I start the VM, the console doesn't connect to it anymore. So I don't get to see what is happening in the VM anymore. (I did switch to OVMF.) (At first, I tried without adding an EFI file in PVE - because I thought that...

Thank you. I shall look out for upgrade guides in the future. I had not even considered there might be one.

Ah, no I didn't follow that guide, didn't even know it existed. The upgrade "happened" somewhat unplanned: I have a three node cluster and when one node went into a boot loop I seized the opportunity to replace it with more powerful hardware. When I installed the new node, I installed the latest...

I have this on my Ceph status page. It is my understanding that squid is the latest CEPH release and it is available for PVE. So why does PVE tell me it wants an earlier release?

Thank you, that worked!

The way I understand it, in the folder /etc/pve/nodes/<node B>/qemu-server there are only the conf files for the VMs on node B. And the same goes for nodes C and D. So if I want the VM to be on node D, I need to put the conf file in the <node D> folder (the VM's disks should be on each node via...

I tried that. I rebooted node A without access to the Corosync network (so that it would not mess things up again) and copied all VM conf files to a USB stick. But when I try to copy an old conf file onto node D, it won't let me. It tells me that the file already exists (in...

Hi, I want to shrink my vm disk (I have already shrunk the file system inside. So that's fine). Above, there is a howto for ZFS but my VMs reside in CEPH. What is the right approach here? Thanks!

After I took node A offline again, nodes B, C and D started operating normally again.

Small update: I can now also log in to the GUI of node B when I access its IP directly (all my nodes have LE certificates and can -- normally -- be reached internally via the respective domain names). And when I look into node B's GUI, I see this: Cluster consists of A, B, C, D: B, C and D are...

I have a small three node cluster in my home lab. Everything was working fine until recently one of the nodes ("A") went into a reboot loop (I don't what caused this yet), so I turned it off for later trouble shooting. The other two nodes ("B" and "C") have been working fine since then (Ceph did...

I do have one follow-up question: Now that I know that my normal profile is somehow messed up, is there a way to repair it or am I better off making that new test profile my normal profile and deleting the messed up one?

Never heard of that before. But a new clean profile actually did the trick. I guess I'll have to read up on profiles in Firefox. Thank you.

That's a good idea. But, alas, it didn't help. Thanks anyway.