danmc00 did you ever get anything back using DiskWarrior?
I'm on 22,627 and still grinding.
Yes new (1 week old) Hitachi 3TB enterprise (HUA723030ALA640) may be dead ... (I don't need warnings or to told I should have backup!).
but I wouldn't be trying to salvage something is it wasn't irreplaceable.
Beyond a specialist company, anyone have any ideas for recovery?
Diskwarrior has been running for several days uninterrupted. Huge numbers of console logs in the form:
12/6/1 5:29:34 PM [0x0-0x51051].com.alsoft.diskwarrior[570] DiskWarrior App: disk3s2: Read I/O error for block range 224049 to 224049
Oddly, this disk is in 2 partitions. The other partition runs OK, hence I am hoping the media itself is actually OK.
BTW Alsoft say: ---------------------------
The message "speed reduced by disk malfunction" means there is a problem reading data from the disk due to a disk malfunction.
As long as the mouse cursor still moves during step 5, then the computer did not hang or freeze. DiskWarrior is still working on reading the directory of the disk.
Such slowdowns are usually the result of having bad blocks on the media. DiskWarrior is having trouble reading data from the locations on disk where the directory structures are stored.
You will also notice that an error count is kept at the end of the message. This feedback allows you to see that DiskWarrior is still working on reading data from the drive.
NOTE: This count does not increase at a regualr interval as disk errors are not distributed evenly across a drive.
Please let DiskWarrior run for as long as it takes. This can take quite a few hours but should eventually complete. On rare occasions, it might even be necessary to run this for a day or two.