Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Boot problem at the first boot
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 1:05 pm    Post subject: Boot problem at the first boot Reply with quote

Hello i'm new in Linux and Gentoo,
i get the following message at starting:

no filesystem coul mount root, tried: ext3 ext2 vfat iso9660
kernel panic -not syncing: VFS: Unable to mount root fs on unkown block(3,3)

I formated the root parition with ext3. I activate this in the menuconfig.

Had anyone an idea what i make wrong?
Back to top
View user's profile Send private message
elestedt
Guru
Guru


Joined: 13 Mar 2005
Posts: 383

PostPosted: Sun Oct 15, 2006 1:17 pm    Post subject: Re: Boot problem at the first boot Reply with quote

aks wrote:
Hello i'm new in Linux and Gentoo,
i get the following message at starting:

no filesystem coul mount root, tried: ext3 ext2 vfat iso9660
kernel panic -not syncing: VFS: Unable to mount root fs on unkown block(3,3)

I formated the root parition with ext3. I activate this in the menuconfig.

Had anyone an idea what i make wrong?

Sounds like an incorrect entry in either the grub.conf file (invalid root kernel parameter) or in /etc/fstab
Back to top
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 1:29 pm    Post subject: Reply with quote

In the first moment i also think so but i didn't find a mistake here my fstab:

/dev/hda1 /boot ext2 defaults,noatime 1,2
/dev/hda3 / ext3 noatime 0,1
/dev/hda2 none swap sw 0,0


and grub.conf:

title=test
root(hd0,0)
kernel /boot/kernel-2.6.17-gentoo-rb8-b1 root=/dev/hda3
Back to top
View user's profile Send private message
elestedt
Guru
Guru


Joined: 13 Mar 2005
Posts: 383

PostPosted: Sun Oct 15, 2006 1:42 pm    Post subject: Reply with quote

aks wrote:
In the first moment i also think so but i didn't find a mistake here my fstab:

/dev/hda1 /boot ext2 defaults,noatime 1,2
/dev/hda3 / ext3 noatime 0,1
/dev/hda2 none swap sw 0,0


and grub.conf:

title=test
root(hd0,0)
kernel /boot/kernel-2.6.17-gentoo-rb8-b1 root=/dev/hda3

assuming that's correct the only whing I can think of is that you've missed the device driver for your controller.
Does the message appear after the kernel has started? (i.e. is grub complaining or the kernel)
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Oct 15, 2006 1:45 pm    Post subject: Reply with quote

Have you got ext3 support built in to your kernel not a module?

"unknown-block (3,3)" seems to show that you haven't got support for IDE and your particular IDE chipset built in to your kernel (again, not a module).

You may find some helpful hints in [FAQ] KC13: I just installed a new kernel and it won't boot

Finally, "no filesystem could mount root, tried: ext3 ext2 vfat iso9660" may show that your root filesystem can't be recognized. Would you like to boot up your install CD again and run
Code:
tune2fs -l /dev/hda3
If you get something like
Code:
tune2fs 1.39 (29-May-2006)
Filesystem volume name:   2006.1-home
Last mounted on:          <not available>
Filesystem UUID:          8b8d8232-f09e-403c-927d-57277698ea29
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              528000
Block count:              1054265
Reserved block count:     52713
Free blocks:              806347
Free inodes:              516548
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16000
Inode blocks per group:   500
Filesystem created:       Sat Sep  9 11:46:02 2006
Last mount time:          Sun Oct 15 13:48:51 2006
Last write time:          Sun Oct 15 13:48:51 2006
Mount count:              18
Maximum mount count:      -1
Last checked:             Mon Oct  9 14:21:19 2006
Check interval:           2592000 (1 month)
Next check after:         Wed Nov  8 13:21:19 2006
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:      1349a4fa-e8de-4c1d-b74b-55ac91075b59
Journal backup:           inode blocks
Note particularly "Filesystem features: has_journal filetype needs_recovery sparse_super" and the presence of "Journal inode" and "Journal backup" then it is probably OK.
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 1:48 pm    Post subject: Reply with quote

The message appear after grub. I think the problem must be in the kernel configuration.
Back to top
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 1:58 pm    Post subject: Reply with quote

First thx for the many replies in the short time at all.

I do tune2fs -l /dev/hda3, i get a similar output like you the only think which is different is, by the features i have no "needs_recovery".
Ext3 support is built in the kernel.
Back to top
View user's profile Send private message
elestedt
Guru
Guru


Joined: 13 Mar 2005
Posts: 383

PostPosted: Sun Oct 15, 2006 2:03 pm    Post subject: Reply with quote

aks wrote:
First thx for the many replies in the short time at all.

I do tune2fs -l /dev/hda3, i get a similar output like you the only think which is different is, by the features i have no "needs_recovery".
Ext3 support is built in the kernel.

Which harddrive controller chipset do you have? And how did you compile support for it?
Back to top
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 2:21 pm    Post subject: Reply with quote

I have a harddrive controller from intel:
when i do lspci:

IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)

So i select "Intel PIIXn chipsets support" in the menuconfig.
Back to top
View user's profile Send private message
elestedt
Guru
Guru


Joined: 13 Mar 2005
Posts: 383

PostPosted: Sun Oct 15, 2006 2:22 pm    Post subject: Reply with quote

aks wrote:
I have a harddrive controller from intel:
when i do lspci:

IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)

So i select "Intel PIIXn chipsets support" in the menuconfig.

And you compiled it into the kernel or as a module?
Back to top
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 2:23 pm    Post subject: Reply with quote

I compiled it in the kernel with "*".
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Oct 15, 2006 2:31 pm    Post subject: Reply with quote

Quote:
So i select "Intel PIIXn chipsets support" in the menuconfig. I compiled it in the kernel with "*".
So that just leaves the high level drivers.

From the KC13 candidate
Quote:
These are the high level drivers you will need
Code:
   Device Drivers  --->
    ATA/ATAPI/MFM/RLL support  --->
<*> ATA/ATAPI/MFM/RLL support
<*>   Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
<*>     Include IDE/ATA-2 DISK support
[*]     Use multi-mode by default
<*>     Include IDE/ATAPI CDROM support
<*>     generic/default IDE chipset support
[*]     CMD640 chipset bugfix/support
[*]     PCI IDE chipset support
[*]       Sharing PCI IDE interrupts support
<*>       Generic PCI IDE Chipset Support
<*>       RZ1000 chipset bugfix/support
[*]       Generic PCI bus-master DMA support
[*]         Use PCI DMA by default when available
You can probably do without "CMD640 chipset bugfix/support" and "RZ1000 chipset bugfix/support" but it does no harm to leave them in.
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 2:36 pm    Post subject: Reply with quote

I have done it completly like it is said in the KC13 FAQ. I have selected all the parts that you have written.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Oct 15, 2006 2:42 pm    Post subject: Reply with quote

Just one small thing, you've got a boot partition and your grub.conf is
Code:
title=test
root(hd0,0)
kernel /boot/kernel-2.6.17-gentoo-rb8-b1 root=/dev/hda3
The kernel line should be
Code:
kernel /kernel-2.6.17-gentoo-rb8-b1 root=/dev/hda3
because, when GRUB looks at it, it isn't mounted under root, the kernel image is in this partition's root directory.

However, this may make no difference as, when GRUB is installed, there is a symlink
Code:
lrwxrwxrwx  1 root root       1 Sep  9 11:56 boot -> ./
put in the /boot/directory which should take care of changing "/boot/kernel-2.6.17-gentoo-rb8-b1" into "./kernel-2.6.17-gentoo-rb8-b1"

Another thing is, when you installed your kernel, was the boot partition mounted? That is, is the kernel image in /dev/hda1 and not the directory /boot on /dev/hda3.

You have recompiled your kernel several times, can you check that you are trying to boot the latest one (check the timestamps in /usr/src/linux and the kernel image timestamp)?
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 3:02 pm    Post subject: Reply with quote

The kernel gets loaded by the system so i think the path is correct.
Yes the boot partition was always mounted and i copy the bzImage in the boot- directory.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Oct 15, 2006 6:01 pm    Post subject: Reply with quote

Sorry, that was my last shot. No further ideas :(
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 6:44 pm    Post subject: Reply with quote

Ok thx for your help i hope i can find the mistake in the kernel configuration.
Back to top
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Sun Oct 15, 2006 7:09 pm    Post subject: Reply with quote

Ok now let us think a moment! The kernel starts and then the failure advents. The failure means that the kernel can't mount the root partition. What are the reasons for this. Could it be that my harddrive have a wrong format? Thats the only idea i have but i format the harddrive with ext3! Is there a way to control that?
Does someone have a idea please post.


I have a Thinpad 600e is there someone woh run gentoo on this notebook?
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Oct 15, 2006 7:39 pm    Post subject: Reply with quote

aks wrote:
Ok now let us think a moment! The kernel starts and then the failure advents. The failure means that the kernel can't mount the root partition. What are the reasons for this. Could it be that my harddrive have a wrong format? Thats the only idea i have but i format the harddrive with ext3! Is there a way to control that?
Yes, and I'm afraid you've just done that with tune2fs. This displays the information from the filesystem's superblock and it will show an error if it can't find it or the superblock has the wrong "magic number". It has loaded the kernel from the boot partition so this filesystem is OK and the root filesystem has been checked by tune2fs.
aks wrote:
I have a Thinkpad 600e
There is a HOWTO on installing Gentoo in the 600e at Gentoo Linux i686-1.4-20030911 on a IBM Thinkpad 600e but it's very old, it talks about a 2.4.29 kernel.

Rather more modern, Ubuntu 6.06 Ubuntu 6.06 on the Thinkpad 600E might have some useful tips.

This last has ThinkWiki's Category:600E which you might find useful too.
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Wed Oct 18, 2006 5:28 pm    Post subject: Reply with quote

Hello,
it works now, i copy the kernel config file from the page you told me. Now i have still a small problem, when i boot gentoo say to me:

*Mounting proc at /proc ...
*The "mount" command failed with error:
line 25: mount command not found

then i give root password and it continues.

Is that a problem ?

fstab:

proc /proc proc defaults 0 0

i try too with:

none /proc proc defaults 0 0

same error

Does someone have an idea?
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Wed Oct 18, 2006 6:21 pm    Post subject: Reply with quote

Could you post all your /etc/fstab, please? The mount command is "/bin/mount" and, by the time the initscripts are running, root should have been mounted and /bin should be accessible.

When it gives the error, does it say "Give the root password for maintenance or Control-D for a shell"? If it does, could you type Control-D and then run
Code:
ls -l /bin/mount
and post what happens?
_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Wed Oct 18, 2006 6:43 pm    Post subject: Reply with quote

When i type control+D the system reboots.
When i give the root password a console starts.
I make: ls -l /bin/mount

--> no such file or directory.

Befor the failer with proc appears, i can see:

VFS:Mounted root (ext3 filesystem) readonly could be there a interrelationship?

Here my fstab:
/dev/hda1 /boot ext2 defaults,noatime 1 2
/dev/hda3 / ext3 noatim,rw 0 1
/dev/hda2 none swap sw 0 0
proc /proc proc defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Wed Oct 18, 2006 7:04 pm    Post subject: Reply with quote

Your fstab looks OK.

I haven't been able to find a kernel message matching "VFS:Mounted root (ext3 filesystem) readonly could be there a interrelationship?".

All I can think of is that somehow the partitions have got mixed up. Could you post the output of
Code:
sfdisk -l /dev/hda

_________________
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
View user's profile Send private message
aks
n00b
n00b


Joined: 15 Oct 2006
Posts: 26

PostPosted: Wed Oct 18, 2006 7:18 pm    Post subject: Reply with quote

The kernel message is ""VFS:Mounted root (ext3 filesystem) readonly". Sorry I forgot the ",".

sfdisk -l /dev/hda

--> Device........Boot..Start..End..#cyls...#blocks....Id...System
/dev/hda1...... *.....0+..... 8...... 9-.......68008+..83...Linux
/dev/hda2..............9.......75..... 67......506520...82...Linux Swap /solaris
/dev/hda3.............76......832....757....5722920..83...Linux
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Wed Oct 18, 2006 7:50 pm    Post subject: Reply with quote

aks wrote:
The kernel message is ""VFS:Mounted root (ext3 filesystem) readonly". Sorry I forgot the ",".
I misread your sentence, this message will always appear as the root partition is first mounted readonly for the filesystem check and then remounted read/write for normal use.
aks wrote:
sfdisk -l /dev/hda

--> Device........Boot..Start..End..#cyls...#blocks....Id...System
/dev/hda1...... *.....0+..... 8...... 9-.......68008+..83...Linux
/dev/hda2..............9.......75..... 67......506520...82...Linux Swap /solaris
/dev/hda3.............76......832....757....5722920..83...Linux
This also looks perfectly OK.

Can you boot back into the install CD, mount /dev/hda3 on /mnt/gentoo and /dev/hda1 on /mnt/gentoo/boot and then see if there is a /mnt/gentoo/bin/mount?
_________________
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
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
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