error deploying windows 11

[robertkwild]

hi all,

im getting this error when i deploy a windows 11 image

sorry no idea what the error could be, i was hoping you guys can let me know

thanks,
rob

[Tom Elliott]

@robertkwild Did you actually capture an image to deploy?

It looks like you should expect an image in: /images/w11_24H2

Based on the message, it seems like if you had captured this before, it may not have completed or maybe was not written to /images/w11_24H2?

[robertkwild]

@Tom-Elliott this is interesting

yes i sysprep’d and then captured it using fog

ls /images/win10-22h2gi/
d1.fixed_size_partitions  d1.original.swapuuids  d1p4.img
d1.mbr                    d1p1.img               d1.partitions
d1.minimum.partitions     d1p2.img               d1.shrunken.partitions
d1.original.fstypes       d1p3.img
[root@lon-c-fog10 ~]# ls /images/w11_24H2
/images/w11_24H2

du -sh /images/w11_24H2
0       /images/w11_24H2
[root@lon-c-fog10 ~]# du -sh /images/win10-22h2gi/
18G     /images/win10-22h2gi/

but when i look on the fog web gui i get this

its saved the image as a file not a dir, why is this?

[Tom Elliott]

@robertkwild I don’t know why it did this.

There was some showing if this exact type of thing happening where/when

/images is one mount, and /images/dev is another individual mount

For example:
2TB HDD (SSD or otherwise) drive that /images is tied to in fstab.
Another 1TB HDD (or something like it) that /images/dev is tied to in fstab.

When the file gets moved from /images/dev/<mac_of_host> to /images/<image_name> for some reason the system moves it and makes it as a file instead of moving it as a directory.

You might (though I’m not holding my breath) still have the image in /images/dev/<mac_of_host> that captured?

[robertkwild]

@Tom-Elliott you are the main man, thanks so much !!!

rm -f /images/W11_24H2_GI
cp -rf /images/dev/00505692a681 /images/
mv /images/00505692a681 /images/W11_24H2_GI
chown -R fogproject:fogproject /images/W11_24H2_GI
chmod -R 775 /images/W11_24H2_GI/d1*

when i deploy it now works

is it ok to delete the folder in dev or leave it?

[Tom Elliott]

@robertkwild I think you’re okay to delete the folder /images/dev/00505692a681 But I leave that trigger totally up to you so long as you tested your copy of the W11_24H2_GI folder is good

[robertkwild]

@Tom-Elliott Hi Tom, this is happening all the time now, im having to run the commands everytime now i create new image

is there anyway i can automate this as in /dev folder i see the mac address of the host so in that folder would it contain the image name of what i called the image, if i know this i can definately automate it?

[Tom Elliott]

@robertkwild Is what I asked correct?

You have one drive mounted for /images, and another totally different drive mounted for /images/dev?

This used to work I suspect, so something changed and I’m going on a limb suspecting the issue is the inclusion of a secondary drive for the singular mount point.

[robertkwild]

@Tom-Elliott sorry Tom

no i only have one /images mounted

df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                  95G     0   95G   0% /dev
tmpfs                     95G     0   95G   0% /dev/shm
tmpfs                     95G   18M   95G   1% /run
tmpfs                     95G     0   95G   0% /sys/fs/cgroup
/dev/mapper/centos-root   50G  7.1G   43G  15% /
/dev/md6                 3.6T  902G  2.6T  26% /images
/dev/sdf4               1014M  154M  861M  16% /boot
/dev/mapper/centos-home  835G  309M  835G   1% /home
tmpfs                     19G     0   19G   0% /run/user/0
[root@lon-c-fog10 ~]# ls /images/
backup  dev  lon-transkoder  lost+found  os  postdownloadscripts  w11-gi  win10-22h2gi  Win10H22_Theatres
[root@lon-c-fog10 ~]# ls /
bin   dev  home    lib    media  opt   root  sbin    srv           sys       tftpboot.prev  usr
boot  etc  images  lib64  mnt    proc  run   script  swapfile.sys  tftpboot  tmp            var
[root@lon-c-fog10 ~]#

[robertkwild]

any news on this as all of a sudden its not working, ie i have to manually copy to /images from /images/dev

[Tom Elliott]

@robertkwild I, unfortunately, don’t have any news as I don’t quite understand why it’s creating a file instead of a folder.

If I recall, this used to be a file based system when Windows 7, and earlier were used (it’s been a long while though) and has long since been moved to folder based.

I’m not sure what answer I can say or give here.

Is there any way to know what actual version of FOG you’re currently running?

I can’t say I’ll figure out what’s wrong, but maybe somebody else has thoughts as well.

I’m 90% certain there’s something to do with the FTP statement, but unsure exactly what or why.

The other thing I think would help fix this would be to move to working-1.6 branch if you’re willing, but I realize that’s a huge ask, and may not really help fix the problem at hand.

I can say, with relative certainty at least, that if this was a completely widespread issue we’d have heard about this exactly issue many many more times. I am thinking there may be a PHP-FTP issue on your machine. Working-1.6 is setup, now, to attempt using straight SSH statements to copy and move files around, rather than FTP which should work more consistently (in theory.)

I realize the ask is large and probably overly much for the time being if this isn’t an approach you’d like to take.

[robertkwild]

@Tom-Elliott

when you say move to a working-1.6 branch what do you mean?

[Tom Elliott]

@robertkwild If you have the git installation method:

cd /opt
git clone https://github.com/fogproject/fogproject
cd fogproject
git checkout working-1.6
cd bin
sudo ./installfog.sh -y

Should do the trick.

(You don’t have to copy paste and everything, it’s just how I think of it all).

I don’t know how you installed originally or how you stay updated.

I am of the mind git is the easiest method as to get the lastest items you just have to cd to the install and run git pull

But that’s one developer’s opinion

Hope that helps?

[robertkwild]

@Tom-Elliott thanks Tom,I will try this, so how many versions are there of fog and where do I see the list of different versions please

[Tom Elliott]

@robertkwild There’s only one “stable” one “major/master” and then the one we’re working toward.

Technically there’s also “nightly” so 4 main versions:

• master branch = 1.5.10 (Currently) - Baseline for stable and current updates of the master.

• stable branch = 1.5.10.1634 (Currently) - This is considered (if you will in linux terms) LTS (we’re wanting 1.6 to come out but in the mean time we still need to keep things up and running of the stuff most people are using.)

• dev-branch branch = 1.5.10.x >= 1634 (currently) - This is where we do updates for issues found/reported/ and hopeful fixes to go into the next release of stable. This is what I would call “nightly” but it’s not quite bleeding edge either as this is just holding fixes for hte 1.5.10 and later versions.

• working-1.6 branch = 1.6. This is what some might consider alpha/beta (all working branches will be intended in this manner at least) in that it is where it’s the fully latest bleeding where we hope and want to get to with fog.

[robertkwild]

@Tom-Elliott Hi Tom, Im on stable

Latest Version:
1.5.10.1634

Latest Development Version:
1.5.10.1639

i get above on the login screen and below on the fog configuration page

You’re running the latest stable version: 1.5.10.1634

so your saying go to alpha/beta?

[robertkwild]

@Tom-Elliott sorry took my time in replying back tom my bad

in the end i updated my stable to the latest 1.5.10.1650 and now when i capture the image it saves it as a folder not a file

[Tom Elliott]

@robertkwild I’m suspecting there may have been a php module update that FTP was working similarly to a found issue in 1.6 and they finally addressed that. I apologize for not thinking of it sooner and glad it’s working. To my knowledge, we didn’t change anything regarding the Folder/File issue, so much appreciated in letting us know it’s working for you now.

[robertkwild]

@Tom-Elliott looks like i have to update my fog to 1.6 instead of 1.5 as i thought i resolved it by updating fog to the latest 1.5 but the error is still there on 1.5, i thought it went at first as when i made my first image it saved as a folder but on my second capture its saving as a file again