All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:45:20 -0500	[thread overview]
Message-ID: <1072374319.3636.6.camel@binkley> (raw)
In-Reply-To: <Pine.GSO.4.44L.0312251811450.3919-100000@legolas.mdh.se>

On Thu, 2003-12-25 at 12:27, Peter Jonsson wrote:
> On Thu, 25 Dec 2003, seth vidal wrote:
> 
> > if this was running on a sparc then you might want to look at:
> >
> > mdadm --update=sparc2.2
> 
> I wasn't clear enough. I got into problems when I moved the array from the
> sparc to the PC so I backed up all the data and then I recreated the array
> and formatted the drive (ext3) before moving all the data back.
> 
> But I tried it anyway with this result :

hmm. I bet the drive labels are screwed up. For fun, stop the array,
load up fdisk on one of the disks and type 'o' - that should make new
dos disk labels.

it's something I ran into, but this was a long time ago, so the above
info might be out of date./

so make new drive labels, repartition and recreate the array.

see if that doesn't fix it.

> It had been running for about 1½ days before something happend. I actually
> don't have any idea what might have happend. Something is wrong with the
> superblocks but I have idea how that happend. Act of God? ;)

migration from sun to pc or possibly general system gremlins.

good luck
-sv


-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2003-12-25 17:45 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
2003-12-25 17:27   ` Peter Jonsson
2003-12-25 17:45     ` seth vidal [this message]
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=1072374319.3636.6.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.