linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: linux-raid@vger.kernel.org
Subject: Re: RAID migration from 2.4 -> 2.6
Date: Thu, 12 Aug 2004 20:51:01 +0200	[thread overview]
Message-ID: <200408122051.06092.bernd-schubert@web.de> (raw)
In-Reply-To: <20040812152939.GD5326@romulus.a-s-i.com>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On Thursday 12 August 2004 17:29, you wrote:
> At the moment I'm stumped, so I wonder if someone might be able
> to give me a hand.
>
> First, my RAID setup: I have a pair of Adaptec 7899 controllers
> with five 9GB SCSI disks on each.  The first disks on each controller
> are allocated in a RAID 1 configuration for boot, swap, /usr, etc.,
> while the next three disks on each controller are allocated in
> a RAID 5 configuration to our running services and data.  The last
> disk on each controller is designated as a spare disk for each RAID.
>
> These RAIDs work well with 2.4.  I've got them configured
> for autodetect, so the system brings them up at startup in 2.4.
>
> Now I'm trying to migrate to 2.6.7, and autodetection basically
> ignores all my SCSI disks.  I get three lines:

Does those partions have the FD type flag (linux raid autodetect)? With some 
2.4.X kernel versions it worked without it, but I think with 2.6.X you really 
need to mark the partitions with this partition type.

Hope it helps,
	Bernd

PS: Sometimes I forget to set this flag and then have the same problem ;)



[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-12 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 15:29 RAID migration from 2.4 -> 2.6 Bob Glamm
2004-08-12 18:51 ` Bernd Schubert [this message]
2004-08-16 22:35 ` Bob Glamm
2004-08-16 22:55   ` Michael Tokarev
2004-08-17  3:23     ` Bob Glamm

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=200408122051.06092.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).