Improperly replaced failing drive

[Proximate]

I don't recall where but I had a link showing that when a drive fails, you need to run a few commands to properly replace it.
Over the weekend, I accidentally replaced a failing drive in a 4 drive ZFS array without running any commands.

Now, around 8hrs later, I'm back from the location and looking at the host.
There is no mention of any problems, all four drives are in OK smart status.
Should I be concerned? Migrate the last two vms off that host, rebuild it or can it be trusted to move vms back onto it?

 

[sterzy]

Hi,

can you provide the output of zpool status $poolname (where $poolname is the name of the zfs pool the drive is in)?

 

[Dunuin]

In case you boot from that pool you should now be missing the grub/ESP partition so you can't boot of that disk anymore. How to replace a failed drive is described in the paragraph "Changing a failed bootable device" there: https://pve.proxmox.com/wiki/ZFS_on_Linux#_zfs_administration

 

[Proximate]

Ah yes, I didn't look at the pool and sure enough, it is degraded.

# zpool status rpool pool: rpool state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'.

Since I only have two vms on this host, it will probably be easier to just migrate them away, re-install proxmox and put those and the others I moved off back. Unless, there is a way to fix this in the condition it's in.
I've already replaced it so 'zpool replace' seems like it's too late?

Thanks for the link btw, I was going to look for that to put into my notes.

 

[Proximate]

I just went ahead and rebuilt the host. Next time, I'll follow the guidelines but it seems faster to rebuild than waiting for a drive to sync up after being replaced.