LinuxQuestions.org
Visit Jeremy's Blog.
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 10-14-2009, 12:44 AM   #1
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Rep: Reputation: 227Reputation: 227Reputation: 227
just compiled kernel will not boot


there is a boat load of messages but
here is the last messages
Code:
All bugs added by David S. Miller <davem@redhat.com> -- WTF?
Using IPI Shortcut mode
hd: no drives specified - use hd=cyl,head,sectors on kernel  command line
VFS: Cannot open root device "301" or unknown-block(3,1)
VFS: Cannot open root device "/dev/hda1" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
Pid: 1, comm, swapper not tainted 2.6.31.2 #2
Call Trace
panic+0x38/0xd9
mount_block_root+0x104/0x118
mount_root+0x96/0x9b
? kernel_init+0x0/0x8b
prepare_namespace+0x141/0x165
kernel_init+0x82/0x8b
kernel_thread_helper+0x7/0x10
 
Old 10-14-2009, 02:19 AM   #2
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 611

Rep: Reputation: 219Reputation: 219Reputation: 219
Are you using LILO or GRUB?
 
Old 10-14-2009, 02:28 AM   #3
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
LILO grub does not work at all
 
Old 10-14-2009, 02:31 AM   #4
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Hi smeezekitty,

it looks like your kernel lacks the driver for your harddrive.

If it where a problem with the bootloader you should not have been able to boot the kernel or (while the configuration) to add the partition to the bootloader.

What kind of harddrive are you using? IDE or SATA? if SATA, did you select the appropriate settings in the kernelconfiguration?

Markus
 
Old 10-14-2009, 02:38 AM   #5
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
i think its IDE
here is lilo.conf
Code:
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda1

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=80

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
	prompt
	single-key
#	delay=100
	timeout=100

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce noapic root=/dev/hda1"

# Boot up Linux by default.
#
default=Linux

image=/boot/linux24
	label=Linux
	
	read-only
#	restricted
	alias=1

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
	alias=2
image=/bzImage
       label=Compiled
       read-only
#       optional
       alias=3
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hdb1
#	label=Custom_Linux
#	restricted
#	alias=3

Last edited by smeezekitty; 10-14-2009 at 02:40 AM.
 
Old 10-14-2009, 02:52 AM   #6
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
well, seems this bootloader resides on the bootsector of your boot partition but not on the masterbootrecord of your harddrive, is this correct?
And you do not have a separated /boot partition?
Have there been any error-messages or warnings when you executed lilo?

Markus
 
Old 10-14-2009, 02:55 AM   #7
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
i have two kernels 2.4 and 2.6 both on the same partition
2.4 boots 2.6 does not
 
Old 10-14-2009, 03:06 AM   #8
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
And this kernels reside in the same directory?
There is a /boot/Linux24, a /vmlinuz.old and a /bzImage. Is /bzImage the new compiled kernel?
Maybe there is a conflict between the lilo-settings for a 2.6 and a 2.4 kernel. But I don't know enough about this.

Markus
 
Old 10-14-2009, 03:22 AM   #9
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Ich bin die Kompilierung des Kernels zusatzliche Treiber
Dies kann eine Weile dauern
 
Old 10-14-2009, 03:24 AM   #10
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
ok, I've to go to work now. I'll look here later in the evening.

good luck

Markus
 
Old 10-14-2009, 04:41 AM   #11
doc.nice
Member
 
Registered: Oct 2004
Location: Germany
Distribution: Debian
Posts: 274

Rep: Reputation: 34
be sure to include the partition support for dos partitions, the support for ext2/3 or whatever your root partition uses and the support for your ide controller. All these options muste be compiled into the kernel, not loaded as Modules.
when you switch from an old 2.4 kernel to a rather new 2.6 kernel, maybe you use the new libata interfaces that may use /dev/sd* instead of /dev/hd* for your hard disks. you could try to set root=/dev/sda1 in your lilo.conf or specify it in the boot command line.

ATTENTION: when you do this, your old kernel will NOT BOOT. be sure to have a bootable CD (like www.grml.org) with which you can revert the changes if it doesn't help.
 
Old 10-14-2009, 01:24 PM   #12
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
i am confused - i have conflicting data
i cant tell if hda is IDE or ATA
i thought it was ide but now there is evedance otherwise
 
Old 10-14-2009, 01:45 PM   #13
doc.nice
Member
 
Registered: Oct 2004
Location: Germany
Distribution: Debian
Posts: 274

Rep: Reputation: 34
ide is (p)ata, but not SATA...
 
Old 10-14-2009, 01:54 PM   #14
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Originally Posted by doc.nice View Post
be sure to include the partition support for dos partitions, the support for ext2/3 or whatever your root partition uses and the support for your ide controller. All these options muste be compiled into the kernel, not loaded as Modules.
when you switch from an old 2.4 kernel to a rather new 2.6 kernel, maybe you use the new libata interfaces that may use /dev/sd* instead of /dev/hd* for your hard disks. you could try to set root=/dev/sda1 in your lilo.conf or specify it in the boot command line.

ATTENTION: when you do this, your old kernel will NOT BOOT. be sure to have a bootable CD (like www.grml.org) with which you can revert the changes if it doesn't help.
this was bad advice now i cannot boot ether kernel
and i do not know how to fix it with a live cd
 
Old 10-14-2009, 02:16 PM   #15
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,330

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
both kernels say cannot open sda1
 
  


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
Custom compiled kernel will not boot corgi Debian 11 10-18-2008 08:36 AM
new kernel compiled doesn't boot luca74 Slackware 13 02-22-2008 10:15 AM
kernel 2.6.21 wont boot after being compiled AceofSpades19 Linux - General 2 05-09-2007 07:47 PM
Newly compiled kernel won't boot nivantha Linux - Kernel 3 09-14-2006 04:02 AM
Which compiled kernel has been used to boot system? aliamiri Linux - General 2 05-02-2006 11:17 AM


All times are GMT -5. The time now is 05:45 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration