bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md
All checks were successful
GitOps Automatic Deployment / GitOps Automatic Deployment (push) Successful in 8s
Details

Browse Source
This commit is contained in:
Nicole Rappe
2025-08-11 02:50:45 -06:00
parent 46f2babee4
commit 57a65f1225
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md
View File

@@ -29,4 +29,10 @@ Now we need to tell TrueNAS / FreeBSD to re-scan all disks to locate the new one
!!! success "Resilvering Started"
At this point, TrueNAS core will start taking parity data from the rest of the drives in the storage pool to reconstruct the replaced drive. This may take an hour or two depending on the speed of the drives and used capacity within the pool itself.
It is recommended to run a SCRUB right after resilvering to ensure that all data is accurate and healthy.
It is recommended to run a SCRUB right after resilvering to ensure that all data is accurate and healthy.
!!! info "Checking on Resilvering Process via CLI"
If you feel so inclined, you can check on the resilvering process by running the following command:
```sh
zpool status | grep "to go"
```