diff --git a/Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md b/Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md
index ac9e131..870b678 100644
--- a/Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md	
+++ b/Hardware/Storage Node 01 (TrueNAS Core)/Replacing a Drive.md	
@@ -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.
\ No newline at end of file
+    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"
+    ```
\ No newline at end of file