LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-08-2017, 09:26 PM   #1
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Rep: Reputation: 13
LILO partition not found in GRUB bootloader.


So I recently installed the killx.linuxbbq.org distro (it comes with LILO as its default bootloader). I have two hard drives, three partitions--including killx--OpenSUSE with GRUB on /dev/sda1 (and on MBR). Devuan with GRUB on /dev/sdb1, and finally, killx on /dev/sdb2. I *must* have GRUB on my MBR--I can't afford to have LILO as an alternative, *no exceptions*. I modified my lilo.conf, and updated GRUB on my host system by running: update-bootloader && grub2-mkconfig
After I rebooted, the partition was nowhere to be found.


My lilo.conf:

#
# minimal LILO configuration
#
lba32
append=" vt.default_utf8=0"
boot = /dev/sdb2
prompt
timeout = 30
change-rules
reset

image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sdb2
label = Linux
read-only


Then I ran /sbin/lilo:
Warning: '/proc/partitions' does not exist, disk scan bypassed
Warning: /dev/sdb is not on the first disk
Fatal: Trying to map files from unnamed device 0x002b (NFS/RAID mirror down ?)

So I changed to boot = /dev/sda, and the same output as above appeared.

Any help is appreciated. This is the FIRST time I've ever used LILO.
 
Old 07-08-2017, 10:14 PM   #2
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,420

Rep: Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088
If you have Grub on the MBR of sda and nothing in the MBR of sdb, you will need an entry in the Opensuse grub.cfg file for the new OS. Modifying Lilo isn't going to help if all you have is Lilo on the partition, you need to get to it from Opensuse first and you don't actually need Lilo if you have Grub in Opensuse. What output did you get when running grub-2mkconfig from Opensuse?
 
Old 07-09-2017, 09:08 AM   #3
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
This:

Generating grub configuration file ...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -f ${config_directory}/grubenv ]; then
load_env -f ${config_directory}/grubenv
elif [ -s $prefix/grubenv ]; then
load_env
fi

if [ "${env_block}" ] ; then
load_env -f "${env_block}"
fi

if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
if [ "${env_block}" ] ; then
save_env -f "${env_block}" next_entry
fi
set boot_once=true
else
set default="${saved_entry}"
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
if [ "${env_block}" ] ; then
save_env -f "${env_block}" saved_entry
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='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
font="/usr/share/grub2/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
Found theme: /boot/grub2/themes/openSUSE/theme.txt
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
insmod gfxmenu
loadfont ($root)/boot/grub2/themes/openSUSE/ascii.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans10.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans12.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2
insmod png
set theme=($root)/boot/grub2/themes/openSUSE/theme.txt
export theme
if [ x${boot_once} = xtrue ]; then
set timeout=0
elif [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=8
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=8
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/00_tuned ###
set tuned_params=""
### END /etc/grub.d/00_tuned ###

### BEGIN /etc/grub.d/10_linux ###
Found linux image: /boot/vmlinuz-4.11.8-1-default
Found initrd image: /boot/initrd-4.11.8-1-default
menuentry 'openSUSE Tumbleweed' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.8-1-default ...'
linux /boot/vmlinuz-4.11.8-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d splash=silent quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.8-1-default
}
submenu 'Advanced options for openSUSE Tumbleweed' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-502a7675-42c1-419b-abbd-d99be3bc058d' {
menuentry 'openSUSE Tumbleweed, with Linux 4.11.8-1-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.8-1-default-advanced-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.8-1-default ...'
linux /boot/vmlinuz-4.11.8-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d splash=silent quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.8-1-default
}
menuentry 'openSUSE Tumbleweed, with Linux 4.11.8-1-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.8-1-default-recovery-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.8-1-default ...'
linux /boot/vmlinuz-4.11.8-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.8-1-default
}
Found linux image: /boot/vmlinuz-4.11.7-1-default
Found initrd image: /boot/initrd-4.11.7-1-default
menuentry 'openSUSE Tumbleweed, with Linux 4.11.7-1-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.7-1-default-advanced-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.7-1-default ...'
linux /boot/vmlinuz-4.11.7-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d splash=silent quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.7-1-default
}
menuentry 'openSUSE Tumbleweed, with Linux 4.11.7-1-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.7-1-default-recovery-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.7-1-default ...'
linux /boot/vmlinuz-4.11.7-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.7-1-default
}
Found linux image: /boot/vmlinuz-4.11.6-1-default
Found initrd image: /boot/initrd-4.11.6-1-default
menuentry 'openSUSE Tumbleweed, with Linux 4.11.6-1-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.6-1-default-advanced-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.6-1-default ...'
linux /boot/vmlinuz-4.11.6-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d splash=silent quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.6-1-default
}
menuentry 'openSUSE Tumbleweed, with Linux 4.11.6-1-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.11.6-1-default-recovery-502a7675-42c1-419b-abbd-d99be3bc058d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd2,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 --hint='hd2,msdos1' 502a7675-42c1-419b-abbd-d99be3bc058d
else
search --no-floppy --fs-uuid --set=root 502a7675-42c1-419b-abbd-d99be3bc058d
fi
echo 'Loading Linux 4.11.6-1-default ...'
linux /boot/vmlinuz-4.11.6-1-default root=UUID=502a7675-42c1-419b-abbd-d99be3bc058d
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.11.6-1-default
}
}

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

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

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

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found Devuan GNU/Linux 1 (jessie) on /dev/sdb1
menuentry 'Devuan GNU/Linux 1 (jessie) (on /dev/sdb1)' --class devuan --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-50681546-3eb1-47ea-8f43-e7771393c834' {
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 50681546-3eb1-47ea-8f43-e7771393c834
else
search --no-floppy --fs-uuid --set=root 50681546-3eb1-47ea-8f43-e7771393c834
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
submenu 'Advanced options for Devuan GNU/Linux 1 (jessie) (on /dev/sdb1)' $menuentry_id_option 'osprober-gnulinux-advanced-50681546-3eb1-47ea-8f43-e7771393c834' {
menuentry 'Devuan GNU/Linux (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--50681546-3eb1-47ea-8f43-e7771393c834' {
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 50681546-3eb1-47ea-8f43-e7771393c834
else
search --no-floppy --fs-uuid --set=root 50681546-3eb1-47ea-8f43-e7771393c834
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Devuan GNU/Linux, with Linux 3.16.0-4-686-pae (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--50681546-3eb1-47ea-8f43-e7771393c834' {
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 50681546-3eb1-47ea-8f43-e7771393c834
else
search --no-floppy --fs-uuid --set=root 50681546-3eb1-47ea-8f43-e7771393c834
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro quiet
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Devuan GNU/Linux, with Linux 3.16.0-4-686-pae (sysvinit) (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--50681546-3eb1-47ea-8f43-e7771393c834' {
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 50681546-3eb1-47ea-8f43-e7771393c834
else
search --no-floppy --fs-uuid --set=root 50681546-3eb1-47ea-8f43-e7771393c834
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro quiet init=/lib/sysvinit/init
initrd /boot/initrd.img-3.16.0-4-686-pae
}
menuentry 'Devuan GNU/Linux, with Linux 3.16.0-4-686-pae (recovery mode) (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae-root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro single-50681546-3eb1-47ea-8f43-e7771393c834' {
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 50681546-3eb1-47ea-8f43-e7771393c834
else
search --no-floppy --fs-uuid --set=root 50681546-3eb1-47ea-8f43-e7771393c834
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=50681546-3eb1-47ea-8f43-e7771393c834 ro single
initrd /boot/initrd.img-3.16.0-4-686-pae
}
}

Found killX 0.1b (Nietzsche) on /dev/sdb2

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###

### 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/80_suse_btrfs_snapshot ###
### END /etc/grub.d/80_suse_btrfs_snapshot ###

### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###

### BEGIN /etc/grub.d/95_textmode ###
### END /etc/grub.d/95_textmode ###
done




I am very new to modifying GRUB. And in this case, I have no idea what to do next.

Last edited by NewbProgrammer; 07-09-2017 at 10:57 AM.
 
Old 07-09-2017, 11:59 AM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,420

Rep: Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088
Did you follow the instructions at the killx site below?

http://killx.linuxbbq.org/docs.html

The only reference to it in your grub.cfg file is:
Quote:
Found killX 0.1b (Nietzsche) on /dev/sdb2
which is at the end of your menuentries. Have you tried just putting a chainloader entry in the Opensuse grub.cfg file and rebooting to test. If you put it in grub.cfg, don't run grub-mkconfig but reboot to test and if it fails just delete it and if it works, put it in /etc/grub.d/40_custom. Is this an MBR system? I've never heard of killx so you would need to see if there is a boot directory and kernel on sdb2. If so, the chainload entry should work. If not, good luck.

Quote:
menuentry "killx" {
set root=(hd1,1)
chainloader +1
boot
}
 
Old 07-09-2017, 12:54 PM   #5
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
Yes of course I followed the killx installation guide! If I hadn't chrooted into it, I wouldn't have shown you the lilo.conf.

I put

menuentry "killx" {
set root=(hd1,1)
chainloader +1
boot
}

in /etc/default/grub and ran grub2-mkconfig:

/etc/default/grub: line 45: menuentry: command not found
 
Old 07-09-2017, 02:26 PM   #6
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,500

Rep: Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077
Quote:
Warning: '/proc/partitions' does not exist, disk scan bypassed
Quote:
Yes of course I followed the killx installation guide! If I hadn't chrooted into it, I wouldn't have shown you the lilo.conf.
what commands did you use to chroot into the killx installation? looks like might be missing some files in /proc when you chrooted into your system.
 
Old 07-09-2017, 03:35 PM   #7
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,420

Rep: Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088
Did you not think that message was a little odd since you have a number of "menuentry" lines in the grub.cfg you posted?
Why exactly did you put it in /etc/default/grub when you were explicitly told to put in in /etc/grub.d/40_custom?
Might be helpful to read a little more carefully in the future.

Last edited by yancek; 07-09-2017 at 03:43 PM.
 
Old 07-09-2017, 04:20 PM   #8
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
I copied /proc/partitions over to my killx session and reran /sbin/lilo, the complaint disappeared but the two other lines stayed.

Commands after first chroot:

passwd
nano /etc/hostname
nano /etc/fstab https://www.zerobin.net/?201b8e37baa...K3cHIqa/HiQjo=
nano /etc/mtab https://www.zerobin.net/?4b2c83743f8...lg30ag3pgPXrA=
dhcpcd
nano ~/.bashrc
nano ~/.bash_profile
nano /lilo.conf
/sbin/lilo

I added the menuentry chunk to /etc/grub.d/40_custom and updated GRUB. Rebooted, killx showed up in the menu. Couldn't boot into it because of no kernel parameters. Any idea on what parameters to put in? Which file to put in? /etc/grub.d/40_custom? /etc/grub.d/41_custom?

Thanks in advance.

EDIT: I see, are the parameters supposed to be in /etc/grub.d/30_os-prober?

Last edited by NewbProgrammer; 07-09-2017 at 04:28 PM.
 
Old 07-09-2017, 07:15 PM   #9
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,513

Rep: Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009Reputation: 1009
Copy the kernel parameters from another entry, and customize them for the different disk location. In the kernel line there is a root= entry. You can use a UUID or a device node like /dev/sdb1.
 
Old 07-09-2017, 07:47 PM   #10
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,500

Rep: Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077Reputation: 1077
did you run the following commands to chroot:
Code:
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt /bin/bash
this is assuming killx is mounted at /mnt .
 
Old 07-09-2017, 08:16 PM   #11
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
I mounted the necessary filesystems, no noticeable change in anything.

I added modifications to my /etc/grub.d/40_custom

#!/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 "killx" {
set root=(hd1,1)
chainloader +1
boot
linux /boot/vmlinuz-huge-3.10.9 root=/dev/sdb2 #it exists
initrd /boot/initrd.gz
}
# EOF

I updated GRUB and rebooted into killx, it said /boot/vmlinuz-huge-3.10.9 does not exist and I need to load my kernel. So it didn't boot.

I have no idea what I'm doing wrong. Please help.
 
Old 07-09-2017, 08:42 PM   #12
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 9,420

Rep: Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088Reputation: 2088
If you are going to put kernel and initrd lines, you don't want the chainloader entry, try the entry below, if the hugh kernel exists in the boot directory, hopefully it will boot:

Code:
menuentry "killx" {
set root=(hd1,1)
linux /boot/vmlinuz-huge-3.10.9 root=/dev/sdb2 #it exists
initrd /boot/initrd.gz
}
The boot parameters are generally on the kernel line in grub.cfg, the line beginning with linux. I have no idea what parameters this OS would want and their site doesn't have much for documentation. Did you get a message regarding parameters when you tried to boot? If so, what exactly was it?
 
2 members found this post helpful.
Old 07-09-2017, 09:38 PM   #13
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
I removed chainloader, updated GRUB, and rebooted. I still get the same output:

error you need to load the kernel first
error /boot/vmlinuz-huge-3.10.9 does not exist
error you need to load the kernel first
 
Old 07-10-2017, 12:36 AM   #14
aragorn2101
Member
 
Registered: Dec 2012
Location: Mauritius
Distribution: Slackware
Posts: 553

Rep: Reputation: 277Reputation: 277Reputation: 277
Quote:
Originally Posted by NewbProgrammer View Post
error you need to load the kernel first
error /boot/vmlinuz-huge-3.10.9 does not exist
error you need to load the kernel first
Hi, I think the series of lines which yancek gave you lead to the correct solution. You are getting the error because maybe you need to modify the path to the kernel and also check if you have the initrd.gz at that location.

So, mount your killX partition and check the paths:
Code:
menuentry 'killX' {
    set root='hd1,msdos2'
    linux PATH_TO_YOUR_KERNEL root=/dev/sdb2 ro
    initrd PATH_TO_YOUR_INITRD
}
I used 'hd1,msdos2' for killX based on the entry for Devuan, since you said Devuan and killX are on the same hard drive.
If you don't have an initrd there and if the kernel is not a "huge" one, you will have a kernel error at boot, but at least it will start to boot. Then, you just have to chroot into killx and make an initrd.

Last edited by aragorn2101; 07-10-2017 at 12:45 AM.
 
Old 07-10-2017, 10:24 AM   #15
NewbProgrammer
Member
 
Registered: Jun 2017
Location: Check my IP address.
Distribution: Gentoo, Puppy, Mint Rosa, Arch, SliTaz, Crunchbang, LinuxBBQ, OpenSUSE, NanoLinux, LFS CentOS.
Posts: 54

Original Poster
Rep: Reputation: 13
I followed your steps. Updated GRUB, rebooted. Killx gave me a kernel error. It booted. While I was in the environment, I couldn't type anything because there was no active kernel present. In dmesg, there was an error saying /sbin/init does not exist. How do I create an init? I do have sysVinit on killX, it's just not doing anything. Should I remove the existing kernel in /boot and compile my own?


EDIT: Never mind, I'm going to mark this thread as solved because this is on a different topic now.

Thank you very much.

Last edited by NewbProgrammer; 07-10-2017 at 10:39 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Bootloader Lilo competing with Grub, Grub wins vcfstephen Slackware 3 05-11-2007 12:05 AM
Lilo not writting over grub bootloader Thaidog Linux - General 1 12-13-2006 12:33 PM
BootLoader Help (GRUB or LILO) drumstick Linux - Newbie 3 10-19-2006 08:33 AM
How can I disable the grub bootloader and enable the lilo bootloader? abefroman Linux - General 1 08-06-2005 08:53 AM
How do you use GRUB instead of LILO as the bootloader? randon Linux - Newbie 3 09-26-2003 07:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 08:49 PM.

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