LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
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
 
Search this Thread
Old 03-20-2008, 11:31 PM   #1
r00tb33r
Member
 
Registered: Feb 2007
Distribution: Vector
Posts: 318

Rep: Reputation: 31
Ubuntu 7.04/7.10 GRUB won't boot anything after install with Intel SATA on laptop


GRUB doesn't seem to work with my SATA controller/drives on my laptop.
The laptop is HP dv8327cl, two (2x) 120GB hard drives, Intel SATA controller.
Installing Linuxes to the second drive, choose (hd1) to install GRUB to, GRUB boots from the second drive, but won't boot the other distro or Windows from the first drive. It can't mount or access any of the partitions.
In case of trying to boot the fresh Ubuntu install I get error 15, file not found (can't find the kernel).
LILO boots Slackware just fine.
Can anyone walk me through installing LILO onto the fresh Ubuntu installation from the Ubuntu LiveCD? I have 7.10 now, I tried 7.04 earlier with same result.
Thanks in advance.
 
Old 03-21-2008, 10:43 PM   #2
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
i know you may not like me....but your title suggesting you were having trouble with grub but your question is on lilo.

" GRUB boots from the second drive, but won't boot the other distro or Windows from the first drive. It can't mount or access any of the partitions."

1) so grub is allowing a system to boot?

2) you can use grub to chainload...see my signature if like

3) grub could be in either mbr of your drives.
the root (hdx,y) command tells grub where to jump to.

you can use my troubleshooter to point to each partition and use the find command if you desire.

4) you have not menitioned if some of your systems are on raid striped = raid 1...grub does not understand these.
 
Old 03-22-2008, 12:05 AM   #3
r00tb33r
Member
 
Registered: Feb 2007
Distribution: Vector
Posts: 318

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by aus9 View Post
i know you may not like me....but your title suggesting you were having trouble with grub but your question is on lilo.

" GRUB boots from the second drive, but won't boot the other distro or Windows from the first drive. It can't mount or access any of the partitions."

1) so grub is allowing a system to boot?

2) you can use grub to chainload...see my signature if like

3) grub could be in either mbr of your drives.
the root (hdx,y) command tells grub where to jump to.

you can use my troubleshooter to point to each partition and use the find command if you desire.

4) you have not menitioned if some of your systems are on raid striped = raid 1...grub does not understand these.
No I have no personal problems with anyone.
I mentioned LILO as the probable solution.(It's confirmed to work for me) I would probably need help installing it on a system that does not boot though.

1) Answered in the title of the thread and in the body of the first post. GRUB is not booting anything.
2) At the bottom of this post is the Ubuntu menu.lst, it is chainloading from what I see.
3) Is also answered in the first post. GRUB is located in MBR of the second drive. The root commands in the Ubuntu menu.lst are at the bottom of this post.
4) No RAID here.

The primary question is still why GRUB doesn't work.

My partition layout is something like this:

Code:
First Drive (hd0 for GRUB, /dev/sda device file):
MBR:  NT (HP with recovery functionality)
Partition 1:  Windows XP         NTFS, primary, active
Partition 2:  HP Utilities       NTFS, primary
Partition 3:  HP Recovery        NTFS, primary

Second Drive (hd1 for GRUB, /dev/sdb device file):
MBR:  GRUB
Partition 1:  Backtrack 2 (Slax) ext2, primary
Partition 2:  Ubuntu 7.10        ext3, primary, active
Partition 3:                     swapspace, primary
I do not touch the first drive to preserve the HP MBR to preserve the recovery functionality. And for convenience.
I select boot device using the BIOS boot device selection.
Order of detection of drives is identical every time, I have checked.
There is no LILO anywhere in the system, it was overwritten with GRUB in MBR when Ubuntu was installed.

GRUB menu and boot result, as Ubuntu configured it:

Code:
Item                                                       Result

Ubuntu 7.10, kernel 2.6.22-14-generic                      Error 15: File not found
Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)      Error 15: File not found
Ubuntu 7.10, memtest86+                                    Error 15: File not found
Other operating systems:                                   Error 11: Unrecognized device string
Windows XP Media Center Edition                            Error 13: Invalid or unsupported executable format
Windows NT/2000/XP                                         Error 13: Invalid or unsupported executable format
Microsoft Windows XP Embedded                              Error 13: Invalid or unsupported executable format
bt (on /dev/sdb1)                                          Error 17: Cannot mount selected partition
Note:
"Other operating systems:" is a dummy item placed by Ubuntu to make the menu looking "nicer".
"Windows NT/2000/XP" is the HP Utilities partition, detected and placed in the menu by Ubuntu.
"Microsoft Windows XP Embedded" is the HP Recovery partition, detected and placed in the menu by Ubuntu.

Here is my(not modified) GRUB menu.lst:
Code:
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=d650f70f-86e9-4507-b8b0-394bdf3c8248 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,1)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Ubuntu 7.10, kernel 2.6.22-14-generic
root		(hd1,1)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=d650f70f-86e9-4507-b8b0-394bdf3c8248 ro quiet splash
initrd		/boot/initrd.img-2.6.22-14-generic
quiet

title		Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root		(hd1,1)
kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=d650f70f-86e9-4507-b8b0-394bdf3c8248 ro single
initrd		/boot/initrd.img-2.6.22-14-generic

title		Ubuntu 7.10, memtest86+
root		(hd1,1)
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title		Windows XP Media Center Edition
root		(hd0,0)
savedefault
chainloader	+1


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title		Windows NT/2000/XP
root		(hd0,1)
savedefault
chainloader	+1


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda3
title		Microsoft Windows XP Embedded
root		(hd0,2)
savedefault
chainloader	+1


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title		bt (on /dev/sdb1)
root		(hd1,0)
kernel		/boot/vmlinuz root=current ro vga = 0x317 
initrd		/boot/splash.initrd
savedefault
boot
So thats that.

The SATA controller is as follows:
Code:
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 01)
Nothing boots with this default setup. All drive and partition numbers match up.
I'm clueless. This isn't the first time I've had issues with GRUB though.

LILO might not work out though, at least on Ubuntu. It is obsoleted in Ubuntu package list. Debian etch LILO package cannot be installed because libdebmapper1.02 required by it conflicts with udev.
I tried it just now, chrooting into the system and trying to install the above packages with dpkg. Doesn't work. I might be able to restore the LILO MBR by chrooting into the Backtrack 2 on the other partition and adding lines for Ubuntu.

Last edited by r00tb33r; 03-22-2008 at 01:06 AM.
 
Old 03-22-2008, 08:06 AM   #4
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
ok, I guess you initially installed slackware...ran setup and installed lilo....later you installed ubuntu and (presumely) allowed grub to overwrite your "lilo" mbr

so there are alternatives to your lilo question

1) boot a live cd...mount your slack then chroot to it...run setup and redo lilo.

but I will restrict myself to your grub stuff.

2) when you say
I select boot device using the BIOS boot device selection.

do you agree you mean that you have changed the bios boot order to hd1 instead of hd0.

if you change bios to boot order hd0....ms should boot, yes?

BUT

as soon as you change boot order to hd1....all of the grub hd numbers are wrong.

so the easiest to prove I am wrong...heh heh...is to boot a live cd...mount your ubuntu as read/write.....edit its grub menu to hd0 for linux

but you will need a map command for ms

title ms is on hd1 with bios boot order
root (hd1,0)
map (hd0,0) (hd1,0)
map (hd1,0) (hd0,0)
makeactive
chainloader +1

title ubuntu
root (hd0,1)
kernel /boot/vmlinuz etc
initrd /boot/initrd etc

no quiet is to show on the last line pls

3) the map command is explained in my signature....of course I respect you for not wanting to interfere with hd0 mbr....but I am not sure when you did the bios boot order swap so I forgive ubuntu for getting you in this mess
 
Old 03-22-2008, 08:10 AM   #5
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
let me know if you need advise on how to chroot

if you do not want to stay with grub...this may help
http://www.psg.com/~brian/doc/linux/slackins.htm
 
Old 03-22-2008, 04:07 PM   #6
r00tb33r
Member
 
Registered: Feb 2007
Distribution: Vector
Posts: 318

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by aus9 View Post
let me know if you need advise on how to chroot

if you do not want to stay with grub...this may help
http://www.psg.com/~brian/doc/linux/slackins.htm
Yeah I restored LILO from the other distro and added Ubuntu lines... It took me a while to figure it out - I didn't know that LILO requires copying of kernels from the other partitions to the home partition of LILO. I guess thats the only downside of LILO, inability to read kernel and initrd from other partitions.

I didn't realize that GRUB depends on the BIOS boot order. I expected it to just follow the bus ID order (SATA numbers don't actually change).

So much for getting Ubuntu. Even after updates it fails on every source build attempted.(and I do know what I am doing)
It can't even build "xconfig" in the kernel source tree (a paradox: the kernel source was downloaded from from the Ubuntu repository, I thought their own stuff would work)
This was the reason I abandoned Debian several years ago. I thought it got better now.
I admit Ubuntu is well configured for a laptop though, LCD brightness controls, volume controls, hibernate and suspend(suspend hangs but still I give browney points for the effort). Hopefully I will dissect it as an example and configure the distro of my choice (Vector or Backtrack) the way this is.

So now I know a little more about GRUB.
Thanks for the help.
 
Old 03-22-2008, 06:41 PM   #7
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
when you know what distro works out of the box....consider adding a HCL entry pls.

btw....quite a few distros have laptop kernels including Mdv but with no hcl entry yet I can not tell you what to go for.

sometimes fedora...being bleeding edge....may offer better support....they have live cds i think.
 
  


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
Install Ubuntu on Sata Raid 0 - dmraid - dual boot windows xp matsie Ubuntu 4 07-11-2011 10:59 AM
ubuntu 6.10 install (dual boot with XP) - how to put grub in /dev/hda9? Airidh Ubuntu 5 04-05-2007 08:54 AM
Ubuntu server (2.6.12) on a SATA drive, Intel chipset? Dee-ehn Linux - Hardware 2 04-21-2006 07:47 AM
GRUB fails to install on sata disk with Ubuntu 5.04 nonutopia Linux - Software 5 08-16-2005 03:09 AM


All times are GMT -5. The time now is 05:25 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration