From: seth vidal <skvidal@phy.duke.edu>
To: Peter Jonsson <dal01pjn@mds.mdh.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Invalid superblock on drives in array
Date: Thu, 25 Dec 2003 11:58:48 -0500 [thread overview]
Message-ID: <1072371527.3636.1.camel@binkley> (raw)
In-Reply-To: <Pine.GSO.4.44L.0312251708280.28023-100000@legolas.mdh.se>
On Thu, 2003-12-25 at 11:58, Peter Jonsson wrote:
> Hi!
>
> I'm running a RAID-5 setup using six Seagate ST19171W SUN9.0G drives off a
> Sun Multipack connected to an Adaptec 2940UW. I used to have the multipack
> connected to a Sparcstation 5 but I moved it yesterday. Everything was
> running fine until I rebooted the machine.
>
if this was running on a sparc then you might want to look at:
mdadm --update=sparc2.2
look at the mdadm man page:
The sparc2.2 option will adjust the superblock of
an array what was created on a Sparc machine run-
ning a patched 2.2 Linux kernel. This kernel got
the alignment of part of the superblock wrong. You
can use the --examine --sparc2.2 option to mdadm to
see what effect this would have.
> I'm not really sure what happend. I think what I did was to reboot the
> machine to use a new kernel. This machine was a clean RH9 installation and
> I applied a 'yum upgrade' to it after installing yum. I have since tried
> to use the array with the older kernel but that don't work either.
>
Oh and I'm also the yum author and I assure you, yum doesn't touch
ANYTHING related to raid arrays, it just updates packages :)
-sv
next prev parent reply other threads:[~2003-12-25 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 16:58 Invalid superblock on drives in array Peter Jonsson
2003-12-25 16:58 ` seth vidal [this message]
2003-12-25 17:27 ` Peter Jonsson
2003-12-25 17:45 ` seth vidal
2003-12-25 18:22 ` Peter Jonsson
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=1072371527.3636.1.camel@binkley \
--to=skvidal@phy.duke.edu \
--cc=dal01pjn@mds.mdh.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.