Thank you very much! Changing CAPTURERESIZEPCT option from 5 to 8 has helped to capture image.
The description to this option is “This setting defines the amount of padding applied to a partition before attempting resize the ntfs volume and capturing it”.
As I understand this option impacts to partition shrinking and so to image size. Am I right?
I’ve updated fog server as you suggested below. And I still run into this error.
The total score is 3:2. Three PC with big hdd disks were successfully captured and deployed to small ssd. Capturing another two big hdd disks ended with same error.
PS I successfully captured image from one of problematic PC with old acronis backup & recovery 10.0.12703.
@sebastian-roth , thank you for reply! I will try Partclone!
Fog tells that:
You are currently running version: 1.5.8
Latest stable version is 1.5.9
We are trying to replace old PC with hdd 500Gb to new PC with sdd 240Gb. Old PC is in Windows domain. So we capture old big hdd, and then deploy in to small sdd. We’ve tested this procedure with such image settings:
Image Type - Single disk (Resizable)
Partition - Everything
Replicate? - Yes
Image Manager - Partimage
Two old big hdd were successfully migrated to new small sdd with such method.
But next two drives captures were ended in failure:
Collecting resizing constraints...
Needed relocation: 2486382 (10185 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile .. (this might take a while)
Relocating needed data ...
100.00 percent completed
Updating $BadClust file ...
Updating $Bitmap file ...
ERROR(5): Could not map attribute 0x80 in inode 23779: Input/output error
(shrinkPartition)
How could we fix such error to successfully capture image?
Thank you very much for reply!
Before deploying Windows 10 Pro x64 to PC, UEFI BIOS boot order is:
#1 - UEFI: PXE IPv4 Intel I211 Gigabit Network Connection
#2 - Windows Boot Manager
After deploying Windows 10 Pro x64 to PC, Windows 10 once changes UEFI BIOS boot order itself to:
#1 - Windows Boot Manager
#2 - UEFI: PXE IPv4 Intel I211 Gigabit Network Connection
How could I prevent Windows 10 to change itself UEFI BIOS boot order after deploying?
Some information:
I experience such problem on Asrock-X570 Phantom Gaming4, MSI Z370-A PRO, MSI H270 PC MATE, MSI H170A PC MATE motherboards. But MSI Z77A-G43 motherboard is OK, Windows 10 doesn’t change itself UEFI BIOS boot order after deploying.
Fog settings:
EFI BOOT EXIT TYPE - REFIND_EFI
BOOT EXIT TYPE - SANBOOT
Windows image: WIndows 10 20h2 Pro 64 bit with GPT partition tables
Thank you! What is the purpose of /opt/fog/snapins directory? Is it required for capturing? Or for deployment too?
Could I mount /images on separate drive (ssd) with nodev and noexec mounting options?
Thank you very much!
What do you think about installing FOG on the system with one hdd (mounted like /) and one ssd (mounted like /images)?
As I understand placing /images on ssd will help to improve deployment, because reading image from ssd is more quickly by comparison to reading image from hdd.
thank you very much for reply and the link to your testing!
I will test my partclone speed to evaluate my environment.
@george1421 , could you at least answer to some my questions without this “number of performance of my imaging”?
Today is holiday in our country and I’m not at work.
We have one FOG server and about 300 client computers in our LAN.
The main usage of our FOG server is capturing and deploying images to the workstations. Mostly it’s unicast, but sometimes it’s multicast deploying.
Our images contain a lot of CAD’s and Graphics software. Average size of image is about 85Gb.
Workstations have 1Gb/s connection to the switches. Switches have 10Gb/s connection to each other.
Main workstation configuration is 8700K (3.7Ghz/4.7Ghz, 6cores/12 threads), 32Gb 3200MHz, ssd, 1Gb/s LAN connection.
What is optimal hardware requirements for FOG server in such case?
CPU
1. What is workload on the CPU during image capturing/deploying? Is the main workload of CPU on client? Or is on FOG server CPU? Or are on the both?
2. What is more important for FOG server CPU during capturing/deploying? Core and threads? Or CPU frequency? Does FOG use multi-threading?
RAM
3. How much RAM does FOG server need?
DISK
4. What is performance dependence of FOG server disk system?
5. How could RAID 5 array improve performance in comparison of single 7200 RPM disk?
NETWORK
6. What is performance dependence of FOG server LAN connection speed? How could 10Gb/s LAN connection of FOG server improve performance in comparison of 1Gb/s LAN connection?
I use ubuntu 12.04.5 and fog 1.2.0.
I would like to add “windows 7 64 bit.iso” to boot options.
So, I
:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item win7sp1x64 Windows 7 sp1 64 bit
item shell ipxe shell
item return return to previous menu
choose --default return --timeout 5000 target && goto ${target}
:win7sp1x64
initrd http://${fog-ip}/${fog-webroot}/service/ipxe/iso/win7sp1x64.iso
chain memdisk iso raw ||
goto MENU
:shell
shell ||
goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU
autoboot
But client hangs at “Loading Boot Sector…booting…” during boot.
Please, coould you help me?