Image header is corrupted or not accessible (error C0000098)

Started by Ben

Ben

Image header is corrupted or not accessible (error C0000098)   03 August 2019, 04:39

Having this issue: "Image header is corrupted or not accessible (error C0000098)". Can't open a 16GB RAM disk.

I do have a full backup of the .img volume from December 2018, and some part dirs backups from the latest version of it, but it's quite the hassle to not have my most recent one back. Seems to me it's not irreparable, it can be fixed. The data in the new corrupt file is all there, from the looks of it (using hex-editor).
Its size has expanded from 15,6 GB (16.777.224.192 bytes) to 16,7 GB (17.996.717.056 bytes) after a restart of the Win10 PC in question.

Looking inside the newer corrupt version with a hex-editor, I see that both the header and the end of the file are quite different from the working backup.

Can someone at SoftPerfect tell me what to cut out or correct of the larger corrupted file-volume, so that I can perhaps get the most recent version mountable again?

I already tried a few things using HxD64.exe, copy pasting header from the functional backup, cutting out the end to match size etc. but to no avail thus far.
It would open and mount, but then SoftPerfect RAM Disk would ask me to format it before showing me a drive-letter. That's the best I got thus far.

Please shed some light as to where inside the file volume the added rubbish has appeared and can possibly be edited out. I'd very much like to get that newer file uncorrupted again.

TIA
Attachments:
open | download – signal-attachment.jpeg (181.7 KB)
SoftPerfect Support forum - Andrew avatar image

Re: Image header is corrupted or not accessible (error C0000098)   03 August 2019, 20:08

There are two identical 4KB headers: a primary header in the beginning of the file and a backup header in the end of the file.

Try a third-party disk mount utility that supports entering an offset, like OSFMount v2 (see under Downloads/Previous version). You need to enter the offset of 4096 bytes as shown below to the data when mounting the image file. An image file is essentially a 4K header followed by raw disk data.

By the way, do you have CCleaner installed by any chance? We have seen a set of image corruption cases linked to CCleaner software.

SoftPerfect support forum
Ben

Re: Image header is corrupted or not accessible (error C0000098)   04 August 2019, 20:32

Thanks for the pointers, with that and some fiddling with a hex-editor I got some, not all, lost files back simply by treating it as a broken/deleted HDD using testdisk.

Through that I also found out it had been damaged by CoveCube's StableBit DrivePool software, which had overwritten parts of the file system of the RAM disk .img volume. I guess they are using a RAM-based FS for caching purposes etc, and it got messed up somewhere.

It's my own fault too, since I've set StableBit DrivePool to bypass file system filters, which is probably a risky endeavor in conjunction with RAM disk. Although I must say it has been working flawlessly in unison for years now (aside from the Drivepool virtual volume not being able to hold the RAM disk image, for some reason that made the RAM disk occasionally unwritable)

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

  *******   ********  **    **  **     **  ******** 
 **     **     **     ***   **   **   **   **       
 **     **     **     ****  **    ** **    **       
  ********     **     ** ** **     ***     ******   
        **     **     **  ****    ** **    **       
 **     **     **     **   ***   **   **   **       
  *******      **     **    **  **     **  **       

Message: