Gentoo Archives: gentoo-amd64

From: Felipe Ribeiro <felipernb@×××××.com>
To: gentoo-amd64@l.g.o, gentoo-user@l.g.o
Subject: [gentoo-amd64] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(2,0)
Date: Mon, 12 Dec 2005 02:18:30
Message-Id: b5deea460512111816g50d7da01v961959d330512757@mail.gmail.com
In Reply to: [gentoo-amd64] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(2,0) by Felipe Ribeiro
1 I've removed Windows from the grub.conf file, just to test, and now
2 when i try to start linux, it reboots the system instead of showing
3 the message: "Kernel panic - not syncing: VFS: Unable to mount root fs
4 on unknown-block(0,0)
5
6 On 12/11/05, Felipe Ribeiro <felipernb@×××××.com> wrote:
7 > Hi,
8 >
9 > I've disabled CONFIG_ROOT_NFS and enabled CONFIG_MSDOS_PARTITION but i
10 > still have the problem :-(
11 > Kernel Panic - not syncing: VFS: Unable to mount root fs on
12 > unknown-block(0,0)
13 >
14 > On 12/11/05, Florian D. <flockmock@×××.at> wrote:
15 > > Felipe Ribeiro wrote:
16 > > > Root-NFS: No NFS server available giving up.
17 > > > VFS: Unable to mount root fs via NFS, trying floppy.
18 > > disable CONFIG_ROOT_NFS (-> File systems
19 > > -> Network File Systems); you don't need it unless you have
20 > > a diskless terminal or something
21 > >
22 > > > VFS: Insert root floppy and press ENTER
23 > > > end-request: I/O error, dev fd0, sector 0
24 > > > VFS: Cannot open root device hda2 or unknown-block(2,0)
25 > > > Please append a correct "root=" boot option.
26 > > > Kerenel panic - not syncing: VFS: Unable to mount root fs on
27 > > > unknown-block(2,0)
28 > > do you have CONFIG_MSDOS_PARTITION enabled?
29 > > ( Location: -> File systems -> Partition Types -> Advanced partition
30 > > selection)
31 > >
32 > > cheers, f
33 > > --
34 > > gentoo-amd64@g.o mailing list
35 > >
36 > >
37 >
38
39 --
40 gentoo-amd64@g.o mailing list

Replies

Subject Author
Re: [gentoo-amd64] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(2,0) Ian McCulloch <ianmcc@××××××××××××××××××.de>