Bad blocks question - 11/13/14 08:29 AM
My daughter took her MacBook to the Genius Bar, Apple's diagnostic tool immediately spit out an I/O error, and the Genius sold her a Seagate external (best for cross-platform use, he said) and assisted her in saving her (un-backed-up ) data. (It didn't occur to him to advise her to back up ~/Library. )
Unfortunately, she was unable to save all her data, because numerous good files lived in folders that also housed bad files, and once the Genius's software choked on the first bad file in a folder she was reduced to dealing with the rest of its contents with drag & drop...one file at a time to avoid choking on bad ones that weren't absolutely necessary, and she just plain ran out of time, because the store was closing.
So, my question is this: Since Apple hasn't got one, I assume that it's impossible to develop a cloning program that can detect a bad block, leapfrog past the file in which it resides, and keep chugging away until it detects the next bad block..., and I'm wondering why not?
Thanks.
Unfortunately, she was unable to save all her data, because numerous good files lived in folders that also housed bad files, and once the Genius's software choked on the first bad file in a folder she was reduced to dealing with the rest of its contents with drag & drop...one file at a time to avoid choking on bad ones that weren't absolutely necessary, and she just plain ran out of time, because the store was closing.
So, my question is this: Since Apple hasn't got one, I assume that it's impossible to develop a cloning program that can detect a bad block, leapfrog past the file in which it resides, and keep chugging away until it detects the next bad block..., and I'm wondering why not?
Thanks.