DHCP FAILED
-
Sebastian :
I do this in the day
Thanks -
@jeremyvdv said in DHCP FAILED:
Regarding the DELL I do not understand … what should I do?
The typical problem in the Dell firmware the disk controller mode is configured for Raid-ON even if the computer only has a single disk. Go into the Dell firmware (BIOS) and change this mode from Raid-ON to AHCI and then test imaging. You can leave the disk mode in AHCI mode without a problem.
-
Hello
on my dell
Whether I’m in AHCI mode or RAID mode … I always have this message:
-
@jeremyvdv said in DHCP FAILED:
Whether I’m in AHCI mode or RAID mode … I always have this message:
This isn’t a hardware issue or a FOG issue, but you have bitlocker enabled on that target computer. This is a warning from FOG saying that a partition is protected by bitlocker. If you were to clone this disk, it would not boot on the new target computer because the tpm chips are different.
Disable bitlocker on all disk partitions and attempt to capture again.
-
That’s what I understood also yes but the problem is that bitloker is not activated.
Bitlocker can be activated from the bios?
Because on windows it is notthanks a lot for your help
-
@jeremyvdv Try this:
manage-bde -status manage-bde -off C: -
that’s what I did yes.
Same problem
and the HP post always at the same point DHCP failed -
I disabled the TPM in the bios but here is the problem I have now
-
my capture is in court it’s good.
It was necessary to disable the hibernation of the hard disk.
I still have the problem on my hp for DHCP FAILED
IF you have ideas … I test everything in bios
-
@jeremyvdv said in DHCP FAILED:
I still have the problem on my hp for DHCP FAILED
What do you mean by that? We see that you get past the DHCP stuff und ran into other issues. So does the DHCP fail only on random occation??
-
Hello
When I want to capture from an HP post, I always have this message:
I can decend an image on it but not capture
Thanks for your help
-
@jeremyvdv OK for the HP lets take these steps.
- Cancel any current tasks if imaging is still setup.
- Create a new capture task, but before you hit the schedule task button tick the debug checkbox. Then schedule the task.
- PXE boot the target computer like you are going to image it.
- After several screens of text on the target computer that you must clear by pressing enter key, you will be dropped to the FOS Linux command prompt. You may see the error messages again from your last picture but the system will continue to the command prompt.
- Key in the following and post the output picture here.
lspci -nn | grep -i net - Remain in this debug mode because there maybe additional commands based on the answer provided in the picture.
What this command does is print out all of the network interfaces that the HP has onboard. It will also give us the vendor and model numbers of the network adapter. We can then use those numbers for debugging.
-
Thank you for your reply.
I can not do “|” keyboard .
I tried lots of things … an idea?
thank you -
@jeremyvdv said in DHCP FAILED:
I can not do “|” keyboard .
What language keyboard do you have? The pipe symbol ( | ) is kind of a required key for unix.
If you can’t get the pipe symbol then just run the
lspci -nnand hope we get luck that the network adapter is towards the end of the list. -
that’s what I get with this command:
-
@jeremyvdv
Luckily the answer I was looking for is the realtek ethernet adapter [10ec:5227] RTS5227 PCI Express CardSo now we know what we are looking for. Let me check a few things.
I see the version of the FOS Linux kernel is 4.19.0 (a bit strange for having 1.5.7 installed. But let me look up some things.
Edit: Ugh, RTS5227 PCI Express Card is not the nic adapter, that’s a card reader, which is wrong… The correct card is the intel I218LM [8086:15a2] that should have been supported by the linux kernel since 4.12.0. Very strange.
-
Great if you have any info
i do not understand … what do you want as information -
@jeremyvdv said in DHCP FAILED:
Great if you have any info
i do not understand … what do you want as informationOk so the target computer should be sitting at the FOS Linux command prompt at the moment. Post the output of this command
ip addr showMake sure the network adapter is plugged into the ethernet cable then issue the command. After issuing theip addr showcommand issueuname -aPost both answers to this thread. -
this is what I have:
-
@jeremyvdv Ok from the picture the network adapter appears to be UP as well as we can see a link light. I can see the driver is loaded and is talking to the card because we have a mac address.
At the FOS Linux command prompt lets key in this
/sbin/udhcpc -i enp0s25 --nowand see if we can pick up an IP address now.
