Deploy OK, but system won't boot (stays looping in Fog menu)
-
if it’s a simple standard image of windows 7 enterprise, there should only be 2 partition img files
-
Well, it has drive C and D, so thats why it has 3. But that shouldn’t be a problem.My HDD are 1TB (all equal).My computers are i7 4770, in an Asus B85M-G motherboard,mwith 8GB RAM. I have latest BIOS (0908) and UEFI is disabled (legacy mode).After preparing the image (with fogprep and all), I shut down the computer. Then, make an image using Acronis TrueImage and then I upload the image.If I deploy it in Fog, I have the problem of after the Fog menu getting an bkank screen.If I use Acrojis to restore image from external HDD, then image is correctly deployed, name is changed by Fog, and the machine is added to my Active Directory.
-
So, I’m guessing it is something with the image itself… or not being correctly uploaded, or not being correctly deployed.One question… can I use a boot disk with some software that creates an image compatible with Fog 1.1.0, save it to an external HDD, and then manually placing it in the image folder?
-
I’m sorry for asking this again… but I would really appreciate if I could get someone’s help.
My images are being deployed, but them computer won’t boot.
How can I assure images are uploaded successfully and then deployed also successfully? -
That’s why we keep asking if you partitions are in GPT format.
Start an upload-debug or download-debug task.
When you’re at the “command” prompt, type:
gdisk -l /dev/sdaWhat is the output?
-
I’ve checked and my images are NOT in gpt.
-
How did you check? There is a reason I ask to get output from the commands above.
-
Well, I checked in the original image… and answered before reading your post… sorry (shame on me).
When I run your command, I get:
“Found valid GPT with protective MBR; using GPT.” -
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present -
Well… this is saying I have GPT partition, right?
I searched online about what protective MBR is, and it figures out that:
“You can also see that there is a protective MBR at the first sector of the hard disk. Such hybrid setup is to allow a BIOS-based system to boot from a GPT disk using a boot loader stored in the protective MBR’s code area. In addition, it protects the GPT disk from damage by GPT-unaware disk utilties.” -
I guess this might be a BIOS problem… i read ([url]http://technet.microsoft.com/en-us/library/dn336946.aspx[/url]) that if I had my BIOS in compatibility mode, the Windows should automatically create partitions in MBR…
As it is creating them in GPT, I’m assuming that BIOS isn’t passing the right info to Windows. Going to check how to overcome this and get back soon.Meanwhile… shouldn’t GPT partitions also work in Fog? Is there any configuration I need to make?
-
They should work for fog but only for imaging. Not currently passing back to Uefi. Meaning to image disable secure boot->net boot->image-> reenable secure boot-> do not NetBoot
-
Tom:
Thank you for your patiente…
-
Just started a new image… made sure every boot option in BIOS were set to Compatible Mode.
In WinPE, used DISKPART to clean disk entirely.
Started Windows Setup from USB flash drive.
When I got to
Started setup and created partition for OS. Finished setup and went to Disk Management - Disk 0 - Properties says it’s MBR
Started Image-Download Debug and run #gdisk -l /dev/sda
It says:
Partition table scan:
[INDENT=1]MBR: MBR only[/INDENT]
[INDENT=1]BSD: not present[/INDENT]
[INDENT=1]APM: not present[/INDENT]
[INDENT=1]GPT: present[/INDENT]Founf valid MBR and GPT. Which do you want to use?
1 - MBR
2- GPT
3 -Create blank GPTYour answer:_
So I guess somethings happen when i upload my image. Seems like Fog is converting MBR to Protective MBR the partition where Windows 7 is installed. Maybe it is getting confused about Microsoft Reserved Partition is in GPT format.
What do you think?
-
If everything is Legacy based, the FOG Installer will install it as MBR based image. If the system is in and type of UEFI mode, it will automatically default to GPT.
My guess is the boards not properly disabling UEFI.
-
To bypass this… do you think it is possible to install everything until image is ready, then use older computer to upload image (by older I mean withouth EFI)?
I mean, install HDD from my new system in a Lagacy computer…
-
That wouldn’t work because the drive partitioning would already be setup in GPT.
-
Another message that I’m getting might be important.
I’ve created a simple image, made sure Windows 7 was on a MBR partition.
When I made an Upload with Debug, when I execute #gdisk -l /dev/sda, i receive also this information:
Found invalid GPT and valid MBR; converting MBR to GPT format.
I guess it’s here the problem… the drive isn’t in GPT before uploading… it’s at that moment that it is converted to GPT.
-
DISKPART erases partitions, but i don’t think it modifies the boot sector. you didn’t wipe the old gpt data off the drive. you can use gdisk to wipe the boot sector
-
(after reading all previous posts and the following thread: [url]http://fogproject.org/forum/threads/clonezilla-works-fog-does-not-both-use-partclone-0-2-69-help-please.10699/[/url])
I have 35 computers with ASUS B85M-G motherboard. They all have an Intel 4770 processor and 8 GB RAM.
This board is UEFI, but as a CSM (Compatibility Support Module) with is enabled and all configurations are set to “Legacy OPROM only”. This options I set are:
[INDENT=1]Boot Device Control[/INDENT]
[INDENT=1]Boot from Network Devices[/INDENT]
[INDENT=1]Boot from Storage Devices[/INDENT]
[INDENT=1]Boot from PCI-E/PCI Expansion Devices[/INDENT]
Secure boot is set as:
[INDENT=1]OS Type = “Other OS” (the other option was “Windows UEFI mode”).[/INDENT]My server is a x64 Intel system, with CentOS 6.5 (updated). Had previously Fog 0.32 working here. Reinstalled OS and installed non-official version 1.1.0 of Fog (through SVN). Installed Fog and everything is working fine (hostname changer, add to AD tested so far), except for the deployment of images.
Here are a few experiments I made to help debug this problem:
[B]Experiment #1A[/B] - Made in computers with ASUS B85M-G motherboard (UEFI in Legacy Mode)
Made a “Download Debug” job in Fog and, at prompt, typed:
[INDENT=1]# sgdisk -Z /dev/sda[/INDENT]
Rebooted and started Windows 7 Enterprise x64 installation. Accepted License Agreement and chose Custom Installation (Advanced).
Created a 200GiB partition and Windows automatically created also an MSR partition (100MB). Created another partition with the remaining space. Chose the 200GiB partition to install Windows into and pressed Next. Windows copied files, extracted files and so on.
After reboot, uploaded image immediatly with an Upload task in Fog (image created as “Multiple Partition Image - Single Disk (not resizable)”)
Then, in the same computer, without changing anything, created a Deploy task in Fog and all went well. After image was deployed, computer shows default Fog menu, but after 3 seconds it starts loops in other menu (a different type of menu, with blue background and text options on the left) every 3 second ([I]see attached img2.jpg[/I])
Went to BIOS and deactivated boot from NIC. Turned computer on, but doesn’t boot… returns to BIOS after a few seconds, never booting
This type of image upload/deploy is [COLOR=#800000][B]not working[/B][/COLOR] on this type of system.
Configured machine to Download Debug and at the “command prompt” typed:
[INDENT=1]gdisk -l /dev/sda[/INDENT]
Got:
[INDENT=1]Partition table scan:[/INDENT]
[INDENT=2]MBR: protective[/INDENT]
[INDENT=2]BSD: not present[/INDENT]
[INDENT=2]APM: not present[/INDENT]
[INDENT=2]GPT: present[/INDENT]
[INDENT=1]Found valid GPT with protective MBR; using GPT.[/INDENT]
[INDENT=1]Disk /dev/sda: 1953525168 sectors, 931.5 GiB[/INDENT]
INDENT=1[/INDENT]
[INDENT=1]Number Start (Sector) End (sector) Size Code Name[/INDENT]
[INDENT=1]1 2048 206847 200.0 GiB 0700 Microsoft basic data[/INDENT]
[INDENT=1]2 206848 1953519615 931.4 GiB 0700 Microsoft basic data[/INDENT]
([I]see attached img1.jpg[/I])[B]Experiment #2[/B] - Made in computers with ASUS B85M-G motherboard (UEFI in Legacy Mode)
Made a “Download Debug” job in Fog and, at prompt, typed:
[INDENT=1]# sgdisk -Z /dev/sda[/INDENT]
Rebooted and started Windows 7 Enterprise x64 installation. Accepted License Agreement and chose Custom Installation (Advanced).
Created a 200GiB partition and Windows automatically created also an MSR partition (100MB). Created another partition with the remaining space. Chose the 200GiB partition to install Windows into and pressed Next. Windows copied files, extracted files and so on.
After reboot, uploaded image immediately with an Upload task in Fog (image created this time as “Single Disk (NTFS only, Resizable)”).
Gave me an error saying this type of image only allows for a maximum of 3 partitions.
Went to Windows and removed the partition with the remaining space and expanded the 200 GiB partition to use all free space (then, I got the MSR partition and a second partition with the remaining space where Windows was installed; the 3rd partition is MBR).
Then, in the same computer, without changing anything, created a Deploy task in Fog and all went well. After image was deployed, everything is [COLOR=#339966][B]working fine[/B][/COLOR].
The only difference from the original image that was uploaded is that I got a not used 9,31 GiB of disk space.
Configured machine to Download Debug (to compare with previous experiment results) and at the “command prompt” typed:
[INDENT=1]gdisk -l /dev/sda[/INDENT]
Got:
[INDENT=1]Partition table scan:[/INDENT]
[INDENT=2]MBR: MBR only[/INDENT]
[INDENT=2]BSD: not present[/INDENT]
[INDENT=2]APM: not present[/INDENT]
[INDENT=2]GPT: damaged[/INDENT]
[INDENT=1]Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.)[/INDENT]
[INDENT=1] 1 - MBR[/INDENT]
[INDENT=1] 2 - GPT[/INDENT]
[INDENT=1] 3 - Create blank GPT[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Your answer:[/INDENT]([I]see attached image img3.jpg[/I])
If I answer 2, I get what’s in [I]attached img4.jpg[/I].
Then reboot computer and everything is still working fine.[B]Experiment #1B[/B] - Made in computers with ASUS B85M-G motherboard (UEFI in Legacy Mode)
[B]Note:[/B] After running Experiment #2 with only 3 partitions, repeated Experiment #1 with the same 3 partitions, but the result is the same: [B][COLOR=#800000]not working[/COLOR][/B].
[url=“/_imported_xf_attachments/0/916_img1.jpg?:”]img1.jpg[/url][url=“/_imported_xf_attachments/0/917_img2.jpg?:”]img2.jpg[/url][url=“/_imported_xf_attachments/0/918_img3.jpg?:”]img3.jpg[/url][url=“/_imported_xf_attachments/0/919_img4.jpg?:”]img4.jpg[/url]
