Kernel panic - not syncing: VFS

george1421

Ok first lets put virtual box to the side for a while and only focus on a physical computer (virtual box adds some head aches to the testing, so a physical machine is the best).

You have a dhcp server already. Do you have the ability to make changes to dhcp or is that locked/managed by another group?

I see you are running dnsmasq, so first I want to understand is that required? If it is required, then what is the configuration for dnsmasq?

Tom Elliott

This REALLY sounds/looks like the “bootfile” in use right now is still set to pxelinux.0

cleric.marcos

Thanks for the quick reply.
Yes I manage the dhcp.
I follow this tutorial for the dnsmasq: https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

I will install debian and fog in a desktop and try again. I’ll update the post.

Thanks.

george1421

@cleric.marcos Lets understand what you are doing before you jump and do something. This may avoid a lot of extra work for you.

If you manage the local dhcp server, can you change/set dhcp options 66 and 67?

cleric.marcos

@Tom-Elliott

Do i have to change it to other in the /tftpboot folder?

Tom Elliott

@cleric.marcos What do you mean?

Is your dhcp server trying to hand out pxelinux.0

cleric.marcos

@george1421 I did the changes in the dhcp, but the result war the same.
i follow this tutorial, and the transaction of the image is working, and the xinit the menu shows me the options, but when i select to inventory o any other option, the kernel panic message appear.

in fact, i select deploy, login with the credentials, and ir shows me the image definition that i previously create on the web management, so i asume that this has to be something with the kernel or image booting.

Thank you so much for the help!

george1421

@cleric.marcos OK I’m a bit lost where exactly we are in this thread. Because we’ve jumped around a bit.

I just want to reconfirm everything here.

You updated your campus dhcp server to set dhcp option 66 {next-server} should be the IP address of your FOG server.
You set dhcp option 67 {boot-file} should be undionly.kpxe

This is currently what you have setup?

cleric.marcos

@Tom-Elliott Yes, is trying to hand out the pxelinux.0

# The boot filename.
#dhcp-boot=pxelinux.0,10.5.14.237

Do I have to change it to some other?

george1421

@cleric.marcos Yes for sure. You MUST change the iPXE boot file to undionly.kpxe for legacy (bios) hosts or ipxe.efi for uefi systems. Pxelinux.0 will cause the exact error message you are seeing. That image is old and only left in fog for a highly specific reason (which you don’t need).

cleric.marcos

@george1421
It will be like this?

dhcp-boot=66,ip.fog
dhcp-option=67,undionly.kpxe

george1421

@cleric.marcos for legacy/bios systems yes that is correct.

cleric.marcos

@george1421 I did the change, but it happens the same. kernel panic.

Tom Elliott

@cleric.marcos I think you need to be clear.

You made the change, but this appears to be a linux service. After making the change did you restart the service?

cleric.marcos

@Tom-Elliott after i made the changes i restart the service (/etc/init.d/dnsmasq restart)
do you think I have to wait and install the FOG 1.3.5 RC 15? I see that they remove the pxelinux.0 default file

george1421

@cleric.marcos Wait, you never said you were running dnsmasq. We need all info or we make assumptions based on what we think you have.

Please post your dnsmasq configuration here.

cleric.marcos

@george1421 Oh sorry, i thought I did in my original post.
I follow this tutorial to setup in FOG.
I also have a DHCP in my network. It’s a dnsmasq too.
It’s like this:

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=undionly.kpxe,,10.5.14.237

# rootpath option, for NFS
dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", pxelinux

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
#pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=10.5.14.237,proxy

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

george1421

@cleric.marcos said in Kernel panic - not syncing: VFS:

pxe-service=X86PC, “Boot from network”, pxelinux

Change this line

pxe-service=X86PC, "Boot from network", pxelinux

To

pxe-service=X86PC, "Boot from network", undionly.kpxe

And then on the fog server you need to create a symbolic link from undionly.kpxe to undionly.kpxe.0

ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe.0

cleric.marcos

@george1421
The file is in the folder, and the symbolic link is made:

rwxr-xr-x  6 fog  root   4096 Mar 16 13:35 .
drwxr-xr-x 25 root root   4096 Mar 15 10:41 ..
drwxr-xr-x  2 fog  root   4096 Mar 15 10:31 10secdelay
-rw-r-xr-x  1 fog  root    868 Mar 15 10:41 boot.txt
-rw-r-xr-x  1 fog  root    426 Mar 15 10:41 default.ipxe
drwxr-xr-x  2 fog  root   4096 Mar 15 10:31 i386-7156-efi
drwxr-xr-x  2 fog  root   4096 Mar 15 10:31 i386-efi
-rw-r-xr-x  1 fog  root 199200 Mar 15 10:41 intel7156.efi
-rw-r-xr-x  1 fog  root 220960 Mar 15 10:41 intel.efi
-rw-r-xr-x  1 fog  root  93889 Mar 15 10:41 intel.kkpxe
-rw-r-xr-x  1 fog  root  93937 Mar 15 10:41 intel.kpxe
-rw-r-xr-x  1 fog  root  93969 Mar 15 10:41 intel.pxe
-rw-r-xr-x  1 fog  root 942112 Mar 15 10:41 ipxe7156.efi
-rw-r-xr-x  1 fog  root 981696 Mar 15 10:41 ipxe.efi
-rw-r-xr-x  1 fog  root 866304 Mar 15 10:41 ipxe.iso
-rw-r-xr-x  1 fog  root 344618 Mar 15 10:41 ipxe.kkpxe
-rw-r-xr-x  1 fog  root 344666 Mar 15 10:41 ipxe.kpxe
-rw-r-xr-x  1 fog  root 344118 Mar 15 10:41 ipxe.krn
-rw-r-xr-x  1 fog  root 344884 Mar 15 10:41 ipxe.pxe
-rw-r-xr-x  1 fog  root 123448 Mar 15 10:41 ldlinux.c32
-rw-r-xr-x  1 fog  root 187820 Mar 15 10:41 libcom32.c32
-rw-r-xr-x  1 fog  root  26468 Mar 15 10:41 libutil.c32
-rw-r-xr-x  1 fog  root  26140 Mar 15 10:41 memdisk
-rw-r-xr-x  1 fog  root  29208 Mar 15 10:41 menu.c32
-rw-r-xr-x  1 fog  root  43186 Mar 15 10:41 pxelinux.0
-rw-r-xr-x  1 fog  root  43210 Mar 15 10:41 pxelinux.0.old
drwxr-xr-x  2 fog  root   4096 Mar 15 12:53 pxelinux.cfg
-rw-r-xr-x  1 fog  root 199168 Mar 15 10:41 realtek7156.efi
-rw-r-xr-x  1 fog  root 220448 Mar 15 10:41 realtek.efi
-rw-r-xr-x  1 fog  root  94755 Mar 15 10:41 realtek.kkpxe
-rw-r-xr-x  1 fog  root  94803 Mar 15 10:41 realtek.kpxe
-rw-r-xr-x  1 fog  root  94807 Mar 15 10:41 realtek.pxe
-rw-r-xr-x  1 fog  root 197984 Mar 15 10:41 snp7156.efi
-rw-r-xr-x  1 fog  root 219520 Mar 15 10:41 snp.efi
-rw-r-xr-x  1 fog  root 198176 Mar 15 10:41 snponly7156.efi
-rw-r-xr-x  1 fog  root 219744 Mar 15 10:41 snponly.efi
-rw-r-xr-x  1 fog  root  93515 Mar 15 10:41 undionly.kkpxe
-rw-r-xr-x  1 fog  root  93563 Mar 15 10:41 undionly.kpxe
lrwxrwxrwx  1 fog  root     23 Mar 16 13:19 undionly.kpxe.0 -> /tftpboot/undionly.kpxe
-rw-r-xr-x  1 fog  root  29728 Mar 15 10:41 vesamenu.c32

george1421

@cleric.marcos You might have an older version of dnsmasq on your system than I think.

Lets try this. Change this line

pxe-service=X86PC, "Boot from network", undionly.kpxe

to

pxe-service=X86PC, "Boot from network", undionly

The version of dnsmasq you have may not like the extension on the boot from menu

Then you need to create a new symbolic link:
ln -s /tftpboot/undionly.kpxe /tftpboot/undionly.0

From your picture you can see its launching the section:
pxe-service=X86PC, "Boot from network"

because its printing “Boot from network” on the screen. I’m guessing it didn’t like the .kpxe as part of the boot file.

If this doesn’t work we’re going to need to get a pcap of the dhcp process to understand what dnsmasq is sending to the target computer.

Kernel panic - not syncing: VFS

222

12.0k

17.3k

155.2k