Describe the disk manager behaviour as the scripts run it

- Wipe all trims the whole disk when discard is supported and is not a secure erase
- Declining the privileged conversion changes nothing, and accepting backs up the configuration first
- The by-id path is used when it exists, with /dev/sdX as fallback
- Full report opens in a scrollable dialog; SAS progress comes from the self-test log
This commit is contained in:
MacRimi
2026-10-18 13:47:58 +02:00
parent ab2dd5dc02
commit 163c964314
32 changed files with 42 additions and 42 deletions
@@ -12,7 +12,7 @@
},
"intro": {
"title": "What this does",
"body": "This attaches a raw physical disk as the backing device for a virtual disk interface. The guest does not automatically receive native SMART data or the physical controller’s features; use controller PCI passthrough when those are required. The disk is attached through <code>/dev/disk/by-id/…</code>, not <code>/dev/sdX</code>, so a changed device enumeration order at boot does not break the assignment."
"body": "This attaches a raw physical disk as the backing device for a virtual disk interface. The guest does not automatically receive native SMART data or the physical controller’s features; use controller PCI passthrough when those are required. The disk is attached through its <code>/dev/disk/by-id/…</code> path when one exists, so a changed device enumeration order at boot does not break the assignment; otherwise <code>/dev/sdX</code> is used."
},
"howRuns": {
"heading": "How the script runs",