diff --git a/zfs/General info.md b/zfs/General info.md
index 4583f18..a725dca 100644
--- a/zfs/General info.md	
+++ b/zfs/General info.md	
@@ -1,4 +1,5 @@
 default command: 
 `zpool`
+`zfs`
 
-[[Add cache drives]]
\ No newline at end of file
+[[Add cache drives]]
diff --git a/zfs/Replace failing drives.md b/zfs/Replace failing drives.md
new file mode 100644
index 0000000..a955993
--- /dev/null
+++ b/zfs/Replace failing drives.md	
@@ -0,0 +1,46 @@
+Physically replace the failed drive
+
+`zpool list -v`
+The replaced drive should show up by its uuid
+
+https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs_change_failed_dev 
+
+## Changing a failed device 
+`zpool replace -f <pool> <old-device> <new-device>`
+
+## Changing a failed bootable device
+Depending on how Proxmox VE was installed it is either using systemd-boot or GRUB through proxmox-boot-tool or plain GRUB as bootloader (see Host Bootloader). 
+
+You can check by running:
+`proxmox-boot-tool status`
+
+The first steps of copying the partition table,   
+```sh 
+sgdisk <healthy bootable device> -R <new device>
+```
+reissuing GUIDs   
+```sh 
+sgdisk -G <new device>
+```
+and replacing the ZFS partition are the same.    
+```sh 
+zpool replace -f <pool> <old zfs partition> <new zfs partition>
+```
+
+> [!NOTE] Disclaimer
+> Use the zpool status -v command to monitor how far the resilvering process of the new disk has progressed.
+
+To make the system bootable from the new disk, different steps are needed which depend on the bootloader in use.
+
+### With proxmox-boot-tool:
+```sh
+proxmox-boot-tool format <new disk's ESP>
+proxmox-boot-tool init <new disk's ESP> [grub]
+```
+> [!NOTE] Disclaimer
+> ESP stands for EFI System Partition. By default partition #2 on bootable disks since Proxmox VE version 5.4. 
+
+### With plain GRUB:
+`grub-install <new disk>`
+> [!NOTE] Disclaimer
+> Plain GRUB is only used on systems installed with Proxmox VE 6.3 or earlier, which have not been manually migrated to use proxmox-boot-tool yet.