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

推荐订阅源

Microsoft Security Blog
Microsoft Security Blog
Jina AI
Jina AI
量子位
博客园 - 叶小钗
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
IT之家
IT之家
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
雷峰网
雷峰网
博客园 - 聂微东
美团技术团队
Last Week in AI
Last Week in AI
罗磊的独立博客
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 三生石上(FineUI控件)
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园_首页
V
Visual Studio Blog
大猫的无限游戏
大猫的无限游戏
The Cloudflare 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
Proxmox 9.1.1 Cannot install CEPH
invalid@exam · 2026-06-02 · via Proxmox Support Forum

I have upgraded a 5 node Proxmox 8 cluster to Proxmox 9 and the last node failed. Somehow the PVE packages got removed and I could not reinstall them,

So I thought I'd reinstall the host to PVE 9.1.1 and re-join it to the cluster.
But I cannot install CEPH. This node wants to install the OLDER version of CEPH:

root@PVE05:~# pveceph install

WARN: Enterprise repository selected, but no active subscription!

This will install Ceph 19.2 Squid - continue (y/N)? y
update available package list
E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-squid/dists/trixie/InRelease 401 Unauthorized [IP: 102.222.103.110 443]
E: The repository 'https://enterprise.proxmox.com/debian/ceph-squid trixie InRelease' is not signed.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/trixie/InRelease 401 Unauthorized [IP: 102.222.103.110 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve trixie InRelease' is not signed.
start installation
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ceph-common is already the newest version (19.2.3-pve2).
ceph-fuse is already the newest version (19.2.3-pve2).
gdisk is already the newest version (1.0.10-2).
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
ceph-mds : Depends: ceph-common (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
ceph-mgr : Depends: ceph-common (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
Depends: python3-ceph-argparse (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
Depends: python3-cephfs (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
ceph-mon : Depends: ceph-common (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
ceph-osd : PreDepends: ceph-common (= 18.2.7+ds-1) but 19.2.3-pve2 is to be installed
Depends: ceph-base (= 18.2.7+ds-1) but it is not going to be installed
python3-ceph : Depends: python3-cephfs (< 18.2.7+ds-1.1~) but 19.2.3-pve2 is to be installed
Depends: python3-rados (< 18.2.7+ds-1.1~) but 19.2.3-pve2 is to be installed
Depends: python3-rbd (< 18.2.7+ds-1.1~) but 19.2.3-pve2 is to be installed
Depends: python3-rgw (< 18.2.7+ds-1.1~) but 19.2.3-pve2 is to be installed
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. ceph-common:amd64=18.2.7+ds-1 is not selected for install
2. ceph-common:amd64=18.2.7+ds-1 is selected as a downgrade because:
1. ceph-mds:amd64=18.2.7+ds-1 is selected for install
2. ceph-mds:amd64 Depends ceph-common (= 18.2.7+ds-1)
apt failed during ceph installation (25600)

All other nodes are running Proxmox 9.1.14 / CEPH 19.2.3