Search results

Wow! Thanks so much for the detailed update @Max Carrara ! I (and I'm pretty sure everyone else in this thread) greatly appreciate all of the time you spent down this rabbit hole. Also thanks for all of the links and references! Truly above and beyond

The patch is also not working for me using Proxmox 8, 6.2.16-8-pve kernel on a DL360 G6 with a P410i. I ran all of the commands successfully but I still can't seem to see any of my disks after the os restarts. If anyone has any suggestions for how I could get this to work please let me know...

I'm also encountering the same issue on a brand new PVE8 install. I'm also curious to know when the update will propagate to PVE's ceph-quincy

Sure! arch: amd64 cores: 2 hostname: Heimdall memory: 2048 net0: name=eth0,bridge=vmbr0,gw=192.168.1.1,hwaddr=16:77:88:68:9D:6F,ip=192.168.1.221/24,type=veth onboot: 1 ostype: ubuntu rootfs: local-zfs:subvol-100-disk-0,size=32G swap: 512 lxc.apparmor.profile: unconfined...

Good question! It seems to only be CT 106. The only thing I'm seeing in syslog during the backup job is this: Nov 14 09:18:32 vmworld pvedaemon[222298]: INFO: starting new backup job: vzdump 106 --compress zstd --mode snapshot --node vmworld --notes-template '{{guestname}}' --remove 0 --storage...

Hi everyone! During one of my automated weekly backup jobs, I noticed one of my new containers that I setup this week seems to make the job get stuck when doing a snapshot backup. For some reason, it gets stuck saying INFO: create storage snapshot 'vzdump'. I also tried doing a snapshot backup...

Gotcha. Thanks for the heads up! EDIT: Everything appears to be working! Thanks for the help again!

Hi everyone! Another post in the saga of upgrading my Proxmox node from PVE 6 to 7. This time I'm trying to switch my legacy boot system to the Proxmox Boot Tool. For reference I've been following this guide on the wiki and am currently using RAID-Z1 with two disks. When I run lsblk to find...

Thanks for the help! I got it to work now. It looks like I also needed to comment out an additional line

Awesome, thanks! I found the file in /usr/share/perl5/PVE/CLI/pve6to7.pm, although it seems my changes are not taking any effect. I found from an old forum post that I need to restart pvedaemon, but unfortunately that didn't fix the issue. I assume I'm missing something? Thanks!

Hi everyone! I'm currently in the process of finally getting my host ready to upgrade to pve7 and I've been running into an annoying issue with the checklist tool. One of the warnings I get is: Since I have quite a few containers, I basically have to go through each one at a time and fix the...

Many updates after I'm still running into this issue even after creating a new VM and converting it into a template and then backing it up. However, I've decided that I don't think it's worth pursuing the issue any further. Thinking back on it now it seems a little redundant to automatically...

I'm assuming that probably would have done the trick. It seems to be working now. I never got an email notification about your reply, so here we are a few weeks later. Thanks!

Hi! Whenever I go to the datacenter summary page and scroll down the scroll bar jumps back up again. This happens about every 5 seconds. I've tested this on Chrome and the non-Chromium version of Edge. Is anyone else having this issue or is it just me? Thanks! PVE Version: 6.2-4 Package...

Ah, gotcha. Thanks for info! EDIT: For future reference, this has been fixed as of PVE 6.2

Thanks! I find out a bug in the bug tracker which matches my issue and I found the fix that you made for this. Any ETA for when this will hit the test repo or the stable one? I found somewhere that the fix was coming in version 6.1-12. I used to be able to create 128K efi disks with ZFS...

That is the correct way to update. However, it is strongly encouraged to create a backup of the host and all VMs before updating in case something goes wrong. There should be minimal interference with your VMs, however, don’t quote me on that. Just a heads up, Proxmox 5.x will reach its end of...

I found a nice backup script on github if you’re interested Link: https://github.com/DerDanilo/proxmox-stuff

Yes, deleting the template won't cause any problems. If you have any doubts you can always backup the template and then restore it if things don't work out. As the clone you made was a full clone that means that the VM is completely separate from the template VM. If it was a linked clone then...

I guess that settles the issue. I'll set up some new templates and clone the linked VMs. I'll set this topic to solved after a few weeks of monitoring if all goes well. Thanks for the help and all of the patience with trying to work this out!