Search results

SOLVED: Okay- I had to disable CSM, and then ensure that M.2 and/or pcie were set to disable legacy mode, rather than "auto" mode. After that, the installer picked up that it was an EFI boot, and everything working beautifully. Hope this helps someone else! Cheers.

Not sure if it's helpful information, but when the installer has finished and I select to reboot the device, there are a bunch of SQUASHFS errors that show up (attached). When trying to boot from the proxmox ISO, into recovery boot I get errors too (attached).

Hi there, I currently have 3 working Proxmox Nodes on various OVH dedicated servers, all working well. New one (ADVANCE-APAC) is not playing nice though. After installing over IPMI, utilising ZFS and raid1 (2 x 1.92TB SSD NVMe), it fails to boot stating there is no bootable media. Seemed like...

Nevermind. (Was going to remove this to save embarrassment, but I guess it may help someone else down the track). IOPS was indeed extremely poor due to network latency. I spun up a public cloud instance in the same DC as one of the nodes and read IOPS are approx 2000, with read/write being 150-200.

I have two nodes set up, geographically 3-4,000 KMs away (200ms). Node 1 (3 x 1.92GB SSD) scores great IOPS testing using FIO, around 470,000 for sequential reads, and around 2000MB/s. For random read/write, around 2500 IOPS, and 10MB/s. Node 2 (2 x 480GB SSD) scores great IOPS testing using...

Turns out following this advice helped: On every node do systemctl stop pve-cluster This may take a while On every node do sudo rm -f /var/lib/pve-cluster/.pmxcfs.lockfile On each node – one by one do systemctl start pve-cluster Which is odd, considering I don't use a cluster? Any ideas as...

Nope! /dev/fuse 30M 24K 30M 1% /etc/pve root@s5:/etc/pve# du 2.5K ./priv 5.0K ./nodes 1.0K ./.le 13K .

Thanks for the quick reply, Stoiko. Not a cluster unfortunately. Single node. The first line in the log that has kicked off the issue both times is Mar 24 05:40:24 s5 pmxcfs[1780]: [database] crit: commit transaction failed: database or disk is full#010 Which database or disk? No disks are full.

Hi there, This is the second time I've ran into this issue over the past few weeks. Server working fine, when suddenly I'm unable to log in via Web UI. Syslog shows "Mar 24 21:01:19 s5 pvedaemon[14546]: authentication failure; rhost=xxx user=root@pam msg=error with cfs lock 'authkey': got lock...

Well there you go! After waiting 35-40 minutes, the GUI showed. How very strange!

"Above 4GB decoding" was disabled for me. Enabling it made no difference.

Unfortunately, my drives are SATA. Also, bios is on 2.2 (2.2a is latest, but a minor update). Image attached of last seen on IPMI before "No signal"

Any other suggestions to solve this?

Just to add to my stats- it's a Supermicro X11SSE-F board. Supermicro issue? I'd love to be able to use Proxmox 6!

I'm having the same issue today, using Proxmox 6.0 ISO. Using IPMI, booting via virtual ISO, get past the first prompt and then "No Input" where partition setup usually is. Xeon E3-1245v5 - 32GB

Ahh nevermind. I simply changed the password (after being asked a large number of times to login) and it seems to be working again. (Even though I only changed the password back to itself). Very strange.

Starting yesterday, I am asked to login MANY times in the web GUI. When I first load the GUI, I am asked about 12-15 times. From then, each time I click on anything it will ask me 1-5 times depending on the resources to load. Each time it accepts my user/password, it loads one more resource...

Hi there, I've been running a new node with 4.3 for a couple of weeks now and everything has been pretty great. Just now, the server became unresponsive (even to pings) for several minutes. Looking in syslog I found a few kernel errors: Oct 08 12:12:16 s1 kernel: INFO: task pvestatd:5982...

Great, thanks for your help wbumiller and dietmar. Problem solved!

I would assume utilise ".pve-ignore." for the interfaces in the guest and manage internally, but still unsure how to assign the IP addresses from the host, as there is no GUI option now.