Kernel Offset disabled end Kernel panic not syncing: VFS unable to mount root fs
- FOG Version: 1.34
- OS: ubuntu 16.04
- Service Version:
- OS: windows 7
New installed fog server had previous server that was ubuntu 12.04 and .32 fog We had a kernel that worked with all out machines, now with the new setup we can not get the clients to perform any tasks from bootup screen with out getting the kernel offset disables error. Uncertain as to whether this is a permissions issue on ubuntu or if a fog kernel issue. Our DHCP and DNS is controlled by State.
@craigtighe Can/Will you confirm the exact settings of dhcp option 66 and 67?
dhcp option 66 must be the IP address of the new FOG server
dhcp option 67 should be undionly.kpxe (or undionly.kkpxe) Make sure its spelled correctly. Using pxelinux.0 WILL generate a kernel sync error. That is known, fog moved away from syslinux quite a few years ago.
And as Junkhacker said, if you could snap a clear picture with a mobile and place it here we can see the context of the error too.
@craigtighe can we get a picture or video of the actual problem taking place?
had state change to undionly.kkpxe and now my clients can not find tftp . Is There a log file somewhere so that I can see where it is failing. It is as though it is not able to find the file. I did check and the file is there in my tftpboot folder. So before my machines would boot to fog menu and any option I chose I got the kernel error. Now after having the state change dhcp to boot to undionly.kkpxe machines do not boot pxe said can not find the file. Truly stumped.
if you can’t change the DHCP options, then you can rename a copy of undionly.kpxe in the tftpboot directory to pxelinux.0 so that it will be served out, and document it for future reference.
Not really sure about this, but everything did work with old server and we had a kernel that was working fine. Surely there is something that can be done on my end to fix the problem as involving them is always an issue. Every once in awhile I would have to update a kernel and all was fine.
Our DHCP and DNS is controlled by State.
While true, you can request changes. According to this old thread, your issue is probably that you are using
pxelinux.0as your option 067. Ask them to set DHCP option 067 to
undionly.kkpxeThen ask them if they want to be awesome or not, and if they say they do, show them this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence Because eventually you will need UEFI imaging capabilities, plain and simple.