Hi,
Had an interesting morning with a planned upgrade of a node.
We're currently on 7.3-4 and I started upgrading one node from ceph Pacific to Quincy following the guide:
https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
During the update I noticed that one of the boot NVME's had failed...i bit late though so I noticed it during the apt full-upgrade process with this:
Copying and configuring kernels on /dev/disk/by-uuid/4635-9057
Copying kernel and creating boot-entry for 5.15.104-1-pve
Copying kernel and creating boot-entry for 5.15.83-1-pve
WARN: /dev/disk/by-uuid/4635-FC86 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
Processing triggers for libc-bin (2.31-13+deb11u6) ...
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
So now to my question....planning for the worst after reading about replacing a failed zfs boot device (https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_zfs_administration) I'm not 100% sure what I need to do now
After som troubleshooting I got the failed drive online again and my pool looks fine but since only p3 is part of the pool what do I need to do with p1 and p2 on this disk as it was skipped during the upgrade process.
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
nvme-eui.002538bb21a03f57-part3 ONLINE 0 0 0
nvme-eui.002538bb21a03f81-part3 ONLINE 0 0 2
Can I simply re-run this upgrade or should I do something manually on that disk?
Appreciate any help!
--Mats
Had an interesting morning with a planned upgrade of a node.
We're currently on 7.3-4 and I started upgrading one node from ceph Pacific to Quincy following the guide:
https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
During the update I noticed that one of the boot NVME's had failed...i bit late though so I noticed it during the apt full-upgrade process with this:
Copying and configuring kernels on /dev/disk/by-uuid/4635-9057
Copying kernel and creating boot-entry for 5.15.104-1-pve
Copying kernel and creating boot-entry for 5.15.83-1-pve
WARN: /dev/disk/by-uuid/4635-FC86 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
Processing triggers for libc-bin (2.31-13+deb11u6) ...
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
So now to my question....planning for the worst after reading about replacing a failed zfs boot device (https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_zfs_administration) I'm not 100% sure what I need to do now
After som troubleshooting I got the failed drive online again and my pool looks fine but since only p3 is part of the pool what do I need to do with p1 and p2 on this disk as it was skipped during the upgrade process.
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
nvme-eui.002538bb21a03f57-part3 ONLINE 0 0 0
nvme-eui.002538bb21a03f81-part3 ONLINE 0 0 2
Can I simply re-run this upgrade or should I do something manually on that disk?
Appreciate any help!
--Mats