Corrupted imgc image

[samuelrh]

Hi all,

I hope someone will be able to help with that. I have a fairly large (2TB) .imgc image created with HDD Raw Copy Tool. I was hoping to uncompress it to a raw image in order to recover some data - but whenever I try to open it, HDD Raw Copy Tools tells me "Selected file cannot be open; it is either damaged or inaccessible."

Since I can open other images from the same location without any issue, I do believe that the image is corrupted.

Question is: can I force it to open? Is there any other software that will allow me to convert it to a usable (even if corrupted) raw image?

Thanks!

[olinyer]

have you try to clean it to make sure it does not have a virus? just making sure it does not have a virus bothering you on this.

[HaQue]

does 7-zip extract those? you might get a lot from it if it does, apart from the corrupted bit.

[samuelrh]

does 7-zip extract those? you might get a lot from it if it does, apart from the corrupted bit.

Unfortunately I wasn't able to extract it with any common compression software, 7zip included.

[samuelrh]

have you try to clean it to make sure it does not have a virus? just making sure it does not have a virus bothering you on this.

What ?

My thoughts exactly. Didn't know what to reply, frankly.

[HaQue]

It isn't that silly at all. I have an image from an Edu institution, a so called gold image for workstations that was built and somehow a virus got into it at an early stage. I wanted to extract some configs and data from it and was stopped by AV, the extraction software gave errors about not being able to find the file IIRC.

[samuelrh]

It isn't that silly at all. I have an image from an Edu institution, a so called gold image for workstations that was built and somehow a virus got into it at an early stage. I wanted to extract some configs and data from it and was stopped by AV, the extraction software gave errors about not being able to find the file IIRC.

Good point. However, that's (unfortunately) not the case. Something apparently went wrong when creating the image (and I should have tested it right away!)