From: Hulin Thibaud <hulin.thibaud@wanadoo.fr>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, darkhack@gmail.com
Subject: Re: kernel panic - not syncing: VFS - unable to mount root fs on unknown-block
Date: Mon, 14 Aug 2006 16:44:32 +0200 [thread overview]
Message-ID: <44E08C50.5070904@wanadoo.fr> (raw)
In-Reply-To: <44E07B36.6070508@gmail.com>
Sorry, new kernel is 2.6.17. to install suspend2.
I believe using LVM, but I'm not sure.
In effect, initrd is not present ! I rode this lines in my menu.lst :
title Ubuntu, kernel 2.6.171915
root (hd1,4)
kernel /boot/vmlinuz-2.6.171915 root=/dev/hdb5 ro quiet splash
savedefault
boot
So, I suppose that's the center of the problem, but actually, I don't
know how to solve it.
Nick Manley a écrit :
> I think you meant 2.6.18? Anyways, I'm not expert but I usually have
> problems when using oldconfig. It seems you have your kernel settings
> configured properly and have included all the proper stuff (ext3, ide
> drivers) to be built in. I would try disabling SCSI if you aren't
> using it. Another thing to look at would be your settings in GRUB (or
> lilo). Your particular setup might vary but it should look something
> like this...
>
> title Linux 2.6.18
> root (hd0,2)
> kernel /boot/bzImage-2.6.18 root=/dev/hda3 ro
> # you might also have an "initrd" placed here
>
> If you search Google you can find other suggestions as well and also
> posting to your distribution's forum might be a good idea too as the
> kernel mailing list is usually a place for reporting bugs and
> discussing kernel development. Basically it is a last resort kind of
> thing if you can't find the information anywhere else.
>
> On 8/13/06, Hulin Thibaud <hulin.thibaud@wanadoo.fr> wrote:
>> Hello !
>> I'm trying to compile my own kernel for drivers on two computers, but
>> that fails. A the boot, I have this error :
>> kernel panic - not syncing: VFS Unable to mount root fs on unknow-block
>> (3.69)
>>
>> I'm using the kernel 2.6.19 with Ubuntu Dapper. I use the old boot
>> config and I type make oldconfig, so I don't understand why there are an
>> error with the near same configuration.
>> I suppose that I must compile not in module but in hard support for my
>> IDE chipset, harddisk and file system. Probably, I don't understand how
>> do exactly. I do that :
>> lspci |grep IDE
>> 0000:00:11.1 IDE interface: VIA Technologies, Inc.
>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>> make xconfig
>> -Device Drivers
>> --* ATA/ATAPI/MFM/RLL support
>> --- * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
>> --- * Include IDE/ATA-2 DISK support
>> --- * PCI IDE chipset support
>> ---- * Generic PCI IDE Support
>> ----- * VIA82CXXX chipset support
>> - File systems
>> -- * Ext3 journalling file system support
>> --- * Ext3 extended attributes
>> ---- * Ext3 POSIX Access Control Lists
>> ---- * Ext3 Security Labels
>>
>> Have I forgot anything ?
>>
>> Thanks very much,
>> Thibaud.
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
>
Jiri Slaby a écrit :
> Hulin Thibaud wrote:
>> Hello !
>> I'm trying to compile my own kernel for drivers on two computers, but
>> that fails. A the boot, I have this error :
>> kernel panic - not syncing: VFS Unable to mount root fs on
>> unknow-block (3.69)
>>
>> I'm using the kernel 2.6.19 with Ubuntu Dapper. I use the old boot
>
> Wow, 2.6.18 wasn't released yet and you have 2.6.19, cool.
>
>> config and I type make oldconfig, so I don't understand why there are
>> an error with the near same configuration.
>> I suppose that I must compile not in module but in hard support for my
>> IDE chipset, harddisk and file system. Probably, I don't understand
>> how do exactly. I do that :
>> lspci |grep IDE
>> 0000:00:11.1 IDE interface: VIA Technologies, Inc.
>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>> make xconfig
>> -Device Drivers
>> --* ATA/ATAPI/MFM/RLL support
>> --- * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
>> --- * Include IDE/ATA-2 DISK support
>> --- * PCI IDE chipset support
>> ---- * Generic PCI IDE Support
>> ----- * VIA82CXXX chipset support
>> - File systems
>> -- * Ext3 journalling file system support
>> --- * Ext3 extended attributes
>> ---- * Ext3 POSIX Access Control Lists
>> ---- * Ext3 Security Labels
>>
>> Have I forgot anything ?
>
> RAID or LVM? Try initrd.
>
> regards,
next prev parent reply other threads:[~2006-08-14 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 1:17 kernel panic - not syncing: VFS - unable to mount root fs on unknown-block Hulin Thibaud
2006-08-14 1:33 ` Nick Manley
2006-08-14 13:32 ` Jiri Slaby
2006-08-14 14:44 ` Hulin Thibaud [this message]
2006-08-14 14:52 ` Jiri Slaby
2006-08-14 14:52 ` Reinaldo Carvalho
2006-08-14 19:46 ` Jiri Slaby
2006-08-14 18:06 ` Phillip Susi
2006-08-14 21:15 ` Hulin Thibaud
2006-08-14 21:35 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E08C50.5070904@wanadoo.fr \
--to=hulin.thibaud@wanadoo.fr \
--cc=darkhack@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox