• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. mbghost
    3. Topics
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 7
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by mbghost

    • M

      Solved UEFI Boot - Kernel panic: Unable to mount root fs on /dev/ram0

      FOG Problems
      • • • mbghost
      10
      0
      Votes
      10
      Posts
      827
      Views

      L

      Hi there
      If someone else reads this and they aren’t using autoexec.ipxe (just the default.ipxe like me) and still has this error I’ve got the solution that worked for me:

      I had to downgrade the GRUB version from 2.12 to 2.06 in my Linux images (mostly Kali Linux).
      Version 2.12 has a bug (bug #67078) which is mentioned here: https://savannah.gnu.org/bugs/?67078

      The downgrade works as follows:
      Create a pin file: sudo vim /etc/apt/preferences.d/grub-pin
      Content of the file:

      Package: grub* grub2* Pin: version 2.06* Pin-Priority: 1001

      sudo apt update
      Downgrade grub packages: sudo apt full-upgrade
      sudo grub-install
      sudo update-grub
      verify the installed version: dpkg -l | grep grub-common

      You can now capture and deploy the the image.

      Edit: of course I am and was using the latest FOG 1.5.10.1667 with newest Kernel and Initrd versions.

    • M

      Solved Unable to Get IP Address After PXE Menu on Physical PC (FOG Project on ESXi)

      FOG Problems
      • • • mbghost
      3
      0
      Votes
      3
      Posts
      471
      Views

      M

      @george1421 Thank you so much! I enabled portfast on the switch port, and it works on physical PCs.

      Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/ram0" or unknown-block(1,0) Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/ram0" or unknown-block(1,0)

      But sometimes this error appears even if I haven’t changed anything in the configuration and files. Even if I update or roll back the init.xz or bzImage file to a previous version, it doesn’t help. The only thing that seems to work is setting up a completely new FOG server, but after some time, the problem can come back. How I can find right version or how I can solve this problem? Most time it error on PCs with UEFI

    • 1 / 1