this post was submitted on 09 Jan 2026
14 points (88.9% liked)

Selfhosted

55809 readers
311 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Recently, when I reboot my Proxmox hardware, I'm greeted with this message after the bootloader splash screen. It won't progress any further, even after letting it sit overnight.

But restarting it 5-10 times will eventually get past it.

I suspect it might have something to do with me passing a physical disk and the whole GPU to a Windows VM (my temp solution for TV gaming until I can get Sunshine issues ironed out) but I'm not sure where to start looking for the issue.

I thought it might be freezing when the VM tries to take control of the GPU, but with a continuous ping to both the server and the VM, I never get a response. That makes me think the issue is happening before the VM is started.

I'm basically just hoping someone could point me to a log that might have a related error message.

you are viewing a single comment's thread
view the rest of the comments
[–] village604@adultswim.fan 1 points 3 weeks ago

I feel like it's unlikely to be a hardware issue unless the drive Proxmox is on is dying. SMART is fine, but it's on an SSD that's nearly 15 years old, so it very well might be the cause. I need to migrate it to one of my nvme disks eventually.

But, I can boot into the Windows physical disk just fine (instead of booting into Proxmox and running it as a VM). Same with a live ISO on USB.

The fact that it's perfectly stable after I do get it to boot is why I'm chasing down a software issue first. I also don't want to think about the cost of having to replace hardware yet. But I'm definitely not ruling it out completely.

I'm going to take the advice of another commenter and turn off quiet in grub so I can get a better look at what's actually going on under the hood.