dwipe 3.0.0__tar.gz → 3.0.2__tar.gz

dwipe-3.0.2/.github/workflows/tests.yml

@@ -0,0 +1,47 @@
+name: tests
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package with test extras
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e '.[test]'
+
+      - name: Run unit tests with coverage
+        run: pytest --cov=dwipe --cov-report=term-missing --cov-fail-under=40
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install pylint
+        run: python -m pip install --upgrade pip pylint
+
+      - name: Static checks (undefined names / bad calls)
+        # Full advisory lint is available locally via ./linter. This job blocks
+        # only on the error classes that indicate real bugs (undefined name,
+        # bad call signature) and currently passes at 10.00/10.
+        run: pylint --disable=all --enable=E0601,E0602,E0603,E1120,E1121 dwipe

{dwipe-3.0.0 → dwipe-3.0.2}/.gitignore

@@ -6,4 +6,5 @@ venv.zd/
 *.pyc
 *egg-info*
 dist/
-.github/
+.coverage
+htmlcov/

{dwipe-3.0.0 → dwipe-3.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dwipe
-Version: 3.0.0
+Version: 3.0.2
 Summary: A tool to wipe disks and partitions for Linux
 Keywords: disk,partition,wipe,clean,scrub
 Author-email: Joe Defen <joedef@google.com>
@@ -11,13 +11,16 @@ Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: POSIX :: Linux
 License-File: LICENSE
 Requires-Dist: console-window == 1.4.2
+Requires-Dist: pytest >= 7.0 ; extra == "test"
+Requires-Dist: pytest-cov >= 4.0 ; extra == "test"
 Project-URL: Bug Tracker, https://github.com/joedefen/dwipe/issues
 Project-URL: Homepage, https://github.com/joedefen/dwipe
+Provides-Extra: test
 
 # dwipe
 `dwipe` is a tool to wipe disks and partitions for Linux to help secure your data. `dwipe` aims to reduce mistakes by providing ample information about your devices during selection.
 
-![Demo of dwipe](https://raw.githubusercontent.com/joedefen/dwipe/master/images/dwipe-2025-12-31-09-37.gif)
+![Demo of dwipe](https://raw.githubusercontent.com/joedefen/dwipe/master/images/dwipe-2026-02-05.07-58.gif)
 ### Quick Comparison
 
 | Feature | dwipe | nwipe | shred | dd |
@@ -31,7 +34,7 @@ Project-URL: Homepage, https://github.com/joedefen/dwipe
 | Device/partition blocking | ✓ | ✗ | ✗ | ✗ |
 | Resume interrupted software wipes | ✓ | ✗ | ✗ | ✗ |
 | Wipe operation logging | ✓ | ✗ | ✗ | ✗ |
-| Mount detection/prevention | ✓ | ✓ | ✗ | ✗ |
+| Mount & LUKS/LVM/RAID/swap detection | ✓ | ✓ | ✗ | ✗ |
 | Fast Statistical sampling verification | ✓ | ✗ | ✗ | ✗ |
 | Certified destruction (DoD/Gutmann standards, full verification, certificates) | ✗ | ✓ | ✗ | ✗ |
 
@@ -46,7 +49,7 @@ Project-URL: Homepage, https://github.com/joedefen/dwipe
 * **Multiple simultaneous wipes** - Start wipes on multiple devices at once with individual progress tracking and completion states
 * **Persistent state tracking** - Wipe status survives reboots; partially wiped and completed states persist on the device (can resume wipes across power cycles)
 * **Smart device identification** - Uses UUID/PARTUUID/serial numbers for stable device tracking across reconnections
-* **Safety protections** - Prevents wiping mounted devices, detects overlapping wipes, supports device blocking, inline confirmation prompts
+* **Safety protections** - Prevents wiping mounted or in-use devices (including LUKS/LVM/RAID containers and swap), detects overlapping wipes, supports device blocking, inline confirmation prompts
 * **Intelligent verification with statistical sampling** - Fast verification that covers entire disk even at low percentages (1% verification samples from all 100 disk sections)
 * **Direct I/O to disk** - Fast and efficient wiping that avoids page cache pollution with automatic slowdown/stall detection and graceful abort
 * **Multiple color themes** - Terminal color themes designed for readability with context-sensitive visual feedback (mounted devices dimmed, active wipes bright)
@@ -81,7 +84,7 @@ Project-URL: Homepage, https://github.com/joedefen/dwipe
 1. **Drives and the OS often lie about drive type.** Outwit them both:
     * For spinning HDDs, **always** use `Rand` or `Zero` (interruptible, shows progress).
     * For SSDs, **always** use firmware wipes if available (faster, reaches hidden blocks).
-1. **If a drive is 'Frozen'**, press `DEL` to detach it and, when gone, press `r` to rescan; it should come back unfrozen.
+1. **If a drive is 'Frozen'**, suspend your system briefly and resume; `dwipe` auto-detects the resume and rescans. Or press `r` to rescan manually. The drive should come back unfrozen.
 1. **If a drive is 'Locked'**, you must unlock it manually (see "Unlock Locked Device" section below). If `dwipe` locked it, the password is `NULL`; otherwise use the password that locked it.
 1. **Hot-swap workflow for SATA drives**: `DEL` to detach, physically swap drives, then `r` to rescan (if needed).
 
@@ -91,7 +94,7 @@ Project-URL: Homepage, https://github.com/joedefen/dwipe
 `dwipe` provides comprehensive disk wiping capabilities with safety features:
 
 * **Smart device display** - Shows disks and partitions with labels, sizes, types, and vendor/model information to help identify devices correctly
-* **Safety protections** - Prevents wiping mounted devices, detects overlapping wipes, supports manual disk blocking
+* **Safety protections** - Prevents wiping mounted or in-use devices (including LUKS/LVM/RAID containers and swap), detects overlapping wipes, supports manual disk blocking
 * **Hot-swap detection** - Updates the device list when storage changes; newly added devices are marked with **^** to make them easy to spot
 * **Multiple simultaneous wipes** - Start wipes on multiple devices at once, with individual progress tracking and completion states
 * **Flexible wipe modes** - Choose between Rand, Zero, Rand+V (with auto-verify), or Zero+V (with auto-verify)
@@ -141,6 +144,10 @@ Simply run `dwipe` from the command line without arguments: `dwipe`
 - `--firmware-wipes` or `-F` - Enable firmware wipes
   - Enables hardware-based secure erase operations (NVMe Sanitize/Format, SATA ATA Security Erase)
   - Without this flag, only software wipes (Zero/Rand) are available
+- `--auto-block-containers {on,off}` - Auto-block encrypted/stacked containers on first sight (default: on)
+  - Blocks devices whose filesystem is a container (LUKS, LVM, RAID member, swap) the first time they are seen, so wiping requires an explicit unblock (**b**)
+  - The block is remembered per device; once you unblock, it stays unblocked
+  - Set to `off` when re-provisioning many encrypted disks to avoid unblocking each one
 - `--dump-lsblk` - Dump parsed device information and exit (for debugging)
 - `--help` - Show help message with all available options
 
@@ -148,7 +155,7 @@ Simply run `dwipe` from the command line without arguments: `dwipe`
 
 `dwipe` uses color coding to provide instant visual feedback about device and operation status:
 
-- **Dimmed (gray)** - Mounted or blocked devices (cannot be wiped)
+- **Dimmed (gray)** - Mounted, in-use (LUKS/LVM/RAID/swap), or blocked devices (cannot be wiped)
 - **Default (white)** - Ready to wipe, idle state, or previously wiped (before this session)
 - **Bright cyan/blue + bold** - Active wipe or verification in progress (0-100% write, v0-v100% verify)
 - **Bold yellow** - Stopped or partially completed wipe
@@ -190,15 +197,41 @@ The **STATE** column shows the current status of each device:
 |-------|---------|
 | **-** | Device is ready for wiping |
 | **^** | Device is ready for wiping AND was added after `dwipe` started (hot-swapped) |
-| **Mnt** | Partition is mounted or disk has mounted partitions - cannot be wiped |
+| **Mnt** | Partition/disk is mounted, or in use via a swap/LUKS/LVM/RAID mapping - cannot be wiped |
 | **N%** | Wipe is in progress (shows percentage complete, 0-100%) |
 | **vN%** | Verification is in progress (shows percentage complete, v0-v100%) |
 | **STOP** | Wipe or verification is being stopped |
 | **s** | Wipe was stopped - device is partially wiped (can restart or verify) |
 | **W** | Wipe was completed successfully (can wipe again or verify) |
-| **Blk** | Disk is manually blocked - partitions are hidden and cannot be wiped |
+| **Blk** | Device/disk is blocked (with **b**, or auto-blocked when it is a LUKS/LVM/RAID/swap container) - cannot be wiped |
 | **Unbl** | Disk was just unblocked (transitory state) |
 
+### Mounts / Status Column
+
+The **MOUNTS/STATUS** column shows how a device is currently in use:
+
+| Display | Meaning |
+|---------|---------|
+| **/**, **/data** | A real mount point (mounted directly, or through a LUKS/LVM/RAID mapping) |
+| **\busy** | In use but not mounted — e.g. an *open* LUKS container, an active LVM volume group, a running RAID array, or active swap |
+
+Both are treated as mounted: the device is dimmed and **w** (wipe) is not offered. `\busy` uses a backslash (not `/`) to make clear it is not a real mount point, yet it is treated like one for safety. To wipe such a device, first release the layer holding it (see [Wipe issues](#wipe-issues)).
+
+> **Note:** A device held by a lower layer (dm-crypt/LUKS, LVM, md/RAID, swap) is protected even when it is not itself mounted. Wiping the backing device while a mapping is active would corrupt the container, so `dwipe` treats it as mounted. Mount points reached through a mapping are attributed back to the underlying device, so a LUKS partition shows the mount of its unlocked mapping.
+
+### Auto-Blocking Containers
+
+`dwipe` auto-blocks devices that hold encrypted or stacked containers **the first time they are seen**, whether or not they are currently in use. This guards data that is otherwise easy to wipe by accident, since a *closed* container shows almost no hint beyond its type:
+
+- `crypto_LUKS` (dm-crypt/LUKS)
+- `LVM2_member` (LVM physical volume)
+- `linux_raid_member` / `isw_raid_member` / `ddf_raid_member` (RAID members)
+- `swap`
+
+Such a device shows state **Blk** with an `auto-blocked` status, and its whole disk is protected too (inherited block). To wipe it, press **b** to unblock — the unblock is remembered, so it is not re-blocked on later scans.
+
+Auto-blocking is on by default. Disable it for bulk re-provisioning with `--auto-block-containers off` (saved as a preference).
+
 ### Available Actions
 
 The top line shows available actions. Some are context-sensitive (only available for certain devices):
@@ -464,9 +497,14 @@ Press **ESC** from the main screen to clear the filter and return to showing all
 - **Colors don't work** - Ensure your terminal supports colors (most modern terminals do)
 
 ### Wipe issues
-- **Can't wipe a device** - Check the STATE column:
+- **Can't wipe a device** - Check the STATE and MOUNTS/STATUS columns:
   - **Mnt** - Unmount the partition first: `sudo umount /dev/sdXN`
-  - **Blk** - Press **b** to unblock
+  - **`\busy`** status, or **Mnt** caused by a lower layer - release the mapping/volume first, then rescan (**r**):
+    - LUKS: unmount, then `sudo cryptsetup close <name>`
+    - LVM: `sudo vgchange -an <vg>` (deactivate the volume group)
+    - RAID: `sudo mdadm --stop /dev/mdX`
+    - Swap: `sudo swapoff /dev/...`
+  - **Blk** - Press **b** to unblock (containers such as LUKS/LVM/RAID/swap are auto-blocked until you do)
   - **Busy** - Another partition on the disk is being wiped
 - **Wipe is very slow** - Normal for large drives; check write rate to verify progress
 - **Wipe seems stuck** - Most likely due to bad disks; Direct I/O makes progress almost constant on good disks.
@@ -477,11 +515,10 @@ Press **ESC** from the main screen to clear the filter and return to showing all
 Firmware wipes (SATA/NVMe secure erase operations) have different characteristics than software wipes:
 
 **Frozen Drives:**
-- Firmware wipes sometimes report the drive as "Frozen" if the device is present (mounted or in use) when capabilities are detected
+- SATA drives are typically frozen by the BIOS/UEFI during POST as a security measure
 - This is a drive-level security feature, not a `dwipe` limitation
-- **Solution**: Unmount the device, wait briefly (often just a few seconds of idle time is enough), then use **r** to rescan capabilities
-- The freeze state is usually temporary and clears after the device is no longer actively in use
-- If the drive remains frozen, try hot-swapping (remove and reinsert) or power-cycling the device
+- **Solution**: Suspend your system briefly and resume; `dwipe` auto-detects the resume and rescans (or press **r** manually). The suspend/resume power-cycles the SATA link which clears the freeze.
+- If the drive remains frozen after suspend/resume, try a full power-off (10+ minutes to drain drive capacitors) followed by boot and rescan
 
 **Device Quirks and Compatibility:**
 - Storage devices have various firmware implementations and hardware quirks that affect secure erase operations

{dwipe-3.0.0 → dwipe-3.0.2}/README.md

@@ -1,7 +1,7 @@
 # dwipe
 `dwipe` is a tool to wipe disks and partitions for Linux to help secure your data. `dwipe` aims to reduce mistakes by providing ample information about your devices during selection.
 
-![Demo of dwipe](https://raw.githubusercontent.com/joedefen/dwipe/master/images/dwipe-2025-12-31-09-37.gif)
+![Demo of dwipe](https://raw.githubusercontent.com/joedefen/dwipe/master/images/dwipe-2026-02-05.07-58.gif)
 ### Quick Comparison
 
 | Feature | dwipe | nwipe | shred | dd |
@@ -15,7 +15,7 @@
 | Device/partition blocking | ✓ | ✗ | ✗ | ✗ |
 | Resume interrupted software wipes | ✓ | ✗ | ✗ | ✗ |
 | Wipe operation logging | ✓ | ✗ | ✗ | ✗ |
-| Mount detection/prevention | ✓ | ✓ | ✗ | ✗ |
+| Mount & LUKS/LVM/RAID/swap detection | ✓ | ✓ | ✗ | ✗ |
 | Fast Statistical sampling verification | ✓ | ✗ | ✗ | ✗ |
 | Certified destruction (DoD/Gutmann standards, full verification, certificates) | ✗ | ✓ | ✗ | ✗ |
 
@@ -30,7 +30,7 @@
 * **Multiple simultaneous wipes** - Start wipes on multiple devices at once with individual progress tracking and completion states
 * **Persistent state tracking** - Wipe status survives reboots; partially wiped and completed states persist on the device (can resume wipes across power cycles)
 * **Smart device identification** - Uses UUID/PARTUUID/serial numbers for stable device tracking across reconnections
-* **Safety protections** - Prevents wiping mounted devices, detects overlapping wipes, supports device blocking, inline confirmation prompts
+* **Safety protections** - Prevents wiping mounted or in-use devices (including LUKS/LVM/RAID containers and swap), detects overlapping wipes, supports device blocking, inline confirmation prompts
 * **Intelligent verification with statistical sampling** - Fast verification that covers entire disk even at low percentages (1% verification samples from all 100 disk sections)
 * **Direct I/O to disk** - Fast and efficient wiping that avoids page cache pollution with automatic slowdown/stall detection and graceful abort
 * **Multiple color themes** - Terminal color themes designed for readability with context-sensitive visual feedback (mounted devices dimmed, active wipes bright)
@@ -65,7 +65,7 @@
 1. **Drives and the OS often lie about drive type.** Outwit them both:
     * For spinning HDDs, **always** use `Rand` or `Zero` (interruptible, shows progress).
     * For SSDs, **always** use firmware wipes if available (faster, reaches hidden blocks).
-1. **If a drive is 'Frozen'**, press `DEL` to detach it and, when gone, press `r` to rescan; it should come back unfrozen.
+1. **If a drive is 'Frozen'**, suspend your system briefly and resume; `dwipe` auto-detects the resume and rescans. Or press `r` to rescan manually. The drive should come back unfrozen.
 1. **If a drive is 'Locked'**, you must unlock it manually (see "Unlock Locked Device" section below). If `dwipe` locked it, the password is `NULL`; otherwise use the password that locked it.
 1. **Hot-swap workflow for SATA drives**: `DEL` to detach, physically swap drives, then `r` to rescan (if needed).
 
@@ -75,7 +75,7 @@
 `dwipe` provides comprehensive disk wiping capabilities with safety features:
 
 * **Smart device display** - Shows disks and partitions with labels, sizes, types, and vendor/model information to help identify devices correctly
-* **Safety protections** - Prevents wiping mounted devices, detects overlapping wipes, supports manual disk blocking
+* **Safety protections** - Prevents wiping mounted or in-use devices (including LUKS/LVM/RAID containers and swap), detects overlapping wipes, supports manual disk blocking
 * **Hot-swap detection** - Updates the device list when storage changes; newly added devices are marked with **^** to make them easy to spot
 * **Multiple simultaneous wipes** - Start wipes on multiple devices at once, with individual progress tracking and completion states
 * **Flexible wipe modes** - Choose between Rand, Zero, Rand+V (with auto-verify), or Zero+V (with auto-verify)
@@ -125,6 +125,10 @@ Simply run `dwipe` from the command line without arguments: `dwipe`
 - `--firmware-wipes` or `-F` - Enable firmware wipes
   - Enables hardware-based secure erase operations (NVMe Sanitize/Format, SATA ATA Security Erase)
   - Without this flag, only software wipes (Zero/Rand) are available
+- `--auto-block-containers {on,off}` - Auto-block encrypted/stacked containers on first sight (default: on)
+  - Blocks devices whose filesystem is a container (LUKS, LVM, RAID member, swap) the first time they are seen, so wiping requires an explicit unblock (**b**)
+  - The block is remembered per device; once you unblock, it stays unblocked
+  - Set to `off` when re-provisioning many encrypted disks to avoid unblocking each one
 - `--dump-lsblk` - Dump parsed device information and exit (for debugging)
 - `--help` - Show help message with all available options
 
@@ -132,7 +136,7 @@ Simply run `dwipe` from the command line without arguments: `dwipe`
 
 `dwipe` uses color coding to provide instant visual feedback about device and operation status:
 
-- **Dimmed (gray)** - Mounted or blocked devices (cannot be wiped)
+- **Dimmed (gray)** - Mounted, in-use (LUKS/LVM/RAID/swap), or blocked devices (cannot be wiped)
 - **Default (white)** - Ready to wipe, idle state, or previously wiped (before this session)
 - **Bright cyan/blue + bold** - Active wipe or verification in progress (0-100% write, v0-v100% verify)
 - **Bold yellow** - Stopped or partially completed wipe
@@ -174,15 +178,41 @@ The **STATE** column shows the current status of each device:
 |-------|---------|
 | **-** | Device is ready for wiping |
 | **^** | Device is ready for wiping AND was added after `dwipe` started (hot-swapped) |
-| **Mnt** | Partition is mounted or disk has mounted partitions - cannot be wiped |
+| **Mnt** | Partition/disk is mounted, or in use via a swap/LUKS/LVM/RAID mapping - cannot be wiped |
 | **N%** | Wipe is in progress (shows percentage complete, 0-100%) |
 | **vN%** | Verification is in progress (shows percentage complete, v0-v100%) |
 | **STOP** | Wipe or verification is being stopped |
 | **s** | Wipe was stopped - device is partially wiped (can restart or verify) |
 | **W** | Wipe was completed successfully (can wipe again or verify) |
-| **Blk** | Disk is manually blocked - partitions are hidden and cannot be wiped |
+| **Blk** | Device/disk is blocked (with **b**, or auto-blocked when it is a LUKS/LVM/RAID/swap container) - cannot be wiped |
 | **Unbl** | Disk was just unblocked (transitory state) |
 
+### Mounts / Status Column
+
+The **MOUNTS/STATUS** column shows how a device is currently in use:
+
+| Display | Meaning |
+|---------|---------|
+| **/**, **/data** | A real mount point (mounted directly, or through a LUKS/LVM/RAID mapping) |
+| **\busy** | In use but not mounted — e.g. an *open* LUKS container, an active LVM volume group, a running RAID array, or active swap |
+
+Both are treated as mounted: the device is dimmed and **w** (wipe) is not offered. `\busy` uses a backslash (not `/`) to make clear it is not a real mount point, yet it is treated like one for safety. To wipe such a device, first release the layer holding it (see [Wipe issues](#wipe-issues)).
+
+> **Note:** A device held by a lower layer (dm-crypt/LUKS, LVM, md/RAID, swap) is protected even when it is not itself mounted. Wiping the backing device while a mapping is active would corrupt the container, so `dwipe` treats it as mounted. Mount points reached through a mapping are attributed back to the underlying device, so a LUKS partition shows the mount of its unlocked mapping.
+
+### Auto-Blocking Containers
+
+`dwipe` auto-blocks devices that hold encrypted or stacked containers **the first time they are seen**, whether or not they are currently in use. This guards data that is otherwise easy to wipe by accident, since a *closed* container shows almost no hint beyond its type:
+
+- `crypto_LUKS` (dm-crypt/LUKS)
+- `LVM2_member` (LVM physical volume)
+- `linux_raid_member` / `isw_raid_member` / `ddf_raid_member` (RAID members)
+- `swap`
+
+Such a device shows state **Blk** with an `auto-blocked` status, and its whole disk is protected too (inherited block). To wipe it, press **b** to unblock — the unblock is remembered, so it is not re-blocked on later scans.
+
+Auto-blocking is on by default. Disable it for bulk re-provisioning with `--auto-block-containers off` (saved as a preference).
+
 ### Available Actions
 
 The top line shows available actions. Some are context-sensitive (only available for certain devices):
@@ -448,9 +478,14 @@ Press **ESC** from the main screen to clear the filter and return to showing all
 - **Colors don't work** - Ensure your terminal supports colors (most modern terminals do)
 
 ### Wipe issues
-- **Can't wipe a device** - Check the STATE column:
+- **Can't wipe a device** - Check the STATE and MOUNTS/STATUS columns:
   - **Mnt** - Unmount the partition first: `sudo umount /dev/sdXN`
-  - **Blk** - Press **b** to unblock
+  - **`\busy`** status, or **Mnt** caused by a lower layer - release the mapping/volume first, then rescan (**r**):
+    - LUKS: unmount, then `sudo cryptsetup close <name>`
+    - LVM: `sudo vgchange -an <vg>` (deactivate the volume group)
+    - RAID: `sudo mdadm --stop /dev/mdX`
+    - Swap: `sudo swapoff /dev/...`
+  - **Blk** - Press **b** to unblock (containers such as LUKS/LVM/RAID/swap are auto-blocked until you do)
   - **Busy** - Another partition on the disk is being wiped
 - **Wipe is very slow** - Normal for large drives; check write rate to verify progress
 - **Wipe seems stuck** - Most likely due to bad disks; Direct I/O makes progress almost constant on good disks.
@@ -461,11 +496,10 @@ Press **ESC** from the main screen to clear the filter and return to showing all
 Firmware wipes (SATA/NVMe secure erase operations) have different characteristics than software wipes:
 
 **Frozen Drives:**
-- Firmware wipes sometimes report the drive as "Frozen" if the device is present (mounted or in use) when capabilities are detected
+- SATA drives are typically frozen by the BIOS/UEFI during POST as a security measure
 - This is a drive-level security feature, not a `dwipe` limitation
-- **Solution**: Unmount the device, wait briefly (often just a few seconds of idle time is enough), then use **r** to rescan capabilities
-- The freeze state is usually temporary and clears after the device is no longer actively in use
-- If the drive remains frozen, try hot-swapping (remove and reinsert) or power-cycling the device
+- **Solution**: Suspend your system briefly and resume; `dwipe` auto-detects the resume and rescans (or press **r** manually). The suspend/resume power-cycles the SATA link which clears the freeze.
+- If the drive remains frozen after suspend/resume, try a full power-off (10+ minutes to drain drive capacitors) followed by boot and rescan
 
 **Device Quirks and Compatibility:**
 - Storage devices have various firmware implementations and hardware quirks that affect secure erase operations