LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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-01-2005, 11:55 AM   #1
ajunt_ornj
LQ Newbie
 
Registered: Mar 2004
Distribution: Mandrake 10
Posts: 7

Rep: Reputation: 0
Boot Issue


I have searched and searched but cannot find what appears to be a suitable answer to my dilemma.

I have this old computer and decided to put Vector Linux on it. My first problem was that I could not get any CD's to boot from it. So I pulled the hard drive out and put it in another machine and used that to install Linux. After that I put the hard drive back into the first machine and went to boot up. I made it to the LILO screen just fine. However, after that I was unable to get Linux to boot up. All I can get is this error message:

VFS: Cannot open root device "301" or 03:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:01

After searching around a bit, it seems to me that there is an issue with the LILO config file. I managed to put my hard drive back into another machine and boot up with a Knoppix LiveEval CD and here is what I came up with for my lilo.config:

--------------------------------------------------------------------------------------------------

#LILO configuration file
#generated by 'liloconfig'
#
#Start LILO global section
boot = /dev/hda
default = linux
prompt
timeout = 1200
#Override dangerous defaults that rewrite the partition table:
change-rules
reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ 640x480x256
vga = 769
# Normal VGA console
# vga = normal
#VESA framebuffer console @ 1024x768x64k
# vga=791
#VESA framebuffer console @ 1024x768x32k
# vga=790
#VESA framebuffer console @ 1024x768x256
# vga=773
#VESA framebuffer console @ 800x600x64k
# vga=788
#VESA framebuffer console @ 800x600x32k
# vga=787
#VESA framebuffer console @ 800x600x256
# vga=771
#VESA framebuffer console @ 640x480x64k
# vga=785
#VESA framebuffer console @ 640x480x32k
# vga=784
#VESA framebuffer console @ 640x480x256
# vga=769

# end LILO global section
# Partition 1: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hda1
label = linux
append = " "
read-only

# Partition 2: Linux TUI mode
image = /boot/vmlinuz
root = /dev/hda1
label = linux-tui
append = "2 "
read-only

# Partition 3: Linux GUI mode
image = /boot/vmlinuz
root = /dev/hda1
label = linux-gui
append = "5 "
read-only

# Partition 4: Linux
image = /boot/vmlinuz-2.6.11.7
root = /dev/hda1
label = 2.6.11.7
append = " "
read-only
# Partition 5: Linux
image = /boot/vmlinuz-acpi-2.4.29
root = /dev/hda1
label = acpi-2.4.29
append = " "
read-only
# Partition 6: Linux
image = /boot/vmlinuz-adaptec-2.4.29
root = /dev/hda1
label = adaptex-2.4.29
append = " "
read-only
# Partition 7: Linux
image = /boot/vmlinuz-sata-2.4.29
root = /dev/hda1
label = sata-2.4.29
append = " "
read-only
--------------------------------------------------------------------------------------------------

During a few searches I found something that suggested that I change the first:

boot = /dev/hda

to this:

boot = /dev/hda1

I went to try and do that while under Knoppix live-eval but wasn't allowed to.

I think I have given all relevant information. If I need to give more let me know.

thanx
 
Old 10-01-2005, 12:04 PM   #2
rextor
Member
 
Registered: Jul 2005
Location: india
Posts: 47

Rep: Reputation: 15
i had similar problems. This helped me solve it. actually before looking at lilo/grub see if you have compiled the kernel with proper options.
 
Old 10-01-2005, 12:50 PM   #3
ajunt_ornj
LQ Newbie
 
Registered: Mar 2004
Distribution: Mandrake 10
Posts: 7

Original Poster
Rep: Reputation: 0
Okay, I've have read that post about three times now. My new problem is this:

Where do I start?

I'm not really sure what my first move should be.

thanx
 
Old 10-01-2005, 01:57 PM   #4
rextor
Member
 
Registered: Jul 2005
Location: india
Posts: 47

Rep: Reputation: 15
if your two machines (motherboards/chipsets/HDD etc) are not exactly same then you are bound to get errors. i beieve thats because the mobo does not match.the kernel was installed accordingly. so when you changed the machine the driver required for that machine were not present.
two solutions
one - try and install it on the required machine (with the requied h/w in place)
two - compile the kernel on the present installation with proper options
 
  


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
VFS-boot-issue dranath Linux - Software 2 01-17-2005 03:51 PM
Boot Issue GAMEOVER Fedora 13 12-16-2004 07:22 PM
Boot issue GAMEOVER Fedora 2 12-16-2004 12:27 AM
Boot issue prufrock Linux - Software 3 01-26-2004 10:00 PM
boot issue Hobobob Linux - Newbie 6 08-25-2001 07:17 PM


All times are GMT -5. The time now is 05:44 AM.

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