[SOLVED] I can't add an SSD to rpool (Mirror)

kymera

New Member
Feb 12, 2024
2
0
1
Hi , i need your help I don't understand where I'm wrong
Proxmox was installed on 2 mirrored 250GB SSDs. A few days ago by mistake I wiped one, now I'm trying to add this SSD into rpool pool .
First of all I removed the SSD from the server and formatted it with gparted , then in proxmox Initialize Disk with GPT

disk.png

clone sdd partitions to sdg
Code:
sgdisk /dev/sdd -R /dev/sdg
The operation has completed successfully.

Code:
sgdisk -G /dev/sdg
The operation has completed successfully.

install proxmox into sdg2
Code:
proxmox-boot-tool init /dev/sdg2
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
UUID="1AE9-5B05" SIZE="1073741824" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="sdg" MOUNTPOINT=""
Mounting '/dev/sdg2' on '/var/tmp/espmounts/1AE9-5B05'.
Installing systemd-boot..
Created "/var/tmp/espmounts/1AE9-5B05/EFI/systemd".
Created "/var/tmp/espmounts/1AE9-5B05/EFI/BOOT".
Created "/var/tmp/espmounts/1AE9-5B05/loader".
Created "/var/tmp/espmounts/1AE9-5B05/loader/entries".
Created "/var/tmp/espmounts/1AE9-5B05/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/1AE9-5B05/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/1AE9-5B05/EFI/BOOT/BOOTX64.EFI".
Random seed file /var/tmp/espmounts/1AE9-5B05/loader/random-seed successfully written (32 bytes).
Created EFI boot entry "Linux Boot Manager".
Configuring systemd-boot..
Unmounting '/dev/sdg2'.
Adding '/dev/sdg2' to list of synced ESPs..
Refreshing kernels and initrds..
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Copying and configuring kernels on /dev/disk/by-uuid/1AE9-5B05
    Copying kernel and creating boot-entry for 6.5.11-8-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD48-53C2
    Copying kernel and creating boot-entry for 6.5.11-8-pve
WARN: /dev/disk/by-uuid/DEF2-464B does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping

I get the error and i Clean the kernel
Code:
proxmox-boot-tool clean
Checking whether ESP '1AE9-5B05' exists.. Found!
Checking whether ESP 'DD48-53C2' exists.. Found!
Checking whether ESP 'DEF2-464B' exists.. Not found!
Sorting and removing duplicate ESPs..

install proxmox into sdg2
Code:
proxmox-boot-tool init /dev/sdg2
Adding '/dev/sdg2' to list of synced ESPs..
Refreshing kernels and initrds..
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Copying and configuring kernels on /dev/disk/by-uuid/1AE9-5B05
    Copying kernel and creating boot-entry for 6.5.11-8-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD48-53C2
    Copying kernel and creating boot-entry for 6.5.11-8-pve

proxmox-boot-tool refresh
Code:
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/1AE9-5B05
    Copying kernel and creating boot-entry for 6.5.11-8-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD48-53C2
    Copying kernel and creating boot-entry for 6.5.11-8-pve

Disk ready

diskready.png

Now the next command I put the new ssd in the rpool pool
Code:
zpool attach rpool /dev/disk/by-id/ata-Samsung_SSD_870_EVO_250GB_S6PENZ0TC01790Z-part3 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_250GB_S6PENZ0TC01784X-part3

Resilvering
resilvering.png

Resilvering after ferw second , the SSD is no longer visible in the disk list
Screenshot from 2024-02-12 12-59-57.png
 
Hi,

do you have in the early days installed on that ssd on diffrent computer? ill think you did ill recommend it to have a Sata to USB plug the ssd in your USB to sata and usb in your laptop. then you go to Disk manager and formate the disk / delete entry's. then add it again in your zfs pool.

its kicked this SSD because you have existing OS running you see it here. its has a BIOS and EFI boot disk??
1707743583865.png
try to format it :)
and redeploy it :)
 
Hi @Netwerkfix
thanks to you I remembered that in the motherboard bios it was set to Legacy, I changed to FastBoot ON and chose EFI, after this I did the above procedure more than once, but it didn't work, I've been using Proxmox for years, I don't remember this change in the bios
I solved my problem by typing the command
Code:
proxmox-boot-tool clean
first , and then I continued with the other cmd , I honestly don't know if it's a coincidence, I tried booting one disk at a time and it works perfectly
Thank you
 

Attachments

  • Screenshot from 2024-02-12 16-17-31.png
    Screenshot from 2024-02-12 16-17-31.png
    45.6 KB · Views: 4

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!