Unsolved problem : partition is too big for the disk (in deploy)
-
Hello everyone,
Still as part of my deployment tests:
So, I managed to create a capture from a PC master. I linked it to the image.
When deploying the image on a target-pc, here is my error message:
I think this screen will give you more details about my problem :
I am a beginner, forgive my mistakes, what do you advise me to do/change?
Thank you -
I had the same problem :
- Source Disk was 500GB
- Image size (without page-file of course) was 120GB
- Destination Disk was 250GB
My solution was :
- Edit/resize the Souce Disk (With Paragon/MiniToolPartitionMagic…etc) to the approximate size (in my case, i had 1 partition “C:” to 130GB )
- Delete the existing Image from FOG
- Re Capture the Source Disk
- Re Deploy
-
@AlexPDX I re-image and change my partition disk before deployment with MiniToolPartitionMagic ?
I imagine that I can no longer modify my capture of my pc master ? -
@UserBxl well…if you still have the Source PC up and running…you should resize it before capture it to FOG…so that you have an “working source PC” …and i advise you to first of all to ALWAYS make backups before any other changes…that way you can “play” with your system as you wish.
I repete , in my case : the SOURCE disk was biger (even if the actual used size was smaller) , and the DESTINATION (deployment) disk was smaller (even if the captured image was even smaller that the disk)
But first of all…tell me…what disk’s and what partitions did the SOURCE had when you first captured the image ? (if its Thinkbook, i guess its a laptop)
And one more thing…why don’t you select “Resizable” in stead of “Not Resizable” ? …this little thing “Not Resizable” could be the cause for your problem
In theory, if you capture lets say, an WesternDigital 500GB HDD with “Not Resizable” , then you will have to deploy that immage to an identical drive in order for it to work properly.
Thats why i always use “Single Disk - Resizable” …for me it works just fine
But if your “Thinkbook” has 2 hard drives…i don’t know what to say…that is tricky -
@AlexPDX I selected different types of partitions (in FOG image creation) because I got several errors.
I will recreate another image.
Concretely :
- I install a windows10 via USB (in UEFI)
- I enter OOBE mode
- I install Windows ADK & FOG-client$
- I personalize my image: installation of my programs, system settings, drivers, etc.
- I stop the Windows Media Networking service to avoid errors during Sysprep by typing in CMD: net stop wmpnetworksvc (going to o cd c:\windows\system32\sysprep)
- I launch SYSPREP
Do I have an error in my procedure?
I will listen to your advice and incorporate it into my procedure.
-
@UserBxl said in problem : partition is too big for the disk (in deploy):
OOBE mode
…i dont know what to say about this…i have not tried it…here are my captured default images :
-
@UserBxl What does the partition layout look like? Please post the contents of the text file named
d1.partitionsfound in/images/Img_Thinkbook14G3ACL_admin_TEST. -
@UserBxl May I suggest looking at the BIOS . I see you captured an EFI image. Just check the boot settings on the Lenovo make sure it is booting to EFI and not the Auto setting . Also check if secure boot has been disabled.
