Search results

Setting `intel_iommu=off` allowed me to boot and login without error! I was able to do that by editing the grub entry for Proxmox at the boot screen (press 'e') and changing `intel_iommu=on` to `intel_iommu=off`, before pressing F10. Unsurprisingly, I was wrong, and the VM was set to boot...

I edited /etc/network/interfaces at the recovery console and after an `ifreload -a` I confirmed with `ip l` and `ip a` that things looked good. When I reboot I still can't login from the normal login prompt (same reset issue in first post) and I can't access the web GUI. Oh, I didn't see this...

I surprisingly can get into the recovery console (offered as a boot option).

I can't seem to even attempt a login anymore after swapping motherboards. Please note before you read further that the PHYSICAL console login (accessed over IPMI) is broken, not the Web GUI. I know swapping the motherboard rendered my old networking configuration completely wrong. I'm trying to...

These steps worked for me with one addition: After converting an ide disk to scsi you have to add scsi to the boot order or your VM will no longer boot, and NOT from the bios but from the Proxmox GUI here:

Wow that's a pretty intense workaround. Thanks for providing it but I think I'll sit out this upgrade for now.

The youtube video was taken down ("This video has been removed by the uploader"). Anyone have any advice? I'm on Proxmox 7.1-10 and I tried Default, KVM64, and host for CPU. All give me the same error about "Common KVM Processor" being unsupported.

Hah, whoops. That's good that kind of mistake can't break your system, hah. Fixing the repo immediately got me going on 1.1.13. Thanks, @Dunuin !

I'm trying to follow the instructions and upgrade from PBS 1.1 to 2.x. The instructions say: apt update apt dist-upgrade # verify version: proxmox-backup-manager versions proxmox-backup-server 1.1.11-1 running version: 1.1.11 (or higher) But I can't get to version 1.1.11 if I dist-upgrade with...

I wrote-up my full instructions here in case anyone wants to set this up like I did. Please give me feedback.

This did the trick: ip a to get the new interface name (in my case, enp0s4 (see above) nano /etc/network/interfaces, change old device name to new one (in two places). My resulting file is: auto lo iface lo inet loopback auto enp0s4 iface enp0s4 inet static address 192.168.0.19/24...

This seemed easy so I gave it a shot. Since my zfs pool was already setup as storage on the Proxmox side I created the PBS VM using a 'raw' image and UEFI bios and put the disk on the zfs pool. Once I had PBS installed I went to the TrueNAS server and I used `dd` to copy the .raw image into a...

Oooh that makes way more sense. Got it

We're super in the weeds here and I definitely don't think this is important, and I appreciate you indulging me, so if you'd like to keep going: That sounds like a valid case you might want to support but I don't think that's how (good?) password managers work. LastPass at least treats the...

OH I just had an epiphany. I bet LastPass auto-filled the password field with my Proxmox management interface password. I will verify this the next time I setup a new node but that might be a while. If you'd like to prevent this from happening (because you can't fix people not noticing things)...

Oh interesting. I just pasted the info, many fields got filled out, and I clicked "Join". Perhaps it didn't fill out the password field, I didn't notice, and the field wasn't actually required so it let me attempt to join with no password? I can't check anymore because I'm joined and can't...

Not sure where I had the chance to have an incorrect credential. I was never prompted for credentials. I copied the cluster info from the machine in the cluster and pasted it into the node that was trying to join. I just decoded the copied cluster information (JSON.parse(atob('.....'))) and I...

I see this in access.log on the host I created the cluster on: root@<CLUSTER-CREATING-NODE>:/var/log# less pveproxy/access.log | grep <JOINING-NODE-IP> <JOINING-NODE-IP> - - [07/04/2020:17:40:27 -0700] "POST /api2/json/access/ticket HTTP/1.1" 401 13 <JOINING-NODE-IP> - - [07/04/2020:18:00:29...

I wasn't able to join my new cluster through the GUI and I couldn't figure out why. I made sure all the prerequisites from the wiki were met (same version of PVE, same system clock, etc), but everytime I tried to join I got a "401 Authentication Failure" message. Fortunately, it instantly...

For anyone following along, I was able to finally get a stable system by using a recommended (by SuperMicro) as compatible M.2 drive: Toshiba XG5-P (HDS-TMN0-KXG50PNV2T04). The other drives I had in the system (HP EX900 120GB and Intel 760p) didn't seem to have any detectable problems, but this...