TBI Mount - "theres a problem with this drive"

[ZebC]

Hello,

While using TBIMount to mount drive images (Windows 10, IFW 3.61), Windows throws a popup "there's a problem with this drive" and at the same time in the Event Viewer appears Event ID 4:

File System Filter 'wcifs' (Version 10.0, ‎2102‎-‎01‎-‎13T07:06:12.000000000Z) failed to attach to volume '\Device\TBIMount\TBI0'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.

For some reason, error popup only when mount differential part of image (_diff.tbi one) but when mounting base one (.tbi), error doesn't appear. Is this something to worry about?

[TeraByte Support]

validate the diff one which validates as would be a restore.

[ZebC]

Validate went OK.

[TeraByte Support]

you can try mounting with tbihd or use tbiview.

[ZebC]

I can mount image without problem. There is no "visible" problem with images, I can access files as well. Everything seems fine. Just this strange error shows up when mounting .diff images. I just wonder what this is about, because every error about backup integrity is a bit worrying.

[TeraByte Support]

looks like it's just saying it's dirty.

[ZebC]

Well... Dirty... Anyway, but image is "dirty" (whatever that means) only when mounting .dff part of backup. And I don't remember if that behavior occurred earlier. So... is there a problem or there is not (worth overthinking about it, i.e bother official support...)?

[TeraByte Support(PP)]

The differential backup was taken at a different time than the base full image. It could certainly be dirty while the base isn't. If you created another differential backup, its dirty state would depend on the current file system state (not on any previous differential).

If you mount the backup with write access using TBIHD you can run "chkdsk /f" on it and see if any repairs are done and what they are.

If you're concerned about it, run "chkdsk /f" on the partition(s) prior to the next backup so they should be in a clean state. Windows will often clean things up automatically if it detects something but sometimes manual checks are needed.

[ZebC]

Thanks for detail information.

Check disk throws this:

Cleaning up instance tags for file 0x958b.
Cleaning up instance tags for file 0xf55f.
Cleaning up instance tags for file 0xfa72.
Cleaning up instance tags for file 0x100d8.
Cleaning up instance tags for file 0x186e4.

CHKDSK is verifying Usn Journal...
The remaining USN block at offset 0x1642cd2000 in file 0x12f2b is
less than a page.

BTW, what chances are that all .diff throws that error while all base don't? Also, there's an event error ID 4 - "failed to attach to volume '\Device\TBIMount\TBI0", only for .diff images.

[TeraByte Support]

Don't see anything to worry about, although if you used vss it may be cleaner