yup i can hear something going on
🙂
So no OS Mounting information - or at least not enough for OS X to mount it... but you can see the device manufacturer number and etc.? This my imply that part of the damaged area is the servo information data / UBS / MFT / ETC..
yup i can see the drive number and even the partition but there is no information on the size of the partition (can see the overall size of the drive). thats why i tried the recovery thing, hoping that it would eventually pass over the damaged parts.
Sometimes using "MacDrive" on a PC will allow you to mount it with the error and then you can recover the data anyway. 😉 OS X is too picky in lots of cases. If the entire self-check doesn't complete it won't mount the drive. Part of the self-check is reading the drives' System Area and if one of the UBA's is the located where the platter was scratched... No mounty-mounty. Same I think for the partition tables slash MFT too. 🙁 If that's case you won't be able to use it at all after this recovery process. I mean as a normal drive again.
excellent! i have MacDrive, i will try it the minute after this post is sent!!
LUCKILY it didnt finish going what i percieved to be the damaged area (it was at about 200mb when i stopped it). so i am hoping that this means it hasnt damaged any further areas
🙂
At this point I think I would stop it immediately. I would look inside at the platters. And then if not wasted in the areas it's been scanning in until now, I would find a utility that will reverse scan. It's probably already too late tho. If the head moved across the scratched area then usually that damages the head.
as i said above, this utility didnt go past where the damaged heads were, but SpinRite did, so that could of been my mistake.
Damaged head means you need to replace the heads if you're serious about the recovery.
🙂 Additionally the software you're using may be moving a head (damaged enough to scratch a platter further) into an undamaged area potentially damaging it - by trying to read it. This was in Wotan31's post for me when he said:
"Unfortunately, by using this consumer-grade recovery software, it likely eliminates the possibility for a pro to recover the data now. I.e. this kind of software usually does more harm than good."
hmmm replacing the heads could be possible, i have an identical drive - but its my main windows OS/hack drive. dont know if im willing to risk it haha!
x2 that's for sure!!
I know if it was my data, I'd gladly pay the pro's to work their magic. I have 10 years worth of emails, business documents, school projects, vacation photos, home videos, financial records, etc. on my laptop. Stuff that can never be reproduced once it's lost. Plus dozens (hundreds?) of man-hours spent ripping my large CD collection into Apple Lossless format.
My data is easily worth $2500 (to me). But that's why I keep multiple off-site backups that I rotate monthly. Yeah... I'm a little paranoid. 😀
yea ok that is a tad paranoid
😛 im still trying to get my head over the fact that she dropped the HD when it was her only means of data.. idiot
Listen to Tesselator's advice.
I just read the Spin Rite web site, and that is really, really, REALLY the wrong tool for the job here. You've likely buggered up the drive permanently by using Spin Rite. 😱 Seriously. 😱 😱 😱
yup i figured that when Tess said that. ****
Spin Rite doesn't care about your filesystem type, because spin rite is not a data recovery tool! Spin Rite does one thing, and one thing only: bad block relocation.
yup thats why i knew it would work when i scanned it.
What is Bad Block Relocation? Spin Rite attempts to read the bad blocks on your hard drive, relocate that data elsewhere on the drive, then mark those blocks as "unusable" so the drive won't attempt to use them again. That's fine and well - unless you're dealing with a physically damaged drive.
This drive has been dropped. I.e. it is physically damaged. As Tesselator said, Using Spin Rite to forcefully try and access the damaged area will most likely bollocks this drive up even more.
i 100% understand the implications of this here...
however, i have one tiny thing up my sleve that i think may save me.
i started the major scan of the WHOLE drive from AFTER the damaged part on the drive!!! (started the scan from 1%, when i used SpinRite it would always slow down at around 0.419%). do you think this may save me??
There's no way to know the extent of the damage without physically opening the drive and inspecting it - something neither you, nor I are qualified to do. Therefore, there are three possible scenarios; one or more damaged heads, one or more damaged platters, or both.
- A damaged drive head accessing a good platter area can damage the platter.
- A good drive head accessing a damaged platter area can damage the head.
hmmmmm.... in no way am i qualified.. but its tempting. i wont open it but.
Either way you are only causing more damage by using Spin Rite. It is absolutely the wrong tool for the job.
like i said i only ran it once the whole way through - skipping the damaged part in that scan.
Your only chance for success here is to use a data recovery tool. NOT a bad block relocating tool. A data recovery tool is filesystem-specific I.e. it must be compatible with the filesystem type you are trying to recover. It will try to read all files from the disk EXCEPT the bad areas. It is the exact opposite of what Spin Rite does. But now it's likely too late...
see im not sure if it is too late, i stopped the "recovery backup" from Mac Data Rescue II because you all told me to stop immediately haha!! i will try mounting the drive on a PC and see where that gets me.
if that does not (which i am fairly certain it wont). what recovery software is recommended?? all i really need is software that lets me choose where to start the recovery from, because there are no problems reading after the damaged areas are passed..
thanks so much!
Use the
dd command (Google it) to clone to drive (and use the noerror option.) Try running the recovery software on the clone.
Also, try Testdisk/Photorec for recovery.
EDIT:
Command is:
Code:
sudo dd bs=512 if=/dev/damageddisk of=dmgfilehere conv=noerror,sync
excellent thankyou! this could possibly damage the disk further though because it would read over the bad part and then continue to read over the good part?? (see above)
You may need to first unmount the damaged disk, but leave it connected, and have the disk image unmounted.
it doesnt mount anyway, so theres a plus
😛
ok:: MacDrive cannot mount the drive, it says there was an error during the installation process of the drivers :\
i noticed in Data Rescue is says this:
Code:
Name: Unknown, Bus: USB, Dev: /dev/rdisk1s2, Size: 465.4 GB, [B]Start: 0[/B]
i wonder if i can change the start position :\