Skip to content

Disko did not respect dry-run and nuked the partitions on my SSD #1205

@stottm

Description

@stottm

To say I am displeased would be an epic understatement!

I've never ran any tool where dry run was so ambiguously disrespected.

From what I can gather;

Disko’s “dry‑run” mode is misleading.
It means:
“Don’t mount or format after creating the new layout.”

It does not mean:
“Don’t modify the disk.”

Here’s a thought: maybe the “dry run” feature could actually be, you know… dry? Instead of a kamikaze mission for my SSD.

In four decades, I’ve never seen a dry-run so enthusiastic about altering reality. It should be like a cautious friend who inspects the disk, crunches some numbers, prints a neat little “what-if” report, and leaves everything untouched—logging the whole thing for extra reassurance. It should be friendly to automation and manual introspection.

I’m not fishing for help here; just offering some constructive while humorous feedback. No precious data was harmed in the making of this fiasco—unless you count my valuable time and my pride. This was entirely my fault for not reading 800,000 words and not testing in a virtual machine. That does not mean disko shouldn't be improved. Please consider redesigning your dry run or at the least, renaming it to 'nuke disk from outer space'. In the meantime it may help others if you add a warning when using the dry run parameter.

For my fellow, autists; this is humor...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions