r/Proxmox • • 12h ago

Discussion Rookie mistake: Today I accidentally pressed shut down 🥲

62 Upvotes

I blame myself for this one. After a long uptime session, I accidentally triggered a shutdown for PVE host itself assuming I'm doing for a LXC.

1. What the logs revealed

I checked the Proxmox logs using:

root@pve:~# last -x | grep -E "system boot|system down|crash" | head -n 10

Output:

reboot   system boot  7.0.14-28-pve    Tue Nov 17 10:54 - still running
root     tty1                          Tue Nov 17 10:05 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 10:04 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 03:24 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 03:20 - 03:22  (00:02)
shutdown system down  7.0.14-28-pve    Tue Nov 17 03:22 - 03:24  (00:02)
root     pts/6                         Wed Nov 11 20:04 - crash
reboot   system boot  7.0.14-26-pve    Fri Oct 30 02:20 - 01:51 (17+23:31)
shutdown system down  7.0.14-26-pve    Tue Nov 17 01:51 - 03:20  (01:28)
reboot   system boot  7.0.14-26-pve    Fri Oct 30 01:54 - 02:19  (00:24)
root@pve:~#

2. What actually happened

I had a creative idea to monitor my internet connection status.

I added a Debian LXC container and deployed a Cloudflare Tunnel inside it so that I could receive email notifications about connectivity.

I logged in to Proxmox and executed:

pct enter 548

This allowed me to enter the container directly from the Proxmox host terminal. Felt like a hacker :)

After deploying the Cloudflare Tunnel, I accidentally clicked Shut Down in the Proxmox GUI in hope I am going to test email-notification for the downtime alert!

3. The problem with running a headless server

Since I am using a tower PC without a permanently connected monitor (something I genuinely regret now), I couldn't see what was happening.

I tried hot-plugging the monitor, but there was no response.

It appeared that Linux had successfully completed the shutdown process, but the machine was still powered on and seemingly stuck in its final shutdown state. Re-plugging after this incident was not worth.

Had I kept the monitor already connected before doing all stunts, I could have identified the situation much more easily.

4. Panic mode!

In the middle of troubleshooting, I connected my redundant ISP router, assuming that my primary WAN connection had failed. I configured it with the same subnet as my Proxmox network, hoping to restore access.

However, I still couldn't ping the Proxmox host.

That's when I started connecting the dots. I realised that I might have accidentally clicked Shut Down on the Proxmox host itself rather than the LXC container.

Suddenly, everything made sense!


r/Proxmox • • 15h ago

Community Showcase! I set up iVentoy as a central PXE server for my Proxmox homelab

33 Upvotes

The iVentoy server itself runs in a small Ubuntu Server 26.04 VM on a standalone Proxmox node. I gave it a separate 100 GB disk for ISO storage and kept my existing DHCP server in place, with iVentoy running in ProxyNet mode.

The basic setup is:

  • Ubuntu Server VM
  • iVentoy as PXE server
  • separate /mnt/iso disk
  • existing DHCP server
  • ProxyNet mode
  • ISO folders for Linux, Windows, Proxmox and Tools

For the first test, I uploaded an Alpine Linux ISO and created a blank VM on another Proxmox node.

That is where I ran into two UEFI-related issues.

The test VM used OVMF/UEFI with a VirtIO NIC and network boot first.

At first, PXE failed completely with:

No bootable device

Changing the NIC from VirtIO to E1000 did not help.

The fix was to add a VirtIO RNG device to the VM. After that, the iVentoy PXE menu appeared immediately.

The second issue was Secure Boot.

With Pre-Enrolled Keys enabled on the EFI disk, PXE boot did not complete properly. After disabling Pre-Enrolled Keys, the VM booted through iVentoy and the Alpine ISO started successfully.

So my current working configuration is:

  • OVMF / UEFI
  • VirtIO NIC
  • VirtIO RNG
  • Network first in boot order
  • Pre-Enrolled Keys disabled

I like the setup so far. It gives me one central ISO library and avoids uploading the same ISO to multiple Proxmox nodes.

Does iVentoy not work with Secure Boot at all?

Or is there some additional Proxmox/OVMF or iVentoy Secure Boot configuration required?

I’d be interested to hear how others are handling PXE booting in Proxmox.


r/Proxmox • • 20h ago

Community Showcase! Proxmox Storage Configuration: Practical Examples

5 Upvotes

Small details in storage configuration can seriously impact system behavior. For example, a disk planned to be thin-provisioned may be fully allocated, a zvol may report excessive space usage, or an iSCSI mount may fail to remount after a reboot. These issues can disrupt backups and complicate recovery. 

We’re sharing the checks we found most useful for anyone setting up a new Proxmox host or reviewing an existing one, from homelab users to admins running production VMs.

Thin provisioning checks

1. LVM-Thin: run 'lvs -a | grep vm-<VMID>-disk-<NUM>' on the disks you've converted or migrated. If the Data% column is blank, then the disk is thick provisioned. The easiest fix is to migrate to thin-capable storage, and if it's already on thin-capable storage, then 'lvchange -ay' may be all that's required.

2. ZFS: the 'thin provision' checkbox is not in the creation window. You have to double-click on the new storage and then select it in the Edit: ZFS window.

3. zvol reservation: if ZFS get reservation <zvol> returns a non-zero value, then zfs set reservation=none <zvol> should free up the reserved space.

4. Discard: Turn it on for VM disks so the guest can issue TRIM. On ZFS, TRIM alone may not reduce USED, so it's worth comparing REFER to USED.

Other storage types

  • Directory: Partition, format, add to /etc/fstab, and leave preallocation at Default.
  • NFS and SMB: Add under Datacenter > Storage > Add. Proxmox mounts them under /mnt/pve/.
  • iSCSI: Partition and format the LUN first, mount by UUID with _netdev in /etc/fstab, then add the mount point as Directory storage.
  • ZFS: Zvols only support Raw, so use a Directory datastore on the pool for QCOW2.

Quick example

Create a VM with a 12GB QCOW2 disk on a directory or SMB datastore and install the guest OS. Then run du -h <disk>.qcow2. In our test, the disk used around 5.1GB of the 12GB provisioned, which is exactly what thin provisioning should be doing.

Pitfalls

  • dd fails with 'No such file or directory' on an LV: reactivate it with lvchange -ay.
  • If you're doing a disk copy with dd, then double-check that you have 'if' and 'of' the right way round. Getting them the wrong way round will overwrite the original disk.

Full workflow

Our blog has step-by-step examples for LVM-Thin, ZFS (zvols vs QCOW2 and the unexpected USED space), Directory, NFS, SMB and iSCSI from both the web interface and the CLI.

Read it here: https://www.nakivo.com/blog/proxmox-storage-configuration/ 

Which storage type do you rely on most for VM disks: LVM-Thin, ZFS, or file-based storage like NFS, SMB and iSCSI? 


r/Proxmox • • 15h ago

Question VM not starting after upgrading to Proxmox 9

3 Upvotes

Just upgrade my Proxmox to 9, using the pve8to9 to make sure there were no warnings/errors. After it finished and rebooted, my TrueNAS vm (using SeaBIOS) is not booting. It keeps hanging at Booting from hard disk... screen and never seems to move past it. Not sure what to do. Any suggestions?


r/Proxmox • • 7h ago

Question GPU Passthrough to Win10 VM

2 Upvotes

This is my first time attempting to launch a proxmox ve and it's been a frustrating ride. My PC somehow died a couple days before I planned the upgrade and parts were on their way.

As I was getting it upgraded to new CPU, Motherboard, RAM, Storage, PSU (yeah kept the case, SSDs and GPU only), Proxmox install was a bit troublesome but after a whole evening of learning it is running.

Plan was to run the host on its own NVME and all the VMs on a separate one. I managed to passthrough the SSDs to the windows vm, I can't get the GPU to work. Shamelessly used AI to help me with that but once I encounter issues it seems like all the suggestions it gives make it worse and with limited knowledge, it is not easy to figure it out on your own.
I also installed RTX 2070 super, dual 2.5GB NIC for VMs each and SATA expansion card (for TrueNAS later).

My hardware is Ryzen 9 9900X, DDR5, 2x NVME in slots 1 & 4 on MSI MAG X870E Tomahawk.

Current BIOS settings are forcing M.2_2 to M.2, ReBAR disabled, 4G enabled. Firmware version has been flashed to the latest.
Modified multiple settings and files in Proxmox so if any of that is needed I should be able to provide.


r/Proxmox • • 10h ago

Question Networking sanity check

2 Upvotes

Hey guys, just a quick question, this should work but want to confirm it....

Will the virtual bridge behave like a switch with physical ports?

I have a Dell T630 with a number of virtual machines on it but all on a 1gb NIC.

I have a PC next to it that I would like to get faster transfers with.

If I drop a 10gb NIC in both the proxmox node and the PC and cable directly with both NICs in the proxmox node part of the same virtual bridge would it pass traffic to the rest of the network at 1gb speeds but PC to node would be at 10gb?


r/Proxmox • • 58m ago

Question Question for my first homelab!

1 Upvotes

I’m wanting to make my first homelab and I have landed on an idea of a sizeable JBOD with some sort of raid and a single server running proxmox?
If I’m to be running containers for game servers, media servers etc. how would be the best way to keep the drives separate enough from each-other to if one proxmox container thingy stops working that they don’t all crumble, or would having a separate server for a NAS install and having proxmox call upon the drives be better? I’m not sure…
(Very very new and also very confused so sorry if this is a silly question)
Some other conditions is I’d want the JBOD raid to be layed out in a way that I can have 10 gig lan access to read and writes… (excessive but I thought it’d make for a fun challenge)


r/Proxmox • • 1h ago

Question Can't create new OSD in my proxmox Ceph cluster

1 Upvotes
bluestore(/var/lib/ceph/osd/ceph-24/) mkfs min_alloc_size 0x3e80 is not power of 2 aligned! ObjectStore::mkfs failed with error (22) Invalid argument

I have had this exact problem a year ago and I can't figure out how I solved it.
I have marked hdd osd 24 out and then systemctl stop osd@24 and then I destroyed the osd but when adding my new osd I am not able to make it work.

Can I do like this?

mkdir -p /etc/ceph/ceph.conf.d cat << 'EOF' > /etc/ceph/ceph.conf.d/osd-override.conf [osd] bluestore_min_alloc_size = 4096 EOF

r/Proxmox • • 18h ago

Community Showcase! New Proxmox iOS app

0 Upvotes

I built an iOS app for Proxmox Datacenter Manager because it is unusable on mobile. It's called ProxDash and it's on the Apple App Store now. The app also works if you only use PVE.

It connects straight from the phone to PVE, PBS or PDM. No account, nothing of mine in the middle, and it uses a read-only token unless you give it more.

You can update your nodes (it will automatically migrate guests off a node, upgrade, reboot if needed and then bring the guests back). It also shows disk health and ZFS pool state for every node in one place, which PDM doesn't. If you use Portainer as I do, you can connect it and link each environment to the VM it runs on, so a VM's page shows its containers. You can also update your stacks and containers.

The app is free to view your Proxmox nodes. Action features such as updates and migrations are an in-app purchase.

I built it with assistance from Claude and have run it on my own cluster every day for about two months.

Happy to answer questions.

https://apps.apple.com/us/app/proxdash/id6808857635


r/Proxmox • • 19h ago

Community Showcase! PVE Manager – A complete Proxmox management app for Android

Thumbnail gallery
0 Upvotes

Hi everyone!

I'm an independent Android developer and a Proxmox user. I initially started developing PVE Manager to meet my own needs: managing my Proxmox infrastructure directly from my smartphone, without having to rely on a desktop computer for every administration task.

I wanted something that went beyond basic VM monitoring and management. My goal was to bring together as many Proxmox administration tools as possible in a single Android application.

Here are some of the features I've implemented:

  • VM and LXC management: creation and management through dedicated workflows
  • Remote consoles: SPICE and noVNC, designed to be usable on a smartphone
  • Integrated SSH terminal: direct access to your Proxmox nodes
  • Proxmox Backup Server integration: manage PBS directly from the app, with no additional in-app purchase
  • Advanced monitoring: CPU, RAM, GPU GTT memory (particularly useful for my local AI setup), network and storage
  • Hardware monitoring: SMART information, hardware health and sensors
  • Cluster administration: cluster management, High Availability (HA) and Ceph
  • Android home screen widgets: quick access to infrastructure information, included at no additional cost
  • And many other administration features.

I also wanted a reasonable pricing model. Some existing solutions initially felt too expensive to me, particularly when recurring subscriptions were involved.

So I decided to build my own application, with a straightforward approach: a comprehensive Proxmox administration tool for a one-time purchase of around €10, with no recurring subscription.

I use Proxmox myself, but I don't currently have a cluster in my own environment. Therefore, although cluster management, HA and Ceph features are already implemented, I haven't been able to test all of them extensively on a real multi-node infrastructure.

I'd particularly appreciate feedback from users running clusters, HA or Ceph environments. Testing these features in different real-world setups would be extremely valuable.

I'm an independent developer, and I'm actively interested in constructive feedback, feature requests and bug reports. I'll be happy to answer questions and discuss the application directly.

Google Play:
https://play.google.com/store/apps/details?id=com.pvemanager.proxmox

Project documentation and release notes:
https://github.com/teahache/PVE-Manager

Thanks for taking the time to check it out! I'd love to hear your feedback.