Search results

from the new node. note we have not moved the subscription over so it is using testing # pveversion -v proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve) pve-manager: 9.0.5 (running version: 9.0.5/9c5600b249dbfd2f) proxmox-kernel-helper: 9.0.3 proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2...

using pve 9.0.5 . 5 node ceph cluster. nodes have a mix of zfs and non zfs root/boot disks along with one large nvme formatted ext4 for vzdumps. we also use pbs . i have a cronscript which we have used for years that checks this: dmesg -T | grep hung | grep -v vethXChung ## **URGENT**...

we had a crashed node. it is deleted from cluster. we did not have a chance to remove it as a ceph monitor. [ we did replace the monitor ]. ceph -s shows: health: HEALTH_WARN .. mon: 4 daemons, quorum pve11,pve2,pve5 (age 7m), out of quorum: pve4 how can I delete a monitor assigned...

generally I destroy the OSD on old node , move it to new node then create a new osd. Or is there a stable way to do the osd ? A few months ago I checked threads and had no luck. Also I did not see an osd move in manual.

I see there are more steps to do. the above only takes care of partition 3 Okay thanks.

So I read the above, have a rpool device to replace. I read https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_zfs_administration and want to verify that just this one step is needed: zpool replace -f <pool> <old-device> <new-device>

to find device name 1 - plug in cable 2 - dmesg: [Fri Aug 8 09:19:59 2025] mlx5_core 0000:a8:00.1: Port module event: module 1, Cable plugged 3 - find device name ls /sys/bus/pci/devices/0000\:a8\:00.1/net/ and this is a great tool, I ran this first: see manual...

I found the cause. bad node can not reach cluster network.. this is the only node that i did not use systemctl aliases for network interface names...

osd's are mounted at bad node: tmpfs tmpfs 378G 24K 378G 1% /var/lib/ceph/osd/ceph-6 tmpfs tmpfs 378G 24K 378G 1% /var/lib/ceph/osd/ceph-2 tmpfs tmpfs 378G 24K 378G 1% /var/lib/ceph/osd/ceph-23 tmpfs...

I noticed osd's down at pve web page. tried to start , fail . at a not where ceph is up: # ceph -s cluster: id: 220b9a53-4556-48e3-a73c-28deff665e45 health: HEALTH_WARN noout flag(s) set 10 osds down 1 host (10 osds) down Degraded...

I agree, and had to use PVE console for the kvm

send output of ifup enp1s0 also in case it applies check: https://forum.proxmox.com/threads/main-exception-rawconfigparser-object-has-no-attribute-readfp.169352/#post-789444

another kvm running trixie did not need the fix. source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface #allow-hotplug ens18 #iface ens18 inet dhcp auto ens18 iface ens18 inet static address 10.1.3.5/24...

well the error was from inside the VM . pve network is fine.

maybe i did not explain this: pve runs v8 . KVM runs trixie I did not put trixie on v8 pve

I upgraded a KVM running Debian bookworm to trixie. pve runs v8 after upgrade and reboot the network was down. tried to bring up network: ifup ens19 main exception 'RawConfigParser' object has no attribute 'readfp' my interfaces file is below. the solution from grok ai: Edit...

perfect , thanks.

this fixed the 1st issue wget https://enterprise.proxmox.com/debian/proxmox-release-trixie.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-trixie.gpg however neither of these work yet. deb http://download.proxmox.com/debian/pbs-client trixie pbs-test # or deb...

i put this to sources: deb http://download.proxmox.com/debian/pbs-client trixie pbs-test apt update error: Err:4 http://download.proxmox.com/debian/pbs-client trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key...

that was as fast as the speed of light for an answer. thank you!