accumulated collection of notes about my server shenanigans
add info about replacing failing drives
+48
-1
+2
-1
zfs/General info.md
+2
-1
zfs/General info.md
+46
zfs/Replace failing drives.md
+46
zfs/Replace failing drives.md
···
1
+
Physically replace the failed drive
2
+
3
+
`zpool list -v`
4
+
The replaced drive should show up by its uuid
5
+
6
+
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs_change_failed_dev
7
+
8
+
## Changing a failed device
9
+
`zpool replace -f <pool> <old-device> <new-device>`
10
+
11
+
## Changing a failed bootable device
12
+
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).
13
+
14
+
You can check by running:
15
+
`proxmox-boot-tool status`
16
+
17
+
The first steps of copying the partition table,
18
+
```sh
19
+
sgdisk <healthy bootable device> -R <new device>
20
+
```
21
+
reissuing GUIDs
22
+
```sh
23
+
sgdisk -G <new device>
24
+
```
25
+
and replacing the ZFS partition are the same.
26
+
```sh
27
+
zpool replace -f <pool> <old zfs partition> <new zfs partition>
28
+
```
29
+
30
+
> [!NOTE] Disclaimer
31
+
> Use the zpool status -v command to monitor how far the resilvering process of the new disk has progressed.
32
+
33
+
To make the system bootable from the new disk, different steps are needed which depend on the bootloader in use.
34
+
35
+
### With proxmox-boot-tool:
36
+
```sh
37
+
proxmox-boot-tool format <new disk's ESP>
38
+
proxmox-boot-tool init <new disk's ESP> [grub]
39
+
```
40
+
> [!NOTE] Disclaimer
41
+
> ESP stands for EFI System Partition. By default partition #2 on bootable disks since Proxmox VE version 5.4.
42
+
43
+
### With plain GRUB:
44
+
`grub-install <new disk>`
45
+
> [!NOTE] Disclaimer
46
+
> 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.