Hello
i would like to request this feature below.
make a easyer way to change a failed ZFS drive from the GUI.
Currently, replacing a failed ZFS disk in Proxmox VE requires following the CLI-based guide documented here: ZFS on Linux – Change Failed Device. While this procedure works well for experienced administrators, it can be intimidating and error-prone for less technical users.
Introduce a user-friendly GUI workflow for managing failed ZFS drives directly within the Proxmox VE interface.
EDIT: submitted the same request at bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=6698
i would like to request this feature below.
make a easyer way to change a failed ZFS drive from the GUI.
Background
Currently, replacing a failed ZFS disk in Proxmox VE requires following the CLI-based guide documented here: ZFS on Linux – Change Failed Device. While this procedure works well for experienced administrators, it can be intimidating and error-prone for less technical users.
Proposal
Introduce a user-friendly GUI workflow for managing failed ZFS drives directly within the Proxmox VE interface.
Suggested Workflow
- Navigate to the ZFS Pool
Within the Proxmox GUI, select the relevant ZFS pool from the storage overview. - Identify the Failed Drive
- A button such as “Failed ZFS Drive” should be available in the pool view.
- Clicking this button automatically selects the failed drive.
- Alternatively, users can manually select the affected pool and drive.
- Take Drive Offline
Once selected, the GUI should provide an option to put the drive into offline mode, ensuring it can be safely removed without disturbing the pool. - Replace the Drive
The user swaps the failed physical disk with a new one. - Automated Recovery
After insertion, the system should:- Automatically copy the partition layout from a healthy drive in the pool.
- Start the resilvering process, rebuilding the missing data onto the new drive.
Benefits
- Accessibility: Makes ZFS drive replacement manageable for non-CLI users.
- Reduced Risk: Minimizes potential user errors during a critical recovery operation.
- Consistency: Aligns with the intuitive GUI-first experience that Proxmox VE strives to deliver.
EDIT: submitted the same request at bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=6698
Last edited: