Search results

I'm still kind of curious if there's a way to tell PVE to not start at boot time. Feels handy for backups for sure, but also if I'm just troubleshooting something, and I want to look around on the PVE Host without the complexity of PVE running....

I'm trying to be smart, and do a bare-metal backup of my Proxmox VE. But clonezilla is failing to start. I'm trying to simply backup the entire boot disk for my PVE. Should just be the device "nvme0n1", which happens to have three partitions on it. That's how Proxmox configured it. But...

Agree with you on the risk, for sure. Thx for sharing your backup methodology. Do you restore files one-by-one, or just restore the entire /etc/pve directory over the existing /etc/pve directory ?

Booted into a debian liveOS, and tried same. Same result as above. You have to manually create ~root/.local/share. Weird.

Agreed, the risk is real. Just sort of surprised there isn't a simple way to shutdown PVE and start it back up. I like your model (infrequent block-level backups). Is there a known list of config files that need to be restored during a recovery ?

That's exactly right. If I can quiesce the filesystem, reduces the risk of open files during a backup.... Not perfect for sure, but I don't really need perfect here.... "Good" is good enough.

Anybody know how to shutdown Proxmox VE from the command-line ? There are a surprising number of unit files.... root@cube:~# systemctl list-unit-files --state=enabled | grep ^pve pve-cluster.service enabled enabled pve-firewall.service enabled enabled pve-guests.service...

Thanks for the confirmation.... I'll investigate clonezilla to see if it's any better than dd (I know dd is rudimentary, but it works).

After suffering recent failure of my Proxmox VE boot disk, I'm contemplating a better (but simple) Disaster Recovery Strategy. Option 1: Boot from a LiveOS, use "dd" to backup my (now unmounted) Proxmox boot disk (safest, but requires prep) Option 2: Shutdown Proxmox VE application, use "dd"...

Thanks for your quick reply, Bob. You didn't really ask, but "tldr" is an abbreviated version of the man pages. Shows you the "useful" version of super long man pages, kinda handy. And yes, you're right, usually, the first time you run tldr, it grabs (and caches) a copy of the popular tldr...

In case it's helpful, a bit of info on my environment: root@red:~# cat /etc/os-release...

Love "tldr" on all my linux machines, so figured I would install it on Proxmox VE, which is just Debian 11 after all. Doesn't seem to work, tldr pages aren't available root@red:~# apt install tldr...

Contents of /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Proxmox Virtual Environment" GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="text" # Disable os-prober, it might add menu entries for each guest GRUB_DISABLE_OS_PROBER=true # Uncomment to enable BadRAM...

I installed Proxmox on a 2013 MacBook Pro. Works reasonably well. But can't get the text console working (I prefer the text console as underlying OS doesn't need any desktop env) Here's the process I followed: Couldn't boot from proxmox USB key So I installed Debian (standard) instead Text...

In case it's useful, here's the handy command for setting a root password in a qcow2 image before booting: virt-customize -a /var/lib/vz/images/101/vm-101-disk-0.qcow2 --root-password password:topSecretPassword

I'm a fan of grabbing pre-built qcow2 files from the big distros (e.g. Fedora), and booting them right up. Saves me have to build VM's, and they boot right up. Here's my process: build a dummy vm Grab a qcow2 from vendor using wget copy right over the VM's generic qcow2 file Use...