• 0

Clonezilla - Restore Windows 7 image in a virtual machine


Question

FDtoRA

I captured an image from a Windows 7 computer using clonezilla.  The image is stored on an external usb drive.

 

Within the folder that clonezilla created are files:

sda5.vfat-ptcl-img.gz.aa

sda1.vfat-ptcl-img.gz.aa

sda2.info

sda2.ntfs-ptcl-img.gz.aa

sda3.ntfs-ptcl-img.gz.aa

sda3.ntfs-ptcl-img.gz.ab

sda3.ntfs-ptcl-img.gz.ac

sda3.ntfs-ptcl-img.gz.ad

sda3.ntfs-ptcl-img.gz.ae

sda3.ntfs-ptcl-img.gz.af

sda3.ntfs-ptcl-img.gz.ag

sda3.ntfs-ptcl-img.gz.ah

sda3.ntfs-ptcl-img.gz.ai

sda3.ntfs-ptcl-img.gz.aj

sda3.ntfs-ptcl-img.gz.ak

sda3.ntfs-ptcl-img.gz.al

sda3.ntfs-ptcl-img.gz.am

sda3.ntfs-ptcl-img.gz.an

sda3.ntfs-ptcl-img.gz.ao

sda3.ntfs-ptcl-img.gz.ap

 

I want to browse the files that were stored on the laptop from which the clonezilla image was obtained.  I cannot restore the image to a laptop as I do not have identical hardware of the laptop from which the image was obtained.

 

I would like to mount the image in a virtual machine, but do not know how to do this base don't he information I have read.  The closest I get is that I create a windows 7 vm, somehow boot clonezilla in the vm and then restore the image from the external usb hard drive to the vm.  How do I boot clonezilla in the vm and then get clonezilla to restore the image to the vm?

 

Another option I have heard is that I can mount the clonezilla image in OS X as a Samba share.  If I can mount a clonezilla image as a Samba share, will this allow me to browse the files from the laptop (e.g. docx, xlsx, pptx, bmp, mp3, etc.)?  What steps are required to mount the clonezilla in OS X?

 

A third option (if it is eve possible based on my understanding of reading about restoring clonezilla images) is to create a bootable usb drive with the image on it.  From http://clonezilla.org/fine-print-live-doc.php?path=./clonezilla-live/doc/04_Create_Recovery_Clonezilla/09-select-options-then-create.doc, "If you want to create a recovery USB flash drive, choose to create zip file, then follow the same method as creating USB flash drive version of Clonezilla live to put the created zip file on USB flash drive and make it bootable."   The method for creating a usb flash drive version of clonezilla is to use tuxboot and select the clonezilla iso.  The problem I have with this method is that I already created an iso file of the image using clonezilla, but the iso contained the same img.gz.a* files so it didn't get me to a point where I could boot the iso.  Will the zip file create a bootable usb drive where I can browse the files the image captured, or will it just create a bootable usb drive with clonezilla on it where I can then use clonezilla to restore the image to the internal hard drive?

 

TL;DR I have a clonezilla image of a laptop using windows 7, and I want to be able to browse the files of the laptop that are contained in the clonezilla image.  How can I do this?

 

Thank you for your help.

Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0
+BudMan

I am leaving to get on a plane, but pretty sure you can just mount a clonezilla image and access the files.  For sure in linux you could do this.

Link to post
Share on other sites
  • 0
FDtoRA

Some more info of the contents/files I have as a result of the clonezilla image process.

 

The image was stored in a folder titled "2016-1025-img".  Within this folder are the following files:

blkdev.list

blkid.list

clonezilla-img

dev-fs.list

disk

ecryptfs.info

Info-dmi.txt

Info-lshw.txt

Info-lspci.txt

Info-packages.txt

Info-saved-by-cmd.txt

parts

sdb-chs.sf

sdb-hidden-data-after-mbr

sdb-mbr

sdb-pt.parted

sdb-pt.parted.compact

sdb-pt.sf

sdb1.vfat-ptcl-img.gz.aa

sdb2.info

sdb2.ntfs-ptcl-img.gz.aa

sdb3.ntfs-ptcl-img.gz.aa

sdb3.ntfs-ptcl-img.gz.ab

sdb3.ntfs-ptcl-img.gz.ac

sdb3.ntfs-ptcl-img.gz.ad

sdb3.ntfs-ptcl-img.gz.ae

sdb3.ntfs-ptcl-img.gz.af

sdb3.ntfs-ptcl-img.gz.ag

sdb3.ntfs-ptcl-img.gz.ah

sdb3.ntfs-ptcl-img.gz.ai

 

I opened "sdb3.ntfs-ptcl-img.gz.aa" in 7-zip and extracted the file "sdb3.ntfs-ptcl-img.gz".  When I try to open this file with 7-zip, "Can not open file 'path\sdb3.ntfs-ptcl-img.gz' as archive.

 

I also have an iso file "2016-1025-img.iso" with the following folders

.disk

boot

EFI

home

live

syslinux

utils

[BOOT]

Clonezilla-Live-Version (this is a file)

GPL (this is a file)

 

Within the home folder a couple folders deep is the same contents of the "2016-1025-img" folder described above.  I don't think the will be helpful, but I already have it if it is needed.

 

So from these files, how would I go about mounting the image?  I can mount it in OS X, VirtualBox running  Linux (you tell me what the best distro is for this scenario), or Windows.

 

Link to post
Share on other sites
  • 0
+BudMan

well you would need to put them into 1 file.. so something like

 

cat <imagename>.gz.a* | gzip -d -c | partclone.restore -W -o <output filepath>

 

The you would end up with say file.img

 

Then mount that image.. Do you have partclone installed, if not apt-get install partclone.  Assuming your part was ntfs, so you prob want ntfs-3g as well..

 

user@ubuntu:~$ partclone.restore --help
partclone.restore v0.2.51 http://partclone.org
Usage: partclone.restore [OPTIONS]
    Efficiently clone to a image, device or standard output.

    -o,  --output FILE      Output FILE
    -O   --overwrite FILE   Output FILE, overwriting if exists
    -W   --restore_raw_file create special raw file for loop device
    -s,  --source FILE      Source FILE
    -L,  --logfile FILE     Log FILE
    -dX, --debug=X          Set the debug level to X = [0|1|2]
    -C,  --no_check         Don't check device size and free space
    -N,  --ncurses          Using Ncurses User Interface
    -I,  --ignore_fschk     Ignore filesystem check
    -i,  --ignore_crc       Ignore crc check error
    -F,  --force            Force progress
    -f,  --UI-fresh         Fresh times of progress
    -m,  --max_block_cache  The used block will be cache until max number
    -q,  --quiet                 Disable progress message
    -B,  --no_block_detail  Show progress message without block detail
    -v,  --version          Display partclone version
    -h,  --help             Display this help
user@ubuntu:~$ ntfs-3g -help

ntfs-3g 2013.1.13AR.1 external FUSE 29 - Third Generation NTFS Driver
                Configuration type 7, XATTRS are on, POSIX ACLS are on

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2012 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  http://tuxera.com
user@ubuntu:~$

 

Once you have your image, then could mount it with say

 

ntfs-3g /dir/file.img /mnt/somedir

 

Link to post
Share on other sites
  • 0
FDtoRA

Sorry the delayed response.  I just got around to a working Ubuntu 16.04 system to try this.

 

cat <imagename>.gz.a* | gzip -d -c | partclone.restore -W -o <output filepath>

returns the error "gzip: stdin: not in gzip format"

 

When I type file <imagename>.gz.aa in the terminal I get <imagename>.gz.aa: data

 

I don't understand how the gz.a* files are not in gzip format because when I run Clonezilla and try to restore the image, Clonezilla can restore the image.  My problem is that I don't want to restore the image, but simply browse the files so I can select certain files to copy to a new location.

 

I'm hoping you BudMan or someone else has encountered this issue and knows the fix because I have not been successful in finding this same problem duplicated by someone in all the reading of Clonezilla and Ubuntu forums.

 

Thank you.

Link to post
Share on other sites
  • 0
+BudMan

your not using <imagename> are you??  that is a placeholder for your files are actually called.

 

Your files are called sda3.ntfs-ptcl-img.gz right?  This is the image of your sda3 partition.

Link to post
Share on other sites
  • 0
FDtoRA

I am not using <imagename>.  I was using that to be consistent with your message.

 

What I typed is "cat sdb3.ntfs-ptcl-img.gz.a* | gzip -d -c | partclone.restore -W -o sdb3.img"

I then get the error message that the file is not in gzip format.

Link to post
Share on other sites
  • 0
+BudMan

well if its not in gzip format why does it have gz in its name.. Did you not compress when you did your clone?

 

Do the commands 1 at a time vs piping them..

Link to post
Share on other sites
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Copernic
      Ventoy 1.0.33
      by Razvan Serea



      Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)

      Ventoy features:

      100% open source Simple to use Fast (limited only by the speed of copying iso file) Directly boot from ISO/WIM/IMG/VHD(x)/EFI file, no extraction needed Legacy + UEFI supported in the same way UEFI Secure Boot supported (since 1.0.07+) Persistence supported (since 1.0.11+) MBR and GPT partition style supported (1.0.15+) WIM files boot supported (Legacy + UEFI) (1.0.12+) IMG files boot supported (Legacy + UEFI) (1.0.19+) Auto installation supported (1.0.09+) File injection supported (1.0.16+) ISO files larger than 4GB supported Native boot menu style for Legacy & UEFI Most type of OS supported(Windows/WinPE/Linux/Unix/Vmware/Xen...), 550+ iso files tested Not only boot but also complete installation process ISO files can be listed in List mode/TreeView mode Linux vDisk boot supported (vdi/vhd/raw) "Ventoy Compatible" concept Plugin Framework Menu Alias/Menu Style/Customized Menu supported USB drive write-protected support USB normal use unaffected Data nondestructive during version upgrade No need to update Ventoy when a new distro is released Ventoy 1.0.33 changelog:

      Add support for Keyboard layout F5 Tools ---> Keyboard Layouts Add support for boot Linux vDisk file from other bootloaders. Notes Add persistence support for Kali/CloneZilla Fix a bug when using workaround for Legacy BIOS access limitation in GPT partition style Fix a bug when using Ventoy2Disk.sh -l (PR #703) New iso support (total 600+)

      Clover-5128-X64.iso (UEFI) austrumi64-4.3.5.iso (Legacy + UEFI) slacko64-7.0.iso (Legacy + UEFI) bionicpup32-8.0-uefi.iso (Legacy + UEFI) ldiag_4.37.0_linux.iso (Legacy + UEFI) LinuxRa1n-V3.4_Ultimate.iso (Legacy + UEFI) checkra1n-0.12.1_linux_live.iso (Legacy + UEFI) ubuntu-20.10-live-server-arm64.iso (ARM64 UEFI) ubuntu-20.04.1-live-server-arm64.iso (ARM64 UEFI) ubuntu-18.04.5-server-arm64.iso (ARM64 UEFI) See https://www.ventoy.net/en/doc_news.html for detail.

      Download: Ventoy 1.0.33 | 10.3 MB (Open Source)
      Download: Ventoy Live CD | 40.5 MB
      Link: Ventoy Home Page | Project Page @GitHub

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      Ventoy 1.0.32
      by Razvan Serea



      Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)

      Ventoy features:

      100% open source Simple to use Fast (limited only by the speed of copying iso file) Directly boot from ISO/WIM/IMG/VHD(x)/EFI file, no extraction needed Legacy + UEFI supported in the same way UEFI Secure Boot supported (since 1.0.07+) Persistence supported (since 1.0.11+) MBR and GPT partition style supported (1.0.15+) WIM files boot supported (Legacy + UEFI) (1.0.12+) IMG files boot supported (Legacy + UEFI) (1.0.19+) Auto installation supported (1.0.09+) File injection supported (1.0.16+) ISO files larger than 4GB supported Native boot menu style for Legacy & UEFI Most type of OS supported(Windows/WinPE/Linux/Unix/Vmware/Xen...), 550+ iso files tested Not only boot but also complete installation process ISO files can be listed in List mode/TreeView mode Linux vDisk boot supported (vdi/vhd/raw) "Ventoy Compatible" concept Plugin Framework Menu Alias/Menu Style/Customized Menu supported USB drive write-protected support USB normal use unaffected Data nondestructive during version upgrade No need to update Ventoy when a new distro is released Ventoy 1.0.32 changelog:



      Linux vhd/vdi/raw file now is bootable in both Legacy BIOS mode and UEFI mode. Notes vtoyboot-1.0.7 release. Notes Add support for DragonFly BSD distro Fix a bug when booting wifislax64-2.1-final.iso New iso support (total 600+)

      MX-18.3_386.iso (Legacy) MX-18.3_x64.iso (Legacy + UEFI) bitdefender.iso (Legacy + UEFI) dfly-x86_64-5.8.3_REL.iso (Legacy + UEFI) dfly-x86_64-5.8.2_REL.iso (Legacy + UEFI) dfly-x86_64-5.8.1_REL.iso (Legacy + UEFI) dfly-x86_64-5.8.0_REL.iso (Legacy + UEFI) dfly-x86_64-5.6.3_REL.iso (Legacy + UEFI) dfly-x86_64-5.6.0_REL.iso (Legacy + UEFI) dfly-x86_64-5.4.3_REL.iso (Legacy + UEFI) dfly-x86_64-5.4.0_REL.iso (Legacy + UEFI) dfly-x86_64-5.2.2_REL.iso (Legacy + UEFI) dfly-x86_64-5.0.2_REL.iso (Legacy + UEFI) dfly-x86_64-5.0.0_REL.iso (Legacy + UEFI) See https://www.ventoy.net/en/doc_news.html for detail.

      Download: Ventoy 1.0.32 | 10.5 MB (Open Source)
      Download: Ventoy Live CD | 40.8 MB
      Link: Ventoy Home Page | Project Page @GitHub

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      Ventoy 1.0.31
      by Razvan Serea



      Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)

      Ventoy features:

      100% open source Simple to use Fast (limited only by the speed of copying iso file) Directly boot from ISO/WIM/IMG/VHD(x)/EFI file, no extraction needed Legacy + UEFI supported in the same way UEFI Secure Boot supported (since 1.0.07+) Persistence supported (since 1.0.11+) MBR and GPT partition style supported (1.0.15+) WIM files boot supported (Legacy + UEFI) (1.0.12+) IMG files boot supported (Legacy + UEFI) (1.0.19+) Auto installation supported (1.0.09+) File injection supported (1.0.16+) ISO files larger than 4GB supported Native boot menu style for Legacy & UEFI Most type of OS supported(Windows/WinPE/Linux/Unix/Vmware/Xen...), 550+ iso files tested Not only boot but also complete installation process ISO files can be listed in List mode/TreeView mode Linux vDisk boot supported (vdi/vhd/raw) "Ventoy Compatible" concept Plugin Framework Menu Alias/Menu Style/Customized Menu supported USB drive write-protected support USB normal use unaffected Data nondestructive during version upgrade No need to update Ventoy when a new distro is released Ventoy 1.0.31 changelog:

      Fix a bug in Ventoy2Disk.exe for 2TB+ disk Fix a bug when use workaround for Legacy BIOS access limitation. Fix a bug about source media missing when boot rhel 8.3/CentOS 8.3 Rebuild some x86_64 binraries with musl-libc to avoid virus false positive. (issue #660) Change default label from ventoy to Ventoy in Ventoy2Disk.sh (PR #656) New iso support (total 580+)

      blackarch-linux-full-2020.12.01-x86_64.iso (Legacy + UEFI) anarchy-1.3.1-x86_64.iso (Legacy + UEFI) austrumi64-4.3.3.iso (Legacy + UEFI) austrumi-3.4.7.iso (Legacy)

      See https://www.ventoy.net/en/doc_news.html for detail.

      Notes:

      The install program Ventoy2Disk.exe has not been updated for some releases. It seems that it has been added to the whitelist of anti-virus software vendors. But Ventoy2Disk.exe is updated in this release, so there may be some false positives again.

      Download: Ventoy 1.0.31 | 10.2 MB (Open Source)
      Download: Ventoy Live CD | 40.5 MB
      Link: Ventoy Home Page | Project Page @GitHub

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      Ventoy 1.0.30
      by Razvan Serea



      Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)

      Ventoy features:

      100% open source Simple to use Fast (limited only by the speed of copying iso file) Directly boot from ISO/WIM/IMG/VHD(x)/EFI file, no extraction needed Legacy + UEFI supported in the same way UEFI Secure Boot supported (since 1.0.07+) Persistence supported (since 1.0.11+) MBR and GPT partition style supported (1.0.15+) WIM files boot supported (Legacy + UEFI) (1.0.12+) IMG files boot supported (Legacy + UEFI) (1.0.19+) Auto installation supported (1.0.09+) File injection supported (1.0.16+) ISO files larger than 4GB supported Native boot menu style for Legacy & UEFI Most type of OS supported(Windows/WinPE/Linux/Unix/Vmware/Xen...), 550+ iso files tested Not only boot but also complete installation process ISO files can be listed in List mode/TreeView mode Linux vDisk boot supported (vdi/vhd/raw) "Ventoy Compatible" concept Plugin Framework Menu Alias/Menu Style/Customized Menu supported USB drive write-protected support USB normal use unaffected Data nondestructive during version upgrade No need to update Ventoy when a new distro is released Changelog:

      Add experimental support for IA32 UEFI (ia32-efi). Notes Add experimental support for ARM64 UEFI (aarch64-efi). Notes Expand dual mode option to multi-mode option. Notes Add a simple Password plugin. Notes Fix a bug in Ventoy2Disk.exe for 2TB+ disk (issue #614) Keep the Secure Boot Support option when update Ventoy. (issue #630) Add class property for submenu of Ventoy UEFI Utilities New iso support (total 580+)

      TrueNAS-12.0-RELEASE.iso (Legacy + UEFI) primeos_mainline_0.4.5.iso (Legacy + UEFI) avira-rescue-system.iso (Legacy + UEFI) See https://www.ventoy.net/en/doc_news.html for detail.

      Download: Ventoy 1.0.30 | 10.2 MB (Open Source)
      Download: Ventoy Live CD | 40.4 MB
      Link: Ventoy Home Page | Project Page @GitHub

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      Ventoy 1.0.29
      by Razvan Serea



      Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With Ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. Both Legacy BIOS and UEFI are supported in the same way. Most type of OS supported (Windows/WinPE/Linux/Unix/Vmware/Xen...)

      Ventoy features:

      100% open source Simple to use Fast (limited only by the speed of copying iso file) Directly boot from ISO/WIM/IMG/VHD(x)/EFI file, no extraction needed Legacy + UEFI supported in the same way UEFI Secure Boot supported (since 1.0.07+) Persistence supported (since 1.0.11+) MBR and GPT partition style supported (1.0.15+) WIM files boot supported (Legacy + UEFI) (1.0.12+) IMG files boot supported (Legacy + UEFI) (1.0.19+) Auto installation supported (1.0.09+) File injection supported (1.0.16+) ISO files larger than 4GB supported Native boot menu style for Legacy & UEFI Most type of OS supported(Windows/WinPE/Linux/Unix/Vmware/Xen...), 550+ iso files tested Not only boot but also complete installation process ISO files can be listed in List mode/TreeView mode Linux vDisk boot supported (vdi/vhd/raw) "Ventoy Compatible" concept Plugin Framework Menu Alias/Menu Style/Customized Menu supported USB drive write-protected support USB normal use unaffected Data nondestructive during version upgrade No need to update Ventoy when a new distro is released Changelog:

      Image file name now can contain space and unicode characters(Chinese/Japanese/Korean ...).

      Add Driver Update Disk (DUD) plugin. Notes

      Skip Ventoy EFI part when searching for bootx64.efi (issue #592)

      Display a warning message when booting a non-bootable WIM file

      Add -l command in Ventoy2Disk.sh to display Ventoy information in disk.

      Download: Ventoy 1.0.29 | 7.3 MB (Open Source)
      Download: Ventoy Live CD | 37.1 MB
      Link: Ventoy Home Page | Project Page @GitHub

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware