even if I gave you the description of the 2066 error, it would mean very little to you. I have been dealing with Mac's for over 20 years.
#Try diskwarrior 5 before you buy Pc
If it a drive that was / is from an external enclosure then you could still use the enclosure and just place a new hard drive in there.Īnother way to test it it to remove it from the enclosure and connect it directly to a PC with a suitable interface eg. This is very old fashioned advice and meant for very old types of drives that used to get very hot.
If you are advised to place it in a freezer or anything similar then that is up to youīut my advise would be to run from the person who may give this advise. In which case you could sent it to a data recovery specialist but this is usually VERY expensive. There is no known cure unless the data is mission critical Most common causes are that the drive unit was dropped or mishandled or just plain old age Make sure you only user the power supply that CAME WITH IT. Make sure you use ONLY the cable that came with it or a SHORTER one. The noise you can hear is usually known as "the click of death" when referring to hard drives. If you can hear clicking then I am afraid there is a serious problem with the hard drive. SOURCE: My LaCie 500GB Quadra spins and clicks. The disk activity stops, and you can then run DiskWarrior. To kill it, type kill followed by the second number from the left, in this case: kill 67332 So opened Terminal and typed: ps -ef ' grep fsck_hfs and there was the culprit:Ġ 67332 18 0 6:26am ? 1:02.06 /System/Library/Filesystems/hfs.fs/Contents/Resources/././././././sbin/fsck_hfs -y /dev/disk5s2
#Try diskwarrior 5 before you buy full
Unfortunately that takes HOURS on this large volume full of time machine backups. I suspected that TimeMachine or something else on the mac is trying to fsck the file system in preparation for mounting. My disk isn't dead, it just has a sick filesystem, as proven by the fact that if I wait long enough, DiskWarrior can try to do something with it. Scratched my head over this for a while, so figured I would post the solution in case anyone has the same problem.Īll the forum posts are about dead disks. If I wait several hours until the DROBO is quiet, then DiskWarrior doesn't get the error, and I can try to recover it. When I connect the DROBO and try to run DiskWarrior, I get an error -36 "hardware failure". I have a DROBO which I am trying to recover with DiskWarrior.
0 kommentar(er)
