public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Resident Boxholder <resid@boxho.com>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test4] VFS: Cannot open root device
Date: Tue, 26 Aug 2003 01:46:12 -0400	[thread overview]
Message-ID: <3F4AF424.1070502@boxho.com> (raw)
In-Reply-To: <20030825130331.GA20696@vinku.pingviini.net>

I don't think that is a kernel problem. I've seen those errors with 2.6 
yesterday and today
but it was a messed up lilo situation and root in need of fsck and once 
due to switching
drives/controller positions so root wasn't the same root. devfs, moving 
drives, bios
settings to boot offboard disk controllers, somehow the root isn't the 
same as for the
lilo op.

Sounds like you could just boot an install disk or an old kernel, open a 
shell, fsck, then lilo.
Just make sure your new kernel lists /dev/ide/host?/bus? the same so 
your lilo root= is
pointing to the disk you think it is.

-Bob

Niklas Vainio wrote:

>I get this at boot with 2.6.0-test[3,4]:
>
>VFS: Cannot open root device "341" or unknown-block(3,65) for ext3 error=-6
>Please append a correct "root=" boot option
>Kernel panic: VFS: Unable to mount root fs on unknown-block(3,65)
>
>Before this, kernel seems to detect hard disks just fine.
>
>This system boots fine with 2.2 and 2.4 kernels. I have tried setting
>root=/dev/hdb1 and rootfstype=ext2 (hdb1 is ext2) but this doesn't help.
>Config below. Is something missing?
>
>Thanks a lot for suggestions,
>    - Nikke
>  
>


      parent reply	other threads:[~2003-08-26  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 13:03 [2.6.0-test4] VFS: Cannot open root device Niklas Vainio
2003-08-25 13:49 ` viro
2003-08-26  5:46 ` Resident Boxholder [this message]

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=3F4AF424.1070502@boxho.com \
    --to=resid@boxho.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