public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Diehl <mdiehl@diehlnet.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with new install
Date: Fri, 15 Oct 2010 13:23:22 -0600	[thread overview]
Message-ID: <201010151323.22854.mdiehl@diehlnet.com> (raw)
In-Reply-To: <4CB89212.7020801@f_philipp.fastmail.net>

On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
> Am 15.10.2010 19:29, schrieb Mike Diehl:
> > Hi all.
> > 
> > I've never had this much trouble with a server before, but I've been
> > pulling my hair out.
> > 
> > The install seemed to go well, but when I rebooted it from it's own hard
> > drive, it fails.  fsck claims that it can't open /dev/sda3 or that the
> > superblock doesn't describe a valid ext2 filesystem.

> *All* of the drivers could be too much. There is a generic driver which
> can prevent the "right" driver from taking over. In that case you end up
> with a /dev/hda node and no DMA. Try to deactivate "Generic ATA support"
> = CONFIG_ATA_GENERIC and "generic/default IDE chipset support" =
> CONFIG_IDE_GENERIC.
> I think it is the second option that causes that problem. However, you
> won't need the first option, either.

I tried this, first without success.  I then ran through all combinations of 
sda3, sdb3, hda3, hdb3 in /etc/fstab.  This didn't work.

> Instead of your brute-force "yes to all" approach, newer kernels also
> support `make localyesconfig` which takes all modules currently used in
> the running kernel and compiles them into the new kernel. It is very
> helpful when you already have a good but generic kernel like the one on
> your live CD.

I tried this, next.  At least now, I believe I have a viable kernel.  But it 
still didn't work.

> If even that doesn't help, it might be possible that the device
> numbering has changed and your hard disk is detected as /dev/sdb or so.
> Try mounting it by UUID (google for it, please).

I tried this.  Only now, fsck.ext2 tells me that it can't resolve the UUID.

Here is the new fstab:
/dev/sda1       /boot           ext2            noauto,noatime  1 2                           
                                                                                              
UUID=ba7511dd-a5f9-48d8-8102-cf71c08a0c7b     /       ext2    noatime    0 1   
                                                                                              
/dev/sda2       none            swap            sw              0 0                           
/dev/cdrom              /mnt/cdrom      auto            noauto,ro       0 0  

At this point, I'm going to move the drive to a different port on the SATA 
chain; shouldn't change anything, but I'm running out of ideas.  I'll also 
check the BIOS for anything stupid-obvious.

So, I guess I'm still stuck!

> Hope this helps,
> Florian Philipp

-- 

Take care and have fun,
Mike Diehl.



  parent reply	other threads:[~2010-10-15 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 17:29 [gentoo-user] Problem with new install Mike Diehl
2010-10-15 17:40 ` Florian Philipp
2010-10-15 17:47   ` Mike Diehl
2010-10-15 18:16     ` Dan Cowsill
2010-10-15 20:18     ` Alan McKinnon
2010-10-15 19:23   ` Mike Diehl [this message]
2010-10-15 21:02     ` Florian Philipp
2010-10-16  7:06       ` Mike Diehl
2010-10-15 21:25     ` Bill Longman
2010-10-15 19:47   ` Mike Diehl
2010-10-15 18:17 ` Per-Erik Westerberg

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=201010151323.22854.mdiehl@diehlnet.com \
    --to=mdiehl@diehlnet.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