Disk Warrior 4.1.1 error analyzing external hard drive

Question

Level 10

82,941 points

Disk Warrior 4.1.1 error analyzing external hard drive

Any idea what an error message#2351, -36 means from Disk Warrior while analyzing an external hard drive? I've also submitted a question to Alsoft. I have a Disk Warrior 4.1.1 booting 10.4.8 analyzing an external dual drive DvBox box via Firewire. Only one of the drives thus far has experienced this error, preventing the directory from rebuilding. Occasionally drives mounted in the Finder under 10.5.5 on my Intel Core2Duo Mac have dismounted themselves on their own. Is this an issue with the drive, the DvBox's or the machine's firmware, or something else?

An Apple user since 1981, Mac OS X (10.5.5)

Posted on Apr 11, 2009 5:28 PM

Reply

Answer 1

Kappy

Level 10

361,741 points

Apr 11, 2009 5:54 PM in response to a brody

If it's a standard Apple -36 error then it usually means something corrupted such as a file, although I'm not sure what that might mean in the context of using DW for its normal directory repair. It may have significance if you were using it to scan files. I have no idea what a DvBox is, so I don't know if it means anything with relation to that.

In the past were DW unable to repair a directory for any reason, then I would just erase the drive in question. Always seemed easier than trying to fool with it.

Reply

Answer 2

a brody Author

Level 10

82,941 points

Apr 11, 2009 5:57 PM in response to Kappy

Fortunately, this drive was not erased. It simply stopped scanning and said it couldn't go further.
The DvBox is a dual hard drive Firewire 400/800 USB hard drive case with internal SATA support on a single power supply.

Reply

Answer 3

BDAqua

Level 10

239,177 points

Apr 11, 2009 5:59 PM in response to a brody

Alsoft is pretty good at getting back to you ime.

I'm thinking it's the notorious -36 = ioErr I/O error (bummers), but I'm sure Alsoft has more on the #2351 though.

If the -36 is what I guess, it's most often the Drive, then FW interface, then cable, then SW.

Reply

Answer 4

a brody Author

Level 10

82,941 points

Apr 13, 2009 8:24 AM in response to a brody

It seems the cable might have been a wee bit loose inside the machine for the SATA. Once I disconnected and reconnected the SATA and ran the test again, it was happy with the drive. Let's hope it remains that way!

Reply