From: daid kahl <daidxor@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't see /dev/hda1,2,3 but I know they exist...
Date: Mon, 22 Feb 2010 16:32:45 +0900 [thread overview]
Message-ID: <3ac129341002212332v16e5672cwee2fc3eb85857a5c@mail.gmail.com> (raw)
In-Reply-To: <1266579838.3445.28.camel@localhost>
On 19 February 2010 20:43, Iain Buchanan <iaindb@netspace.net.au> wrote:
> On Fri, 2010-02-19 at 00:49 -0500, James Homuth wrote:
>> I performed a bit of an update on my laptop a day or two ago, and
>> after reboot, I lost the ability to do anything with /dev/hda*. I
>> currently have 0 swap space, and according to stat, ls etc, they don't
>> exist. But, booting to an install CD I burned for diagnostic purposes,
>> it sees them just fine. Also, and this is the strange part. It boots
>> no problem, so the OS is able to mount at least /dev/hda3, even though
>> from the command line I'm not seeing it. I'm probably missing
>> something completely dead obvious (it's after midnight here and all),
>> and Google's turning up nothing, so if someone could kindly slap me in
>> the face with it, that'd be appreciated. Thanks either way for
>> whatever help comes my way.
>
> The first thing that jumps to my mind is you have an older initrd that
> has your HD drivers in it (such as ATA), but the newer kernel you've
> probably just built (is that what you mean by "a bit of an update"?)
> doesn't.
>
> Check for an initrd, and tell us what "a bit of an update" means :) You
> could also compare config files between your rescue CD and your system,
> if you can find it!
>
> HTH,
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
Copy the live cd kernel to your machine and make it an option in grub
and try booting that. Then at least you can stop chrooting and
optical mounting. This will give us some information on if it is a
kernel problem or not. Make sure to make modules_install
If it's the kernel, check out kccmp to compare the kernel options
between Live CD and the machine's kernel configuration after you dig
up the configuration for the kernel on the Live CD.
Other people are mentioning udev, and I wonder about this, too.
Either before or after you check the kernel (whichever you decide is
easier or seems better to you), can you chroot and rebuild udev
through portage and also run a revdep-rebuild please? You said you
updated, but it is not clear to me that the full update was proper.
If you don't have revdep-rebuild, emerge the gentoolkit in the portage
tree to get it, and check out the documentation to see what else it
includes!
~daid
next prev parent reply other threads:[~2010-02-22 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 5:49 [gentoo-user] Can't see /dev/hda1,2,3 but I know they exist James Homuth
2010-02-19 6:55 ` Hung Dang
2010-02-19 8:07 ` James Homuth
2010-02-19 9:18 ` J. Roeleveld
2010-02-19 10:02 ` [gentoo-user] " Nikos Chantziaras
2010-02-19 7:01 ` [gentoo-user] " daid kahl
2010-02-19 7:58 ` James Homuth
2010-02-19 9:24 ` Stroller
2010-02-19 11:51 ` Iain Buchanan
2010-02-19 10:26 ` Alex Schuster
2010-02-19 11:43 ` Iain Buchanan
2010-02-20 2:18 ` Hung Dang
2010-02-20 17:44 ` James Homuth
2010-02-21 3:38 ` Iain Buchanan
2010-02-22 7:32 ` daid kahl [this message]
2010-02-22 7:43 ` daid kahl
2010-02-22 15:13 ` YoYo siska
2010-02-22 16:37 ` YoYo siska
2010-02-22 23:59 ` Iain Buchanan
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=3ac129341002212332v16e5672cwee2fc3eb85857a5c@mail.gmail.com \
--to=daidxor@gmail.com \
--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