Slack partition invisible at boot time after install Debian

ZebraIzToronto · 02-07-2012, 11:04 AM

I have Debian 6 _86 installed on sda4 and on sda5 Slackware ( Slackware has installed LILO on the beginning of sda5). Where and what to add so I can see Slack option at the boot time ( at the moment when system starts there is only Debian and I cannot enter in Slack)?

widget · 02-07-2012, 11:15 AM

Please go to this site, get and use the script. Post the entire results.text here.
http://bootinfoscript.sourceforge.net/

ZebraIzToronto · 02-07-2012, 11:31 AM

There is RESULTS.txt when I executed script

Quote:

Boot Info Script 0.60 from 17 May 2011

============================= Boot Info Summary: ===============================

=> Grub2 (v1.97-1.98) 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 3 for (,msdos3)/boot/grub.

sda1: __________________________________________________________________________

File system: vfat
Boot sector type: Dell Utility: FAT16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /DELLBIO.BIN /DELLRMK.BIN /COMMAND.COM

sda2: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32, Non Bootable
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sda3: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Debian GNU/Linux 6.0
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda4: __________________________________________________________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________________________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sda6: __________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 63 80,324 80,262 de Dell Utility
/dev/sda2 81,920 4,177,919 4,096,000 b W95 FAT32
/dev/sda3 * 4,177,920 609,646,591 605,468,672 83 Linux
/dev/sda4 609,648,638 1,250,263,039 640,614,402 5 Extended
/dev/sda5 609,648,640 1,215,115,263 605,466,624 83 Linux
/dev/sda6 1,215,117,312 1,250,263,039 35,145,728 82 Linux swap / Solaris

"blkid" output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda1 3030-3030 vfat DellUtility
/dev/sda2 2AFF-06CE vfat OS
/dev/sda3 59c85737-6c62-4617-8e2c-2540cb2878e3 ext4
/dev/sda5 1ea2af7f-fa3f-400e-b19f-a805d903db67 ext3
/dev/sda6 843a3129-60e9-48ea-bf13-f2d0c66b5267 swap

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda3 / ext4 (rw,errors=remount-ro)

=========================== sda3/boot/grub/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
load_env
fi
set default="0"
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 load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 59c85737-6c62-4617-8e2c-2540cb2878e3
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 59c85737-6c62-4617-8e2c-2540cb2878e3
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 59c85737-6c62-4617-8e2c-2540cb2878e3
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 59c85737-6c62-4617-8e2c-2540cb2878e3
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=59c85737-6c62-4617-8e2c-2540cb2878e3 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 59c85737-6c62-4617-8e2c-2540cb2878e3
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=59c85737-6c62-4617-8e2c-2540cb2878e3 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###

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

### BEGIN /etc/grub.d/30_os-prober ###
### 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 $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sda3/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda3 during installation
UUID=59c85737-6c62-4617-8e2c-2540cb2878e3 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=843a3129-60e9-48ea-bf13-f2d0c66b5267 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
--------------------------------------------------------------------------------

=================== sda3: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

?? = ?? boot/grub/core.img 1
?? = ?? boot/grub/grub.cfg 1
?? = ?? boot/initrd.img-2.6.32-5-amd64 2
?? = ?? boot/vmlinuz-2.6.32-5-amd64 2
?? = ?? initrd.img 2
?? = ?? vmlinuz 2

========= Devices which don't seem to have a corresponding hard drive: =========

sdb

widget · 02-07-2012, 04:25 PM

The boot info script output does not agree with your statement of what is installed where.

You have 3 primary partitions; sda1 appears to be a MS boot sector, sda2 appears related to sda1, sda3 has Debian installed on it.

You then have an extended partition, sda4. Within it you have 2 logical partitions; sda5 with something identified as Linux, sda6 which is /swap.

Now, assuming that sda5 is the slackware install, the first thing for you to do is to pull up a terminal in Debian and, as root, run;

Code:

update-grub

This should pick up that install. I do not think that using Lilo should stop that but I am not sure. It is the first thing to try anyway.

There should be output in terminal saying that it found thus and so OS's.

Then to make sure what happened, again as root, run on a full screen terminal;

Code:

grub-mkconfig

This should print out your entire /boot/grub/grub.cfg file. This is where your screen menu comes from. There are sections in that file. What you want is the section that says'

Quote:

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

Will have a similar comment at the end of the section starting with "END". That is where the menu entry, if any, will be for that other install.

If it is not there then we will have to do something else.

syg00 · 02-07-2012, 05:42 PM

Looks suspiciously like the Slack install has been blown away - bootinfoscript looks for lilo.

widget · 02-07-2012, 05:54 PM

Quote:

Originally Posted by syg00

Looks suspiciously like the Slack install has been blown away - bootinfoscript looks for lilo.

OK, I give up, where does it look for lilo?

I realize it is not listed there, unless of coarse I missed it.

It does, however, recognize some installation which seems to indicate a kernel anyway.

What I am thinking is to let grub look for a bootloader. If one is not found then there will have to be one installed by chroot or some other method. Not sure what the options are with slack as I have never fooled with it.

I did find this interesting thread;
http://www.linuxquestions.org/questi...estion-863421/

At least I found it interesting because I really like custom menus. I have some on file for a number of different OS's but not one for slackware so I am pretty happy to have it.

syg00 · 02-07-2012, 06:08 PM

It's a script, easy enough to read. It checks for lots of things (Windows, MSDOS, Solaris ...), including lilo.conf, and lilo in the partition boot record.
It only outputs what it finds - else the listing would go for pages.

widget · 02-07-2012, 06:22 PM

I am pretty familiar with the script. Try to keep an up to date copy on here even. I have a lot of installs and it comes in handy.

There have been, however, some glitches recently in it. They are being corrected. Haven't kept up with exactly what is and is not effected.

Figured that running update-grub will run os-prober in a different environment, perhaps with better result. It is rather touchy at times too.

This is why you sometimes do not get all OS's listed when you install. update-grub is run, true, but it is run from "dpkg-configure grub-pc grub-common" and thus the install script rather than straight from grub itself. That is why most of the time simply running that command corrects the problem once you are in the new install.

syg00 · 02-07-2012, 08:01 PM

update-grub is Debian derived. In (classic) grub it was Debian (and derivatives) specific - not part of the (upstream) grub project at all.
As such it (and bootinfoscript) make some assumptions about where things exist that they shouldn't make. Especially now they are generally available.