惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MongoDB | Blog
MongoDB | Blog
B
Blog RSS Feed
MyScale Blog
MyScale Blog
M
MIT News - Artificial intelligence
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
U
Unit 42
Blog — PlanetScale
Blog — PlanetScale
L
LangChain Blog
C
Check Point Blog
WordPress大学
WordPress大学
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
Vercel News
Vercel News
腾讯CDC
GbyAI
GbyAI
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
H
Help Net Security
博客园 - 三生石上(FineUI控件)
D
DataBreaches.Net
Microsoft Security Blog
Microsoft Security Blog
小众软件
小众软件

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
WARNING: Pool 'rpool' has encountered an unreco...
invalid@exam · 2026-06-04 · via Proxmox Support Forum

I updated Proxmox and kernel was updated `6.8.12-23-pve` => `6.8.12-29-pve` After reboot machine did not start fully, it ended up with repeating message each several seconds: WARNING: Pool 'rpool' has encountered an unrecorrectable I/O failure and has been suspended. after update.
I booted again into old kernel and pinned it (so hopefully I'm save for time being)
Note: rpool is on the same NVMe disk I'm booting from.
Any idea how to investigate or (even better) sove this problem? Machine was stable before and is stable again pinning older kernel, so I don't expect real hardware problem (of course cannot be excluded, worked/working is not proof, but...)
I was planning to upgrade (again) to Proxmox 9, but now I'm afraid again. I already upgreded in the past and have to reinstall back to Proxmox 8 because of problem with passthrough PCIe card into VM (issue with Intel N150 CPU). Additionally I'm passing ASM1166 and I saw some articles that there were problems with this as wll in some kernels. Not sure what is state now.
Thanks, hwm

Impact

Distinguished Member

Sep 12, 2022
2,202
1,065
183

To take passthrough out of the equation you can try to disable IOMMU/VT-d in the node's UEFI and see if it boots without such issues then.
For basic troubleshooting check journalctl -r and zpool status -v.

Exact same issue for me when updating from 6.8.12-24-pve to 6.8.12-29-pve
Strangely, it works fine in my test environment on identical hardware and patch level.
Booting 6.8.12-24-pve also works fine so I've pinned this for now.

There is one one difference between my test box running 6.8.12-29-pve where the affected machine has PCI passthrough configured (two Intel I226-V NICs passed through to an OPNsense VM).

Last edited:

Hmm, this passthrough seems to be common denominator. Once I have bigger window to put it down I'll try without IOMMU just to know, but this is not solution for me. Makes me even more scarry about upgrade to Proxmox 9

Seems like this might be fixed in kernel version -30:
https://bugzilla.proxmox.com/show_bug.cgi?id=7671

For me it seemed like PCI passthrough for my SATA controller was causing this issue.

After testing I can confirm that for me kernel version -30 fixed this issue. (available on pvetest)

P.s. upgrading to pve9 also fixed this issue for me.