Loop Device Index Grows on Failed Wipe Attempts

[shreyas-omkar]

Bug: Loop Device Index Grows on Failed Wipe Attempts

Description

When wiping loop-backed devices (e.g. virtual disks in QEMU), SecureWipe assigns synthetic identifiers such as:

• /dev/loop0
• /dev/loop1
• /dev/loop2

If a wipe operation fails and is retried, the loop index keeps increasing, resulting in:

• Mismatched confirmation prompts
• Confusing device identity
• Unsafe user experience for retries

Loop device numbering should remain stable and deterministic across retries.

---

Steps to Reproduce

1. Boot SecureWipe in a virtualized environment
2. Attach a loop-backed disk
3. Attempt a wipe that fails
4. Retry the wipe
5. Observe that the loop identifier changes

---

Expected Behavior

• Loop devices retain a stable identity across retries
• Confirmation prompts remain consistent
• Failed wipes do not create new synthetic identifiers

---

Acceptance Criteria

• Loop device identity remains consistent after failures
• Retrying a wipe does not alter the displayed device name
• Confirmation logic works reliably for loop-backed disks