View previous topic :: View next topic |
Author |
Message |
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Fri Aug 06, 2004 1:00 am Post subject: (boot problems) kernel panic, now i'm panicked-unresolved :( |
|
|
i finished the install tutorial and I guess I used hda when I should've used sda at some place or another. i have no idea where, cuz i'm one PANICKED newb. Please tell me I don't have to redo this long process
when i boot after a good bit of output to the screen i get this message and I can't input to the screen or anything else, computer becomes unresponsive:
Code: |
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a corret "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
|
Please help this struggling gentoo wanna be guru.
Last edited by glory452 on Wed Aug 11, 2004 1:44 am; edited 2 times in total |
|
Back to top |
|
|
bmichaelsen Veteran
Joined: 17 Nov 2002 Posts: 1277 Location: Hamburg, Germany
|
Posted: Fri Aug 06, 2004 1:16 am Post subject: |
|
|
Try typing "e" when the grub screen comes up - you can then edit the "root=/dev/hda3" bootparameter and boot with that. Also check the /etc/fstab file, just to be sure.
BTW, for stuff like this #gentoo (official IRC-channel on freenode) is a good resource (faster answer, you can ask again if something is unclear ... |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Fri Aug 06, 2004 1:43 am Post subject: |
|
|
bmichaelsen wrote: | Try typing "e" when the grub screen comes up - you can then edit the "root=/dev/hda3" bootparameter and boot with that. Also check the /etc/fstab file, just to be sure.
BTW, for stuff like this #gentoo (official IRC-channel on freenode) is a good resource (faster answer, you can ask again if something is unclear ... |
thanks for the help! I never get the grub screen and how can I get to /etc/fstab if I never get a prompt? I'll also check out the irc channel. If I get an answer there I'll make sure and update this thread to reflect that. thanks again! |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Fri Aug 06, 2004 4:39 am Post subject: |
|
|
aight i managed to get to a prompt. to make my life easier i unmerged grub, deleted grub.conf and emerged lilo.
I'm running VMware on an XP machine. The allocated linux space is on a raid array, hence the sda. I've double checked to make sure my filesystem is correct (ext2 boot and ext3 root) and it is compiled with the kernel (not module). I recieve the following error when trying to boot (lilo comes up fine, it is after this)
Code: | VFS: Cannot open root device "803" or unknown-block(8,3)
Please append a corret "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
|
lilo config file
Code: |
boot=/dev/sda
prompt
timeout=50
default=gentoo
vga=788
image=/boot/kernel-2.7.-gentoo-r11
label=gentoo
read-only
root=/dev/sda3
|
fstab
Code: |
/dev/sda1 /boot ext2 defaults,noatime 1 2
/dev/sda2 none swap sw 0 0
/dev/sda3 / ext3 noatime 0 1
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
|
Any help anyone.......plz? |
|
Back to top |
|
|
gnuageux Veteran
Joined: 17 Apr 2004 Posts: 1201
|
Posted: Fri Aug 06, 2004 7:18 am Post subject: |
|
|
Shouldnt this line: Code: | /dev/sda3 / ext3 noatime 0 1 |
in /etc/fstab read: Code: | /dev/sda3 / ext3 noatime 0 0 | ? _________________ The realOTW: http://forums.realotw.org/index.php
Registered Linux user#364538 |
|
Back to top |
|
|
mattjgalloway l33t
Joined: 16 Mar 2004 Posts: 761 Location: Coventry, UK
|
Posted: Fri Aug 06, 2004 5:12 pm Post subject: |
|
|
Quote: | Shouldnt this line: Code:
/dev/sda3 / ext3 noatime 0 1
in /etc/fstab read: Code:
/dev/sda3 / ext3 noatime 0 0
? |
Not by what the install doc says...
But anyway, your problem... I'm guessing it's similar to what I had when I installed. It'll be to do with the modules you installed into your kernel.
Check that you have the correct drivers for your IDE/SATA/SCSI controller(s) installed. I had this error when I thought I would be using sda in my new installation however it was hda in my installation as opposed to sda during LiveCD. _________________ AMD64 3200+, 1024MB RAM, Gentoo Linux
MacBook Core Duo, 1024MB RAM, Leopard |
|
Back to top |
|
|
gnuageux Veteran
Joined: 17 Apr 2004 Posts: 1201
|
Posted: Fri Aug 06, 2004 5:24 pm Post subject: |
|
|
Oh is it 0 1 if its sda then? (never read that section of the install doc, thought that itd be the same)
Hmmm, portions of my /etc/fstab:
Code: | /dev/hda1 /boot ext3 noauto,noatime 1 1
/dev/hda3 / ext3 noatime 0 0
/dev/hda2 none swap sw 0 0
|
? Maybe I am wrong but it hasnt complained. _________________ The realOTW: http://forums.realotw.org/index.php
Registered Linux user#364538
Last edited by gnuageux on Sat Aug 07, 2004 5:57 am; edited 1 time in total |
|
Back to top |
|
|
mattjgalloway l33t
Joined: 16 Mar 2004 Posts: 761 Location: Coventry, UK
|
Posted: Fri Aug 06, 2004 5:32 pm Post subject: |
|
|
From the install manual:
Code: | /dev/hda1 /boot ext2 defaults,noatime 1 2
/dev/hda2 none swap sw 0 0
/dev/hda3 / ext3 noatime 0 1 |
Note the 0 1 _________________ AMD64 3200+, 1024MB RAM, Gentoo Linux
MacBook Core Duo, 1024MB RAM, Leopard |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Fri Aug 06, 2004 10:24 pm Post subject: |
|
|
mattjgalloway wrote: |
Not by what the install doc says...
But anyway, your problem... I'm guessing it's similar to what I had when I installed. It'll be to do with the modules you installed into your kernel.
Check that you have the correct drivers for your IDE/SATA/SCSI controller(s) installed. I had this error when I thought I would be using sda in my new installation however it was hda in my installation as opposed to sda during LiveCD. |
hmmm i hadn't thought about that. I don't know if the correct drivers are installed...i'll check on that. Also I'll try using hda. Weird it would be one way in the liveCD and another way on installation.. |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Sat Aug 07, 2004 4:52 am Post subject: |
|
|
glory452 wrote: | mattjgalloway wrote: |
Not by what the install doc says...
But anyway, your problem... I'm guessing it's similar to what I had when I installed. It'll be to do with the modules you installed into your kernel.
Check that you have the correct drivers for your IDE/SATA/SCSI controller(s) installed. I had this error when I thought I would be using sda in my new installation however it was hda in my installation as opposed to sda during LiveCD. |
hmmm i hadn't thought about that. I don't know if the correct drivers are installed...i'll check on that. Also I'll try using hda. Weird it would be one way in the liveCD and another way on installation.. |
I tried hda but when i run /sbin/lilo it gives errors. |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Sat Aug 07, 2004 5:49 am Post subject: |
|
|
ok after tirelessly trying every combination of lilo.conf and fstab possible, i've found out why I can't boot. I'm using the ASUS P4P800 deluxe motherboard with built in raid which utilizes an onboard via 6410 controller. This is not supported in linux. (see http://forums.viaarena.com/messageview.cfm?catid=28&threadid=41397 for tons of info)
I did find however, that drivers are now available but none are listed for gentoo ( http://www.viaarena.com/?PageID=297#raid )
It seems like I shouldn't even be able to fdisk from the livecd if it wasn't working though?? If it is working, what should I check in the kernel to enable raid support at boot time? I didn't see any raid drivers available in the SCSI section :-/
Please help, I'd love to get into gentoo soon |
|
Back to top |
|
|
RJNFC n00b
Joined: 07 Dec 2002 Posts: 19
|
Posted: Sat Aug 07, 2004 8:15 am Post subject: |
|
|
I believe, though I am not certain, that you should be able to use those drivers in Gentoo. Most linux distros are fundamentally the same, and you probably can use the drivers no problem. However, you'd have to find someone who knows a bit more about the way these things work. It may depend on the kernel you have or the way the drivers are presented. No harm in trying, though.
EDIT: I took a look at the drivers, but I can't say for sure. They don't have source code in them, which may mean you're out of luck unless you have a specific kernel compiled with a specific compiler version, as would come in a boxed distro. I'm really at the limits of my working knowledge here, though. If I were you, I'd just try the drivers out. You won't hurt your system, and it might work
Last edited by RJNFC on Sat Aug 07, 2004 8:33 am; edited 1 time in total |
|
Back to top |
|
|
RJNFC n00b
Joined: 07 Dec 2002 Posts: 19
|
Posted: Sat Aug 07, 2004 8:22 am Post subject: |
|
|
Also, and this is obviously a guess at best, are you sure your kernel is "/boot/kernel-2.7.-gentoo-r11" because that seems weird to me. Notice you have a dot and then a hyphen? Are you sure that's right? Again, just a guess on my part, obviouly. |
|
Back to top |
|
|
vbenares Apprentice
Joined: 13 Aug 2003 Posts: 205
|
Posted: Sat Aug 07, 2004 1:45 pm Post subject: |
|
|
Another complete guess: did you enable the scsi/sata drive options in the kernel? (My box is set up with hdb# and when I enabled the sata option in the kernel, I managed to trigger a kernel panic. Removing the option took it back to bootable.) |
|
Back to top |
|
|
paulecoyote n00b
Joined: 06 Aug 2004 Posts: 61
|
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Sat Aug 07, 2004 6:40 pm Post subject: |
|
|
RJNFC wrote: | are you sure your kernel is "/boot/kernel-2.7.-gentoo-r11" because that seems weird to me. Notice you have a dot and then a hyphen? Are you sure that's right? Again, just a guess on my part, obviouly. |
My kernel is /boot/kernel-2.6.7-gentoo-r11
I don't know where you're referring to that at so I can't address that issue.
I'll give those drivers a shot at least and see what happens
vbenares wrote: |
Another complete guess: did you enable the scsi/sata drive options in the kernel? (My box is set up with hdb# and when I enabled the sata option in the kernel, I managed to trigger a kernel panic. Removing the option took it back to bootable.) |
i did enable the scsi/saa drive options. If the drivers don't do the trick, I'll try that.
I've seen that but wasn't sure if I needed to do that. I don't really even understand what it means cuz i'm just a newbie. I'll try this before the drivers though. One question: Do i just boot into the system through the livecd, execute the command
Code: | mount --bind /dev /mnt/gentoo/dev |
then chroot into the system, make sure my config files are right and reboot? |
|
Back to top |
|
|
Ooblick n00b
Joined: 07 Feb 2004 Posts: 34
|
Posted: Tue Aug 10, 2004 10:36 am Post subject: (boot problems) kernel panic, now i'm panicked |
|
|
Sorry I didn't spot this earlier. I don't know why VMWare kernel panics with a 2.6 kernel on gentoo, but it does. To fix it, in VMWare, whilst your virtual machine is stopped:
Select "Virtual Machine Settings" from the edit menu,
Click the "options" tab
Select "Advanced"
Tick "Disable Acceleration".
In summary, to get this to boot, you need to Disable Acceleration in VMWare. I know not why |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Wed Aug 11, 2004 12:16 am Post subject: Re: (boot problems) kernel panic, now i'm panicked |
|
|
Ooblick wrote: | Sorry I didn't spot this earlier. I don't know why VMWare kernel panics with a 2.6 kernel on gentoo, but it does. To fix it, in VMWare, whilst your virtual machine is stopped:
Select "Virtual Machine Settings" from the edit menu,
Click the "options" tab
Select "Advanced"
Tick "Disable Acceleration".
In summary, to get this to boot, you need to Disable Acceleration in VMWare. I know not why |
thanks but I get the same error _________________ my advice may be hazardous to your systems health. Use at your own risk. |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Wed Aug 11, 2004 1:43 am Post subject: |
|
|
aight, i did the following:
1) boot off of liveCD
2) mount partitions
3) executed: Code: | mount --bind /dev /mnt/gentoo/dev |
4) chroot into system
5) updated lilo.conf and ran /sbin/lilo
I received the following error: Code: | Fatal: raid_setup: start("/dev/hda") |
lilo.conf looks like:
Code: |
boot=/dev/hda
prompt
timeout=20
default=gentoo
vga=755
image=/boot/kernel-2.6.7-gentoo-r11
label=gentoo
read-only
root=/dev/hda3
|
Where should I go from here? _________________ my advice may be hazardous to your systems health. Use at your own risk. |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Wed Aug 11, 2004 1:46 am Post subject: |
|
|
one more question i don't think i ever received an answer to:
If when booting from livecd and fdisk sees my drives, do i need to make sure i have special drivers installed for the kernel for the raid controller? _________________ my advice may be hazardous to your systems health. Use at your own risk. |
|
Back to top |
|
|
AggieEmpeg n00b
Joined: 16 Apr 2002 Posts: 63
|
Posted: Wed Aug 11, 2004 2:59 am Post subject: |
|
|
Glory,
I think that the kernel on the LiveCD is completely modular. So when it autodetects your hardware (or tries to), it loads the modules that it thinks are needed. If you are able to access your drive through the LiveCD, then you should be able to run lsmod to see what modules were loaded. This should give you a clue as to what you need to compile into your kernel.
Good luck. |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Wed Aug 11, 2004 3:34 am Post subject: |
|
|
AggieEmpeg wrote: | Glory,
I think that the kernel on the LiveCD is completely modular. So when it autodetects your hardware (or tries to), it loads the modules that it thinks are needed. If you are able to access your drive through the LiveCD, then you should be able to run lsmod to see what modules were loaded. This should give you a clue as to what you need to compile into your kernel.
Good luck. |
output of lsmod (any ideas which one the raid controller uses?)
Code: |
Module (Used By)
----------------------
ohci_hcd
uhci_hcd
intel_agp
agpgart (intel_agp)
evdev
tsdev
sd_mod
snd_ens1371
snd_rawmidi (snd_ens1371)
snd_seq_device (snd_rawmidi)
snd_pcm (snd_ens1371)
snd_page_alloc (snd_pcm)
snd_timer (snd_pcm)
snd_ac97_codec (snd_ens1371)
snd (snd_ens1371,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer,snd_ac97_coded)
soundcore (snd)
gameport (snd_ens1371)
BusLogic
pcnet32
mii (pcnet32)
parport_pc
parport (parport_pc)
rtc
sbp2
ohci1394
ieee1394 (sbp2,ohci1394)
usb_storage
ehci_hcd
|
_________________ my advice may be hazardous to your systems health. Use at your own risk. |
|
Back to top |
|
|
AggieEmpeg n00b
Joined: 16 Apr 2002 Posts: 63
|
Posted: Wed Aug 11, 2004 3:48 am Post subject: |
|
|
Glory,
The sd_mod module is the scsi disk drive module. It may be that the generic scsi disk support module is all you need compiled into your kernel.
Everything else, with the exception of sd_mod and Buslogic are sound card, firewire, usb, other input drivers.
evdev.... is that a Wacom drawing tablet attached to your machine? |
|
Back to top |
|
|
glory452 n00b
Joined: 27 Sep 2003 Posts: 27
|
Posted: Wed Aug 11, 2004 3:54 am Post subject: |
|
|
AggieEmpeg wrote: | Glory,
The sd_mod module is the scsi disk drive module. It may be that the generic scsi disk support module is all you need compiled into your kernel.
Everything else, with the exception of sd_mod and Buslogic are sound card, firewire, usb, other input drivers.
evdev.... is that a Wacom drawing tablet attached to your machine? |
ok cool i'll look to make sure that's compiled into my kernel...should it just be listed as sd_mod in the kernel configuration menu?
i don't don't what evdev is....i don't have a drawing tablet although that would be cool for something i'm sure. The only peripheals attached are soundcard and nic so I have no idea. _________________ my advice may be hazardous to your systems health. Use at your own risk. |
|
Back to top |
|
|
AggieEmpeg n00b
Joined: 16 Apr 2002 Posts: 63
|
Posted: Wed Aug 11, 2004 3:58 am Post subject: |
|
|
It won't be listed as sd_mod... it is under SCSI Support -> SCSI Support -> SCSI disk support... try compiling it in. |
|
Back to top |
|
|
|