View previous topic :: View next topic |
Author |
Message |
René1983 Tux's lil' helper
Joined: 15 Dec 2003 Posts: 108 Location: Netherlands
|
Posted: Sat Oct 21, 2006 4:23 pm Post subject: Kernel panic : Unable to mount root fs on unknown-block(0,0) |
|
|
I just tried to install gentoo on an old PII system. Everything went smootly till I tried to start my system. I get the following error:
Code: | VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic : Unable to mount root fs on unknown-block(0,0) |
My partition table:
Code: | hda1 = /boot
hda2 = swap
hda3 = /
|
grub.conf Code: |
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux Webserver
root (hd0,0)
kernel /20061021 root=/dev/hda3 |
My mtab
Code: | tmpfs /newroot tmpfs rw 0 0
/dev/hdb /newroot/mnt/cdrom iso9660 ro 0 0
/dev/loop/0 /newroot/mnt/livecd squashfs ro 0 0
proc /newroot/proc proc rw,nodiratime 0 0
sysfs /newroot/sys sysfs rw 0 0
udev /newroot/dev tmpfs rw,nosuid 0 0
devpts /newroot/dev/pts devpts rw 0 0
tmpfs /newroot/mnt/livecd/lib/firmware tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/usr/portage tmpfs rw 0 0
usbfs /newroot/proc/bus/usb usbfs rw 0 0
/dev/hda3 / ext3 rw,data=ordered 0 0
/dev/hda1 /boot ext3 rw,data=ordered 0 0
none /proc proc rw,nodiratime 0 0
udev /dev tmpfs rw,nosuid 0 0 |
In installed gentoo on more than 20 systems the last 2 years, but the last 2 weeks I always get this error!
Could somebody please help me solve this ! |
|
Back to top |
|
|
wynn Advocate
Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Sat Oct 21, 2006 4:32 pm Post subject: |
|
|
Usually when you get "VFS: Cannot open root device "hda3" or unknown-block(0,0)" it means that the high level and the low level IDE chipset drivers are not built in to the kernel.
Would you like to have a look at [FAQ] KC13: I just installed a new kernel and it won't boot and see if it helps?
I can't remember seeing an mtab before, there are a lot of /newroot things, you haven't got an initrd, have you? _________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
|
René1983 Tux's lil' helper
Joined: 15 Dec 2003 Posts: 108 Location: Netherlands
|
Posted: Mon Oct 23, 2006 8:36 pm Post subject: |
|
|
I looked at it and I was able to solve this problem. But I got an other problem for it in return.
Now I get the following message (looks pretty simular)
Code: |
No filesystem could mount root, tried: reiserfs ext3 ext2 vfat iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3-3) |
How can I find out what kind of filesystem my disk uses... I dont understand it, cause I'm pretty sure I use the ext3 filesystem! |
|
Back to top |
|
|
D-M Tux's lil' helper
Joined: 23 Jan 2004 Posts: 103
|
Posted: Mon Oct 23, 2006 9:07 pm Post subject: |
|
|
df -Th
-T = type
-h = human readable
DM |
|
Back to top |
|
|
wynn Advocate
Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Tue Oct 24, 2006 11:03 am Post subject: |
|
|
Ren�1983 wrote: | Now I get the following message (looks pretty simular)
Code: |
No filesystem could mount root, tried: reiserfs ext3 ext2 vfat iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3-3) | How can I find out what kind of filesystem my disk uses... I dont understand it, cause I'm pretty sure I use the ext3 filesystem! | From your posted mtab (the mtab while booted to the install CD it appears) Code: | /dev/hda3 / ext3 rw,data=ordered 0 0
/dev/hda1 /boot ext3 rw,data=ordered 0 0 | both your /boot partition (/dev/hda1) and your root partition (/dev/hda3) are ext3 (probably not a good idea for the boot partition, ext2 is usual).
The error message says that the kernel can't mount /dev/hda3 because the ext3 (and the ext2) filesystem drivers can't recognize it (nor can reiserfs, vfat or iso9660). All these five filesystems have their drivers built in to the kernel.
You probably need to boot up (again!) to your install CD and, without mounting /dev/hda3 on /mnt/gentoo, run Code: | e2fsck -f /dev/hda3 | and post the result. If this doesn't return an error, could you also run Code: | tune2fs -l /dev/hda3 |
_________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
|
René1983 Tux's lil' helper
Joined: 15 Dec 2003 Posts: 108 Location: Netherlands
|
Posted: Tue Oct 31, 2006 12:33 pm Post subject: |
|
|
@D-M
Thnx, I found out I use the ext3 filesystem.
@wynn
Ok, I tried it, and it gives me the following output:
Code: | livecd ~ # e2fsck -f /dev/hda3
e2fsck 1.38 (30-Jun-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda3: 235365/533280 files (0.6% non-contiguous), 439263/1066314 blocks
|
Code: |
livecd ~ # tune2fs -l /dev/hda3
tune2fs 1.38 (30-Jun-2005)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 5dc80b93-9e0d-4ad3-93e9-58ebf07fcce7
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype sparse_super
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 533280
Block count: 1066314
Reserved block count: 53315
Free blocks: 627051
Free inodes: 297915
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16160
Inode blocks per group: 505
Filesystem created: Sat Oct 21 01:06:15 2006
Last mount time: Tue Oct 24 00:05:06 2006
Last write time: Tue Oct 31 14:27:44 2006
Mount count: 0
Maximum mount count: 32
Last checked: Tue Oct 31 14:26:04 2006
Check interval: 15552000 (6 months)
Next check after: Sun Apr 29 14:26:04 2007
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: cf71005a-c464-4e20-84e6-0ec90aca37c0
Journal backup: inode blocks
livecd ~ #
|
I dont know what is wrong with this?
Thnx in advance |
|
Back to top |
|
|
wynn Advocate
Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Tue Oct 31, 2006 7:29 pm Post subject: |
|
|
No, the e2fsck output is fine and there seems nothing out of place in the tune2fs output either.
The only other possibility that suggests itself is that there is another hard drive with three partitions, the third partition hasn't got a filesystem or it is not reiserfs, ext2 or ext3 and the kernel is trying to mount this as root.
If you wish to have a look at all the bootup messages from the kernel and you have a second machine which is networked then you could follow the howto here.
Otherwise I have no idea what's happening _________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
|
René1983 Tux's lil' helper
Joined: 15 Dec 2003 Posts: 108 Location: Netherlands
|
Posted: Tue Oct 31, 2006 9:00 pm Post subject: |
|
|
I dont understand sh*t of it. I got it at many pc's.
Could a broken livecd have something to do with it?
I'm really lost, cause I must do something wrong, cause I cant get any system installed properly! |
|
Back to top |
|
|
wynn Advocate
Joined: 01 Apr 2005 Posts: 2421 Location: UK
|
Posted: Tue Oct 31, 2006 9:08 pm Post subject: |
|
|
You could try installing using Ubuntu, for instance, and the The Gentoo Linux alternative installation method HOWTO if you suspect the install CD.
You could try installing Ubuntu to see if it works, and, if it does, what tweaks to the kernel it uses.
Further thoughts: could you give more details on the "old PII system"? Hard disk type, CPU, BIOS maker and date, lspci?
If the system is old enough, ACPI (which appears to be enabled by default in kernel configs) may not work properly. You could try downloading and running the Linux-ready Firmware Developer Kit from http://www.linuxfirmwarekit.org/ to see if it tells you anything.
Booting the kernel with netconsole enabled will show you all the bootup messages, there may be something there that helps solve the mystery. _________________ The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|