5
Just had a client's server crash because I followed the 'right' procedure
I was at a small office in Austin last Tuesday, fixing their file server that kept throwing disk errors. Everyone says you should always run chkdsk first before anything else, so I did. Big mistake. It locked up the drive mid-scan and corrupted the MFT beyond repair. I had to pull the drive, clone it sector-by-sector with a Linux live USB, and then recover files from the clone. Took me 6 hours and a lot of swearing. Now I think that 'best practice' is fine for healthy drives, but for failing ones, it's a trap. Has anyone else had chkdsk hose a drive when you were just trying to be careful?
3 comments
Log in to join the discussion
Log In3 Comments
owens.laura11d ago
Isn't it weird how the "right way" to do stuff often makes things worse when everything is already falling apart? That's like how my aunt insists on deep cleaning her kitchen when she's sick, and then she just crashes harder. Sometimes you gotta ditch the rulebook and just wing it when the situation is already broken.
6
abbyf7911d ago
Your aunt deep cleaning while sick is honestly such a perfect example. I think we all have that urge to control something small when everything else is chaos. @miaprice made me think of that chkdsk thing too, it's like the computer giving you one last clear sign before it gives up. Sometimes you just have to accept the mess and focus on what actually matters.
3