public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: AARGH! Please help. IDE controller fsckup
Date: Thu, 3 Oct 2002 11:53:16 +0200	[thread overview]
Message-ID: <20021003095316.GC7350@unthought.net> (raw)
In-Reply-To: <200210021516.46668.roy@karlsbakk.net>

On Wed, Oct 02, 2002 at 03:16:46PM +0200, Roy Sigurd Karlsbakk wrote:
> hi all
> 
> I have this cute little server with some 16 120gig IDE drives, and I've got 
> some serious problems with it.
> 
> Controllers:
> One onboard IDE controller (2 channels).
> Two promise ATA100 (2 channels each).
> One CMD649 (2 channels).
> 
> something seriously bad about the CMD649 makes Linux beleive it's the first 
> controller with hd[abcd]. On these, there are two RAID-1s (/ and /var). Due 
> to the fact that the box has some 1,6TB disk space, we haven't got any backup 
> solution (we have an identical box in order to mirror them).
> 
> so - now - the CMD649 has suddenly begun to fail - losing contact with one or 
> two drives, and I _really_ need to get what's on /data (RAID-5 on 
> hd[efghijklmnop]) out. Problem is - the replacement controller I've got from 
> the vendor works fine (turns up as controller 3 serving hd[mnop]). How can I 
> revert this most easily to be able to boot again?

Hindsight:  had you used persistent superblocks, this would not have
been a problem.  The kernel would know the correct ordering from the
superblocks, not the device names.

Solution 1: Write to the RAID mailing list and have one of the mdadm
gurus give you a one-liner to initialize the array with the proper
ordering.

Solution 2: Edit your /etc/raidtab to reflect the new device naming and
run raidstart.

If you start up the array with a bad ordering, no amount of magic is
going to bring back you data (after parity has been "reconstructed" on
various chunks of your existing data).


> 
> I hope this is not too off topic... Please excuse that.
> 

linux-raid is a better place.


Cheers,

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2002-10-03  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 13:16 AARGH! Please help. IDE controller fsckup Roy Sigurd Karlsbakk
2002-10-03  9:53 ` Jakob Oestergaard [this message]
2002-10-03 10:25   ` Roy Sigurd Karlsbakk
2002-10-03 11:40     ` Jakob Oestergaard
2002-10-03 13:13       ` Roy Sigurd Karlsbakk
2002-10-03 13:23         ` Jakob Oestergaard
2002-10-03 20:05           ` Andre Hedrick
2002-10-05 15:42           ` Roy Sigurd Karlsbakk

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=20021003095316.GC7350@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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