Here's a habit I see all the time: someone copies a file to a flash drive, then pulls it straight out of the USB port the moment the copy looks done. It feels harmless — but it's one of the easiest ways to lose your files. To see why, it helps to know what your computer is quietly doing in the background: when it starts up, when it shuts down, and every time it hands a drive back to you.
Not every bit is your data — some are flags
Remember bits — those tiny 1-or-0 switches that everything is built from? Not all of them hold your files. The operating system keeps some bits for its own bookkeeping, using them as little flags — on/off markers that help it keep track of what's going on. One of those flags is about to explain a great deal.
What happens when your computer starts up
Starting a computer up is called booting — from the old phrase "pulling yourself up by your own bootstraps," because the machine essentially has to start itself from nothing. It isn't instant, because a surprising amount has to happen, in order:
- It wakes up the hardware and checks that the essential parts are present and working.
- It finds the operating system on your drive and loads it into memory (RAM) — the working space it actually runs in.
- It starts up the dozens of background helpers and services that make everything function.
- It mounts your drives — meaning it reads each drive's directory and bit map so it knows what's on them and where.
All of that takes a little time — which is why a computer doesn't spring to life the instant you press the power button.
Why shutting down isn't instant either
Shutting down is the same story in reverse, and it matters just as much. Before the power actually cuts off, the computer has to finish what it was doing: write out anything still sitting in memory that belongs on the drive, close every open file cleanly, and update the directory and bit map so the drive's records match reality. Only then does it set one last flag and power off.
That cleanup is why "Shut Down" sometimes takes a few seconds — or longer, if a program is being stubborn about closing. It isn't stalling. It's making sure nothing is left half-finished.
Meet the "dirty bit"
Here's that flag I promised. On every drive, the system keeps a single bit — nicknamed the dirty bit — that answers one simple question: was this drive shut down cleanly?
- When the computer starts up and begins using the drive, it sets the dirty bit to 1 (ON) — meaning "in use, not yet cleanly closed."
- When you shut down properly, that final cleanup sets it back to 0 (OFF) — meaning "all tidy."
So the next time the computer starts, it peeks at that one bit before trusting the drive:
| Dirty bit | What it means | What happens at the next startup |
|---|---|---|
| 0 (OFF) | Last shutdown was clean | Starts normally |
| 1 (ON) | Was not shut down properly — a crash or a power outage | Runs a battery of safety checks first — a slower start |
This is why the reboot after a crash or a power outage takes so much longer. The computer found the dirty bit still set to 1, so it can't assume the drive's records are intact — it runs those extra checks to be sure everything still lines up before relying on it. Nothing is necessarily wrong; it's being careful on your behalf. (Modern systems are better at this than they used to be, but a thorough check still takes time.)
Now — why you must eject a drive
Everything above is about your computer's own built-in drive. Exactly the same thing applies to an external drive or a flash drive — and this is where that bad habit bites.
When you tell the computer to eject (or "safely remove") a drive, it runs that very same little cleanup: it finishes any writes still in progress, pushes out anything it was holding in memory to be written, updates the directory and bit map, and marks the drive clean. Then it tells you it's safe to unplug.
And here's the part that surprises people: when the copy progress bar finishes, the computer often isn't actually done writing yet. For speed, it holds some of the data in memory and writes it out a moment later. So a drive can look completely finished while work is still quietly pending.
Never pull a drive out of the USB port before you've ejected it. Yank it mid-write and you can leave the drive's directory and bit map half-updated — damaged tables the computer can no longer make sense of. The result can be a drive, or files, you simply can't open anymore. Flash drives are especially prone to this. Always eject first, and wait for the all-clear. If it does happen, stop using the drive and see how recovery works.
How to eject safely
On a Mac
Drag the drive's icon on the desktop to the Trash. I know that sounds alarming — but you're not erasing anything. The moment you start dragging a drive, the Trash turns into an Eject symbol, and dropping it there simply ejects the drive. Prefer the keyboard? Click the drive's icon once to select it and press ⌘ E, or choose File → Eject from the menu bar. Once the drive's icon disappears from the desktop, it's safe to unplug. (This assumes your Finder is set to show external drives on the desktop — I always keep mine that way.)
On Windows
Click the Safely Remove Hardware icon in the taskbar (the little USB-plug symbol), choose your drive, and wait for the "Safe to remove hardware" message. Or right-click the drive in File Explorer and choose Eject.
Treat "Eject" like a seatbelt. It costs one extra second, and the one time it matters, it really matters.
Stuck with a drive that won't open?
If a drive has stopped showing up, or your files have gone missing after a yank or a crash, don't keep using it — that's exactly the kind of thing I can help with. Get in touch or call 817-994-7111, and have a look at how recovery works first.