TeraByte Unlimited

tbiview gives an error when opening an image created from a raid1 drive. The imaging software successfully validates the image created.

Can you tell us the nature of the error? Which TeraByte app created the image?

image for windows - imagew64.exe, not sure of the exact version since I upgraded it yesterday in hopes of the tbiviewer working.

http://www.terabyteunlimited.com/kb/article.php?id=581

You also need to be specific as to what message the program is giving you
and what version it shows.

"austin-mtnbiker" wrote in message news:10466@public.image...

image for windows - imagew64.exe, not sure of the exact version since I
upgraded it yesterday in hopes of the tbiviewer working.

error msg: "Unable to mount the image. Common reasons: dirty file system, incorrect partition file system, identifier, unsupported file system, or and error occurred.

[attachment=0]tbiviewer_error.PNG[/attachment]

tbiviewer - v4.36.2

That gives the reason, either dirty file system incorrect FS id, unsupported
file system, or error occurred trying to open or read the data.

what file system type is it? what does it show in the list?


"austin-mtnbiker" wrote in message news:10472@public.image...

error msg: "Unable to mount the image. Common reasons: dirty file system,
incorrect partition file system, identifier, unsupported file system, or and
error occurred.
tbiviewer - v4.36.2

[attachment=0]tbiviewer_2.PNG[/attachment]
[attachment=1]tbiviewer_1.PNG[/attachment]

The file system is NTFS. Not sure which list you are referring to? The windows file explorer shows it as a Terabyte Image File. tbiviewer opens it to a point, see attached image, but when selecting the partition with the data it gives the error msg. A similar popup appears when opening the backup of the windows partition but it opens as expected (I mention this to say that the NTFS file type is not the issue). This issue seems somehow to be related to the fact that it is a raid1 configured drive that is being backed up.

The proprietary Dynamic Drives (OS RAID) are not support. You should do
away with them and use firmware (software BIOS) or hardware based RAID to
maintain compatible with everything and better handling on failures.

"austin-mtnbiker" wrote in message news:10483@public.image...
The file system is NTFS. Not sure which list you are referring to? The
windows file explorer shows it as a Terabyte Image File. tbiviewer opens it
to a point, see attached image, but when selecting the partition with the
data it gives the error msg. A similar popup appears when opening the
backup of the windows partition but it opens as expected (I mention this to
say that the NTFS file type is not the issue). This issue seems somehow to
be related to the fact that it is a raid1 configured drive that is being
backed up.

so, the real question is since image for windows validates the file even though the tbiviewer won't open it, can I really use it to restore in case of catastrophic failure? Moreover, when you say proprietary raid system - are you suggesting that I should have used raid0 or raid5? The raid is implemented via the AMD drivers that came with the mb. It is an AMD processor.

It's backed up everything within those areas. From what I recall they were
supposed to move the metadata that was out at the end of the drive into
partitioned areas (MSR, but maybe they decided on using a special metadata
partition). Anyway, it would restore what was within whatever was backed up
(those partitions), but it's not going to handle any metadata fix up (if
needed) to link multiple (different/new) drives. In general, dynamic drives
are not supported but I can add a note to check that with GPT to see if they
now have what is needed within the GPT partitions to get a single drive
back.

It's possible you set that up but then ended up setting up dynamic drives by
mistake? If you look in drive management, do you have what looks like a
single drive (firmware/hardware RAID) or do you see both drives with the
various partitions (OS RAID)?


"austin-mtnbiker" wrote in message news:10490@public.image...

so, the real question is since image for windows validates the file even
though the tbiviewer won't open it, can I really use it to restore in case
of catastrophic failure? Moreover, when you say proprietary raid system -
are you suggesting that I should have used raid0 or raid5? The raid is
implemented via the AMD drivers that came with the mb. It is an AMD
processor.