Search results

FWIW, I tried to follow the mentioned workarounds and couldn't find something that worked. I ended up editing the VM conf file and replacing the ide parameters: media=cdrom replaced with cache=unsafe, which causes the drives to be treated like normal hard drives, maybe just removing media=cdrom...

Thanks everyone for sharing their insights/scripts. @SimoneGiacomelli I have implemented your script. Nice work. I performed roughly the following after reading the code and running the unit tests. curl -sSL...

As a follow up to my post #73 in this thread from 2019 where I shared steps for installing Proxmox 5.4 on Hetzner. Last July (2023-07-08) I performed the following steps to create a Proxmox 8.x server on Hetzner. Using a ZFS mirror as the rootfs / rpool. FWIW posting my notes for future...

@doxyproxy FWIW, you might want to check out the solution in thread: Cannot mount xfs raw partition inside (privileged) lxc container.

If I ever figure out how to mount an XFS partition from within a CT I'll update this thread.

Thanks @LnxBil, your info gave me some alternative ideas on how to solve this and pushed me towards a solution. As per post #1, I'm still not able to figure out how to mount XFS within CT's. So I searched for alts. Maybe it does have to to do with permissions/visiblity of the /dev/loop*. See...

Nice diagram @git192prox. The steps make sense. I have attached my review of your script. It includes some comments and I think some small fixes you might want to consider/validate. Two things I suggest for your steps Check your partition alignment, see my guide for how to do with this...

@git192prox I have created a flow diagram to see if I understood your steps correctly, please review at your convenience.

You're welcome. Same to you. You made me think of this meme "We'll do it LIVE!": https://youtu.be/vu2NK5REvWM Your steps look good, streamlined and online! I learned something new with the Evacuation... I didn't know ZFS could do that. Time to check the man page! Thanks for sharing! P.S. you...

Those comments feel very real to me! FWIW, I have undertaken and written up: Switching from legacy boot when there is no space for ESP partition.

FWIW, I have undertaken and written up: Switching from legacy boot when there is no space for ESP partition.

Thanks for sharing your steps @whytf. They inspired me to undertake and write up: Switching from legacy boot when there is no space for ESP partition.

The full version of this content is published here, which includes an intro and more background details. I've tried to share the full steps/guide in this post, but I reached the post size limit, so you'll want to refer to the link provided for the full steps/guide. Missing emojis: It looks like...

Note to self: could re-testing after an aa-teardown at least prove that xfs mounts work and that its an AppArmor issue? It would still be nice to get some feedback from others on this topic.

Greetings, I'd appreciate feedback on if my objective is possible or not, and if I'm doing something wrong. NB: I have done a bunch of reading/research to self-help and find a solution but so far: nope, not working - I tried a bunch of things without success. Per topic/subject - My objective...

Thanks @fiona - i checked a few relevant metrics for the rpool mirror - everything seems ok.

I had issues logging in to the web ui today. Via ssh su - was working fine. Standalone node - no cluster. No obvious space issues or kernel messages # journalctl --since='5 days ago' -k Based on the advice from post #2 I took a decision to run # systemctl restart pve-cluster before anything...

Prior to installing ifupdown2 package which normally handles things much more gracefully and non-disruptively... I had an issue after some networking maintenance whereby I needed to ifdown ifup my vmbr0 and the enslaved tap and veth interfaces lost their master - this caused a network outage...

Thanks to those who have contributed solutions on the thread For what its worth I've captured the solutions I know about on a blog post. Proxmox: solutions to restore guest networking after vm bridge interface maintenance on the host - without a reboot Critique / edit suggestions welcome.

Thanks to those who have contributed solutions on the thread For what its worth I've captured the solutions I know about on a blog post. Proxmox: solutions to restore guest networking after vm bridge interface maintenance on the host - without a reboot Critique / edit suggestions welcome.