scientificlinuxforum.org QR code
Scientific Linux Forum.org



  Reply to this topicStart new topicStart Poll

> Dualboot: SL6.2 and Debian6.0 squeeze
Mumrik
 Posted: Jul 20 2012, 02:08 PM
Quote Post


SLF Newbie


Group: Members
Posts: 5
Member No.: 1717
Joined: 20-July 12









Hello)

I'm trying to recover Debian which was failed after the SL's installing. At first it was only SL in the GRUB menu. I edited the grub.conf and now it's two systems in menu, but it can't boot Debian.

Error 17 : Cannot mount selected partition

Why?

Disks:
QUOTE
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xadddaddd

  Device Boot      Start        End      Blocks  Id  System
/dev/sda1  *          1        3697    29690880  83  Linux
/dev/sda2            3825      38914  281853545+  f  W95 Ext'd (LBA)
/dev/sda3            3697        3824    1024000  82  Linux swap / Solaris
/dev/sda5            3825      29932  209712478+  83  Linux
/dev/sda6          29933      32422    19999744  83  Linux
/dev/sda7          32423      32671    1998848  82  Linux swap / Solaris
/dev/sda8          32671      37608    39654400  83  Linux
/dev/sda9          37608      38914    10484736  83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 2087 MB, 2087976960 bytes
28 heads, 27 sectors/track, 5394 cylinders
Units = cylinders of 756 * 512 = 387072 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x26c7631d

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1              1        5395    2038921+  b  W95 FAT32


config file:
CODE
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,0)
#          kernel /boot/vmlinuz-version ro root=/dev/sda1
#          initrd /boot/initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=15
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu

title Scientific Linux (2.6.32-220.el6.i686)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-220.el6.i686 ro root=UUID=b3b361c3-0671-45b1-b1b2-321fd32bb1ac rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
initrd /boot/initramfs-2.6.32-220.el6.i686.img

title Debian 6.0.3 (6.0.3)
       root (hd0,6)
search --no-floppy --fs-uuid --set f827fa87-25bb-4a24-87ed-cb5250298405
echo 'Loading Linux 2.6.32-5-686 ...'
kernel /boot/vmlinuz-2.6.32-5-686 root=UUID=f827fa87-25bb-4a24-87ed-cb5250298405 ro  quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
PM
^
AndrewSerk
 Posted: Jul 21 2012, 06:57 PM
Quote Post


SLF Moderator
******

Group: Moderators
Posts: 524
Member No.: 54
Joined: 14-April 11









Hi Mumrik and welcome to SLF,

The first thing I would try to correct the issue is replace the root=UUID with "root=/dev/sd?"the device location in grub.conf and see if that helps.
PM
^
Mumrik
 Posted: Jul 23 2012, 07:59 AM
Quote Post


SLF Newbie


Group: Members
Posts: 5
Member No.: 1717
Joined: 20-July 12









Hi. Thanks for help!
I made a mistake in the grub.conf:
QUOTE

root (hd0,6)


/dev/sda6 => (hd0,5) http://www.madjacksports.com/forum/images/smilies/facepalm.gif

But, when I correct it and replace root=UUID with root=/dev/sd6:
QUOTE

Error 13 : Invalid or unsupported executable format
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the
supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).

PM
^
U308
 Posted: Jul 23 2012, 11:46 AM
Quote Post


SLF Advocate
*****

Group: Members
Posts: 486
Member No.: 32
Joined: 11-April 11









Use the blkid command to see if the UUID is correct.
#blkid /dev/sda6
PM
^
Mumrik
 Posted: Jul 24 2012, 08:34 AM
Quote Post


SLF Newbie


Group: Members
Posts: 5
Member No.: 1717
Joined: 20-July 12









Yes, UUID is correct. I can't understand, what's problem.

This is Debian's grub.cfg:

QUOTE

#
# 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,msdos6)'
search --no-floppy --fs-uuid --set f827fa87-25bb-4a24-87ed-cb5250298405
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,msdos6)'
search --no-floppy --fs-uuid --set f827fa87-25bb-4a24-87ed-cb5250298405
set locale_dir=($root)/boot/grub/locale
set lang=ru
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set f827fa87-25bb-4a24-87ed-cb5250298405
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=f827fa87-25bb-4a24-87ed-cb5250298405 ro  quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set f827fa87-25bb-4a24-87ed-cb5250298405
echo 'Loading Linux 2.6.32-5-686 ...'
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=f827fa87-25bb-4a24-87ed-cb5250298405 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-686
}
### 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/30_otheros ###

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
menuentry "Windows Vista (loader)" {
set root=(hd0,msdos1)
search --no-floppy --fs-uuid --set 1074434a744331b0
chainloader +1
}

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda9.
menuentry "Debian 6.0.3 (6.0.3) (on /dev/sda9)" {
set root=(hd0,msdos9)
search --no-floppy --fs-uuid --set 29d1f001-b880-4684-b7b9-ed5f758c0897
linux /boot/vmlinuz-2.6.32-5-686 root=/dev/sda9
initrd /boot/initrd.img-2.6.32-5-686
}

### END /etc/grub.d/30_otheros ###

### 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 ###
PM
^
U308
 Posted: Jul 24 2012, 10:32 AM
Quote Post


SLF Advocate
*****

Group: Members
Posts: 486
Member No.: 32
Joined: 11-April 11









As far as I know the old grub (grub legacy) cannot boot grub2 based OS. I had this before and the solution was to simply chainload from the old grub. So, one would need to add something like:-

title Debian
root (hd0,5)
chainloader +1

to menu.lst

Your Debian bootloader should be installed to root (/) and not to Mbr.

Have look at this: http://bootinfoscript.sourceforge.net/
I find it rather useful. smile.gif

PM
^
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

Topic Options Reply to this topicStart new topicStart Poll