• 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 Unsolved
FOG Problems
4
25
6.4k
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 @cleric.marcos
    last edited by Mar 16, 2017, 10:04 PM

    @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.

    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!

    W C 2 Replies Last reply Mar 17, 2017, 1:02 AM Reply Quote 2
    • W
      Wayne Workman @george1421
      last edited by Wayne Workman Mar 16, 2017, 7:02 PM Mar 17, 2017, 1:02 AM

      @george1421 My mind is still blown concerning why anyone would have made dnsmasq add stuff to filenames. I’m so so glad that’s fixed now.

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      T 1 Reply Last reply Mar 17, 2017, 11:51 AM Reply Quote 0
      • T
        Tom Elliott @Wayne Workman
        last edited by Mar 17, 2017, 11:51 AM

        @Wayne-Workman I believe they were trying to follow “best practices” and/or “standards”.

        When DNSMasq started to come into existence, I believe the norm was to boot to a “.0” labelled file. So to lessen typing, you could just request pxelinux instead of the whole pxelinux.0 bit of it. (Pxelinux was pretty much the norm at this point I would say.) Of course as more modern nbp systems came out this didn’t hold any more value for reasons we all know too well now.

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • C
          cleric.marcos @george1421
          last edited by Mar 20, 2017, 5:24 PM

          @george1421 and @Tom-Elliott Thank you SO much!
          After some test, I discover the issue.
          I install fog in a desktop, rename the undionly.kpxe, make the soft link, and enable the tftp service on dnsmasq, and it worked!!!
          I documented everything, and made ir again on virtualbox, and it worked, so the problem was me, hehe.
          Thank you very much for all the help and patience. I’am working in cibersecurity, and Iam also in charge of the workstation here, so FOG really help me out.
          Thanks again to both of you.
          If I find a bug o security issue I will notify it.

          See ya!

          T 1 Reply Last reply Mar 20, 2017, 5:29 PM Reply Quote 0
          • T
            Tom Elliott @cleric.marcos
            last edited by Mar 20, 2017, 5:29 PM

            @cleric.marcos You’re more than welcome. I do want to say I did very little to help anything here. I think @george1421 deserves more of the kudo’s here than I do.

            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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • 1
            • 2
            • 2 / 2
            2 / 2
            • First post
              21/25
              Last post

            188

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project