I just experienced this problem with a non-sysprepped Win7 image I was dealing with, and the steps listed here, [url]http://fogproject.org/forum/threads/windows-7-without-sysprep.862/[/url] , from lkrms, did the trick for me. Quoted below:

[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]"I wasn’t able to find bcdedit commands to replicate what sysprep does to the system BCD store, but here’s what I did to achieve the same result (using VirtualBox snapshots):[/COLOR][/FONT][/SIZE][/LEFT]

[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]1. Capture a snapshot of a working audit-mode Windows 7 machine. 32-bit or 64-bit doesn’t matter - the BCD data seems to be interchangeable.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]2. Boot your machine, open a command prompt and run: “C:\Windows\System32\sysprep\sysprep /generalize /quit”. The /quit is important; you want the machine to stay up after sysprep so you can collect the BCD store as sysprep leaves it.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]3. If curious, run: “bcdedit /enum”. You’ll see what sysprep has done to your BCD store.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]4. Capture your BCD store: “bcdedit /export C:\generalized.bcd”. Save the resulting file with your other deployment files; mine ends up living in C:\Windows\System32\sysprep alongside my unattend.xml etc.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]5. Feel free to discard the sysprep’d virtual machine. Restore to your step 1 snapshot or similar.[/COLOR][/FONT][/SIZE][/LEFT]
[LEFT][SIZE=13px][FONT=Tahoma][COLOR=#141414]6. As part of your FOG pre-capture workflow, when not using sysprep, run “bcdedit /import generalized.bcd”."[/COLOR][/FONT][/SIZE][/LEFT]

Hi all,

I have a real mystery here. I’m trying to reimage a variety of netbooks with a Fog image of Windows 7 Enterprise, etc… Some are HP Minis, some are various Acer, and some are Asus EEEpcs. The Asus EEEpcs are giving me grief.

In general, all the netbooks start PXEboot and begin imaging, although the EEEpcs sometimes need a couple of tries before they get a DHCP lease. But on the EEEpcs only, imaging stops at random points. 5%, 8%, 55%. Eventually, one EEEpc took the image after 4 attempts.

The message I get is:
$MFTMirr does not match $MFT (record 0).
Failed to mount ’ dev/sda2’: Input/output error
[FONT=Verdana][COLOR=#333333]NTFS is either inconsistent, or there is a hardware fault, or it’s a[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]then reboot into Windows twice. The usage of the /f parameter is very[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]important! If the device is a SoftRAID/FakeRAID then first activate[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]it and mount a different device under the /dev/mapper/ directory, (e.g.[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]/dev/mapper/nvidia_eahaabcc1). Please see the ‘dmraid’ documentation[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]for more details.[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]unmount: can’t unmount /ntfs: Invalid argument[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Done[/COLOR][/FONT]

[FONT=Verdana][COLOR=#333333]*Updating Computer Database Status[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]*Database Updated![/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]*Task complete, computer will now restart[/COLOR][/FONT]

Again, the other netbooks take the same image no problem, so I don’t think it’s an image problem. But I’m not sure what’s up. I’ve tried a different switch. I don’t know why it’d work after several attempts. My gut feeling is that the netbooks might have flaky NICs…but…all of them? I could look at kernel updates but I’d think that be more of a problem if the netbooks wouldn’t even PXEboot. That being said, PXEbooting is a bit of an issue. I’ve seen similar posts on the forum but they seem to be failing for all, whereas this is only failing on these EEEpcs, and only some of the time. ???

Any ideas?
Thanks in advance,
Sir_Timbit[FONT=Verdana][COLOR=#333333][/COLOR][/FONT]

Hi there,

Does anyone have some guidelines as to what’s all involved in moving a Fog server from one location to another, in terms of adjusting all the assorted IP address settings and still have Fog work.

A Fog server at one of our schools died recently. It’s a smaller school and not a whole lot of computers to deal with, but I’d prefer to set up the Fog server here at our head office , as opposed to the school. However, I always seem to have grief adjusting IP address settings and still have Fog work as expected. I adjust the IP address of the Fog server, and adjust whatever settings I can find in “Fog Settings” to point to the new address of the Fog server. However, after doing so, I usually end up having problems with either the PXEboot menu not working properly, or just not being able to image a machine.

Not worried about images or clients in the database, etc. Just wondering–is there more to moving a Fog server from one location to another, and still have it work? Do you need to rerun Fog setup or should adjusting the IP address settings in the Fog console and on the Linux box itself be enough?

Thanks in advance for any help,
Sir_Timbit

Reinstalled Ubuntu/Fog, restored the database, and PXEboot on the clients is working again. There was a probably a simpler way to get it going without being so drastic, but I was running out of time…

Hi there, I had a working Fog server setup, until the motherboard died. I had a spare tower available that was similar enough, so I put the hard drives that were in the old Fog server into the new box, adjusted Ubuntu so that eth0 was set to the MAC address of the onboard NIC on the new motherboard. Kept the same IP address. And that was it. I could access the web interface and everything seemed fine. However, today I discovered my client PCs won’t PXE boot. So I’m assuming there is a setting somewhere where I have to tell Fog the new MAC address of the new box. But I haven’t found it yet. Any ideas? Again, the IP address remains the same as it was before.

Thanks in advance,
Sir_Timbit