From: Mads Peter Bach <mpb@hum.auc.dk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 software general crash
Date: Wed, 04 Jun 2003 10:15:37 +0200 [thread overview]
Message-ID: <3EDDAAA9.6010203@hum.auc.dk> (raw)
In-Reply-To: <3EDDA693.1D6D2AF2@cdc.u-cergy.fr>
Compte centre de calcul UCP wrote:
> Hi,
>
> I'm newbie in RAID5 Software.
> I need some help (direct answer on the list or links) to understand and
> repair my NFS server turning with RAID5 software.
[snip]
> Sunday morning there was a crash. I don't now what happened exactly
> until now, but the raid stopped.
[snip]
> sde1's event counter: 0000003f
> sdd1's event counter: 0000003c
> sdc1's event counter: 0000003c
> sdb1's event counter: 0000003c
> sda1's event counter: 0000003c
> md: superblock update time inconsistency -- using the most recent one
> freshest: sde1
Your superblocks are not in sync. See item 6.1 "Recovery from a multiple
disk failure" in the Linux Software RAID howto.
If you set /dev/sde1 as failed-disk instead of raid-disk in you
/etc/raidtab, and do a mkraid on the array, hotadd /dev/sde1 to the array
and set /dev/sde1 back to raid-disk, you should be back in business.
--
Mads Peter Bach
Systemadministrator, Det Humanistiske Fakultet, Aalborg Universitet
Kroghstræde 3 - 5.111, DK-9220 Aalborg Øst - (+45) 96358062
# whois MPB1-DK@whois.dk-hostmaster.dk
-
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
prev parent reply other threads:[~2003-06-04 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 7:58 RAID5 software general crash Compte centre de calcul UCP
2003-06-04 8:15 ` Mads Peter Bach [this message]
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=3EDDAAA9.6010203@hum.auc.dk \
--to=mpb@hum.auc.dk \
--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.