Log in

No account? Create an account
IBNeko's Journal-Nyo~!
Hard drive death...
Looks like most of the data in my bittorrent download's folder is corrupted or gone - thank goodness for Retrospect's ability to skip over unreadable files - I kinda wish it would be able to replace bad blocks with zeros / nulls, but I don't think it does that, being 'backup' software, as opposed to data copying stuff, like dd. Unfortunately, dd takes way too long - I ran it pretty much all day yesterday, and it was only able to get up to 15.3GB before it started stalling really badly.

At current count, there's about 200 files that are messed up due to "i/o error, bad media?", error -36.

Boo. I wonder if their new motion sensing hard drive protection system would have saved me.

Or maybe the hard drive was already corrupted, but I just didn't know until now.

17 GB remaining, 35.3 GB done. 473793 files copied, with 146295 files remaining. 9:30 elapsed. Near 320 files lost, most being downloaded and replacable mp3s, some text files (as we enter the Documents/ folder...)

Lost some of the past schoolwork archived files as well. Nothing vital, as far as I can tell.

Oh, and I lost the Binary Universe CD rar file. Porsupah, you may have to download that on your own. It's on aMule.. I think you can get to it. Lost the Hooked on Classics rar file as well. That may be slightly more irritating.. I'm sure I can find that again though. Hopefully.

::sighs:: I would swear I have backups somewhere, done over the summer, but I don't remember where. Probably at home... Urrr. I hope I don't have to send the system in to get the hard drive replaced.

Tags: , ,

3 happy kittens | Leave catnip
porsupah From: porsupah Date: September 2nd, 2006 11:29 pm (UTC) (Link)
I might be misremembering, but I think I used ditto to perform the mass copying - if it came across a bad file, it just reported the error and carried on with the rest.

No, the motion sensor probably wouldn't have helped - that's only to prevent damage to the disk surface if it would've otherwise caused a head crash. Apparently, some new drives are prone to a little flaking of the surface, but that gets mapped out by the controller - it's only more egregious circumstances which we actually notice, whether through (perhaps) static zapping, bad manufacture, or gremlins.
ibneko From: ibneko Date: September 3rd, 2006 02:56 am (UTC) (Link)
Hmm, ditto. I'm using Retrospect right now. But what I need is something that'll report the error, but fill in that part of the file with NULLs. Then I could easily run BitTorrent to fix the broken segments instead of redownloading again.

I think this might have been damage to the disk surface though - All of these files were fine, and the iBook did slip off my desktop (which is on the floor) and land on an uneven pile of books and stuff with a nasty sounding thud. And I was downloading multiple files at the time, so the disk was definitely spinning. The wikipedia article on head crashes sound scary and bad - that would explain the seemingly increasing number of problems...: "Following a head crash, particles of material scraped free of the drive surface greatly increase the chances of further head crashes or damage to the platters." XP
porsupah From: porsupah Date: September 3rd, 2006 03:45 am (UTC) (Link)
But wouldn't an impact that actually resulted in head contact with a platter surface be essentially terminal for the drive? I may try contacting some recovery lab to see what they make of that entry: is it possible for a drive to have a near miss, as it were?

It's a pity TTP offers nothing more at the end of its scan than a total number of errors - a graphical representation of the distribution of errors would be handy for satisfying geeky curiosity. Some kind of head impact would seem likely to have a skid-like block of errors in proximity, whereas manufacture flaking would seem more likely to be fairly random.
3 happy kittens | Leave catnip