LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
Reload this Page [SOLVED] Clonezilla iso won't boot from grub2 menu
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 09-08-2021, 05:35 PM   #1
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Rep: Reputation: Disabled
Clonezilla iso won't boot from grub2 menu

I just closed my previous thread which was about getting Clonezilla to show up on the grub2 menu. Refer to https://www.linuxquestions.org/quest...nu-4175700341/

Now that I have the menu entry for Clonezilla, when I select it at startup it won't boot. It just blinks and goes back to the grub2 menu.

Do I have to make a bios change to boot an iso file? I've had this working on this laptop in the past, and I don't remember having to jump through these hoops.

Any help will be greatly appreciated!
 
Old 09-08-2021, 06:57 PM   #2
jefro
Moderator
 
Registered: Mar 2008
Posts: 21,987

Rep: Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628Reputation: 3628
https://www.linuxbabe.com/desktop-li...b2-boot-loader

See if this matches yours.
 
Old 09-08-2021, 09:14 PM   #3
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jefro View Post
Here is my 40_custom:

Code:
#!/bin/sh
exec tail -n +3 $0
menuentry "clonezilla-live-20210127-groovy-amd64.iso" {
  insmod ext2
  set isofile="/clonezilla-live-20210525-groovy-amd64.iso"
  loopback loop (hd0,5)$isofile
  linux (loop)/live/vmlinuz boot=live findiso=$isofile
  initrd (loop)/live/initrd.img
}
Only the path and file name are different compared to the sample from your link. When I update grub with this file, the menu entry never shows up. The only way I have been able to get the menu entry to show up is with the grml-rescueboot method as follows:

Code:
grml-rescueboot

A very simple way of creating a GRUB menuentry for a bootable ISO file is to use grml-rescueboot.

The package does the following:

    Creates a /boot/grml folder.

    Automatically adds menuentries to the GRUB menu for any ISO files located in the /boot/grml folder. This is accomplished whenever the update-grub command is executed.
    The created menuentry, when selected, provides submenu options on how to boot the ISO, including the "Try Ubuntu" and "Install" options. 

To use the grml-rescueboot option:

    Install grml-rescueboot

        sudo apt-get install grml-rescueboot

    Place bootable ISO files in the /boot/grml folder.
        Since this is a system folder, the operation must be conducted as "root". For example, if the ISO is located in the user's Downloads folder, the command would be:

            sudo mv ~/Downloads/<filename.iso> /boot/grml/

    Update GRUB

        sudo update-grub
The menu entry appears but when I choose it the iso file does not load. The screen just blinks and goes back to the grub menu.
 
Old 09-08-2021, 09:39 PM   #4
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,354

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
from your other thread
Quote:
I have one file in that folder named: "clonezilla-live-2.7.1-22-amd64.iso"
from this post
Quote:
Here is my 40_custom:

Code:

#!/bin/sh
exec tail -n +3 $0
menuentry "clonezilla-live-20210127-groovy-amd64.iso" {
insmod ext2
set isofile="/clonezilla-live-20210525-groovy-amd64.iso"
loopback loop (hd0,5)$isofile
linux (loop)/live/vmlinuz boot=live findiso=$isofile
initrd (loop)/live/initrd.img
}
Which iso file is it

the (Hd0,5) represents the drive/partition the iso file is counting drives from 0 and partitions from 1. Compare your 40_custom to the /boot/grub/grub.cfg menuentry for the grmlboot. The 40_custom you edited is in /etc/grub.d/40_custom?
 
1 members found this post helpful.
Old 09-08-2021, 09:46 PM   #5
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
from your other thread from this post

Which iso file is it

the (Hd0,5) represents the drive/partition the iso file is counting drives from 0 and partitions from 1. Compare your 40_custom to the /boot/grub/grub.cfg menuentry for the grmlboot. The 40_custom you edited is in /etc/grub.d/40_custom?
Sorry, I didn't change the label for the menu entry. But the iso file is correct. Also, I checked the grub.cfg file in /boot/grub and there is nothing there for the clonezilla entry.

I'll change the label to match the iso file name, but I doubt if that will make a difference.

Here is the corrected 40_custom:

Code:
#!/bin/sh
exec tail -n +3 $0
menuentry "clonezilla-live-20210525-groovy-amd64.iso" {
  insmod ext2
  set isofile="/clonezilla-live-20210525-groovy-amd64.iso"
  loopback loop (hd0,5)$isofile
  linux (loop)/live/vmlinuz boot=live findiso=$isofile
  initrd (loop)/live/initrd.img
}
It didn't make any difference. The menu entry does not appear in grub. I know that grub is on this partition, because I can change the time-out value.
Last edited by Tem2; 09-08-2021 at 09:56 PM.
 
Old 09-09-2021, 01:33 AM   #6
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,813
Blog Entries: 1

Rep: Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068Reputation: 2068
You should expect your custom stanza to be picked up as the first entry displayed at the Grub menu at boot by copying or symlinking the original 40_custom to 06_custom and the original 41_custom to 07_custom, and moving your custom stanza to /boot/[grub,grub2]/custom.cfg. With such configuration, I have found it unnecessary to have any concern for the content of /etc/default/grub or /boot/[grub,grub2]/grub.cfg, unless desiring to boot some os-prober-generated stanza from /boot/[grub,grub2]/grub.cfg (not contained in /boot/[grub,grub2]/custom.cfg). The first entry in custom.cfg booted here ATM ~is:
Code:
# head custom.cfg
menuentry "memtest86 8.3 EFI" {
        search --no-floppy --label --set=root P01ESP
        chainloader /mt83x64.efi
}
Following that I have 11 stanzas that boot the various installed operating systems, another for booting an older memtest86 version, then several stanzas that initialize various distro's NET installers by loading those installers' kernels and initrds.
 
Old 09-09-2021, 05:03 AM   #7
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,354

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
Quote:
The menu entry appears but when I choose it the iso file does not load
post the contents of the gmrl menu entry in the grub.cfg
 
Old 09-09-2021, 05:09 AM   #8
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mrmazda View Post
You should expect your custom stanza to be picked up as the first entry displayed at the Grub menu at boot by copying or symlinking the original 40_custom to 06_custom and the original 41_custom to 07_custom, and moving your custom stanza to /boot/[grub,grub2]/custom.cfg. With such configuration, I have found it unnecessary to have any concern for the content of /etc/default/grub or /boot/[grub,grub2]/grub.cfg, unless desiring to boot some os-prober-generated stanza from /boot/[grub,grub2]/grub.cfg (not contained in /boot/[grub,grub2]/custom.cfg). The first entry in custom.cfg booted here ATM ~is:
Code:
# head custom.cfg
menuentry "memtest86 8.3 EFI" {
        search --no-floppy --label --set=root P01ESP
        chainloader /mt83x64.efi
}
Following that I have 11 stanzas that boot the various installed operating systems, another for booting an older memtest86 version, then several stanzas that initialize various distro's NET installers by loading those installers' kernels and initrds.

Here is the terminal output for the following commands:

cat /etc/grub.d/40_custom
sudo-update-grub2
cat grub.cfg (starting at directory /boot/grub)


Code:
master@master-Latitude-E6440:/boot/grub$ cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
menuentry "clonezilla-live-20210525-groovy-amd64.iso" {
  insmod ext2
  set isofile="/clonezilla-live-20210525-groovy-amd64.iso"
  loopback loop (hd0,5)$isofile
  linux (loop)/live/vmlinuz boot=live findiso=$isofile
  initrd (loop)/live/initrd.img
}	
	
master@master-Latitude-E6440:/boot/grub$ sudo update-grub2
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.11.0-34-generic
Found initrd image: /boot/initrd.img-5.11.0-34-generic
Found linux image: /boot/vmlinuz-5.11.0-27-generic
Found initrd image: /boot/initrd.img-5.11.0-27-generic
Found linux image: /boot/vmlinuz-5.8.0-43-generic
Found initrd image: /boot/initrd.img-5.8.0-43-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 on /dev/sda1
done
master@master-Latitude-E6440:/boot/grub$ cat grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${initrdfail}" = 2 ]; then
   set initrdfail=
elif [ "${initrdfail}" = 1 ]; then
   set next_entry="${prev_entry}"
   set prev_entry=
   save_env prev_entry
   if [ "${next_entry}" ]; then
      set initrdfail=2
   fi
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function initrdfail {
    if [ -n "${have_grubenv}" ]; then if [ -n "${partuuid}" ]; then
      if [ -z "${initrdfail}" ]; then
        set initrdfail=1
        if [ -n "${boot_once}" ]; then
          set prev_entry="${default}"
          save_env prev_entry
        fi
      fi
      save_env initrdfail
    fi; fi
}
function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
else
  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=hidden
    set timeout=35
  # Fallback hidden-timeout code in case the timeout_style feature is
  # unavailable.
  elif sleep --interruptible 35 ; then
    set timeout=0
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
	if [ "${1}" = "keep" ]; then
		set vt_handoff=vt.handoff=7
	else
		set vt_handoff=
	fi
}
if [ "${recordfail}" != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-469b1d8e-889c-4feb-96aa-343b03155e27' {
	recordfail
	load_video
	gfxmode $linux_gfx_mode
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
	else
	  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
	fi
	linux	/boot/vmlinuz-5.11.0-34-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro  quiet splash $vt_handoff
	initrd	/boot/initrd.img-5.11.0-34-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-469b1d8e-889c-4feb-96aa-343b03155e27' {
	menuentry 'Ubuntu, with Linux 5.11.0-34-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.11.0-34-generic-advanced-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.11.0-34-generic ...'
		linux	/boot/vmlinuz-5.11.0-34-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.11.0-34-generic
	}
	menuentry 'Ubuntu, with Linux 5.11.0-34-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.11.0-34-generic-recovery-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.11.0-34-generic ...'
		linux	/boot/vmlinuz-5.11.0-34-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro recovery nomodeset dis_ucode_ldr 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.11.0-34-generic
	}
	menuentry 'Ubuntu, with Linux 5.11.0-27-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.11.0-27-generic-advanced-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.11.0-27-generic ...'
		linux	/boot/vmlinuz-5.11.0-27-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.11.0-27-generic
	}
	menuentry 'Ubuntu, with Linux 5.11.0-27-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.11.0-27-generic-recovery-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.11.0-27-generic ...'
		linux	/boot/vmlinuz-5.11.0-27-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro recovery nomodeset dis_ucode_ldr 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.11.0-27-generic
	}
	menuentry 'Ubuntu, with Linux 5.8.0-43-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.8.0-43-generic-advanced-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		gfxmode $linux_gfx_mode
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.8.0-43-generic ...'
		linux	/boot/vmlinuz-5.8.0-43-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro  quiet splash $vt_handoff
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.8.0-43-generic
	}
	menuentry 'Ubuntu, with Linux 5.8.0-43-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.8.0-43-generic-recovery-469b1d8e-889c-4feb-96aa-343b03155e27' {
		recordfail
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos5'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
		else
		  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
		fi
		echo	'Loading Linux 5.8.0-43-generic ...'
		linux	/boot/vmlinuz-5.8.0-43-generic root=UUID=469b1d8e-889c-4feb-96aa-343b03155e27 ro recovery nomodeset dis_ucode_ldr 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-5.8.0-43-generic
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_linux_zfs ###
### END /etc/grub.d/10_linux_zfs ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
	else
	  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
	fi
	knetbsd	/boot/memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' {
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
	else
	  search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
	fi
	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-D250285B50284895' {
	insmod part_msdos
	insmod ntfs
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  D250285B50284895
	else
	  search --no-floppy --fs-uuid --set=root D250285B50284895
	fi
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/42_grml ###
### END /etc/grub.d/42_grml ###
master@master-Latitude-E6440:/boot/grub$
Would it help or hurt to reinstall grub2?
Last edited by Tem2; 09-09-2021 at 05:11 AM.
 
Old 09-09-2021, 05:42 AM   #9
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
I ran bootinfoscript and found some possible anomolies. See attached file for full RESULTS.

Code:
Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    in partition 112 for .
I would have thought it was installed in partition 5 (sda5).

Code:
================================ sda1/menu.lst: ================================

--------------------------------------------------------------------------------
# menu.lst produced by grub4dosconfig-v1.9.3
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0

# Full installed Linux

title Ubuntu 16.04.7 LTS (sda5)
  find --set-root uuid () 59212b28-0a21-4aad-b5ee-dcf0a3afaa38
  kernel /vmlinuz root=UUID=59212b28-0a21-4aad-b5ee-dcf0a3afaa38 ro 
#                      root=/dev/sda5
  initrd /initrd.img

title Ubuntu 20.04.2 LTS (sda7/boot)
  find --set-root uuid () 42d7528c-4f38-4485-a91b-ffc529773a28
  kernel /boot/vmlinuz root=UUID=42d7528c-4f38-4485-a91b-ffc529773a28 ro 
#                      root=/dev/sda7
  initrd /boot/initrd.img

title Find Grub2\nBoot up grub2 if installed
  errorcheck off
  find --set-root --ignore-floppies --ignore-cd /boot/grub/i386-pc/core.img
  kernel /boot/grub/i386-pc/core.img
  find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
  kernel /boot/grub/core.img
  errorcheck on

# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
  errorcheck off
  find --set-root --ignore-floppies --ignore-cd  /bootmgr
  chainloader /bootmgr
  find --set-root --ignore-floppies --ignore-cd  /ntldr
  chainloader /ntldr
  find --set-root --ignore-floppies --ignore-cd   /io.sys
  chainloader /io.sys
  errorcheck on

# Advanced Menu
title Advanced menu
  configfile /menu-advanced.lst
  commandline
--------------------------------------------------------------------------------

========================== sda1/grldr embedded menu: ===========================
This is an old grub on my windows partition that came with the laptop and hasn't been able to boot. I doubt if it is the root cause of this problem, but who knows?
Attached Files
File Type: txt RESULTS.txt (22.6 KB, 19 views)
 
Old 09-09-2021, 05:55 AM   #10
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
post the contents of the gmrl menu entry in the grub.cfg
Code:
### BEGIN /etc/grub.d/42_grml ###
menuentry "Grml Rescue System (clonezilla-live-20210525-groovy-amd64.iso)" {
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  469b1d8e-889c-4feb-96aa-343b03155e27
        else
          search --no-floppy --fs-uuid --set=root 469b1d8e-889c-4feb-96aa-343b03155e27
        fi
        iso_path="/boot/grml/clonezilla-live-20210525-groovy-amd64.iso"
        export iso_path
        kernelopts="   "
        export kernelopts
        loopback loop "/boot/grml/clonezilla-live-20210525-groovy-amd64.iso"
        set root=(loop)
        configfile /boot/grub/loopback.cfg
}
### END /etc/grub.d/42_grml ###
 
Old 09-09-2021, 07:38 AM   #11
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,354

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
At the grub menu highligh the grml entry press, e for edit and change this
Quote:
configfile /boot/grub/loopback.cfg
to
Code:
configfile /boot/grub/grub.cfg
 
Old 09-09-2021, 07:54 AM   #12
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,526

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Quote:
I would have thought it was installed in partition 5 (sda5
You have an older machine which still uses Legacy/CSM boot which has a small bit of Grub code in the MBR and most of the rest of the Grub files necessary to boot on the Ubuntu partition (sda5). Line 14 of the bootinfoscript shows you have Vista/Win7, neither of which is supported currently. Line 16 shows you have Grub2 files on an ntfs partition where they should never be. Line 21 shows boot files which are used by Grub4Dos. I don't know that any of this impacts your problem but those files are not useful.

Your bootinfoscript also shows Grub version as 1.99 which was first used about 10 years ago. I have Ubuntu 20.04 installed on one partition and it shows Grub version as 2.04 and you indicate you have Ubuntu 20.04 installed. Maybe reinstalling Grub2 from Ubuntu would help. Check what version of Grub2 you have by entering this command in a terminal:

Code:
 grub-install --version
If I understand your situation, you are able to boot Ubuntu. Do you only see one menu on boot, the grub.cfg file from Grub2? Your bootinfoscript output, beginning at line 560, shows the output of os-prober and you can see scrolling down that the 40_custom is not read but other files are? Not sure why that would happen. As a test, could you just copy your clonezilla menuentry to the grub.cfg file on sda5, the Ubuntu partition, save the change and do NOT update grub, but reboot to see if your clonezilla entry is there and it boots. If it does, you will know that the clonezilla iso boots so then the problem is why 40_custom isn't read and included in grub.cfg.
 
1 members found this post helpful.
Old 09-09-2021, 09:12 AM   #13
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
At the grub menu highligh the grml entry press, e for edit and change this

to
Code:
configfile /boot/grub/grub.cfg
Ok we're making some progress. When I made this change I got the splash screen for Clonezilla. But it still didn't boot. I got a screen full of stuff but the error was:

unable to find a medium containing a live file system.

Also, if this becomes the solution, which file do I edit so that I don't have to edit at boot, or is there a way to make the change permanent?
 
Old 09-09-2021, 09:16 AM   #14
Tem2
Member
 
Registered: Dec 2011
Posts: 243

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by yancek View Post
You have an older machine which still uses Legacy/CSM boot which has a small bit of Grub code in the MBR and most of the rest of the Grub files necessary to boot on the Ubuntu partition (sda5). Line 14 of the bootinfoscript shows you have Vista/Win7, neither of which is supported currently. Line 16 shows you have Grub2 files on an ntfs partition where they should never be. Line 21 shows boot files which are used by Grub4Dos. I don't know that any of this impacts your problem but those files are not useful.

Your bootinfoscript also shows Grub version as 1.99 which was first used about 10 years ago. I have Ubuntu 20.04 installed on one partition and it shows Grub version as 2.04 and you indicate you have Ubuntu 20.04 installed. Maybe reinstalling Grub2 from Ubuntu would help. Check what version of Grub2 you have by entering this command in a terminal:

Code:
 grub-install --version
If I understand your situation, you are able to boot Ubuntu. Do you only see one menu on boot, the grub.cfg file from Grub2? Your bootinfoscript output, beginning at line 560, shows the output of os-prober and you can see scrolling down that the 40_custom is not read but other files are? Not sure why that would happen. As a test, could you just copy your clonezilla menuentry to the grub.cfg file on sda5, the Ubuntu partition, save the change and do NOT update grub, but reboot to see if your clonezilla entry is there and it boots. If it does, you will know that the clonezilla iso boots so then the problem is why 40_custom isn't read and included in grub.cfg.
How can I clean up grub and have a clean install? My version is grub 2.04.

I did as you suggested and was able to get Clonezilla to the grub menu. When I tried to boot I got the following:

Code:
error: file 'clonezilla-live-2.7.1-22-amd64.iso not found.
error: disk 'loop' not found.
error: you need to load the kernel first.
 
Old 09-09-2021, 09:24 AM   #15
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,354

Rep: Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590Reputation: 1590
This is from your original thread:

Quote:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

menuentry "clonezilla" {
set isofile="/clonezilla/clonezilla-live-2.7.1-22-amd64.iso"
loopback loop (hd0,5)$isofile
linux (loop)/live/vmlinuz boot=live components config findiso=$isofile ip=frommedia toram=filesystem.squashfs union=overlay username=user
initrd (loop)/live/initrd.img
}
 
  


Reply
Page 1 of 2 1 2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Need help adding Clonezilla to grub2 menu Tem2 Linux - Software 3 09-08-2021 05:29 PM
LXer: Clonezilla-release Stable Clonezilla live (2.0.1-15) Released LXer Syndicated Linux News 0 12-18-2012 09:21 PM
GRUB2 - FreeBSD-8.0 does not show up in triple boot menu, dual boot menu it does.. wiliweld *BSD 7 05-03-2010 01:05 PM
Mount ISO as specific device (ie: /dev/sda1) with GRUB2 to boot KNOPPIX live cd iso BLuFeNiX Linux - General 2 12-23-2009 01:31 AM
Does anyone Know how to open either .iso.rz or these .iso.xdelta,.iso.bz2,.iso.lzma?? maximalred Debian 5 06-09-2004 06:15 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 11:47 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration