Unsolved Win7x64 : Golden Image : partitions problems ... again
-
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,12GoWindows disk Manager on VM :
https://drive.google.com/file/d/0B48PuYLEHxQLUEU5clJOZC1Vb3c/view?usp=sharingDefinition of golden image on FOG GUI :
https://drive.google.com/open?id=0B48PuYLEHxQLdXlTcW90RS1DWncWindows disk Manager on HP8000 after deploy :
https://drive.google.com/open?id=0B48PuYLEHxQLdzRHb0EtY1k2NkUWe 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=0B48PuYLEHxQLSUdpam1STEV0cjgOn 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 … :
-
-
@Quazz Thanks again for your work on this! I’ll add this soon but have one more question about it, see on github.
What are your thoughts on https://forums.fogproject.org/topic/12428/win7x64-golden-image-partitions-problems-again/29 as an alternative system, by the way?
Good you reminded me on this! I moved the issue from repo fogproject to fos#18 where it belongs now that we have those things separated a while ago. Please let’s try to collect information and ideas there.
@Jonathan-Cool Nice you got it working! We’ll add Quazz pull request anyway for the time being. Should be in there in the next couple of days. I’ll mark this solved now.
-
@Jonathan-Cool Glad to hear it’s working
Hopefully this will be fixed in the inits soon enough too.
-
Today, i’m the very happy french of the world … 'cause it’s WORKS !
I tried on o7010, o5050 and o7050 and it’s works !
Wahouuuuuuuuuuuuuuuu
I just want to say many thanks to you both and i think, it’s not enough … !Long live to FOG Project
fog.postinit :
sed -i -e "s#[Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd]#[Rr]*[Ss][Ee][Rr][Vv]#gi" /bin/fog.upload sed -i -e "s#[Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd]#[Rr]*[Ss][Ee][Rr][Vv]*#gi" /usr/share/fog/lib/funcs.sh
Label on C drive removed on the Golden image.
Happy Face
Solved !!
-
@Sebastian-Roth Thanks, I probably should have looked into it earlier, but don’t always have the time for such things.
What are your thoughts on https://forums.fogproject.org/topic/12428/win7x64-golden-image-partitions-problems-again/29 as an alternative system, by the way?
Potentially we could combine multiple systems to increase accuracy and reliability, too.
-
@Jonathan-Cool It’s not a mistake, although you could write the line differently since that’s an if regex pattern match, which does work.
*
means any character in pattern matching, which includes é of courseIt worked for my images anyway, so hopefully you can reproduce those results.
-
@Quazz said in Win7x64 : Golden Image : partitions problems ... again:
@Jonathan-Cool My “fuck this shit” solution atm is the following if you’d like to try it
Note that this is experimental and can cause issues on systems with odd labels so use at own risk… but
sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]#gi" /bin/fog.upload sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]*#gi" /usr/share/fog/lib/funcs.sh
In the second line, we can see a “*”, is-it a mistake or not ? (line concerning funcs.sh)
After your answer, i will try :
- to update my fog.postint
- remove my C label
-
@Quazz Thanks heaps for testing and your pull request. Really weird that it was that hard to figure out for the French accents… Looks pretty good to me although I can’t test it.
@Jonathan-Cool I will see if I can manage to build and upload fresh init files in the next couple of days. This way you wouldn’t need to use the sed stuff.
-
@Jonathan-Cool I’d recommend trying both and seeing if it resolves your problem.
I don’t know when/if the PR will get accepted, could be a while.
updated the sed because the escapes got removed again.
-
@Quazz
Hi.
I can try to remove my C label partition and see the result or it’s not necessary anymore ?
Same question for the last “sed” you proposed …Maybe my best option is waiting the fix in a next release … ?
-
So after some testing, I think the main problem was the case pattern matching not being able to match for some reason in FOS. (works fine on my server, however)
I’ve updated my commit to change it to the if pattern matching instead (which I already tested actually works in FOS).
Don’t know when/if it gets merged, but that should resolve issues for French Windows installs at least.
Pull request here: https://github.com/FOGProject/fos/pull/13
-
@Jonathan-Cool My “fuck this shit” solution atm is the following if you’d like to try it
Note that this is experimental and can cause issues on systems with odd labels so use at own risk… but
sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]#gi" /bin/fog.upload sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]*#gi" /usr/share/fog/lib/funcs.sh
This seems to allow the regex to match at least, of course it’s far less precise now. Still don’t know why it hates é so much, but that seems to be the issue unfortunately.
Should also work on English and Dutch systems I think.
-
I will try to remove this label on the C drive and recapture the image … and try a new download on the optiplex 7050.
I will be back !
-
@Jonathan-Cool Ideally it shouldn’t cause any problems, but because the label system seems to be having some issues, it might be a good idea to remove it before capture at least.
That should leave you with an empty fixed_size_partitions file I think…
Still doesn’t answer why the system reserved isn’t matching, it doesn’t really make any sense to me off the top of my head.
-
@Quazz said in Win7x64 : Golden Image : partitions problems ... again:
Did you assign a label to thedrive per chance?
Yes, my
drive is named “System” into my Golden Image … https://drive.google.com/file/d/0B48PuYLEHxQLUEU5clJOZC1Vb3c/view
Maybe this name is confusing FOG ?
-
@Jonathan-Cool Did you switch to a fixed size as I suggested in the previous thread?
Though, I don’t see how that would cause this exact problem, to be honest.
It’s very weird that you get :2 in fixed_size_partitions as I get an empty file on my W7 French installs instead. Did you assign a label to the
drive per chance?
It seems like our efforts haven’t quite made the difference I hoped yet. The regex matches in my bash tests, but doesn’t seem to match in FOS in a real world scenario. I’m rather baffled as to why that is, though.
-
Maybe i choose wrong parameters when i created my VM with Virtual BOX the first time ? (details on the first topic) ?
-
@Jonathan-Cool It’s very strange. The regex should definitely match now, yet it marks the wrong partition as fixed_size for some reason.
I’ve looked over the code and can’t immediatly find anything desperately wrong or incorrect for the time being.
The strange thing, imo, is that it marks the second partition as fixed, whereas we’d expect it to mark none as fixed if it were to fail (unless I’m missing something in the code, but don’t think so)
-
Yes i can !
d1.fixed_size_partitions :
:2
d1.partitions :
label: dos label-id: 0xc91a5cff device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 204800, type=7, bootable /dev/sda2 : start= 206848, size= 335335424, type=7
d1.minimum.partitions :
label: dos label-id: 0xc91a5cff device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 52316, type=7, bootable /dev/sda2 : start= 206848, size= 335335424, type=7
What do you think about that ?
-
@Jonathan-Cool Can you share the contents of d1.fixed_size_partitions d1.partitions and d1.minimum.partitions