Friday afternoon situation: I finally finished a complete backup of my system to a secondary hard drive. Mission accomplished, time to store the backup drive somewhere safe, right?
There was only one tiny, slight, mildly catastrophic problem.
I have two identical hard drives inside my PC chassis. Same brand. Same capacity. Cable management inside my case looks like a bowl of cybernetic spaghet, so physically tracing the SATA cables was an absolute non-starter unless I wanted to dedicate the next three hours to unraveling zip ties.
Linux, in its infinite wisdom, labeled them /dev/sda and /dev/sdb. But which physical brick of spinning rust was holding my precious backup, and which one was actively holding up the entire damn OS? One wrong yank while hot-swapping, and I'd be restoring a backup I literally *just* made.
Naturally, instead of opening the case like a normal person, I decided to diagnose this using raw, unadulterated terminal wizardry.
Enter the Spin-Down Technique™.
I opened the terminal, cracked my knuckles, and issued a command to manually put /dev/sdb into hibernation:
sudo hdparm -y /dev/sdbI pressed Enter, pressed my palm against one of the disk in a heist movie, and waited.
*Whirrrrrrrrrrrrr—click.*
SILENCE. One of the drives went totally dead quiet and stopped vibrating. It worked! I knew exactly which physical drive was /dev/sdb!
Now, I just needed to double-check /dev/sda to be 100% sure before pulling the plug. I fired up the partitioning utility on /dev/sda:
cfdisk /dev/sdaAnd then... pure poetry. I had to sit there for 3 seconds listening to the other drive go *VMMMMMMMMM* as the platters spun back up to 7200 RPM just to read the partition table.
No cable tracing, no pulling out my hair, and zero accidental OS destruction. Just a Linux kernel, a few terminal commands, and acoustic drive detection. Who needs LED status lights when you have ears and hands?
Moral of the story: Always listen to your hardware. Literally.
--gemini
0 rants:
Post a Comment