ZFS Drive Replacement

B

binarian

Active Member
Apr 23, 2019
11
2
43
35
All,
I am very soon doing a zfs drive replacement on my proxmox server. I have a question about what paths to use. The physical drive is /dev/sdv. However, zpool status shows that the member drives are using the /dev/disk/by-id nomenclature, and specifically are using partition 3 (so zpool status shows ata-<model>_<serial>-part3).

My question:
when I zpool offline the disk, do I need to use /dev/sdv, /dev/disk/by-id/ata-foo_bar-part3, or just use the guid? Additionally, when I put the new disk in, will I need to manually re-create the partition table information, or will zfs handle all of that for me?

Thanks
 
binarian said:
All,
I am very soon doing a zfs drive replacement on my proxmox server. I have a question about what paths to use. The physical drive is /dev/sdv. However, zpool status shows that the member drives are using the /dev/disk/by-id nomenclature, and specifically are using partition 3 (so zpool status shows ata-<model>_<serial>-part3).
Click to expand...
When it is using partition 3 you are most likely booting from that ZFS pool. Otherwise it would be partition 1. And replacing a system disk is more complex. See "Replacing a failed bootable device" in the wiki: https://pve.proxmox.com/wiki/ZFS_on_Linux#_zfs_administration
As you then also need to clone the partition table and write the new bootloader.

And while you could work with "/dev/sdv", as later ZFS won't care what that disk is named, as it will read the metadata stored on the disk to identify it, it would still be better to work with "/dev/disk/by-id". That way it is easier to know what disk needs to be replaced in case that disk will fail later.
 
Last edited:
Dunuin said:
When it is using partition 3 you are most likely booting from that ZFS pool. Otherwise it would be partition 1. And replacing a system disk is more complex. See "Replacing a failed bootable device" in the wiki: https://pve.proxmox.com/wiki/ZFS_on_Linux#_zfs_administration
As you then also need to clone the partition table and write the new bootloader.

And while you could work with "/dev/sdv", as later ZFS won't care what that disk is named, as it will read the metadata stored on the disk to identify it, it would still be better to work with "/dev/disk/by-id". That way it is easier to know what disk needs to be replaced in case that disk will fail later.
Click to expand...
Thanks a lot for this! Those instructions worked perfectly for the first disk. However: I notice that the instructions describe how to handle partition 3 (the data), and partition 2 (the EFI stuff). There's no mention of partition 1. Does anything have to be done there? ALL of my original boot drives will be replaced, one by one, so if I need to copy anything from partition 1, now is the time I have to do it.

Thanks again!
 
Depends on which version of PVE you initially have installed and if you are using systemd or grub to boot. Partition 1 is more a legacy thing when using grub as the bootloader.
 
Dunuin said:
Depends on which version of PVE you initially have installed and if you are using systemd or grub to boot. Partition 1 is more a legacy thing when using grub as the bootloader.
Click to expand...
Gotcha. I'm using the systemd option. I'll assume it's safe to ignore!
 
You must log in or register to reply here.
Top Bottom
Back