Additional Doc Restructure

infrastructure/hardware/cluster-node-01/disk-arrays.md

@@ -0,0 +1,10 @@
+## Purpose
+This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
+
+!!! note "Disk Order Structure"
+    Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
+
+| **Column 01** | **Column 02** | **Column 03** | **Column 04** |
+| :--- | :--- | :--- | :--- |
+| 240GB<br>`SN: 50026B77850B2DA9` | 240GB<br>`SN: 50026B7784D34038` | 240GB<br>`SN: 50026B7784E8A771` | 240GB<br>`SN: 50026B7784E8CB49` |
+| 240GB<br>`SN: 50026B7784D3620D` | 240GB<br>`SN: 50026B7784D45C34` | 240GB<br>`SN: 50026B7784E8AC95` | 240GB<br>`SN: 50026B7784E8A983` |

infrastructure/hardware/cluster-node-02/disk-arrays.md

@@ -0,0 +1,16 @@
+## Purpose
+This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
+
+!!! note "Disk Order Structure"
+    Disks are represented in 3 columns, with the top-down view representing left-to-right.
+
+| **Column 01** | **Column 02** | **Column 03** |
+| :--- | :--- | :--- |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31DHQ` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR4fHA0` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31DJL` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR33GBT` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31D8L` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR33F2W` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR32TFE` |
+| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |

infrastructure/hardware/cluster-node-03/disk-arrays.md

@@ -0,0 +1,11 @@
+## Purpose
+This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
+
+!!! note "Disk Order Structure"
+    Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
+
+| **Column 01** | **Column 02** | **Column 03** | **Column 04** |
+| :--- | :--- | :--- | :--- |
+| 8TB<br>`SN: X1P0A01NFDWF` | 8TB<br>`SN: WWZ1TJT2` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |
+| 8TB<br>`SN: VRK6M6MK` | 8TB<br>`SN: Y1L0A0QQFDWF` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |
+| 8TB<br>`SN: VRK6XEMK` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 1TB<br>`SN: 2417E8A9A7C1` |

infrastructure/hardware/index.md

@@ -0,0 +1,30 @@
+# Hardware
+## Purpose
+Physical assets, node inventories, storage layouts, and power topology for the lab.
+
+## Includes
+- Node build sheets and inventory
+- Disk arrays and drive replacement procedures
+- Power and UPS mapping
+
+## New Document Template
+````markdown
+# <Document Title>
+## Purpose
+<what this hardware doc exists to describe>
+
+!!! info "Assumptions"
+    - <hardware model / firmware / OS assumptions>
+    - <privilege assumptions>
+
+## Inventory
+- <serials, bays, disks, NICs, etc>
+
+## Procedure
+```sh
+# Commands (if applicable)
+```
+
+## Validation
+- <command + expected result>
+````

infrastructure/hardware/storage-node-01-truenas-core/disk-arrays.md

@@ -0,0 +1,16 @@
+## Purpose
+This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
+
+!!! note "Disk Order Structure"
+    Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
+
+!!! note "Boot Drive"
+    Boot drive is an external Samsung PSSD T7 portable SSD.  Serial Number: `S6U5NS0RC09159R`
+
+| **Column 01** | **Column 02** | **Column 03** | **Column 04** | **Column 05** |
+| :--- | :--- | :--- | :--- | :--- |
+| 960GB<br>`SN: 50026B778526FF9F` | 960GB<br>`SN: 50026B778527104D` | 960GB<br>`SN: 50026B778526FFAD` | 960GB<br>`SN: 50026B7785270727` | 960GB<br>`SN: 50026B778526FCD2` |
+| 960GB<br>`SN: 50026B7785270194` | 960GB<br>`SN: 50026B77853B0F4C` | 960GB<br>`SN: 50026B7785270EB4` | 960G<br>`SN: 50026B76870D497D` | 960GB<br>`SN: 50026B778526FCC8` |
+| 960GB<br>`SN: 50026B778526F8F2` | 960GB<br>`SN: 50026B778526F8EB` | 960GB<br>`SN: 50026B778526FCFC` | 960GB<br>`SN: 50026B76870D47DF` | 960GB<br>`SN: 50026B778526F8EC` |
+| 960GB<br>`SN: 50026B7785270E2A` | 960GB<br>`SN: 50026B7785270653` | 960GB<br>`SN: 50026B778526FF67` | 1050G<br>`SN: 163313AAA680` | 960GB<br>`SN: 50026B778526FF4A` |
+| 960GB<br>`SN: 50026B778526FFAA` | 960GB<br>`SN: 50026B778526FFC7` | 960GB<br>`SN: 50026B778526FF49` | 1TB<br>`SN: SI04T000311404D40` | EMPTY<br>`SN: N/A` |

infrastructure/hardware/storage-node-01-truenas-core/replacing-a-drive.md

@@ -0,0 +1,39 @@
+## Purpose
+This document acts as a workflow to understand how to replace a drive on TrueNAS Core when it is hosted on an HPE Proliant server with HBA / IT Mode enabled.  This enables you to hot-swap drives without rebooting TrueNAS Core.
+
+### Offline the Disk
+- You will log into the TrueNAS Core [WebUI](http://192.168.3.3).
+- Navigate to "**Storage > Disks**"
+    - Look for the drive that is having issues / faults / unavailable and reference it's `da` number to reference later. (e.g. `da3`)
+    - Confirm the serial number of the drive and correlate that to the physical location in the [Disk Arrays](./disk-arrays.md) document, 
+- Navigate to "**Storage > Pools**"
+- Look for the gear icon to the right of the storage pool and click on it
+    - Click on "**Status**"
+        - Locate the failing / failed drive and click on the "**...**" elipsis menu button
+        - Proceed to "**Offline**" the disk.  This ensures that TrueNAS Core stops trying to use the disk.
+
+### Physical Disk Replacement
+At this point, we need to physically go to the server and pull out the failing drive and replace it.  
+
+- Take note of the new serial number on the replacement drive and update the [Disk Arrays](./disk-arrays.md) document accordingly.
+- Insert the replacement drive back into the TrueNAS Core server
+
+### Trigger Disk Re-Scan
+Now we need to tell TrueNAS / FreeBSD to re-scan all disks to locate the new one.
+
+- Within the TrueNAS Core WebUI, navigate to "**Shell**" and run the following command: `camcontrol rescan all`
+- Navigate (back) to "**Storage > Pools > Status**"
+    - Locate the failed drive via it's `da` number again, and click the "**...**" elipsis menu button
+    - Proceed to "**Replace**" the disk, and when given a dropdown menu, only the new replacement disk should appear with the same `da` number
+
+!!! 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.
+
+!!! 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"
+    ```
+

infrastructure/hardware/storage-node-02-truenas-scale/disk-arrays.md

@@ -0,0 +1,9 @@
+## Purpose
+This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
+
+!!! note "Disk Order Structure"
+    Disks are represented in 1 column, with the drive positions / topology mirroring the table seen below.
+
+| **Slot 01** | **Slot 02** | **Slot 03** | **Slot 04** | **Slot 05** |
+| :--- | :--- | :--- | :--- | :--- |
+| 4TB<br>`SN: Z305ZNZM` | 4TB<br>`SN: Z305SPL8` | 4TB<br>`SN: Z3051AF8` | 4TB<br>`SN: Z305ZNM1` | 4TB<br>`SN: Z305S03R` |