@Sebastian-Roth Removing the 4th partition did resolve the issue. Thank you for your help. Great work with FOG.
Best posts made by IndustrialTech87
-
RE: Error trying to restore GPT partition tables. Exit returned code 4 (On new PC's)
-
RE: Fog Server throws error when trying to image new HP G4 Desktops
Upgrading the Kernel fixed this issue. I am not sure what version he upgraded to but I can now image these new computers. Thank you for your help @george1421
Latest posts made by IndustrialTech87
-
RE: read ERROR: No such file or directory
@industrialtech87 Captured a new image and used a different compression method. Imaging is working so far.
-
RE: read ERROR: No such file or directory
@tom-elliott Is there a certain compression method that is recommend over another? I am capturing Windows 10 Pro. I will try zstd.
-
RE: read ERROR: No such file or directory
@industrialtech87 Updated Kernel but same message. Computer just goes through a boot loop after the warning/error. Image is the one we have been using for a while but I may try to capture a new image and see if that does it.
-
RE: read ERROR: No such file or directory
@tom-elliott The image is compressed with Partclone Gzip. Have not had a chance to update so I will post back if that works. I have had the onsite tech try four other computers and still get the warning when it is at the end of the image process.
-
RE: read ERROR: No such file or directory
@industrialtech87 Linux Kernel 5.4.0-62-generic
We will update the products and see what happens. -
RE: read ERROR: No such file or directory
@industrialtech87
It also failed on an older computer so now I am not sure why the cause for the error all of the sudden. We imaged a few computers earlier this week. Server has been up for about 63 days. Here is the version info in case you were wondering.You are currently running version: 1.5.9-RC2
Latest stable version is 1.5.9
Latest dev-branch version is 1.5.9.63
Latest alpha-branch version is 1.6.0-alpha.1083 -
read ERROR: No such file or directory
Hello,
Looking for some advice. We have been using FOG for many years and everything is going smoothly. I have been deploying a lot of new computers over the past months and have not had an issue until today. I had the guy onsite try to image some new computers out of the box and it is throwing the following error at the end.
Sorry for the quality.
I am wondering if this is perhaps because the new computers are running NVME? I can’t recall if any of the prior computers used NVME or not so I can’t say if it worked on NVME before.I am having him test the image process on an older computer that has an SSD drive to see if it goes through. Waiting on those results now.
I am going to post the contents of the image directory below along with the contents of the files. Appreciate any help!
Image Type - Resizeable
Partition - Everything
Compression - 6
Image Manager - Partclone Gzipadmin@fog:/images/UnionBankNew$ cat d1.original.fstypes
/dev/sda3 ntfs
admin@fog:/images/UnionBankNew$ cat d1.fixed_size_partitions
1:2
admin@fog:/images/UnionBankNew$ cat d1.minimum.partitions
label: gpt
label-id: 1DE8D736-288E-4F4C-AFF7-CF58B1B11E2F
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 1953525134
sector-size: 512/dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E6C29A23-37C6-4A11-A69A-986F324550D8, name=“EFI system partition”, attrs=“GUID:63”
/dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=FD8A40BA-2517-4CF2-9655-29F8CB55A718, name=“Microsoft reserved partition”, attrs=“GUID:63”
/dev/sda3 : start= 239616, size= 54782784, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=87D213B5-9776-4A9B-8DCE-D31B74933E08, name=“Basic data partition”admin@fog:/images/UnionBankNew$ cat d1.partitions
label: gpt
label-id: 1DE8D736-288E-4F4C-AFF7-CF58B1B11E2F
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 1953525134
sector-size: 512/dev/sda1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E6C29A23-37C6-4A11-A69A-986F324550D8, name=“EFI system partition”, attrs=“GUID:63”
/dev/sda2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=FD8A40BA-2517-4CF2-9655-29F8CB55A718, name=“Microsoft reserved partition”, attrs=“GUID:63”
/dev/sda3 : start= 239616, size= 471040512, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=87D213B5-9776-4A9B-8DCE-D31B74933E08, name=“Basic data partition”Regards,
Sean -
RE: Error trying to restore GPT partition tables. Exit returned code 4 (On new PC's)
@Sebastian-Roth Removing the 4th partition did resolve the issue. Thank you for your help. Great work with FOG.
-
RE: FOG Could not start download: Invalid Argument
@george1421 I had the same problem a while back on FOG 1.4 and updating the kernel fixed the issue.
-
RE: Error trying to restore GPT partition tables. Exit returned code 4 (On new PC's)
@IndustrialTech87 Sorry for bombing you. I was discussing removing that partition or setting it so it resizes. I am going to deploy to a spare pc, delete the partition in disk management and recapture the image. Or use Gpart maybe. Thanks for the help.