Posts made by need2

I’ve had to switch SATA mode a few times in the past. This article covers what you need to do:

[URL=‘http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation’]http://www.overclock.net/t/1227636/how-to-cha[/URL][URL='http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation’]nge-sata-modes-after-windows-installation[/URL]

So I would remove the referenced registry entries, then shut down and upload an image. That way, when you start the source machine back up, it continues to work as is. But when you push the image to a new machine, Windows sees the trigger to recheck what storage driver to use. Just FYI, that first boot on the new machine could take a while as Windows sorts out its driver business.

Update again. Bug was affecting inventory. Bug resolved in 3388.

Just ran into this too. Giving it a poke.

EDIT:
The drive had Windows 10 on it before, and it worked. After running a fast wipe through FOG, I could no longer get any tasks to work (same error as above). More fiddling inbound.

I saw a difference just in upload from a Dell Precision M4800 with a standard 2.5" HDD, running an i7 and 16GB of RAM. Download will be tested later on a crappy machine.

Have you tried rerunning the installer?

Yeah, that could rule out other issues.

There’s also 32bit efi files in the i386-efi folder.

No problem. Glad to see it was resolved!

Also UEFI can boot much faster, and has smarter support of the firmware interface.

Wait… why are you using Ubuntu 10.04?!

[url]https://help.ubuntu.com/lts/serverguide/installing-upgrading.html[/url]

Or you could use this as an opportunity to go to a different Distro all together. The problem is it looks like mysqlnd was never released for 10.04.

I remember this being an issue with a few revisions, but I have 3365 installed just fine. Let me poke about and see if I can find a fix though.

Granted I am running Debian and not Ubuntu, but its like comparing apples and pears, so close enough.

EDIT: Try sudo apt-get -f install . Then tell me the output.

As Wayne pointed out earlier I fail to detail read sometimes. But just in case this wasn’t covered, are the two different machines (working one and not) running the same BIOS/firmware versions? One BIOS revision can make a world of difference.

Failing drive by chance?

VM Replication is your friend.

Don’t create duplicate posts/threads.

Also, I think changing this line will keep you from having to enter in the TFTP server IP manually into each workstation:

You have:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe[/CODE]

Change to:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe, <tftp-server-ip-goes-here>[/CODE]

Reference:
[url]http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html[/url]

I follow. So its the SysAdmin’s responsibility on their end, not the FOG Project’s responsibility.

Right, but you still have to get the hardware to actually let you write the ROM to it. And some manufacturers make their firmware harder to write to than others. And there’s just so many variables to consider when you are trying to take so many manufacturers and models into account.

Well I have always been interested in firmware coding. Hey, maybe I could build a set of ROMs for everyone to install on their devices they want to use with FOG!

No, not really. I’m not going to do that.

I was getting all sorts of weird packets from dnsmasq when I was fiddling with it. It looks like it does some really hacky things to inject the extra DHCP code without being a DHCP server.