cit.: "Ultimately I plan to run this pre-installed Win10 in a VM under F29. The trick
is to get a forensic copy of the existing pre-installed OS that I can read back into a VM
maybe a hint: you are maybe able (raid: don't know) to boot your raw windows
disk(s)/Partition(s) within a VM.
I do this with Virtualbox. My Windows lays on a second sata disk (1st and 2cd partition)
I do "sudo VBoxManage internalcommands createrawvmdk -filename ./Win_RAW.vmdk
-rawdisk /dev/sdb -partitions 1,2 -relative" to get a disk (~800 Bytes only) for my
Vbox Windows VM config.
the command creates 2 files:
- Win_RAW.vmdk and
the first one is your disk for your Window 10 Vbox-VM
you need to chown the created files for your user running the VM, too.
/dev/sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 206848 41019391 40812544 19,5G 7 HPFS/NTFS/exFAT
here, sdb1 is the boot partition and sdb2 the system partition from Windows 7/10
maybe a second hints:
to have a disk image from your shiny new machine isn't a bad idea ( backup, sale in
some years ?)
- => fsarchiver
- delete the Windows swap/hibernation files before doing an image !!!
more right: he above /dev/sdb is a lie/no more current since I moved my sda (F29 !)
stuff to an nvme (Samsung Evo Plus => tested by phoronix.com
), so a sata port came free
and sdb went to sda.