Recent content by bryanpedini

Can you describe a little better the situation? Are you in dual boot with windows? What are the steps you've taken, the expected result, and the outcome instead?

as neobin stated, the "shared" flag on a storage means that the storage will be available to all hosts as configuration, but you have to mount it first on the host system. this can be achieved in several different ways, from the easiest to the hardest. you can create a NAS vm on that host with...

ssh into the machines, look into your known_hosts file, see if keys match what you find in /etc/ssh in the various nodes, and go from there. you can use this command to probe the public key for host B while connected to host A: ssh-keyscan -t rsa <host> | sed "s/^[^ ]* //"

Hello, I'll prefix by saying that I'm a half moron even trying to attempt stuff like this. With that out of the way, I'll explain a bit of circumstance: I recently moved home, and I still have a NUC Proxmox 7.4 node `tinypve01` in my old house (grandma's) and I have a new server at my new...

exactly correct - I thought to ask here just in case the PVE team did something to the installer to make it compatible with ZFS unattended installation. so I either install debian unattended without ZFS, or I install debian manually with ZFS and install PVE on top (useless method), or I install...

this is what I've been doing all along with a Debian unattended installation + Ansible playbooks... thought there was an easier method with PVE directly as I'm more and more transitioning towards two disks with ZFS.

IIRC efi variables are stored in the motherboard nvram, they're entrypoints to your os bootstrap, if you reinstall a lot, and you reinstall systems that do not reuse variables, you could end up with no space left to insert another entry to boot your last installation of [something] - if you...

hello, as per the title, does proxmox support any equivalent to debian preseed.cfg? I'm most interested in the disk layout and custom options (the things the proxmox installer asks that the debian installer usually does not, administrator's email for example). thanks in advance.

the thing is... dunno why, but now login works fine just fine, and I did nothing of that, it just started working like after a reboot or two (something I didn't do after joining the node, I guess rebooting the new node updated the configuration or something). now the issue I need to sort out is...

oh yeah, that. I thought about new nodes and/or renaming old nodes migrating all VMs to other servers first and leaving it empty. it's true that renaming a node is a PITA but if done correctly nothing should break and it would just be a couple of reboots...

if you don't use your search domain to reach other devices by hostname, you can put whatever you want in your hostname as it is just a string. for example, if your machine fqdn is "pve1.mynetwork.net" and your hostname is just "pve1", another machine "otherhost" will resolve to...

Another thing on this new host: I'm unable to start VMs - I can migrate there VMs already on, but this is the error I get when starting a new one, both from command line and from the GUI: start failed: command '/usr/bin/kvm -id 50202 -name 'dns02.home.bjphoster.cloud,debug-threads=on'...

Hello, This morning I installed and joined my existing cluster of 3 nodes with proxmox ve 7.4-3 a fourth node with the latest proxmox 8.0-2 I successfully logged out and back in a couple of time this morning performing a couple of networking changes to bootstrap the new host ready for...

Hi, I recently discovered this error while doing a backup to a target PBS system, tho unfortunately searching "proxmox" backup connection reset by peer ("os error 104") on the internet (emphasis on quotes on "proxmox" and "os error 104" so they would exactly match) returns like only 3 results...

Try to systemctl stop pveproxy.service the daemon and perform the rename with that stopped so it doesn't read the configurations while you're doing so (or try to stop you). Then it's systemctl start pveproxy.service to get it running again...