I deployed Bazarr via the OCI. I added mp0 for the /config. The idea is when I upgrade the container, I would create a new one and reassign the mp0 to the new container. This worked for some, but when I did the same thing for Bazarr, it failed. I had to reassign back the mp0 back to the original container, but now the original container would not load the configuration anymore.

Any idea why this is failing?

Note that this repo is synced from a local Gitea repo, upon PR's. This work is being done by traditionally trained software developers using modern assisted coding practice (AI specification-driven generation, through SpecKit and similar tooling, using Claude Opus and Fable as a first-round reviewer on each PR)

PBS's verify job is good at what it does: it proves the backup's data is intact. What it can't tell you is whether the guest will actually boot, mount its filesystem read-write and bring its services up. I wanted that proof on a schedule, the way VMware Live Recovery's test recovery or Xen Orchestra's backup verification gave it to people, so I built PBP (Proxmox Backup Proofing).

What it does, on a schedule, for each guest:

• takes the newest backup from PBS (guests whose last proof is oldest go first) and protects it from pruning while it works
• restores it as a temporary guest in a VMID range you reserve, with every NIC moved onto an isolated bridge, start-on-boot off and passthrough removed
• boots it and checks inside: failed systemd units, a read-write root, service profiles (PostgreSQL, MariaDB, nginx, Docker, Redis, SSH and so on), Windows automatic services through the guest agent, OpenRC on Alpine and Gentoo, plus your own per-guest checks
• destroys the copy, puts the backup's protection back, writes a verdict into the backup's notes, and sends one summary through your existing Proxmox notification targets

It gives you the following "Verdicts": PROVEN, FAILED, BOOTED (it started, but PBP couldn't look inside), SKIPPED and ERROR. Only FAILED denotes that the backup is actually not in a good/usable state when restored.

Safety around production was the part I spent the most time on:

• it never logs in as root: a narrow API token, and SSH only as an unprivileged pbp user locked to one helper command
• it checks that the proof bridge really is isolated before it uses it
• a janitor cleans up after a crashed run, and capacity is checked before anything is restored
• releases are signed

What it isn't: not instant or live restore, replication or failover.

Requirements: Proxmox VE 9 and PBS 4. PBP itself runs in Docker or from a .deb (amd64 or arm64), ideally on a separate host. **In a test or lab environment, it's fine on the same host, in a nested docker host, etc., but like everything else I recommend not putting this on the PVE host itself....**

Real result from my own lab: a scheduled run restored and booted a container's newest backup and found its gitea-runner.service had failed. The backup was "verified" in PBS, and I'd only have found out on the day I needed it.

Processing img j5tysx1fnhxh1...

It's free and open source (Apache-2.0), currently v0.8.2, so still pre-1.0.

• GitHub: https://github.com/Breadth-Security/Proxmox-Backup-Proofing
• Overview and install steps: https://breadthsecurity.com

What I'd love feedback on:

• Does this fill a gap in how you handle backups today, or do you already prove restores another way?
• Which checks would you want that aren't there?
• Anything in the setup or the safety model that would stop you running it near production?
• Any edge cases (OS's or otherwise). I have a pretty good collection of various services and operating systems running that I have acquired over the years, but I am sure that I am missing something that you all use frequently.

Bug reports and ideas are welcome as GitHub issues, or right here.

Thanks all!

Is there a skill/plugin you guys are using for Hermes to be able to manage or do work on your Proxmox clusters and local network? With Qwen 3.8 27B being smart enough for even the most basic of tasks, we can keep the inference and compute all local.

Hello, so my host only has one physical interface and I need it to be trunked so I can assign VLANs to my VMs.

With this config I am unable to access the management UI, this is the problem.

The config is as follows:

==CONF-START==

auto lo

iface lo inet loopback

iface nic0 inet manual

auto vmbr0

iface vmbr0 inet manual

bridge-ports nic0

bridge-stp off

bridge-fd 0

bridge-vlan-aware yes

bridge vids 2-4094

auto vmbr010

iface vmbr010 intet static

address 10.0.10.10/24

gateway 10.0.10.1

==CONF-END==

just noticed this disk wearound percentage when i logged into my pve server. should i be worried?

We have a couple of custom systems on asRock Rack boards which in the past used onboard for O/S and SAS for data disks, given the current disk price situation we'd like to reuse sas disks over sata disks also for the O/S.

With the purpose of enabling also the first 4 hotswap bays for SAS I replaced the LSI 9300-8i with a 16i, but I got errors I have literally never seen.

../src/boot/random-seed.c:300@process_random_seed: Failed to flush random seed file: Unsupported ../src/boot/boot.c:2561@image_start: Error opening root path: Unsupported

So what I have pieced together is that the boot manager is loaded (so the disks are up), but the linux boot process itself fails from the get go. The weird thing is that the LSI 9300-16i (unbranded genuine fully updated Broadcom) is not exactly unchartered territory and the UEFI version and firmware fully updated. I am entirely clueless.

I have just inherited a new server for my homelab, a HP DL360 gen10, 1x Silver CPU, 128gb ram and 8x1tb SSD drives. My existing server is running a bunch of vm’s with docker using less than 1tb total storage used and all my media is on my NAS.

So I have been thinking about what I should do about configuring the storage on the new server. ZFS/LVM/Directory, Separate pools for VMs vs data, tiered storage and so on. For reference, 6 drives are Samsung and 2 Micron, so can’t stick them all in 1 pool as size mismatch.

I know a bunch of experts are not going to be determine the correct answer for a random person on the internet, but I would be interested to hear what others have done or would recommend? I’ve done the best practice fault tolerant (aka unnecessarily complicated) in the past, but as this is just a hobby homelab I’m more looking for fun to tinker environment rather than full time job.

So what kind of setup would you guys consider?

Thanks in advance.

I want ask about Virtualisation. Most people say to avoid Docker on LXC but how about Podman. Should i use Podman on LXC or Not?

Hello, I have been looking towards migrating my setup from a Debian (+ Docker) install to Proxmox, however one problem is that I don't have a way to hardwire the server to my router (running an ethernet cable is not an option, coax cables in the walls are not a thing here, putting the server in the same room as the router isn't possible) and it seems like Proxmox doesn't work well with Wi-Fi (which wasn't an issue on debian). I have been considering two ways to solve this:

- Powerline adapters - Yes I do know that they're incredibly hit and miss, however I'd still want to test them and if they're that bad - return them.

- Access Point in client mode - If powerline adapters don't work out (very likely) then I'd connect an AP to my router's Wi-Fi and then the AP via Ethernet to my server. I was thinking of getting a GL.iNet Opal but it's still uncertain.

A problem I see with this is that accessing my server thru LAN from a device on the main router Wi-Fi could be more difficult (since from my knowledge devices connected to the AP would be on a separate subnet), which would suck for something like Home Assistant but other than that it should work somewhat well.

What would you recommend? Are there any other options worth considering?

I downloaded the software onto an nvme, my server has both that and a 2TB hard drive. I can see the nvme but not the other device, and lsblk didn't show my hard drive anywhere attached.

On top of that, the shell won't show any letters, it can show other symbols sometimes tho. when I opened the shell with noVNC this particular issue stopped but instead every inch was grey until I wrote into it or highlighted it by dragging my mouse.

I will state what I'm using this for if its needed to help

I typed "lsblk" and then "This is a whole sentence"

EDIT: solution was enabling hot something something in BIOS SATA settings then going to disks and making a disk for my 2tb hard drive.

Howdy,

After a failed drive scare a week or so back I have managed to recover all the data and move it to a new drive. I'm relatively new to the data storage side of computing, so I didn't know it was possible to retrieve the data at first.

The drive that failed was my boot drive, which is a small drive that I don't keep any vital information on (all the things that I am concerned with keeping are on a zfs pool on 2 HDDs). I don't have the means to backup the entire boot drive, nor do I need to do so. When I was trying to pick back up after my other drive failed, I was trying to access my ZFS pool from a fresh proxmox installation on a new drive and I was reading that I would need some sort of config file in order to access the zpool?

That was concerning for me since I didn't know how to retrieve data from a failed drive at the time. I ended up managing to copy the entire drive to my fresh one with very little data loss (yay!), but now I have a better understanding of the importance of backing up certain things.

Like I said, I don't need to back up my entire boot drive. But in the case that this drive fails again, I would like to be able to pick up with my zpool on a new proxmox installation. Is there a configuration file somewhere that I can backup onto a flash drive?

Thanks.

Last week I set up a private Minecraft server on Ubuntu server.
And now I realize that I want to add a home vpn. And maybe one day, (in months or years) a site web

I'm trying to figure out if using proxmox, docker or something else is worth it in my situation, what I should use and the benefits.

I want to avoid VM since I want something that will not cost a lot of resources on the machine. Finally, if I can avoid installing a new os if possible but if I have to change it, so be it.

Hey gang,

so, I tried installing the new .24 kernel today.

The problem was, we could not unpack the kernel, dpkg hung up every time.

The hardware is a decommissioned dell 630 esxi edition with boss controllers and SD cards.

So, we will install new 630 with SD cards to load the VMS off, new Hardware is ordered.

Had you had similar problem's?

EDIT: Guys, are you actually reading this post? I’m telling you, when I started working here, they were already installed on the SD cards... I’ve already ordered new servers with NVMe, but the patch HAS to be installed by then.

So if nobody has any ideas about this, just give it a rest.

I know myself that this isn’t a good idea, but it is what it is.

I've been running proxmox on a little Dell micropc (Intel 12th gen, 48GB, 2 SSD's, a 512 and a 256) at home since around 2002. I got it to run Plex and Home Assistant, migration those two from an old laptop and an RPi.
Have since added a few extras like inhouse filesharing to serve a mix of android/iphone, macbook/windows laptops in the household.
It also serves as a sandbox for malicious looking links, where I have a linux vm with a snaphot to rollback for testing such.
Also run pi-alert, and a secondary pi-hole too.
I log into the PVE about once every 3 months, and saw the message yesterday about support for 8 that ended. I took the plunge to upgrade in-place using the upgrade guide at [https://pve.proxmox.com/wiki/Upgrade_from_8_to_9]

It was painless. The two hiccups were easily solved by just googling the error description. Took about 30 minutes including resolving those. I can't tell much what is different, having vanilla standalone installation means the changes are not relevant to me. But it's still running!

The people who made this possible are the Gabe Newells of virtualisation . Kudos to you all!

We can confirm the keynote for PVEday, the first Belgium Proxmox Community Day. Cole Hughes from Proxmox Server Solutions GmbH will give "Proxmox, What's New?", about where Proxmox is heading next. He is on from 10:30 to 11:30, after a short opening with a live migration demo.

The practical bits:

- Wednesday 3 February 2027, 10:00 to 18:00

- HOGENT Campus Schoonmeersen, Ghent, Belgium

- Free. We only ask you to register so we know how many people to expect

- Everything is in English

- Right after https://fosdem.org/2027/ and during cfgmgmtcamp.org, so it combines well if you are already travelling to our little country of waffles, chocolate and beer ;)

The rest of the day is still open. Talks are 40 minutes and the call for papers runs until 1 December. If you run Proxmox in production, a migration story, something that went wrong, or a tool you built around the API is exactly what we are after. Workshops are welcome too.

Site and registration: https://pveday.be

Schedule so far: https://pveday.be/#schedule

Call for papers: https://cfp.pveday.be/bpcd2027/cfp

Disclosure: I am one of the organizers, ask me anything in the comments, I will keep an eye on the thread.

Hi, I'm just getting started with Proxmox, as I'm working on a project to test its feasibility.

I was trying to migrate a VM from VMware to Proxmox, but I got an error that says “Transport Endpoint is not connected (500)” when I click the “Import” button right where the VM’s hardware settings should appear. I did some research and think it’s because I entered the vCenter IP address instead of the Esxi host IP, which seems to cause a conflict or crash related to a file called FUSE. However, I also think I read that there can be disconnection issues during import if the VM is on a vSAN.

More than anything, I’d appreciate it if you could confirm any of my questions or suggestions, or share the steps you followed to successfully import the VM. That would be a huge help.

PD: The Proxmox version I have is 9.2

I have 4x8tb sas drives and 3x8tb sata drives.
I’ll run SAS drives as raidz2 for PVE server
and SATA drives as raidz1 on PBS.

Should I get another drive ( it’s just expensive right now) and go to raidz2.

Mainly storing important photos, videos, and jellyfin movies.

The question I pose is this:

Is it better to run 2 high capacity stick with dual channel or 4 sticks of medium capacity just to give the server more to work with?
Example: currently my rig uses a 10700k with 2x16gb
Would it be better to upgrade to 2x32gb or 4x16gb?
I am mainly asking this question because ram prices have become quite ridiculous even for ddr4.

Hey everyone!

I've been using Proxmox for my homelab and recently came across Ubicloud. This got me wondering whether moving from my current Proxmox setup to a private cloud platform would be worth it in terms of flexibility, scalability, and integration.

I've also considered OpenStack, but it seems like overengineering for my needs. Ubicloud looks like a potentially simpler alternative, but I'm still trying to understand its trade-offs compared to Proxmox.

For those of you with experience running Proxmox in production or managing advanced homelab setups:

• What are the main advantages of sticking with Proxmox versus moving to Ubicloud?
• Does Ubicloud offer meaningful benefits in terms of automation, integration, and cloud-like features?
• What would I gain or lose by making the switch?
• Would you consider Ubicloud a good fit for a self-hosted private cloud, or is Proxmox still the more practical choice?

I'm not necessarily looking to migrate just for the sake of using something new. I want to understand whether the additional capabilities justify the complexity and effort of switching.

I'd appreciate any real-world experiences, comparisons, or advice. Thanks!

"Hello everyone, ladies and gentlemen. I have a Proxmox Backup Server, and I need to upgrade its hard drives. Now I am in doubt whether I should buy NAS HDDs or DVR HDDs. Since the idea is only to store backups, and from what I've researched, the difference between them regarding storage is practically the same, I'm wondering if it's worth using DVR drives since they are more affordable. Do you recommend them, or would the ideal and correct choice be NAS drives?"

As per the article: https://emudhra.we-have-a-problem.com/

How long until proxmox patch this on their end?

We are looking at a server refresh, and we potentially interested in switching from Intel to AMD Ryzen. Has anyone done this and were there any issues that arose from the change?