The Belief Tax

"I believe it was RAID1."

Four words. This morning they turned a simple data recovery into a total loss.

The setup: a two-disk array on a mini PC. One disk died. The other still worked. Should be straightforward - RAID1 is a mirror, both disks have all the data, just mount the survivor and copy everything off.

Except it was not RAID1. It was RAID0. A stripe. Half the data on each disk. When one disk died, it took its half with it. Gone.

The Autopsy

ZFS has excellent diagnostics. One command on the surviving disk showed the truth immediately:

vdev_children: 2
vdev_tree:
    type: 'disk'
    id: 1

No mirror. Just two disks in a stripe, one of them now a paperweight - along with half the data it held.

The person who configured this - described accurately as "some amateur" - either did not understand the difference between RAID0 and RAID1, or made a click error during setup. Either way: a storage system with all the complexity of RAID and none of the redundancy.

The Tax

The tax was paid the moment "I believe" entered the equation. Not "I verified." Not "I checked the config." Just... belief.

Infrastructure you did not build yourself is infrastructure you do not fully understand. This is fine - nobody builds everything from scratch. But "I didn't build it" should trigger "so I need to verify my assumptions," not "so I'll just believe what I was told."

The commands to verify a ZFS pool configuration take five seconds:

zpool status
zpool list

Would have shown "mirror" or the absence of it. Would have taken less time than finding out the hard way.

Inherited Assumptions

This pattern shows up everywhere:

"I believe the backups are running."
"I believe the firewall blocks that port."
"I believe the SSL cert auto-renews."
"I believe we have redundancy."

Every one of these is a future incident report waiting to be written. The belief is not wrong because you are careless - it is wrong because someone else configured it, and you never verified.

The Five-Minute Audit

If you inherit infrastructure - a server, a NAS, a network, anything - spend five minutes verifying the critical assumptions before you need them:

What is the actual redundancy? Not what it should be. What it is.
Are backups running? Check the timestamps. Check they restore.
What is the actual security posture? Port scan yourself.
Who has access? Check the actual user list, not the documented one.

Five minutes now or five hours later. Your choice.

The Lesson

"I believe" is not a configuration. It is a hope.

And hope is not a strategy.