Deploy OK, but system won't boot (stays looping in Fog menu)
-
Created simple image (just Windows 7 Enterprise)… no drivers, nothing else.
Uploaded image to Fog (image created with “Multiple Partition Image - Single Disk (Not Resizable)”.
Then, on te same computer with exactly the same settings, deployed image and after Fog menu… nothing (keeps returning to Fog menu).
Booted with the same DVD media I used to install Windows, and when I press “Rapair computer”, it says this System Recovery Options version is not compatible with the Windows version your trying to repair (…)".
Really stuck here, and desperetly needing to have my new 35 machines working for teaching purposes…Any help is really welcome. Thank you guys for being available…
-
Checked /image and all images are there (filetype d1.mbr and d1p1.img + d1p2.img + d1p3.img).
Permissions are 777 -
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.
