• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Kernel panic - not syncing: VFS

Scheduled Pinned Locked Moved Solved
FOG Problems
5
40
16.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    george1421 Moderator @George Lebay
    last edited by george1421 Jul 21, 2016, 1:32 PM Jul 21, 2016, 7:29 PM

    @George-Lebay said in Kernel panic - not syncing: VFS:

    For what it’s worth, in the ltsp.conf file, the boot filename line is set to : dhcp-boot=pxelinux.0

    OK this answers the questions, specifically.

    (I was going to go the easy route, but lets do it right way).

    In the ltsp.conf file change pxelinux.0 to undionly.kpxe and save the settings.
    Then in /tftpboot create a symbolic link from undionly.kpxe to undionly.kpxe.0 (the number zero). You would use a command line ln -s /tftpboot/undionly.kpxe /tftpbppt/undionly.kpxe.0
    Restart dnsmasq.
    PXE boot your client.

    This way when you update FOG and the undionly.kpxe file gets updated, dnsmasq will always have the latest file. You could have just copied undionly.kpxe to undionly.kpxe.0 but at some time when you update fog, these files will get out of sync.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

    G 1 Reply Last reply Jul 21, 2016, 8:03 PM Reply Quote 0
    • G
      George Lebay @george1421
      last edited by Jul 21, 2016, 8:03 PM

      @george1421 First, thanks a lot for your help. Unfortunately I get the same error.

      The Fog menu appears correctly on the client, but then whatever option I choose I get the Kernel Panic message …

      G 1 Reply Last reply Jul 21, 2016, 8:33 PM Reply Quote 0
      • G
        george1421 Moderator @George Lebay
        last edited by Jul 21, 2016, 8:33 PM

        @George-Lebay Did you remember to restart the dnsmasq service? If yes then…

        Is the fog server and the target computer in the same subnet/vlan? If so we’ll need to get a packet capture of the booting process to see what’s going on with the client.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        G 1 Reply Last reply Jul 27, 2016, 5:53 PM Reply Quote 0
        • G
          George Lebay @george1421
          last edited by Jul 27, 2016, 5:53 PM

          @george1421 I have decided to reinstall 14.04 server from scratch and fog 1.2.0 with the latest kernel. I need to start a new thread. Thanks again for your help.

          G 1 Reply Last reply Jul 27, 2016, 5:55 PM Reply Quote 0
          • G
            george1421 Moderator @George Lebay
            last edited by Jul 27, 2016, 5:55 PM

            @George-Lebay Why not go with FOG 1.3.0-rc4? Any reason since you are doing a clean install anyway? Just install the rc version https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            G 1 Reply Last reply Jul 27, 2016, 6:12 PM Reply Quote 0
            • G
              George Lebay @george1421
              last edited by George Lebay Jul 27, 2016, 12:22 PM Jul 27, 2016, 6:12 PM

              @george1421 Well I had this old Proliant ML150 G6 doing nothing and I wanted to use it as my next Fog server. Since Fog is not operational at the moment, and it’s pretty quiet around here (I work in a university) I decided to make the hardware switch.

              About the problem I have now, which is the same problem I had at the very beginning:

              I have 2 models of client PC. HP 6200 and HP Prodesk 600 (that I just received).

              Fog works perfectly well with the 6200, but I when try to register a Prodesk 600, I’m getting this error: Unable to register host for the following reasons:
              Then it gives no reason, and then the system displays some inventory data. Then it just slowly scrolls down forever after it displayed the message attempting to register host …

              I tried to upgrade the kernel, then it just got worst. It did not work on either the 6200 or the ProDesk 600… I was getting this message on both models:
              Unable to register host: Invalid MAC Address! (/bin/fog.man.reg)

              G 1 Reply Last reply Jul 27, 2016, 6:30 PM Reply Quote 0
              • G
                george1421 Moderator @George Lebay
                last edited by george1421 Jul 27, 2016, 12:31 PM Jul 27, 2016, 6:30 PM

                @George-Lebay Right, with FOG 1.2.0 the max kernel version you can use is < 4.4. So in your case try 4.1.2 and see if that works with the Prodesk 600. If not you will need to upgrade to 1.3.0.rc4. Since this is not a production server (yet) then there is no harm in upgrading. (Yeah I know I’m pushing, but the new features in 1.3.0 are worth the extra effort to upgrade).

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                G 1 Reply Last reply Jul 27, 2016, 6:38 PM Reply Quote 0
                • G
                  George Lebay @george1421
                  last edited by Jul 27, 2016, 6:38 PM

                  @george1421 I will make the upgrade to 1.3.0. My fear was to get that Kernel Panic message again (Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)) but since I’m working with fresh server and FOG installations, I’ll give it another try. I’ll let you know what happens then.

                  G 1 Reply Last reply Jul 27, 2016, 6:41 PM Reply Quote 0
                  • G
                    george1421 Moderator @George Lebay
                    last edited by Jul 27, 2016, 6:41 PM

                    @George-Lebay Are you running dnsmasq?

                    But if you upgrade then you have a better chance of getting support since you are on a supported OS and active version of FOG.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                    G 1 Reply Last reply Jul 28, 2016, 1:47 PM Reply Quote 0
                    • G
                      George Lebay @george1421
                      last edited by George Lebay Jul 28, 2016, 7:51 AM Jul 28, 2016, 1:47 PM

                      @george1421 It works ! Thanks for your support 🙂
                      edit : Yes I’m running dnsmasq.

                      1 Reply Last reply Reply Quote 1
                      • 1
                      • 2
                      • 2 / 2
                      2 / 2
                      • First post
                        40/40
                        Last post

                      243

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project