public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Date: Mon, 26 Jul 2010 12:02:56 +0100	[thread overview]
Message-ID: <AANLkTinij67t2=C2n2nA8qHmVztinLtKaH1tOdM+ZTom@mail.gmail.com> (raw)
In-Reply-To: <1280141659.8738.15.camel@rattus>

On 26 July 2010 11:54, William Kenworthy <billk@iinet.net.au> wrote:

> Fixed it - was grub after all - it renumbered my drives (0 and 1
> swapped :(
>
> Complicated because this was one of the early sata boards with a fake
> raid chip to handle the sata while the old IDE drives were on the normal
> bus.
>
> Further complicated by the bios and raidchip changing drive assignments
> depending on which drive/cd/floppy you booted from (i.e., what grub sees
> as the drive numbers changes when the real OS is booted).  I forgot what
> hoops I had to jump through to get this going originally.
>
> Might be time for a new setup - amd athlon 2500+ are not so cool these
> days :)

Glad you got it working!  Another gotcha is when you disable the
deprecated CONFIG_IDE in the kernel and you don't update your
grub.conf and /etc/fstab to rename /dev/hda's into /dev/sda's.
-- 
Regards,
Mick



  reply	other threads:[~2010-07-26 11:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24 19:57 [gentoo-user] Problems booting my server - ext2 - e2fsck KH
2010-07-24 20:21 ` Alan McKinnon
2010-07-24 22:04   ` Robert Bridge
2010-07-25  4:57   ` KH
2010-07-25  7:49     ` Alan McKinnon
2010-07-25  8:18       ` Dale
2010-07-25 13:57         ` Mick
2010-07-28  8:50           ` KH
2010-07-28 13:42             ` Mick
2010-07-28 13:53               ` Bill Longman
2010-07-28 14:04                 ` Mick
2010-07-28 14:27                   ` Bill Longman
2010-07-28 14:46                     ` Mick
2010-07-28 15:18                   ` KH
2010-07-28 15:30                     ` Bill Longman
2010-07-28 16:35                       ` KH
2010-07-28 18:54                         ` Mick
2010-07-28 19:29                           ` Bill Longman
2010-07-28 15:21                 ` KH
2010-07-28 13:45             ` Bill Longman
2010-07-28 14:56               ` KH
2010-07-28 15:27                 ` Bill Longman
2010-07-28 16:37                   ` KH
2010-07-28 18:14                     ` Bill Longman
2010-07-29 11:39                       ` Peter Humphrey
2010-11-28 16:16                         ` Peter Humphrey
2010-07-25 15:24         ` covici
2010-07-25 20:10           ` Alan McKinnon
2010-07-25 20:08         ` Alan McKinnon
2010-07-26  1:05           ` Bill Kenworthy
2010-07-26 10:54             ` William Kenworthy
2010-07-26 11:02               ` Mick [this message]
2010-07-26 14:11                 ` Peter Humphrey
2010-07-26 15:13                   ` Mick
2010-07-26 16:44                     ` Peter Humphrey
2010-07-26 18:04                       ` Alex Schuster
2010-07-26 20:46                         ` Mick
2010-07-26 23:56                           ` Peter Humphrey
2010-07-26 14:16               ` Dale
2010-07-24 20:25 ` Alan McKinnon
2010-07-24 21:46   ` James Wall
2010-07-25  5:12     ` KH

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='AANLkTinij67t2=C2n2nA8qHmVztinLtKaH1tOdM+ZTom@mail.gmail.com' \
    --to=michaelkintzios@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