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

[lebrun78]

Server

• FOG Version: 1.3.4
• OS: centos 6.8

Client

• Service Version:
• OS: windows 7

Description

I upgraded my fog server yesterday from 0.32 to 1.3.4

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

I’ve upgraded the kernel, I get the same problem.
I suppose it’s due to my particular nfs and ftp configuration ?

[lebrun78]

Hello

I add this code in my dhcpd.conf, and it works

group {
# Groupe pointant vers le pxe du nouveau serveur  Fog                                                                                                                                                                                                                           
        next-server 148.60.4.10;
#        filename "pxelinux.0";                                                                                                                                                                                                                                                 
#         filename "ipxe.efi";                                                                                                                                                                                                                                                  
# next-server 148.60.15.121;                                                                                                                                                                                                                                                    
class "Legacy" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
        filename "undionly.kkpxe";
    }
    class "UEFI-32-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
        filename "i386-efi/ipxe.efi";
    }
    class "UEFI-32-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
        filename "i386-efi/ipxe.efi";
    }
    class "UEFI-64-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
        filename "ipxe.efi";
    }
    class "UEFI-64-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
        filename "ipxe.efi";
    }
    class "UEFI-64-3" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
        filename "ipxe.efi";
    }

[george1421]

This is interesting. Your dhcp server configuration file looks good. Where we typically see this error is when the dhcp server is still configured to send out pxelinix.0 (which was used in the older versions of FOG). Pxelinux.0 will cause this kernel syncing error.

The other issue we’ve seen is if the FOS kernel (bzImage) is not consistent with its virtual hard drive (init.xz) (i.e. old bzImage kernel with new inits). Please inspect (on the fog linux console) /var/www/html/fog/service/ipxe directory. Make sure the dates on bzImage, bzImage32, init.zx, and init_32.xz are all in a reasonable date span (days not weeks).

[lebrun78]

@george1421
since i added this code in my dhcpd.conf, it works.
I added kernel panic without this options in my dhcpd.conf

[george1421]

@lebrun78 OK just to be clear, you had something else configured for your dhcp options before you added the code below.

The idea is to document the before and after your fix for others that may find your thread later.

Either way I’m glad you got it worked out, the current release of FOG is just amazing. You may need to deploy your images and then recapture them using FOG 1.3.x to take advantage of some of the performance improvements.

[lebrun78]

@george1421
I had Pxelinux.0 in my dhcp, the new code replace it now.