@kermit1991 Do you see this issue on all your clients or just when using an USB ethernet adapter? Have you tried using the ethernet adapter together with different clients. Sometimes adapters and client’s BIOS/UEFI firmware just don’t play together well enough. On the other hand some USB ethernet adapters just don’t play nicely altogether. It’s a long process to figure out what exactly the issue is. So start by telling us more about the exact USB adapter you have and make/model of PC/laptop you use.
Posts made by Sebastian Roth
-
RE: Could not select: Exec format error (http://ipxe.org/2e008081
-
RE: /Fog/management page not coming up
@jackiejack said in /Fog/management page not coming up:
PHP Parse error: syntax error, unexpected ‘&’ in /var/www/html/fog/commons/init.php on line 132
Possibly PHP version is too old? Run
rpm -qa | grep php
and post results here. -
RE: ubuntu install issues
@racorac Is this on a complete fresh Ubuntu installation? Please check to see if you already have a
/opt/fog/.fogsettings
file. -
RE: Chromium Image Issues after Updating Server
@rstockham23 Sorry but the important information is not on the picture. Usually there is a message in the blue partclone screen which should give is more hints on what’s wrong. When scheduling the task you can set the checkbox for debug and after the error happens you’ll get to a command shell. There you can check the mentioned log file:
cat /var/log/partclone.log
-
RE: udhcpc **deleting routers**
@satheesh said in udhcpc **deleting routers**:
deleting routers
That is not the issue I reckon. My guess is that the client fails to reach out to the FOG server via HTTP. Newer versions of FOG check HTTP connection after they got an IP via DHCP (which seems fine from what you posted). Possibly your have some kind of network filter between your VLANs that don’t allow TCP port 80 (HTTP) from the clients to your FOG server?!
-
RE: INFO: rcu_sched self detected stall on CPU when deploying.
@foguser438 Have you read through other related posts on the forum yet? e.g. https://forums.fogproject.org/topic/8918/fog-boot-to-fos-rcu_sched-self-detected-stall-on-cpu/
-
RE: Downloading binaries needed....... Failed
@vinodjotshi You probably have a different issue as you don’t seem to have a proxy server in your network. Please open up your own thread and post your question there. Don’t forget to add the version of FOG you are using.
-
RE: Unable to boot to Fog to capture image UEFI
@tthurston said in Unable to boot to Fog to capture image UEFI:
We were able to get past this stage.
From my understanding this is not the case. In the picture you posted first we see a client booting up going straight into a task (probably because one was scheduled for this ethernet adapter’s MAC address) instead of showing the FOG menu. It hangs at this stage.
Now you switched to a different ethernet adapter (new MAC address) and get the FOG menu. Now when you select the inventory it tries to go ahead bit possibly hangs just at the very same stage where FOS (FOG OS, essentially a Linux kernel) is loaded.Again, please tell us the exact model an make of computers and ethernet adapters you have.
Please try using the adapter you had when taking the first picture and add
debug loglevel=7
to the host kernel parameters for this client (see that you have the correct host entry with that MAC address we see in the picture). Then boot up the client. If that does not show more information on screen we might provide a kernel withCONFIG_EARLY_PRINTK
enabled to see if we can get any printout from the kernel at all.By the way, which version of FOG do you use?
-
RE: PXE Menu on two NIC's
@teddue FOG comes with several services which are all bound / configured to use one specific network interface and IP address. For two different network subnets I’d suggest setting up two separate FOG servers. It’s way easier to handle and causes less issues I reckon. If you need to share images you can still setup your own replication job using cron and rsync for example.
-
RE: can't restore to small disk
@salginer The partition layout looks pretty straight forward. Is your Windows partition bitlocker encrypted? Run
manage-bde -status C:
in a admin command shell. -
RE: After update to 1.5.3 node offline and unable to PXE boot.
@Snaggel I think we need to take a look at the network packets being transfered when this issue is happening. Follow the instructions here: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
-
RE: Unable to boot to Fog to capture image UEFI
@tthurston Do other clients (UEFI or legacy BIOS mode) boot and capture fine? I mean are we looking at a general problem with your FOG server (or possibly network) here or is it one particular model hanging at this stage? Please post the full hardware specs of the client you see this issue on.
-
RE: can't restore to small disk
@salginer Can you provide the contents of
d1.partitions
,d1.minimum.partitions
andd1.fixed_size_partitions
from this image you are trying to restore to the smaller disk. It’s most probably some kind of special partition layout issue causing the error. -
RE: Service unavaible after deployment task
@Lemeunier Sounds strange. Possibly your disk is full? Run
df -h
and post output here. -
RE: I don't see some hosts
@LaurentB I haven’t read through the whole thread, so sorry if this has been said and tried already: Did you reset the encryption data in the web UI for this client (see host settings)?
-
RE: After update to 1.5.3 node offline and unable to PXE boot.
@snaggel said in After update to 1.5.3 node offline and unable to PXE boot.:
I upgraded and still have the same error.
Which error exactly is it?? Please take a picture and post here.
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
@george1421 @rboan Were you able to fix this? Could be just a spanning tree issue from what I read so far.
-
RE: Error trying to restore GPT partition tables
@fogmbr There probably is a way around this but it will cost us together some time to figure out and I thing the image shouldn’t be used on the 5570 as is anyway. Starting from the different disks (needs different windows drivers) and probably there is other hardware being different that needs to be addressed after imaging manually anyway. My guess is you are way better of capturing a separate image…
-
RE: Error trying to restore GPT partition tables
@fogmbr Probably the 5570 has a smaller disk? Possibly just a few sectors less. This together with a complicated partition layout can easily cause an issue.
-
RE: Update failed do to wget
@BREIT Please run
apt-get update ; apt-get upgrade
and post what you see on screen. Probably there is an issue with updating some system packages…