Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

DiskWarrior error codes

Hello,

I'm trying to repair a hard disk for a friend. It won't mount and disk utility can't repair it. Data Rescue says it can't find any file (even in the extensive search). At mount-time, the disk spins and makes the usual noises; when tools try to read to it, no noise happens. The disk is clearly dead (up to some point).


In a last resort (my friend needs the data), I've tried with DiskWarrior. The first time, it ran for 2 days, showing this message: "Speed reduced by disk malfunction: 10'215" (of course, the number was growing). Because I needed to log in another user, I finally aborted this attempt. In further attempts, DiskWarrior won't let me rebuild the disk. When I select it, it says "directory cannot be rebuilt due to disk hardware failure (-36,2738)". My last hope is to discover what 2738 means (I guess -36 is the well-known Mac OS error code for read/write error).

Using Google, I've seen similar messages, sometimes with a different error code (2747 or 2756), but no one seems to be able to actually tell the difference between these codes, nor anything at all; the only answer at each post is "The hard disk has failed, replace it", which is far from informative.


So I want to discover the meaning of this code, but I have not much experience in how the kernel and disks' firmware work. My current guess is that the error code (2738) is what's being reported by the disk's firmware (I doubt DiskWarrior would map codes into its own table). Please, does someone have knowledge about how this works (or how DiskWarrior gets its error codes)?


(posted in the iMac section because the disk comes from such model; if the discussion extends, it'll be in the correct section).

Mac Pro, Mac OS X (10.6.8)

Posted on Sep 2, 2013 7:43 AM

Reply
Question marked as Best reply

Posted on Sep 2, 2013 7:54 AM

Contact Disk Warrior Support here: Disk Warrior

17 replies

Sep 2, 2013 10:41 AM in response to Linc Davis

The drive has physically failed. Neither DIsk Warrior nor any other software is going to work. The data can only be recovered, if at all, by a specialist such as DriveSavers. Their services are very expensive.

Thanks. I already know that. However, I'm convinced that, knowing the meaning of the error code that DiskWarrior reports, I could figure out the origin of the problem and perhaps try to solve it (is it mechanical or logical? Perhaps the offended chip could also be discovered). Of course, if it's a mechanical failure, I don't have the clean room required.

In general, I'm against the use of error codes that no one can know. We should clearly be allowed to repair things by ourselves, as long as we can understand how they work.

Sep 4, 2013 10:41 AM in response to Anic264b

We use a product named Scannerz to test drives. At this point it won't help you, but if you go to their downloads section and get the book on hard drive troubleshooting I think you'll see why the idea of soldering a chip is not feasible. A a link to thier site is here:


http://www.scsc-online.com


The book is free. Scroll through it until you find the picture of a coin sitting on a circuit card. On the version I have it's on page 9, but they might have updated it since then. What you're looking at is a picure of dime next to a connnector. The connector has 50 pins. The connector is smaller than the dime's diameter!!!


The days of pulling chips off and re-soldering them are long over. To be honest if I took one of my finest point soldering irons I couldn't even get it to make contact with less than 2 of those connections simultaneously. The fine point soldering irons I have would be bridging 2 or more pins at best.


The best you could hope for is a drive controller board failure, in which case you could swap out the controller card. That's easy. Usually they're held on with a few screws and then cables running between the drive controller and the heads/platteres/motors, etc.


The reality is that the odds of it being the controller are rare, and the odds of it being a mechanical failure are high. However at this point you have little or nothing to lose by examining all possibilities.


....leaving me with these parting words: Good Luck.

Sep 4, 2013 11:07 AM in response to Anic264b

Anic264b wrote:


Thanks. I had not considered this obvious solution. On the other hand, I doubt they'll tell me this: it's one step forward to replicate their product.

Ye of little faith!


Allsoft tell me that error code -36,2738 is: directory cannot be rebuilt due to disk hardware failure - file structure is damaged


.

As Disk Warrior cant rebuild your drive, I would try Data Rescue from Prosoft, there is a free trial that can scan to see if there is any data that can be recovered. Prosoft applications are used by Apple Genius Bar and many Authorised Mac service cantres. I have used Data Rescue for many clients with very good results


Data Rescue

Sep 4, 2013 3:01 PM in response to CaptH

CaptH wrote:


The book is free. Scroll through it until you find the picture of a coin sitting on a circuit card. On the version I have it's on page 9, but they might have updated it since then. What you're looking at is a picure of dime next to a connnector. The connector has 50 pins. The connector is smaller than the dime's diameter!!!


The days of pulling chips off and re-soldering them are long over. To be honest if I took one of my finest point soldering irons I couldn't even get it to make contact with less than 2 of those connections simultaneously. The fine point soldering irons I have would be bridging 2 or more pins at best.

Well, you're right, especially for a hard disk.

The reality is that the odds of it being the controller are rare, and the odds of it being a mechanical failure are high. However at this point you have little or nothing to lose by examining all possibilities.


....leaving me with these parting words: Good Luck.

Thank you. Actually, the chances of being a controller failure are likely, because the iMac whose this disk came from has problems with the fans (its owner says they don't run (yes, the three fans) and I have to admit I haven't hear them for the short time I saw the computer (before I opened it)); the computer being hot, this likely explains why the disk has failed (it was not that old) and it may have first defeated the controller.

Sep 4, 2013 3:06 PM in response to Gary Scotland

Gary Scotland wrote:


Ye of little faith!


Allsoft tell me that error code -36,2738 is: directory cannot be rebuilt due to disk hardware failure - file structure is damaged

Thank you very much! And yes, you're right, my faith isn't that big.

As Disk Warrior cant rebuild your drive, I would try Data Rescue from Prosoft, there is a free trial that can scan to see if there is any data that can be recovered. Prosoft applications are used by Apple Genius Bar and many Authorised Mac service cantres. I have used Data Rescue for many clients with very good results


Data Rescue

Thanks, but I already tried it (I tried DiskWarrior, Data Rescue and Tech Tool Pro in the same row, prior to asking in this forum). Data Rescue, which I have already registered years ago, tells me it couldn't find any file (even in the extensive and the analysis test).

Sep 4, 2013 3:32 PM in response to Anic264b

In the meantime, I've another problem related to this (sorry for the extra post, the Edit link is now gone).

We went in a shop to buy a new hard disk. We left the bad disk in the shop, because they proposed us to search for another controller for this disk (so we may hope to repair it if the culprit is the controller). Back to my friend's home, I saw the new disk had one connector less than the old one had; at that moment I realised Apple is now shipping disks with built in thermal sensors (and I knew fans run at full speed when one sensor is missing). I phoned the shop (not a Mac one, they are too far away) and they told me they couldn't figure out where to buy disks with such a connector; however, I must solve this.

I then went in my house and managed to find an old sensor, still attached to a malfunctionning disk from an iMac G5. However, its connector is smaller than in my friend's iMac. I tried to make a bridge, by cutting the old sensor's cable and inserting it in the plug of the new iMac's sensor (I thought they are both sensors, with only a couple of years of difference, so their data should be the same) but it didn't work. The new connector has only two wires and the old one has four; I guess the extra two are for the power (that is built into the hard disk in the new iMac version). Still hoping both sensors are compatible.

Otherwise, how would I solve this problem? May I disassemble the original, failed, hard disk to extract its sensor (wouldn't solve the power problem, though)?

Dec 8, 2013 10:21 PM in response to Anic264b

DiskWarrior stupidly assumes that intermittant disk latency is caused by hardware faults. Self-monitoring RAIDs, NAS, and low power drives have intermittant latency during normal operation. DiskWarrior refuses to work on those volumes even when they're in perfect hardware health. I've contacted Alsoft and they stubbornly assure me that they are correct. They said the work-around is to copy a disk image to a different drive!


The MacOS kernel log (/var/log/kernel.log in 10.6) will say if there are really disk errors happening.

Jan 1, 2014 3:22 PM in response to Anic264b

I've found that fsck is trying to repair in the background. open terminal and type ps -ef | grep fsck_hfs. For the listing that corresponds to your drive try to kill the process. use kill <PID> or sudo kill <PID>. This allowed the drive to mount and i was able to copy off user data.


source: http://servalpaul.blogspot.com/2013/05/diskwarrior-error-36-2747-hardware.html

Apr 1, 2014 10:48 AM in response to Trifster

Thanks! I recived the same errors:


My drive did not mount and repeatedly asked for the passcode to unlock:


1- Diskwarrior error msg:

Directory cannot be rebuilt due to disk hardware failure (-36,2738)


2- Disk utility error msg: Disk Utility can't repair this disk. Back up as many of your files as

possible, reformat the disk, and restore your backed-up files.


Simply killed fsck_hfs taks and now it lets me to read data! 🙂

May 14, 2014 2:28 AM in response to eminz

It worked perfectly for me. Thank you Trifster & eminz.


If you have any of theese errors:

1- Diskwarrior error msg:

Directory cannot be rebuilt due to disk hardware failure (-36,2738)

or

Directory cannot be rebuilt due to disk hardware failure (-36,2747)


2- Disk utility error msg: Disk Utility can't repair this disk. Back up as many of your files as

possible, reformat the disk, and restore your backed-up files.



You should kill "fsck_hfs" task:

1. Go to "Apllications/Utilities/" folder then open "Activity Monitor"

2. Search for: fsck_hfs

3. Double click on it and choose force quit.


Good luck.

DiskWarrior error codes

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.