On Thu, Mar 26, 2009 at 9:39 AM, Daniel Rodriguez <[email protected]> wrote:
> When the server was up and running an
> admin would do image backups to a Linux box. These images are in
> <filename>.iso.
Hmmm. That seems weird. Usually an <.iso> extension signifies an
ISO-9660 filesystem image. ISO-9660 can't be used to contain a true
hard disk image (block level). Even as a filesystem, ISO-9660 can't
maintain NTFS ownership or permission. I wonder if it's actually some
other format with a misleading name.
Here's what I would do: Find or make a working Linux system. (I'm
not sure if a "live CD" will do for this; they often omit things like
the "file" command.) Run the "file" command against these <.iso>
files. For example:
file C_drive.iso
The "file" command looks at file contents to determine type; it
doesn't use the file name ir extension.
I might try loopback mounting the file on Linux:
mount -o loop C_drive.iso /mnt/tmp
I'd check the end of the kernel message log after the above, to see
if that provided useful clues:
dmesg | tail
I haven't used G4L myself, but I seem to recall it's just a
front-end to partimage or ntfsclone or something. Once we figure out
what these files are, I can give you commands to examine the contents.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
