TBIView and TBIMount errors processing image

User discussion and information resource forum for Image products.

TBIView and TBIMount errors processing image

Postby Bob Coleman » Thu Sep 15, 2016 5:53 pm

I typically create an image of four partitions, two primaries and two volumes, (single image) on Sunday and then a chain of incrementals approximately daily throughout the week (currently using V3).

Today I discovered that any attempt to mount one of the four partitions with TBIView in the incremental created either today or yesterday produces:

Location is not available
V:\ is not accessible.
The media is write protected.

There is no obvious error from TBIView, but some folders which should contain files appear empty in the view.

There is no problem processing Tuesday's image.

The image seems to restore OK, so the problem appears to be in TBIMount and TBIView.
Bob Coleman
 
Posts: 403
Joined: Fri Aug 12, 2011 10:58 am

Re: TBIView and TBIMount errors processing image

Postby TeraByte Support » Thu Sep 15, 2016 11:47 pm

probably in a dirty state. You'd have to mount with emulated writes
enabled.

"Bob Coleman" wrote in message news:12534@public.image...

I typically create an image of four partitions, two primaries and two
volumes, (single image) on Sunday and then a chain of incrementals
approximately daily throughout the week (currently using V3).

Today I discovered that any attempt to mount one of the four partitions with
TBIView in the incremental created either today or yesterday produces:

Location is not available
V:\ is not accessible.
The media is write protected.

There is no obvious error from TBIView, but some folders which should
contain files appear empty in the view.

There is no problem processing Tuesday's image.

The image seems to restore OK, so the problem appears to be in TBIMount and
TBIView.

TeraByte Support
 
Posts: 2313
Joined: Thu May 05, 2011 3:37 pm

Re: TBIView and TBIMount errors processing image

Postby Bob Coleman » Fri Sep 16, 2016 1:51 pm

TeraByte Support wrote:
> probably in a dirty state. You'd have to mount with emulated writes
> enabled.

I have no idea what that means, but since:

1. As far as I know, this is the first time this has happened.
2. Subsequent incrementals based on the "bad" ones mount OK.
3. Even the "bad" ones restore OK.

I'm going to forget about this.
Bob Coleman
 
Posts: 403
Joined: Fri Aug 12, 2011 10:58 am


Return to Image for DOS/Linux/Windows