Can't get dhcp address.. even if I do a -dhcp in my settings.txt

Question

Ok odd problem. I have already tried the Jan 2010 update to see if it
fixes, no go.
I'm imaging an HP Elitebook 8530w.. I've already done these without issue.
I select maintenance mode imaging and I get the Linux splash screen and
it sits there. If I hit escape to see the console it's got
Sending DHCP Request to eth0...
ctrl-alt-f3 shows scrolling errors of
err, eth0: ARPOP_REPLY received from 192.168.11.98 (mac address here)
In my settings.txt I made the following change
netsetup=-dhcp,now,all
Then I gave it a static ip with the hostip, netmask and gateway commands.
Not my preferred route but I'm on a deadline.
No effect. It's still sending dhcp server requests. I stopped and
started the imaging server as well.
Why is it still trying to do a dhcp request when I have -dhcp in there?

Answer 1

Originally Posted by grimlock
On 2/2/2010 12:45 PM, Patrick Farrell wrote:
> Ok odd problem. I have already tried the Jan 2010 update to see if it
> fixes, no go.
>
> I'm imaging an HP Elitebook 8530w.. I've already done these without issue.
>
> I select maintenance mode imaging and I get the Linux splash screen and
> it sits there. If I hit escape to see the console it's got
>
> Sending DHCP Request to eth0...
>
> ctrl-alt-f3 shows scrolling errors of
>
> err, eth0: ARPOP_REPLY received from 192.168.11.98 (mac address here)
>
> In my settings.txt I made the following change
>
> netsetup=-dhcp,now,all
>
> Then I gave it a static ip with the hostip, netmask and gateway commands.
>
> Not my preferred route but I'm on a deadline.
>
> No effect. It's still sending dhcp server requests. I stopped and
> started the imaging server as well.
>
> Why is it still trying to do a dhcp request when I have -dhcp in there?
FYI I just ran into this again, and I remembered I had posted about it
earlier. Sweet I thought I will just look up the solution. Well there
was none posted. As I've grown older and wiser since I originally
posted this I figured out what it was.
It's an IP Address conflict. Whatever device is the culprit this time
isn't pingable, but the mac address listed on the error line is not the
mac address of the machine you are imaging but rather of the offender.
I didn't pick up on that last time around. For whatever reason it
didn't have anything in dhcp console for this address so it kept giving
it out again. As a temp workaround I assigned a manual bogus mac to
that IP address it was receiving to prevent any devices from being
assigned to it (because it's already in use). After a few days when
leases expire, I'll delete that entry. It's possible that some brain
child manually assigned an IP to their machine. I'll have to track it
down later.
I have the same problem, and your solution worked perfectly. Thanks for this as you have saved me a lot of time in troubleshooting!