FOG beginner needs help
-
Hi there,
im new to this. Have installed FOG Server 1.20 on Ubuntu 12.04 LTS
I have 34 Machines that i wanted to install. The Machines have all the same Hardware.
My Master has 4 partitions on 2 Disks (1 SSD, 1 SATA HD)
If i restore the Image (Image TYPe=Multiple partition Image, All Disks not resizeable) on an Machine that got the same MBR as the Master everythings boots up fine in Windows 7 64. If i restore it on a Machine with an different MBR (ext Partitions and so on) the Windows 7 boots up and crashes with an BSOD (STOP:00000xF4)
how can i fix that?
-
It sounds like the issue is that once imaged the computer doesn’t know what drive is the boot device. In the commands below replace the drive letter with the OS drive, run it before uploading
[CODE]bcdedit /set {bootmgr} device boot {drive letter}
bcdedit /set {default} device boot {drive letter}
bcdedit /set {default} osdevice boot {drive letter}
[/CODE]You also didn’t specify I assume you are using a sysprep process?
-
Hi there, thx for your help. mmh the thing is, it loads up with windows7 after restore. So i think that is correct with the Drive Letter,
and no i didn’t have used sysprep.
-
Might be worth running a chkdsk on both drives before imaging. [this may rule out filesystem corruption/drive problems]
Can you boot the 2nd machine into safe mode? [this may help pinpoint driver/software issue]
Also, so we understand correctly. If you put this image on another computer of the same model/hardware, it works correctly?
Different model/different hardware does not work ? -
Hii there, i will try to boot the second machine into safe mode, but the hardware in detail is absolutely the same (every 34 Machines)
I go into the direction, that anything with the partition tables are not correct. My Master has 4 Partitions (cause i build them new)
But the Dell Machines that are wating for the Image, has different partitions Linux and so on…
The Image only works correct if on the target machine exists the same Partition Table as on the Master…
-
Timo,
If you are using these computers on a domain you really NEED to use the sysprep process otherwise you will run into issues with Windows 7… XP was a different story due to you could use newsid.
-
[quote=“cadyfish, post: 35401, member: 24458”]Timo,
If you are using these computers on a domain you really NEED to use the sysprep process otherwise you will run into issues with Windows 7… XP was a different story due to you could use newsid.[/quote]
Hi thanks for your advice, but the Machines are not in an Windows Domain
-
Timo,
Are the partitions not being wiped before imaging occurs?
What’s supposed to be happening is the hdd get’s zeroed out then the new mbr get’s written to them which generates the new partition layout.
You’re stating that those with ext partitions aren’t imaging, but the ext partitions shouldn’t even exist at that point if you’re running with the same image to the same machines.
-
The drives should have the same partition table etc after imaging…
Perhaps try a fdisk -l under debug mode or in a linux distro to check.
Verify you have the same partitions on the correct drives.
-
[quote=“Tom Elliott, post: 35403, member: 7271”]Timo,
Are the partitions not being wiped before imaging occurs?
What’s supposed to be happening is the hdd get’s zeroed out then the new mbr get’s written to them which generates the new partition layout.
You’re stating that those with ext partitions aren’t imaging, but the ext partitions shouldn’t even exist at that point if you’re running with the same image to the same machines.[/quote]
Hi Tom, how can i do that, that the hdd’s wiped out, before i restore the Image? Manually create an Task?
-
you say the hardware is exactly the same, but are the hard drives plugged into the same sata ports on the motherboards?
-
[quote=“Junkhacker, post: 35407, member: 21583”]you say the hardware is exactly the same, but are the hard drives plugged into the same sata ports on the motherboards?[/quote]
Hi, yes the Machines are untouched and are all on the same SATA Ports, the Windows 7 boots up, thats the Case, but everytime BSOD
-
[ATTACH=full]1297[/ATTACH][ATTACH]1297[/ATTACH] At this Time i run an Debug-Upload from my Master and made an Screenshot from fdisk-l so you get an Idea how the Partition are look like
[url=“/_imported_xf_attachments/1/1297_IMG_20140818_161525.jpg?:”]IMG_20140818_161525.jpg[/url]
-
ok im finished, after finishing my debug-upload, i restored it again on an Machine, and i looked at it the whole restore process. What comes up, was, that the partition sdb1 wasn’t recognized and don’t get restored, why is that so? And could that be the reason cause of the BSOD? SDB1 is just an NTFS partition on the second normal HDD
-
This post is deleted! -
[INDENT]Maybe try unplug/remove the HDD from the master + a test PC, create a new image with SSD only [multipart single disk], and restore that to the test PC ?
will rule out if the HDD/2nd drive is causing any problems.[/INDENT]
-
Other things you could try that [I]may [/I]help;
chkdsk /f [or /R]
sfc /scannowstart fresh, without the dell recovery partition.
-
[quote=“G0dzilla, post: 35431, member: 1692”]
[INDENT=1]Maybe try unplug/remove the HDD from the master + a test PC, create a new image with SSD only [multipart single disk], and restore that to the test PC ?[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]will rule out if the HDD/2nd drive is causing any problems.[/INDENT]
[/quote]Good Morning everyone, will try that now, i just deactivated the SATA Port from the HDD, its the same. Imaging now and will report back, but at the restore i will let the HDD present in Bios.
Another Thing, imaging with Clonezilla and restore runs, but i have to use USB Stick and thats slow and not an nice Solution, but the Machines runs fine after restore…
-
Ok me again, the new Image with Multiple Partition-Single Disk runs! I’ve made an Image without the Data HDD (deactivated in Bios) and now Windows 7 comes up.
Edit!! Ok wrong alert, after multicastin it to 8 Machines, windows 7 starts but again with Bluescreen, dunno why the one machine runs after the restore, any Suggestions?
Was multicastin it, but why my machines wasn’t woke up? any clue?
-
When you originally received these machines, did they come preloaded with Windows 8/8.1?
Even if they didn’t, do they have UEFI capable BIOS’?
I ask these questions because WOL does not work natively with these that I’m aware of. It also doesn’t have support to enable WOL from the BIOS, you have to boot to windows and use the Power saving modes to enable the WOL parts.
