public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <dalek@exceedtech.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] VFS: Cannot open root device - kernel panic
Date: Fri, 25 May 2007 00:09:23 -0500	[thread overview]
Message-ID: <46566F83.7070806@exceedtech.net> (raw)
In-Reply-To: <d9a0a6da0705242153ra2726f4te2bbf9fbd4402111@mail.gmail.com>

Denis wrote:
>> I have ran into things like this before, I usually run make mrproper
>> from within the kernel directory to make sure there is no old cruft
>> laying around in there.
>
> In my case, it was a fresh install, which made it quite a bit more
> painful to fix because I had to go through the procedures twice and
> did not have a working kernel to fall back on.  It's the scenario I've
> always dreaded, and then one day it actually happens.  When I re-did
> the install, I erased the partition table and started anew, so there
> was no old cruft to begin with.
>
> I'm not sure if this contributed to anything, but I enabled all the
> relevant RAID support the second time around.  Since I only have one
> SATA drive, I simply turned off RAID support initially in the kernel,
> but it's possible that this particular combination of hardware was
> expecting a RAID driver...
>
> I'm so clueless sometimes trying to figure out some of these kernel
> options...  haha.  The really technical ones where it's like a foreign
> language.  I love the "if unsure, say N here." or "if you don't know
> what this is, you probably don't need it - say N here."   ;-)

Well, when you download the kernel sources, there can be "old cruft" in
there.  It does seem to start out with some basic options and I was told
once a long time ago to run mrproper to be sure to get it all out.  It
fixed the problem I was having then and I have done it ever since. 
Funny thing is, I wonder if that would have helped.  Most likely not but
something to remember next time. 

I just checked and I have a newer kernel on here.  I may compile the new
version and boot it next time.  I'm on almost 45 days of uptime so don't
hold your breath on me rebooting.  LOL

Glad you got it running though.

Dale

:-)  :-)  :-)

-- 
www.myspace.com/-remove-me-dalek1967

Copy n paste then remove the -remove-me- part.

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-25  5:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 23:14 [gentoo-user] VFS: Cannot open root device - kernel panic Denis
2007-05-24 23:19 ` Hemmann, Volker Armin
2007-05-24 23:52   ` Denis
2007-05-25  0:30     ` david
2007-05-25  0:44       ` Denis
2007-05-25  1:54         ` Hemmann, Volker Armin
2007-05-25  2:27           ` Denis
2007-05-25  3:16             ` Denis
2007-05-25  4:03               ` Dale
2007-05-25  4:53                 ` Denis
2007-05-25  5:09                   ` Dale [this message]
2007-05-25  1:59         ` Mark Knecht
2007-05-25  7:51         ` Neil Bothwick

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=46566F83.7070806@exceedtech.net \
    --to=dalek@exceedtech.net \
    --cc=gentoo-user@lists.gentoo.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