P2V - read ERROR: No such file or directory

Vivaldi

Member
Aug 2, 2022
18
1
8
I'm trying to move physical Windows XP machine to VM. Although every time I get the same error "read ERROR: No such file or directory" after total 1,29%.
What can cause this? I tried different Windows XP machines but still the same.
 
On source PC I boot up Clonezilla > remote-source > beginner > disk to remote disk
On proxmox's VM I boot up Clonezilla > remote-dest > beginner > default options
Machines can ping each other.
The error shows up during the copy procedure and whole thing fails.
 
VM's size is 500 GB and source is 239 GB. Error logs doesn't say much. It just copies blocks up to certain point and then "No such file or directory". Changing PC's doesn't matter. Versions of Clonezilla also. I've run chkdsk /f multiple times.
Does the Guest OS option matter in this process?
 
Does the Guest OS option matter in this process?
should not.

VM's size is 500 GB and source is 239 GB. Error logs doesn't say much. It just copies blocks up to certain point and then "No such file or directory". Changing PC's doesn't matter.
Maybe run in debug more so that there are more messages. Without any error message, there is nothing to do.
 
I ran it in verbose, but I still don't see where the issue is. FYI I checked the PC with chkdsk /f few times (including restarts).

Code:
Starting /usr/sbin/ocs-sr at 2022-08-04 12:36:28 UTC...
*****************************************************.
Clonezilla image dir: /tmp/ocs_onthefly_tgt.qN6NvS
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Running: task_restoreparts "d2d-pseudo" "sda1" "nd2d"
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Creating partition in /dev/sda...
Trying to clean the MBR and GPT partition table on the destination disk first: /dev/sda
Informing the OS of partition table changes... done!
Non-grub boot loader found on /tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-mbr...
The CHS value of hard drive from EDD will be used for sfdisk.
Sfdisk >= 2.26 does not support C/H/S option. Skip using C/H/S option.
*****************************************************.
Thu Aug  4 12:36:36 UTC 2022
Writing the partition table...
No partition table exists in target disk /dev/sda, try to initialize one so that we can get the disk size by parted... Running: parted -s /dev/sda mklabel msdos
done!
Running: LC_ALL=C sfdisk --force /dev/sda < /tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-pt.sf 2>&1 | tee -a /var/log/clonezilla.log
Checking that no-one is using this disk right now ... OK

Disk /dev/sda: 260 GiB, 279172874240 bytes, 545259520 sectors
Disk model: VBOX HARDDISK  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6859121b

Old situation:

>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new DOS disklabel with disk identifier 0xd3cad3ca.
/dev/sda1: Created a new partition 1 of type 'HPFS/NTFS/exFAT' and of size 232.9 GiB.
/dev/sda2: Done.

New situation:
Disklabel type: dos
Disk identifier: 0xd3cad3ca

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1  *       63 488375999 488375937 232.9G  7 HPFS/NTFS/exFAT

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
Checking that no-one is using this disk right now ... OK

Disk /dev/sda: 260 GiB, 279172874240 bytes, 545259520 sectors
Disk model: VBOX HARDDISK  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6859121b

Old situation:

>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new DOS disklabel with disk identifier 0xd3cad3ca.
/dev/sda1: Created a new partition 1 of type 'HPFS/NTFS/exFAT' and of size 232.9 GiB.
/dev/sda2: Done.

New situation:
Disklabel type: dos
Disk identifier: 0xd3cad3ca

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1  *       63 488375999 488375937 232.9G  7 HPFS/NTFS/exFAT

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
This was done by: LC_ALL=C sfdisk --force /dev/sda < /tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-pt.sf 2>&1 | tee -a /var/log/clonezilla.log
Checking the integrity of partition table in the disk /dev/sda...
Informing the OS of partition table changes.... done!
*****************************************************.
The first partition of disk /dev/sda starts at 63.
Restoring the hidden data between MBR (1st sector, i.e. 512 bytes) and 1st partition, which might be useful for some recovery tool, by:
dd if=/tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-hidden-data-after-mbr of=/dev/sda seek=1 bs=512 count=62
62+0 records in
62+0 records out
31744 bytes (32 kB, 31 KiB) copied, 0.00025902 s, 123 MB/s
Informing the OS of partition table changes.... done!
*****************************************************.
*****************************************************.
Restoring partition /dev/sda1...
Using "-l -q 0 -p port" when it's netcat listen mode.
*****************************************************.
Using partclone.ntfs to clone...
Run partclone: nc  192.168.0.5 9015 | zstdmt -dc |       partclone.ntfs -z 10485760 -N -L /var/log/partclone.log -s - -r -o /dev/sda1
Partclone v0.3.17 http://partclone.org
Starting to restore image (-) to device (/dev/sda1)
memory needed: 28602398 bytes
bitmap 7630874 bytes, blocks 2*10485760 bytes, checksum 4 bytes
Calculating bitmap... Please wait...
get device size 250048479744 by ioctl BLKGETSIZE64,
done!
File system:  NTFS
Device size:  250.0 GB = 61046992 Blocks
Space in use:   7.1 GB = 1729377 Blocks
Free Space:   243.0 GB = 59317615 Blocks
Block size:   4096 Byte
read ERROR:No such file or directory
Failed to clone remote image to /dev/sda1
Informing the OS of partition table changes.... done!
*****************************************************.
Finding swap partition(s) in MBR table /tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-pt.sf...
Probing sda with blockdev before restoring EBR...
Finding extended partition(s) in parted table /tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-pt.parted...
Running: ocs-restore-mbr --ocsroot /tmp/ocs_onthefly_tgt.qN6NvS  d2d-pseudo sda
Setting the TERM as linux
Restoring the first 446 bytes of MBR data (executable code area) for sda by:
dd if=/tmp/ocs_onthefly_tgt.qN6NvS/d2d-pseudo/sda-mbr of=/dev/sda bs=446 count=1
done.
*****************************************************.
Now tuning the file system size on partition /dev/sda1 to fit the partition size...
Running: ocs-resize-part  --batch /dev/sda1
ntfsresize -f -f /dev/sda1
ntfsresize v2017.3.23AR.3 (libntfs-3g)
$MFTMirr does not match $MFT (record 0).
ERROR(5): Opening '/dev/sda1' as NTFS failed: Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.
*****************************************************.
Now clear the NTFS volume dirty flag: /dev/sda1...
Running: ntfsfix -d /dev/sda1
Mounting volume... FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... FAILED
Correcting differences in $MFTMirr record 0...OK
Correcting differences in $MFTMirr record 3...OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
*****************************************************.
Running: ocs-tux-postprocess sda1
Trying to remove udev hardware record in the restored OS...
The specified destination device: sda1
Trying to remove udev persistent files. The devices to be searched: sda1...
Skip /dev/sda1 (ntfs).
done!
*****************************************************.
Running: ocs-update-syslinux -b sda1
Device /dev/sda1 is not a FAT partition.
Skip updating syslinux on that.
*****************************************************.
Running: ocs-install-grub -p "sda1 " auto
The grub directory is NOT found. Maybe it does not exist (so other boot manager exists) or the file system is not supported in the kernel. Skip running grub-install.
*****************************************************.
Running: ocs-update-initrd -p "sda1 " auto
The boot and grub directory was NOT found. Maybe it does not exist (so other boot manager exists) or the file system is not supported in the kernel. Skip running .
*****************************************************.
Running: run_ntfsreloc_part -p "sda1" auto
The NTFS boot partition was not found or not among the restored partition(s). Skip running partclone.ntfsfixboot.
*****************************************************.
End of restoreparts job for image d2d-pseudo.
End of restoredisk job for image d2d-pseudo.
Checking if udevd rules have to be restored...
This program is not started by Clonezilla server, so skip notifying it the job is done.
This program is not started by Clonezilla server, so skip notifying it the job is done.
Finished!
Finished!
Now syncing - flush filesystem buffers...

Ending /usr/sbin/ocs-sr at 2022-08-04 14:42:19 UTC...
*****************************************************.
*****************************************************.
Notifying the source machine that my job is done... done!
Now syncing - flush filesystem buffers...
Running ...
Ending /usr/sbin/ocs-onthefly at 2022-08-04 14:42:19 UTC...
 

Attachments

  • 2022-08-04 16_41_51.png
    2022-08-04 16_41_51.png
    18.1 KB · Views: 6
  • Zrzut ekranu 2022-08-04 142412.png
    Zrzut ekranu 2022-08-04 142412.png
    29 KB · Views: 7
  • Zrzut ekranu 2022-08-04 142252.png
    Zrzut ekranu 2022-08-04 142252.png
    24.7 KB · Views: 7
Last edited:
So? Did you found out what the problem was? I have the same error with a windows 10 BM to Proxmox VM... VM disk is bigger and all...
 
Unfortunately no. It must be something wrong with the HDD on source pc. I only managed to clone one windows machine over the network but two others failed like this.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!