Can't recover data from Windows 10 Backup
I am transitioning to Ubuntu from Windows 10. Before installing the new OS, I made a full backup of my windows 10, expecting to extract individual files from the backup on my Ubuntu. Now I'm stuck with a bunch of .xml and .vhdx files How do I proceed?
I have already tried https:/
tsidia@
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x555f823973b0, program = guestmount
libguestfs: trace: set_recovery_proc false
libguestfs: trace: set_recovery_proc = 0
libguestfs: trace: add_drive "c3c7f9c3-
libguestfs: creating COW overlay to protect original drive content
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: disk_create "/tmp/libguestf
libguestfs: command: run: qemu-img
libguestfs: command: run: \ create
libguestfs: command: run: \ -f qcow2
libguestfs: command: run: \ -o backing_
libguestfs: command: run: \ /tmp/libguestfs
qemu-img: /tmp/libguestfs
To replay the log, run:
qemu-img check -r all '/media/tsidia/SP PHD U3/WindowsImage
Could not open backing image to determine size.
libguestfs: error: qemu-img: /tmp/libguestfs
libguestfs: trace: disk_create = -1 (error)
libguestfs: trace: add_drive = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x555f823973b0 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfs
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
How did make the files?
What process and application did you use to make the backup?
Thanks
Simply naming file extensions doesn’t tell us anything
Revision history for this message
|
#2 |
I created the backup files using the built-in "system image backup" feature in windows 10. To be more precise, I followed this guide:
https:/
Revision history for this message
|
#3 |
Did you run:
sudo qemu-img check -r all '/media/tsidia/SP PHD U3/WindowsImage
As stated in your own output?
Revision history for this message
|
#4 |
sudo qemu-img check -r all '/media/tsidia/SP PHD U3/WindowsImage
After running guestmount --add c3c7f9c3-
501f00000000.vhdx --inspector --ro /home/tsidia/
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x56163665d3b0, program = guestmount
libguestfs: trace: set_recovery_proc false
libguestfs: trace: set_recovery_proc = 0
libguestfs: trace: add_drive "c3c7f9c3-
libguestfs: creating COW overlay to protect original drive content
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: disk_create "/tmp/libguestf
libguestfs: command: run: qemu-img
libguestfs: command: run: \ create
libguestfs: command: run: \ -f qcow2
libguestfs: command: run: \ -o backing_
libguestfs: command: run: \ /tmp/libguestfs
Formatting '/tmp/libguestf
libguestfs: trace: disk_create = 0
libguestfs: trace: add_drive = 0
libguestfs: trace: launch
libguestfs: trace: version
libguestfs: trace: version = <struct guestfs_version = major: 1, minor: 36, release: 13, extra: , >
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=guestmount
libguestfs: launch: version=1.36.13
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=
libguestfs: launch: umask=0022
libguestfs: launch: euid=1000
libguestfs: is_openable: /dev/kvm: Permission denied
libguestfs: trace: get_backend_setting "force_tcg"
libguestfs: trace: get_backend_setting = NULL (error)
libguestfs: warning: current user is not a member of the KVM group (group ID 127). This user cannot access /dev/kvm, so libguestfs may run very slowly. It is recommended that you 'chmod 0666 /dev/kvm' or add the current user to the KVM group (you might need to log out and log in again).
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/
libguestfs: command: run: \ -o /var/tmp/
supermin: version: 5.1.19
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/
supermin: build: /usr/lib/
supermin: reading the supermin appliance
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 213 packages, including dependencies
supermin: build: 9946 files
supermin: build: 6726 files, after matching excludefiles
supermin: build: 6729 files, after adding hostfiles
supermin: build: 6726 files, after removing unreadable files
supermin: build: 6729 files, after munging
supermin: kernel: looking for kernel using environment variables ...
supermin: kernel: looking for kernels in /lib/modules/
supermin: kernel: looking for kernels in /boot ...
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: picked vmlinuz /boot/vmlinuz-
supermin: kernel: kernel_version 5.3.0-42-generic
supermin: kernel: modpath /lib/modules/
cp: cannot open '/boot/
supermin: cp -p '/boot/
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x56163665d3b0 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfs
When run with sudo it instead produces this output
guestmount: no operating system was found on this disk
If using guestfish '-i' option, remove this option and instead
use the commands 'run' followed by 'list-filesystems'.
You can then mount filesystems you want by hand using the
'mount' or 'mount-ro' command.
If using guestmount '-i', remove this option and choose the
filesystem(s) you want to see by manually adding '-m' option(s).
Use 'virt-filesystems' to see what filesystems are available.
If using other virt tools, this disk image won't work
with these tools. Use the guestfish equivalent commands
(see the virt tool manual page).
Revision history for this message
|
#5 |
libguestfs: warning: current user is not a member of the KVM group (group ID 127). This user cannot access /dev/kvm, so libguestfs may run very slowly. It is recommended that you 'chmod 0666 /dev/kvm' or add the current user to the KVM group (you might need to log out and log in again).
Did you add your user to the kvm group?
sudo usermod -a -G kvm $USER
Will do it (If you haven't already. You don't need to change the command). You will need to log off and on to make this active in the session (Just as in Windows)
Revision history for this message
|
#6 |
Added. Now it no longer asks me to do it, but otherwise the output is the same.
I also tried to avoid using the -i option, so instead I run virt-filesystems which told me the only filesystem on the vhdx file is /dev/sda2. Next I run guestmount --add c3c7f9c3-
501f00000000.vhdx --ro /home/tsidia/
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x5584fb04d3b0, program = guestmount
libguestfs: trace: set_recovery_proc false
libguestfs: trace: set_recovery_proc = 0
libguestfs: trace: add_drive "c3c7f9c3-
libguestfs: creating COW overlay to protect original drive content
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: disk_create "/tmp/libguestf
libguestfs: command: run: qemu-img
libguestfs: command: run: \ create
libguestfs: command: run: \ -f qcow2
libguestfs: command: run: \ -o backing_
libguestfs: command: run: \ /tmp/libguestfs
Formatting '/tmp/libguestf
libguestfs: trace: disk_create = 0
libguestfs: trace: add_drive = 0
libguestfs: trace: launch
libguestfs: trace: version
libguestfs: trace: version = <struct guestfs_version = major: 1, minor: 36, release: 13, extra: , >
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=guestmount
libguestfs: launch: version=1.36.13
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=
libguestfs: launch: umask=0022
libguestfs: launch: euid=1000
libguestfs: trace: get_backend_setting "force_tcg"
libguestfs: trace: get_backend_setting = NULL (error)
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/
libguestfs: command: run: \ -o /var/tmp/
supermin: version: 5.1.19
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/
supermin: build: /usr/lib/
supermin: reading the supermin appliance
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 213 packages, including dependencies
supermin: build: 9946 files
supermin: build: 6726 files, after matching excludefiles
supermin: build: 6729 files, after adding hostfiles
supermin: build: 6726 files, after removing unreadable files
supermin: build: 6729 files, after munging
supermin: kernel: looking for kernel using environment variables ...
supermin: kernel: looking for kernels in /lib/modules/
supermin: kernel: looking for kernels in /boot ...
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: picked vmlinuz /boot/vmlinuz-
supermin: kernel: kernel_version 5.3.0-42-generic
supermin: kernel: modpath /lib/modules/
cp: cannot open '/boot/
supermin: cp -p '/boot/
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x5584fb04d3b0 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfs
Revision history for this message
|
#7 |
Are you reading the output or just copying and pasting. I’ve identified a few issues and resolved them just by reading your output
Revision history for this message
|
#8 |
If you remove the:
-m /dev/sda2
Is it okay? Can you loop mount the file? I’m not overly familiar with mounting Windows backup files.
Are there guides on YouTube?
Revision history for this message
|
#9 |
I am new to Ubuntu so I may not recognize some issues and if I do I may not know how to resolve them even if the situation is otherwise easy to get out of. I am grateful for the patience. I suppose running the command with sudo would solve the problem, but I was explicitly told not to do that when looking for the solution on the internet
Revision history for this message
|
#10 |
Removing the -m part still results in errors. If there were working guides on youtube, I wouldn't be asking in the first place
Revision history for this message
|
#11 |
Many people don’t think of YouTube for guides. It’s a perfectly sensible suggestion even to find out you tried it. Don’t you think?
Revision history for this message
|
#12 |
guestmount --add c3c7f9c3-
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x55b534a483b0, program = guestmount
guestmount: error: you must specify either -i at least one -m option.
Try `guestmount --help' for more information.
libguestfs: trace: close
libguestfs: closing guestfs handle 0x55b534a483b0 (state 0)
Revision history for this message
|
#13 |
Yes, I did try youtube for help. I found two videos on the matter. I tried both and run into errors that weren't present in the video
Revision history for this message
|
#15 |
We have already tried this here, nevertheless:
guestmount --add '/media/tsidia/SP PHD U3/WindowsImage
results in
libguestfs: trace: set_verbose true
libguestfs: trace: set_verbose = 0
libguestfs: create: flags = 0, handle = 0x5602d71a23b0, program = guestmount
libguestfs: trace: set_recovery_proc false
libguestfs: trace: set_recovery_proc = 0
libguestfs: trace: add_drive "/media/tsidia/SP PHD U3/WindowsImage
libguestfs: creating COW overlay to protect original drive content
libguestfs: trace: get_tmpdir
libguestfs: trace: get_tmpdir = "/tmp"
libguestfs: trace: disk_create "/tmp/libguestf
libguestfs: command: run: qemu-img
libguestfs: command: run: \ create
libguestfs: command: run: \ -f qcow2
libguestfs: command: run: \ -o backing_
libguestfs: command: run: \ /tmp/libguestfs
Formatting '/tmp/libguestf
libguestfs: trace: disk_create = 0
libguestfs: trace: add_drive = 0
libguestfs: trace: launch
libguestfs: trace: version
libguestfs: trace: version = <struct guestfs_version = major: 1, minor: 36, release: 13, extra: , >
libguestfs: trace: get_backend
libguestfs: trace: get_backend = "direct"
libguestfs: launch: program=guestmount
libguestfs: launch: version=1.36.13
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: libvirt
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=
libguestfs: launch: umask=0022
libguestfs: launch: euid=1000
libguestfs: trace: get_backend_setting "force_tcg"
libguestfs: trace: get_backend_setting = NULL (error)
libguestfs: trace: get_cachedir
libguestfs: trace: get_cachedir = "/var/tmp"
libguestfs: begin building supermin appliance
libguestfs: run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/
libguestfs: command: run: \ -o /var/tmp/
supermin: version: 5.1.19
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/
supermin: build: /usr/lib/
supermin: reading the supermin appliance
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: build: visiting /usr/lib/
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 213 packages, including dependencies
supermin: build: 9946 files
supermin: build: 6726 files, after matching excludefiles
supermin: build: 6729 files, after adding hostfiles
supermin: build: 6726 files, after removing unreadable files
supermin: build: 6729 files, after munging
supermin: kernel: looking for kernel using environment variables ...
supermin: kernel: looking for kernels in /lib/modules/
supermin: kernel: looking for kernels in /boot ...
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: kernel version of /boot/vmlinuz-
supermin: kernel: picked modules path /lib/modules/
supermin: kernel: picked vmlinuz /boot/vmlinuz-
supermin: kernel: kernel_version 5.3.0-42-generic
supermin: kernel: modpath /lib/modules/
cp: cannot open '/boot/
supermin: cp -p '/boot/
libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above
libguestfs: trace: launch = -1 (error)
libguestfs: trace: close
libguestfs: closing guestfs handle 0x5602d71a23b0 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfs
Revision history for this message
|
#16 |
"cp: cannot open '/boot/
What's the output of the command
ls -l /boot
Revision history for this message
|
#17 |
This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.