From 0ce6354af489f9bdef029dc846dbde96dc5ae4f8 Mon Sep 17 00:00:00 2001 From: DjP-iX <133042991+DjP-iX@users.noreply.github.com> Date: Mon, 25 Nov 2024 16:08:30 -0500 Subject: [PATCH] Delete HotSpareVdev.md --- static/includes/HotSpareVdev.md | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 static/includes/HotSpareVdev.md diff --git a/static/includes/HotSpareVdev.md b/static/includes/HotSpareVdev.md deleted file mode 100644 index 2425ae4823..0000000000 --- a/static/includes/HotSpareVdev.md +++ /dev/null @@ -1,13 +0,0 @@ - - -A **Hot Spare** vdev sets up drives as reserved to prevent larger pool and data loss scenarios -TrueNAS automatically inserts an available hot spare into a **Data** vdev when an active drive fails. -The pool resilvers once the hot spare is activated. - -Click **Detach** to remove the failed drive from the pool -The activated hot spare is promoted to a full data vdev member and is no longer available as a hot spare. -After physically replacing the failed disc, create a new hot spare vdev to reserve the replacement disc. - -Alternately, after physically replacing the failed disc, click **Replace** on the failed drive to activate the new drive -The hot spare reverts to an inactive state and is available again as a hot spare. -We do not recommend this method, because it requires a second resilver for the new drive.