I'm in the process of recovering a proxmox installation after failure of one of the rpool zfs mirror disks.
And finding that there was no boot partition on the remaining disk...
So I've basically got the rpool happy with 2 disks, with the required 3 partitions. And the Linux boot manager is currently on one of them and boots. However, rather than loading the pve installation from that rpool, it loads the temporary pve2 on the scratch disk /dev/sda that I installed to get to be able to recover to this point.
I suspect this is because I used sgdisk to copy the partition config from /dev/sda to the new rpool drive and then ran proxmox-boot-tool init etc whilst booted into temporary pve2 and it's kept that link. But I may be wrong.
So how do I tell the boot config in rpool to pick up the pve installation in its own partition 3 rather than that on /dev/sda?
Thanks
And finding that there was no boot partition on the remaining disk...
So I've basically got the rpool happy with 2 disks, with the required 3 partitions. And the Linux boot manager is currently on one of them and boots. However, rather than loading the pve installation from that rpool, it loads the temporary pve2 on the scratch disk /dev/sda that I installed to get to be able to recover to this point.
I suspect this is because I used sgdisk to copy the partition config from /dev/sda to the new rpool drive and then ran proxmox-boot-tool init etc whilst booted into temporary pve2 and it's kept that link. But I may be wrong.
So how do I tell the boot config in rpool to pick up the pve installation in its own partition 3 rather than that on /dev/sda?
Thanks