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 -
@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 -
@industrialtech87 Linux Kernel 5.4.0-62-generic
We will update the products and see what happens. -
@industrialtech87 This isn’t really an error. If your image is using Zstd for compression, there’s some oddity still where it fails to send the “null” byte to fully complete the compression and it indicates similar to an issue. The Message you’re seeing is basically saying:
The program just cut out from under me, so I think it’s an issue. We have two types warnings, and errors. Warnings look similar to an error, except a warning will continue processing. Error will not continue processing.
-
@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.
-
@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.
-
@tom-elliott Is there a certain compression method that is recommend over another? I am capturing Windows 10 Pro. I will try zstd.
-
@industrialtech87 Captured a new image and used a different compression method. Imaging is working so far.
-
Hello
I had a problem when deploying an image with the FOG
Error message :
read ERROR: No such file or directory
Args Passed: /images/<image>/d1p2.img /dev/<disk>*For me, it was a problem of user rights on the FOG
Before :
drwxrwxrwx. 2 root root 190 Jun 29 15:07 <image>After:
drwxrwxrwx. 2 fogproject root 190 Jun 29 15:07 <image>I had to do a “chown” on my image folder in the /images directory to add the owner to “fogproject”
When creating a new image in the FOG GUI, the folder rights management is not well handled
Sincerely