Win7x64 : Golden Image : partitions problems ...
-
@sebastian-roth Well the issue (I see as a non-programmer) is that the fixed partitions names may be in a number if different base languages (I tried to find how many native language versions of windows there are, but failed. I can tell you there are 101 native language packs) managing that many different variations would be huge. Other than their label I’m not sure how we could properly identify the partitions. I’m open for ideas too. I wonder if windows uses a consistent UUID of the partition(??).
We could either poke the right values into the inits using a post install script, or the main inits would have to be able to reach out and read a file on the FOG server that would tell it about the native language for the windows clients. But some how the settings need to be IT Admin configurable. Possibly even via a FOG run time variable where it would pass the real (native language) name of reserved and system partitions… (just thinking out loud here).
-
Hi,
Thanks to Tom … the issue is not completely resolved but “in progress” …- I edited the d1.fixed_size_partitions : “2:1”
- after a new DL of the image, the resultt is :
https://drive.google.com/file/d/0B48PuYLEHxQLWWNDR2E0QWhPZEU/view?usp=sharing
Same result o7010, hp8000 or 640G2.
How can expand the space of C after deploy ?
My stuff :
Server :
FOG Version : Running Version 1.5.9
OS : Debian GNU/Linux 10
FOG Client Version : 0.12
Specifications :
> All images are on a Synology NAS storage : mounted with NAS_ip:/images
> French user :)
> “If everything would work the first time, what would you have learned?”
Challenges make knowledge growth … by George1421 ;) -
@jonathan-cool Remove the 2 in the fixed file and deploy the image to a client…
-
Hi,
If i add only « :1 » in the d1.fixed_size_partitions, i have this error :
https://drive.google.com/file/d/0B48PuYLEHxQLaUMxaWpOcmRnb3M/view?usp=sharingIf i add « 2:1 » in the file d1.fixed_size_partitions and use setupcomplete.cmd to expand the space of C after deploy (by using diskpart utility, https://forums.fogproject.org/topic/1178/extend-your-disk-partition-to-max/4), it work on Optiplex7010 … but NOT in a smaller disk (hp2530p, « Target partition size is smaller than source ») …
-
@jonathan-cool Can you share a picture of the device that fails? (please check for plugged in USB sticks, SD cards and such as well)
-
@quazz Hi,
You wants a picture of the error with the HP2530 computer ?(no usb stick or any SD cards …)
-
@jonathan-cool Yes, plus some info on the disk would be nice too.
-
I used ssh connection to copy and paste the result …
* Imaging using Partclone (gzip) Partclone fail, please check /var/log/partclone.log ! ################################################## # # # A warning has been detected! # # # #################################################### Image failed to restore and exited with exit code 1 (writeImage) Info: Partclone v0.2.89 http://partclone.org Starting to restore image (-) to device (/dev/sda2) note: Storage Location xxxxx/images/, Image name ImgUniverselle we need memory: 5247876 bytes image head 4160, bitmap 5239616, crc 4100 bytes Calculating bitmap... Please wait... get device size 159935889408 by ioctl BLKGETSIZE64, Target partition size(159936 MB) is smaller than source(171692 MB). Use option -C to disable size checking(Dangerous). Args Passed: /images/ImgUniverselle/d1p2.img* /dev/sda2 ###################################################### # # # Will continue in 1 minute # # # ##################################################### * Press [Enter] key to continuefdisk -l on the hp2530p :
Disk /dev/ram[0 – 15] : 124 MiB, 130048000 bytes, 254000 sectors ## there is many ram disk here ... Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc91a5cff Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sda2 206848 312581631 312374784 149G 7 HPFS/NTFS/exFAT -
@jonathan-cool Makes sense. With 2:1 it will think that the OS partition shouldn’t get resized, so it reads the original size (which is 160GB) which in turn is bigger than the target hard drive.
I am not sure why :1 by itself wouldn’t work though.
Can you try leaving the file empty and see if that helps?
I have Dutch Windows which also doesn’t get have reserved system picked up properly and for me the file is simply empty. Which seems to work alright.
-
@quazz said in Win7x64 : Golden Image : partitions problems ...:
Can you try leaving the file empty and see if that helps?
Failed … and same error.
But i agree with your idea and, it’s make sense.Maybe i don’t use the right process to create my VM into Virtualbox …
I choosed a 160Gb Virtual Size disk … -
@jonathan-cool Dynamic or Static? (Dynamic could cause issues, not to mention it’s slow)
You do seem to have a lot of empty space in your virtual environment, but this shouldn’t really impact the deployment process, imo.
Resizable image type should be able to resize it correctly.
-
During creation process of Golden Image, in VirtualBox, i choosed Dynamic disk …
On VirutalBox, i can see : Virutal Size : 160Gb. -
I’m alone now ? …
-
@jonathan-cool Sorry, forgot to reply.
As far as I can recall, dynamic disk can give issues for resizable image type. I haven’t been able to find when/how this was a problem using the search, however.
Only advice I can give is to try and make it a fixed size drive and see if that helps at this point
-
Marked this solved as the initial issue can be circumnavigated and we have a github issue open on that topic.
