Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Kernel Offset: disabled

[b.nelson]

Server

• FOG Version: 1.4.0
• OS: ubuntu server 16.04.2 LTS (GNU/Linux 4.4.0-31-generic x86_x64)

Description

The problem appears when I try to capture an image system
(Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Kernel Offset: disabled
—[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0))

[Tom Elliott]

Whats output of:

sha512sum /var/www/fog/service/ipxe/init{,_32}.xz
sha512sum /var/www/fog/service/ipxe/bzImage{,32}

They should be:

90744197466056e6c216ae071f6397e0eb1908b15a17ca92d16d88720784bab638673cac83423c766170a2ffa59e06737c171426ffd77aff57c85abfbd4a1dff  /var/www/fog/service/ipxe/init.xz

d1d4ff715da92cd23bf10ea9e8e24913d0da974ac1bc805e9afaae7ae0e9a41fc6577d097b157ced0af1e05400052d3e782bc6abb616f1b7069c8fef037ea062  /var/www/fog/service/ipxe/init_32.xz

c75abc75be06a219920c5c29809436ba66f9d1b5f56af757ee8a28393620e83d0b44f3f8bb582b4e8ad01c4c3e247fde99916d06ff3374631ac3453e042dc3f8  /var/www/fog/service/ipxe/bzImage

0e465ea8c7607377d5f023c5be9838392ba3ef3ab0c793125cde4d5d1cf40c60dc17518be7d6c71ef65e8b261a3d0fce3fa380f6e07bbcaa0fbf59bd72d59b4f  /var/www/fog/service/ipxe/bzImage32

What bootfile are you using to boot from? We often see this error if you’re using pxelinux.0.

[george1421]

Was this an upgrade from a previous release of FOG?

What precisely do you have configured for dhcp option 67 {boot-file}?

[b.nelson]

the output of:
sha512sum /var/www/fog/service/ipxe/init{,_32}.xz
sha512sum /var/www/fog/service/ipxe/bzImage{,32}
is:

user@FOG:~$ sha512sum /var/www/fog/service/ipxe/init{,_32}.xz
90744197466056e6c216ae071f6397e0eb1908b15a17ca92d16d88720784bab638673cac83423c766170a2ffa59e06737c171426ffd77aff57c85abfbd4a1dff  /var/www/fog/service/ipxe/init.xz
d1d4ff715da92cd23bf10ea9e8e24913d0da974ac1bc805e9afaae7ae0e9a41fc6577d097b157ced0af1e05400052d3e782bc6abb616f1b7069c8fef037ea062  /var/www/fog/service/ipxe/init_32.xz
user@FOG:~$

[b.nelson]

@george1421 No, it’s the first time I install FOG and OS to use it.

[george1421]

@b.nelson I’ll follow up with my second question then;

What precisely do you have configured for dhcp option 67 {boot-file}?

And follow up with what hardware are you trying to pxe boot on? (mfg, model)

[george1421]

@george1421 The error message you posted basically means that the FOS Kernel (operating system) bzImage, doesn’t understand the format of its virtual hard drive (init.xz). We’ve seen that happen when the wrong pxe boot file is used or the bzImage file gets out of sync with its virtual hard drive (init.xz)

[b.nelson]

@george1421 It is not a virtual machine

[b.nelson]

This post is deleted!

[b.nelson]

@george1421 Excuse me in what directories can I see this information? And as far as DHCP is by default I have not made any configuration.

[george1421]

@b.nelson OK dhcp is where I would start.

To get the iPXE menu to boot you need to adjust your dhcp server to send the IP address of your fog server for dhcp option 66 {boot-server} and for dhcp option 67 {boot-file] need to be undionly.kpxe for bios systems and ipxe.efi for uefi systems
Let first start with what device is issuing dhcp address for your pxe booting clients? Is it a windows server, router, FOG server or something else?

[b.nelson]

@george1421 With a router and the server is with a static IP

[george1421]

@b.nelson OK good, how is your pxe booting clients able to pxe boot? Did you set the dhcp options in the router or did you enable a service like dnsmasq? Its kind of, sort of working. What’s not clear right now is how??

Did you have fog set up in the past?

[b.nelson]

@george1421 There is a VLAN dedicated to the servers which is handled by static IP.

No, we did not have fog in the past.

[Tom Elliott]

@b.nelson Can you get us this information?

sha512sum /var/www/fog/service/ipxe/bzImage{,32} (I’m just trying to make sure you don’t have a corrupt file along the way.)

Do you see the iPXE Menu on the client machines?

What is providing network addresses to the client machines? (Is this your vmware vlan switch handing dhcp to the client machines?)

[b.nelson]

@Tom-Elliott

root@FOG:/home/user# sha512sum /var/www/fog/service/ipxe/bzImage{,32}
c75abc75be06a219920c5c29809436ba66f9d1b5f56af757ee8a28393620e83d0b44f3f8bb582b4e8ad01c4c3e247fde99916d06ff3374631ac3453e042dc3f8  /var/www/fog/service/ipxe/bzImage
0e465ea8c7607377d5f023c5be9838392ba3ef3ab0c793125cde4d5d1cf40c60dc17518be7d6c71ef65e8b261a3d0fce3fa380f6e07bbcaa0fbf59bd72d59b4f  /var/www/fog/service/ipxe/bzImage32

[Tom Elliott]

When you ran the FOG Installer, did you choose to have it install DHCP?

[b.nelson]

@Tom-Elliott no

[Tom Elliott]

@b.nelson Is there a windows machine somewhere on the vlan handing out DHCP addresses then?

[b.nelson]

@Tom-Elliott In the VLAN there is no DHCP the server is with static IP.

The windows that we want to clone are in another VLAN with DHCP.