Hi,
so (again) a disk went bad ("faulted") in a ZFS pool.
Server is a hp Proliant Microserver Gen 8 w. 4 x 4TB - the bad/new disk was/is the 1st/left one in the row, no hardware-RAID configured, not hot-plug.
I removed the faulted HD ("zpool offline").
Systems boots fine w. 3 HDs.
After shutdown, I plug in the new blank HD.
System does not boot.
I did
Yet, with the new HD plugged in, box does not boot, hence I cannot even get to zpool add, replace, sgdisk, etc.
Q: How do I get the box to boot w. the new blank HD installed?
Cheers,
~R.
so (again) a disk went bad ("faulted") in a ZFS pool.
Server is a hp Proliant Microserver Gen 8 w. 4 x 4TB - the bad/new disk was/is the 1st/left one in the row, no hardware-RAID configured, not hot-plug.
I removed the faulted HD ("zpool offline").
Systems boots fine w. 3 HDs.
After shutdown, I plug in the new blank HD.
System does not boot.
I did
proxmox-boot-tool clean
and proxmox-boot-tool status
gives:Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
57C2-AE3A is configured with: grub (versions: 5.15.104-1-pve, 5.15.107-1-pve)
57C4-2424 is configured with: grub (versions: 5.15.104-1-pve, 5.15.107-1-pve)
57C5-58D7 is configured with: grub (versions: 5.15.104-1-pve, 5.15.107-1-pve)
Yet, with the new HD plugged in, box does not boot, hence I cannot even get to zpool add, replace, sgdisk, etc.
Q: How do I get the box to boot w. the new blank HD installed?
Cheers,
~R.
Last edited: