[SOLVED] Proxmox Re-silvering by ID?

[killmasta93]

Hi, I was wondering if someone could shed some light on the issue im having. Recently one of the Disks died and put in a new one and replace it using this command

 zpool replace vmdata 14183783644472836319 /dev/sde

it resilver perfectly and then i rebooted no issue there. Then one day the Server rebooted and got an alert about the zpool i checked it running zpool status -v and I saw the other disks by Disk ID rather then sdX also looking at the disk id seems that the ID changed the sde to sdf i need the disk ending in 7AS to go back in the pool

My question is what part did i do wrong from these steps? Im going to try it again on Sunday because its a production server.

First delete all the partitions and convert to gpt:

 fdisk /dev/sdf

Then:

sgdisk --replicate=/dev/sdf /dev/sde

then randomize the guids

 sgdisk --randomize-guids /dev/sdf

then finally replace it but i think this time with the disk id?

 zpool replace vmdata 10946115601346650490  /dev/disk/by-id/ata-TOSHIBA_HDWD120_672SBE7AS-part1

Thank you

 

[killmasta93]

EDIT: for anyone else having this issue

first export

 zpool export vmdata

then after exported i labclear it

zpool labelclear -f /dev/disk/by-id/ata-TOSHIBA_HDWD120_672SBE7AS-part1

then import the

zpool import vmdata

then i replace it and let it resilver then a reboot all is good

zpool replace vmdata ata-TOSHIBA_HDWD120_672SBE7AS-part1  /dev/disk/by-id/ata-TOSHIBA_HDWD120_672SBE7AS