error 39 premature end no such file or directory
-
ok, I got curious with the alternative binaries… same result … re-captured with the new ones, deployed with the new ones, same same … premature end
-
and just for fun, i tried the same with the older init.xz (capture -> deploy) with the non-resizable option, no dice … same
-
@iamyogo Ok so we know now the version of zstd and partclone changing between version 1.5.7 and 1.5.8 doesn’t have an impact on ability to capture/deploy. (just to be clear the newer version of partclone can capture and deploy older versions of partclone captured images, but the older version of partclone can’t reader the newer versions format. So that’s why you need to recapture).
So the issue has to be in the source image or the target computer’s hardware. So what size hard drive are you deploying this image to?
-
@george1421 said in error 39 premature end no such file or directory:
So the issue has to be in the source image or the target computer’s hardware. So what size hard drive are you deploying this image to?
100GB, source and target are the same VM to rule out incompatibility …
And I tried again this morning and this time i got the repair windows screen… (resizable)
then I tried with the fixed size option and success! … still errored, but the system booted! (newer init.xz)
-
In any case… i’m going to stick with gzip, as that seems the most flexible and reliable… just thought I’d let you know
-
@iamyogo I would say let’s try to see if different versions of Zstd all show the same issue. Download a FOS init build with the latest Zstd github commit as of now.
I can also build inits with older versions of Zstd to find out when the issue might have started. Are you keen to figure this out and maybe help find a bug in Zstd - if there is one…
-
Sure … my kids are going back to school next week, so i’ll have a bit more free time to troubleshoot …
-
@iamyogo Looking forward to hear if the latest version is doing any better.
Update: Just compiled a few more inits…
- 1.3.7
- 1.3.8
- 1.4.0
- 1.4.1
- 1.4.2
- 1.4.3
- 1.4.4 - the default we currently use in our inits, just to have the list completed
- commit 17226f59
Please try those and report back if they all show the same issue or not.
-
@iamyogo I’d be keen to hear if any of these did not show the error.
-
Hi guys,
Was having the same issue: partclone-Zstd failing at 98%. Managed to resolve it by using compression: 6 instead of compression: 18 and recapturing the image. Attached images show the error I was getting.
-
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
