Menu

Kernel Panic regression (happens only when invoking the 'To RAM' option of Clonezilla)

2017-07-23
2017-07-23
  • Ken Pergola

    Ken Pergola - 2017-07-23

    Hello,

    There seems to be a regression that has been introduced since Clonezilla live 2.5.2-17 or 20170626-artful were first released -- at least on both of my machines that worked fine before Clonezilla live 2.5.2-17 or 20170626-artful were released.

    The issue that I am getting a Kernel Panic and it happens only when invoking the 'To RAM' option of Clonezilla.

    run-init: /sbin/init: No such file or directory
    [   14.513811] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 
    

    I even tried the recent 'clonezilla-live-20170717-artful-amd64.iso' image and it also produces a Kernel panic using the 'To RAM' option.

    I am not sure if this OneDrive screen shot of the Kernel panic dump will come through or not:

    https://onedrive.live.com/?id=D9D8C35D1490E72C%21107&cid=D9D8C35D1490E72C

    Has anyone else seen this issue when running Clonezilla via the 'To RAM' option?

    Thanks very much.

    Best regards,

    Ken

     
  • Ken Pergola

    Ken Pergola - 2017-07-23

    The last release that does not exhibit this Kernel panic with the 'To RAM' option is:
    'clonezilla-live-20170220-yakkety-amd64.iso'.

    So something appears to have regressed sometime after the 'clonezilla-live-20170220-yakkety-amd64.iso' release.

     
  • Steven Shiau

    Steven Shiau - 2017-07-23

    What did you mean?
    The "To RAM" options in the latest Clonezilla live (2.5.2-17 or 20170626-zesty) work very well here. You can try the iso file in the virtual machine then you will see it works. Did you customize your Clonezilla live?

    Steven

     
  • Ken Pergola

    Ken Pergola - 2017-07-23

    Hello Steven,

    Thank you very much for your time and help.

    Update -- I have an interesting data point to report.

    (I don't expect any more help from you but thought I would just update this thread for closure and in case it may help others.)

    I have not customized my Clonezilla but I have always used YUMI – Multiboot USB Creator to boot and run Clonezilla from a USB drive. Specifically I am using YUMI-2.0.4.9.exe.
    https://www.pendrivelinux.com/yumi-multiboot-usb-creator/

    Today I decided to burn 'clonezilla-live-20170626-zesty-amd64.iso' to a DVD and selecting the Clonezilla menu item 'To RAM, Boot Media can be removed later' it loads fine without any Kernel Panic issue.

    So this test proves that the 'To RAM' option works with 'clonezilla-live-20170626-zesty-amd64.iso' when booting from a DVD.

    So it seems somehow there is some interaction between later versions of Clonezilla and YUMI that causes this regression that I don't fully understand with regard to the 'To RAM' menu item and the Kernel Panic.

    YUMI-2.0.4.9.exe works fine with'clonezilla-live-20170220-yakkety-amd64.iso' but for some reason using it with later versions of Clonezilla causes a Kernel Panic.

    Thank you for your time and help Steven.
    I will try to contact PenDriveLinux and refer them to this thread.

    Best regards,

    Ken

     
  • Steven Shiau

    Steven Shiau - 2017-07-24

    Got it. So you have found the culprit. Did you try Tuxboot instead of YUMI?

    Steven

     
  • Ken Pergola

    Ken Pergola - 2017-07-24

    Hello Steven,

    Thanks very much for telling me about Tuxboot.

    Yes, 'tuxboot-0.8.3.exe' allows me to use the 'To RAM' menu option with 'clonezilla-live-20170626-zesty-amd64.iso' and there is no Kernel Panic.

    I contacted PenDriveLinux about this issue I have experienced so hopefully someone there may be able to know what the issue is and fix it. YUMI version 'YUMI-2.0.4.9.exe' and also prior/older versions of YUMI can't seem to work together on both my PCs without a Kernel Panic on 'clonezilla-live-20170626-zesty-amd64.iso' and using Clonezilla's 'To RAM' menu item.

    I like YUMI because I can install multiple ISO images and choose whatever I want to run with the menu it has, but at least I have a workaround right now with Tuxboot.

    Thanks very much for your time and help -- it is greatly appreciated!

    Best regards,

    Ken

     

Log in to post a comment.

MongoDB Logo MongoDB