Hi,

Thank you both for you precious help …

Back with the results : https://drive.google.com/file/d/1hJXQ-H7C4gZPvAUlPlVz9CzmFmBeVLK2/view?usp=sharing

@Quazz : How i can fix my funcs.sh ? i can hack it with my fog.postinit i think ? With sed tool …

I think, this fix is not good : https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L493

Maybe the good fix is : line 493 :

if [[ $label =~ [Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd] || $label =~ [Rr][Éé][Ss][Ee][Rr][Vv][Éé] ]]; then

Hi !

You right @Quazz … the good word is “Réservé” and not “Résérvé”.

I’m back with the results of commands (on VM Golden Img) :
https://drive.google.com/file/d/13gj87dVq2SThjy5IYdbmtiyOCZuXXtDu/view?usp=sharing

my fog.postint :

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#RM-CM-\\\)servM-CM-\\\)#gi" /bin/fog.upload
sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#RM-CM-\\\)servM-CM-\\\)#gi" /usr/share/fog/lib/funcs.sh```

Hi !

@Sebastian-Roth I ran an upload debug task on VM and did the command : https://drive.google.com/file/d/1s1CVoUuPlNNCEK7bcn6TBpclbK4hc2bK/view?usp=sharing

What do you think about the result ?

Hm, we are close to find the issue … I can confirmed … when i renamed the system partition in my Golden Image, the reserved partition has the good size after a deploy on a o7010 …
So, the intuition was good … !

Screenshot on o7010 : https://drive.google.com/file/d/1btji1AQSUx7SmOQU5JsplMbENy6DFl1u/view?usp=sharing

You totally right …
I will try the download with the modified name partition.
If it’s works, we can realize new tests with the “sed” command hack to permanently fix this issue for all french people.

Hi,

I’m back after few off days …

I tried your patch on the VM, upload the new image and tried a new download … it’s didn’t work.

I tried to play with backslashes and no more sucess …

BUT, i have an other idea :

• run the VM
• go to the Disks Management tool
• right click on the “Partition réservé au système”
• rename this damn partition to “System Reserved” (<-- it is the right US/english name ?)
• upload the image on FOG
• try a new DL on client …

What do you think about that idea ?

@Sebastian-Roth said in Win7x64 : Golden Image : partitions problems ... again:

Save the file and boot up your client with a debug upload task

i understand your way and your test … but if i really understood, i do the debug upload task on my VM ? Because you said “upload task” …

Hi !
I ran a new debug task on a client …

[Wed Sep 12 root@fogclient ~]# blkid -po udev $part | grep FS_LABEL
blkid: The low-level probing mode requires a device

[Wed Sep 12 root@fogclient ~]# blkid                               
/dev/ram0: UUID="885cb2cc-e11f-4e88-8182-ee60a35f43d1" TYPE="ext2"
/dev/sda1: LABEL="RM-CM-)servM-CM-) au systM-CM-(me" UUID="8E4C92C44C92A70D" TYPE="ntfs" PARTUUID="c91a5cff-01"
/dev/sda2: LABEL="System" UUID="46E2941BE29410F3" TYPE="ntfs" PARTUUID="c91a5cff-02"

On the 2nd command, we can see the very strange label of /dev/sda1 … !

Edit : I deployed a classic image on o7010 and tried the same commands : same results … :

[Wed Sep 12 root@fogclient ~]# blkid
/dev/ram0: UUID="885cb2cc-e11f-4e88-8182-ee60a35f43d1" TYPE="ext2"
/dev/sda1: LABEL="RM-CM-)servM-CM-) au systM-CM-(me" UUID="A27C916A7C9139CD" TYPE="ntfs" PARTUUID="3f61e1ac-01"
/dev/sda2: LABEL="System" UUID="34C09543C0950BEC" TYPE="ntfs" PARTUUID="3f61e1ac-02"
[Wed Sep 12 root@fogclient ~]# blkid -po udev $part | grep FS_LABEL
blkid: The low-level probing mode requires a device

Hi !
I’m back after the 1.5.4.8 update … and the issue is still there

I tried to deploy my Golden Image on the 3 optiplex and i had the same results … very large reserved partition.

I opened the fog.upload on a debug client task (ssh session) and checked the funcs.sh file :

            local label=$(getPartitionLabel "$part")
            if [[ $label =~ [Rr][Ee][Cc][Oo][Vv][Ee][Rr][Yy] ]]; then
                echo "$(cat "$imagePath/d1.fixed_size_partitions" | tr -d \\0):${part_number}" > "$imagePath/d1.fixed_size_partitions"
                echo " * Not shrinking ($part) recovery partition"
                debugPause
                return
            fi
            if [[ $label =~ [Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd] || $label =~ [Rr][�~Ié][Ss][�~Ié][Rr][Vv][�~Ié] ]]; then
                echo "$(cat "$imagePath/d1.fixed_size_partitions" | tr -d \\0):${part_number}" > "$imagePath/d1.fixed_size_partitions"
                echo " * Not shrinking ($part) reserved partitions"
                debugPause
                return
            fi

I take a picture of the same file directly on screen … : https://drive.google.com/open?id=12wiSow0jfowtj85T0AI9NF_CvkH9eMyW

What can i do to find the culprit ? Maybe it’s not a FOG problem but a problem during the Golden Image creation with Virtualbox ?

Thank you

I wil try to update my fog server to 1.5.4

I will be back for the feedbacks

Thank you for the answer !

I have already saw theses topics

But … i’m on FOG 1.4.2 … i searched if newer version fix the label partition problem and i can’t found any annoncement to say that … Maybe i can update my FOG Server to the lastest … but i just want to be sure this issue has fixed …

Hi !

First, you can see my configuration into my signature

Since one year, i use universal image to deploy Windows 7 x64 on many differents models (o3020, o3040, o7010, HP820G3 …) but i have a problem partition …

After a deploy, the Reserved System partition (in french «Réservé au système ») don’t have a right size … :

• on Optiplex7010 : 305Gb for the « Réservé au système » partition. 159Gb for the C drive

• on Optiplex7050 : 78Gb for the « Réservé au système » partition. 159Gb for the C drive

• on Optiplex5050 : 771Gb for the « Réservé au système » partition. 159Gb for the C drive

This issue can be circumnavigated by editing the d1.fixed_size_partitions file but it’s not a real good solution because it’s need an human intervention after every update of the universal image … so, i think, the solution recommanded by @george1421 seem the good way … but, i not sure if i really understood the answer …

I need to edit the postinit file but, what i exactly do with this file ? Searching for the « Réservé au système » partition to set it to 100Mb ?
I’m confused about that …

VirtualBox configuration :
Version : 5.0.26
VM configuration disk :
Virtual Size : 160Go
Real Size : 9,12Go

Windows disk Manager on VM :
https://drive.google.com/file/d/0B48PuYLEHxQLUEU5clJOZC1Vb3c/view?usp=sharing

Definition of golden image on FOG GUI :
https://drive.google.com/open?id=0B48PuYLEHxQLdXlTcW90RS1DWnc

Windows disk Manager on HP8000 after deploy :
https://drive.google.com/open?id=0B48PuYLEHxQLdzRHb0EtY1k2NkU

We can see the big size of the reserved parition … not 100Mb but 72Go !

Windows disk Manager on DELL o7010 after deploy :
https://drive.google.com/open?id=0B48PuYLEHxQLSUdpam1STEV0cjg

On the optiplex 7010, same problem … the reserved partition is more larger … 305Go.

On the both computers, the system C partition is always 159Go ….

I juste want this simple partitionning :

"Réservé au système" : always 100Mb
System C partition : rest of the disk ……

I don’t use sysprep to expand or touch any partition.

What can i do to use all space for the C partition and have a classic 100Mb reserved partition ?

PS : linked with these topics … :

• https://forums.fogproject.org/topic/10963/win7x64-golden-image-partitions-problems
• https://github.com/FOGProject/fogproject/issues/195

After reflexion, i wiil use the postinit script … Why ? Because if i receive a new model with the VBoxMouse.sys conflit driver, i will need to search again the culprit file into the Driver Pack … and waste many times …

So, in the fog.bonus, i added this :

# suppression du fichier VBoxMouse.sys ... eviter conflit et BSOD avec les Optiplex5050 durant SYSPREP (au 2nd reboot, durant verif perf. videos)
rm /ntfs/Windows/System32/drivers/VBoxMouse.sys
echo "Suppression du fichier VBoxMouse.sys pour eviter BSOD durant SYSPREP  (au 2nd reboot) ... Done !";

I also added this in the SetupComplete.cmd :

rem uninstall VirutalBox Guest Additions : eviter les BSOD comme VBoxMouse.sys sur machine cible
"C:\Program Files\Oracle\VirtualBox Guest Additions\uninst.exe" /S

I retried a download task on the Optiplex 5050 … and no BSOD

So … just many thanks again George for your help ! Knowledge growth up !

PS : how can pass the subject to “Solved” ?!

Hi again,

George, thank you for the advice

I tried to deploy the image without drivers (rename the drivers folder on NAS) and … no BSOD.

So … i found the culprit : drivers pack …

After, i tried to download the lastest .CAB Drivers pack (https://www.dell.com/support/article/fr/fr/frbsdt1/how13575/optiplex-5050-windows-7-driver-pack?lang=en) and same error …

I think, i can try to find the culprit driver in .CAB archive … but it can take many long time … no ?

I can try to :

• extract .CAB to a folder
• put the folder on NAS with the .inf files in folders (storage, chipset etc …)
• delete one folder
• retry a download …
• if BSOD, delete an other folder and retry a DL … etc etc …

Other idea before i will that very long debug step ?

Hi !

First, you can see my configuration into my signature

Since one years, i use universal image to deploy Windows 7 x64 on many differents models (o3020, o3040, o7010, HP820G3 …)

Recently, we received new model : Optiplex 5050.

For all computers, i :

• disable secure boot
• enable legacy boot
• enable AHCI mode …

After that, i deploy my Virtualbox sysprepped universal image on the computer … for the others models, it’s works … but with the Optiplex 5050, i have a BSOD …

In the BSOD, i can see the culprit : VBoxMouse.sys …

So, i tried this trick :

• debug task on the o5050
• mount the Windows partition on /ntfs
• mv /ntfs/Windows/System32/drivers/VBoxMouse.sys VboxMouse.OLD
• run “fog” … and the sysprep passed without BSOD.

So … to fix the problem, i can write this command into my “fog.bonus” script executed during the postinit … but, why the BSOD appear only on o5050 ?

Is it possible the drivers pack 5050-WIN7-A07-8Y01N.CAB is the real culprit ?

If you think not, have you an idea ?

Many thanks for your help

hi,
I find an interesting feature in FOG PXE Configuration : the hide menu option / no menu option.

I want to use this feature in the idea to choose the LAN card first boot on my classroom
computers : after to set the LAN card at first boot, the idea is :

• use a WOL soft to wake up my 25 computers …
• IF there is an image => deploy the image.
• IF theren’t an image => boot on the HDD.
  AND i don’t want the students to see the FOG menu …
  BUT, i’m not the only user on the FOG server (our FOG is used in different geographic locations) and my collegues want to display the 3sec menu boot FOG on theirsclassroom computers …

Is there a way to applies the hide menu / no menu configuration only on a group of hosts ?

I found a subject about a same request (https://forums.fogproject.org/topic/9671/add-enhanced-ipxe-boot-menu-capabilities-based-on-host-associations/2) but no mores informations about this request …

Thank you for your reply.
I will try that

Thanks for reply.
There is a way to have more verbose snapin output with the new version of fog client ?

Server :
FOG Version: 1.4.2 SVN 6072
OS: Debian 8

Client :
Service Version: SmartInstaller v0.11.12
OS: Win7x64 PRO

Description :
Hi,
I’m really sorry for the “UP” but i try to have more verbose logs for the Snapins …
In my case, for SnapinPack, into the fog.log, i have “just” this :

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 12/01/2018 16:07 Client-Info Client Version: 0.11.12
 12/01/2018 16:07 Client-Info Client OS:      Windows
 12/01/2018 16:07 Client-Info Server Version: 1.4.2
 12/01/2018 16:07 Middleware::Response Success
 12/01/2018 16:07 SnapinClient Running snapin algobox_64
 12/01/2018 16:07 Middleware::Communication Download: http://xxx.xxx.xxx.xxx/fog/service/snapins.file.php?mac=xx:xx:xx:xx:xx:xx||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=xxx
 12/01/2018 16:07 SnapinClient C:\Program Files (x86)\FOG\tmp\algobox_x64.zip
 12/01/2018 16:07 SnapinClient Processing SnapinPack algobox_x64.zip
 12/01/2018 16:07 SnapinClient Extracting SnapinPack
 12/01/2018 16:07 Bus Emmiting message on channel: Notification
 12/01/2018 16:07 SnapinClient Starting snapin
 12/01/2018 16:07 SnapinClient Snapin finished
 12/01/2018 16:07 SnapinClient Return Code: 0
 12/01/2018 16:07 Bus Emmiting message on channel: Notification
 12/01/2018 16:07 Middleware::Communication URL: ...............
------------------------------------------------------------------------------```

In your case, it’s seem to be more verbose …

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 14/09/2016 11:18 Client-Info Client Version: 0.11.5
 14/09/2016 11:18 Client-Info Client OS:      Windows
 14/09/2016 11:18 Client-Info Server Version: 1.3.0-RC-10
 14/09/2016 11:18 Middleware::Response Success
 14/09/2016 11:18 SnapinClient Snapin Found:
 14/09/2016 11:18 SnapinClient     ID: 1381
 14/09/2016 11:18 SnapinClient     Name: Clone
 14/09/2016 11:18 SnapinClient     Created: 2016-09-14 11:17:34
 14/09/2016 11:18 SnapinClient     Action: 
 14/09/2016 11:18 SnapinClient     Pack: False
 14/09/2016 11:18 SnapinClient     Hide: False
 14/09/2016 11:18 SnapinClient     Server: 
 14/09/2016 11:18 SnapinClient     TimeOut: 0
 14/09/2016 11:18 SnapinClient     RunWith: c:\windows\system32\cmd.exe
 14/09/2016 11:18 SnapinClient     RunWithArgs: /c
 14/09/2016 11:18 SnapinClient     Args: 
 14/09/2016 11:18 SnapinClient     File: Clone2.cmd
 14/09/2016 11:18 Middleware::Communication Download: http://192.168.10.60/fog/service/snapins.file.php?mac=E8:40:F2:3B:C7:AA&taskid=1381
 14/09/2016 11:18 SnapinClient C:\Program Files (x86)\FOG\tmp\Clone2.cmd
 14/09/2016 11:18 Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"Installing Clone\",\r\n  \"message\": \"Please do not shutdown until this is completed\"\r\n}"
}

It’s a fog version problem or it’s just a specific configuration checked in the Global Configuration GUI ?

Many thanks for your help