Hi,
This drive is detected by BIOS, but very slow. Once computer boots, DMDE/Find and Mount will see it, and I was able to start imaging it.

Imaging was VERY slow, started last night at 11pm and stopped it today at 6pm for a total of 16GB of the image copied.. would have taken 62 days at that rate.

Terminal shows only:


Doesn't make any nasty sounds.

This drive was replaced by Dell under warranty. Owner needs to send it back probably tomorrow, or if I can do anything, maybe stall a smidge, but they aren't going to do any pro DR. I only wanted to take a look as it isn't the standard bell ringing for lunch sound, and it belongs to a colleague in Edu sector.

Can anyone suggest anything I might be able to try?

Thanks in advance

speed is same in reverse imaging as well ?

_________________
RAID/Server Recovery

cant get into terminal to do so. Remember Spildit, Im not a HDD Guy, so what you said is like telling someone when the car doesn't start to go check the engine

I can work out how to stop reallocation from whats already posted on the forums I reckon.

edit: you wouldn't believe it, after posting I thought I would check terminal again and now get F3 prompt. doh!

Background processes. Need to edit SA.

ok, so just let them return it to dell them?

I disabled realloc and it started to image quickly, first 2 partitions were fine, but at LBA 23,804,065 got CRC error, and would not copy any data. Of course this is basically where the user 988GB Partition is. I guess that's that.
Thanks guys, pity I couldn't have given it to a pro, may not have been a hard one.

what about reverse imaging as chinopk mentioned above ?

Reverse imaging just had CRC error straight away.

From memory there is a 40 odd MB partition, a 12GB and the 988GB. seems the first 2 image ok, though I don't know why the CRC errors would be divided by partition.

988gb encrypted partition or protected

Interesting thought. I know the users wouldn't know anything about encryption, and this was out of a regular desktop. I am sure these are regular users running windows. I am not sure what encryption could be here, no evidence of it.