From: PFC <lists@peufeu.com>
To: linux-raid@vger.kernel.org
Subject: Re: Kanotix crashed my raid...
Date: Fri, 06 Jan 2006 13:02:09 +0100 [thread overview]
Message-ID: <op.s2yg1vkdcigqcu@apollo13> (raw)
In-Reply-To: <op.s2yecmeocigqcu@apollo13>
I forgot :
I tried these :
mdadm --assemble /dev/md2 /dev/hdb1 /dev/sd{a,b,c,d}1
with --run, --force, and both, --stop'ping the array before each try, and
everytime is the same error, and the same line in dmesg : "cannot start
dirty degraded array for md2"
apollo13 ~ # mdadm --stop /dev/md2
apollo13 ~ # mdadm --assemble --verbose /dev/md2 /dev/hdb1
/dev/sd{a,b,c,d}1
mdadm: looking for devices for /dev/md2
mdadm: /dev/hdb1 is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sda1 is identified as a member of /dev/md2, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdd1 is identified as a member of /dev/md2, slot 2.
mdadm: added /dev/sdb1 to /dev/md2 as 1
mdadm: added /dev/sdd1 to /dev/md2 as 2
mdadm: added /dev/sdc1 to /dev/md2 as 3
mdadm: added /dev/hdb1 to /dev/md2 as 4
mdadm: added /dev/sda1 to /dev/md2 as 0
mdadm: /dev/md2 assembled from 4 drives - need all 5 to start it (use
--run to insist).
apollo13 ~ # mdadm --run /dev/md2
mdadm: failed to run array /dev/md2: Input/output error
apollo13 ~ # mdadm --stop /dev/md2
apollo13 ~ # mdadm --assemble --verbose --run /dev/md2 /dev/hdb1
/dev/sd{a,b,c,d}1
mdadm: looking for devices for /dev/md2
mdadm: /dev/hdb1 is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sda1 is identified as a member of /dev/md2, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdd1 is identified as a member of /dev/md2, slot 2.
mdadm: added /dev/sdb1 to /dev/md2 as 1
mdadm: added /dev/sdd1 to /dev/md2 as 2
mdadm: added /dev/sdc1 to /dev/md2 as 3
mdadm: added /dev/hdb1 to /dev/md2 as 4
mdadm: added /dev/sda1 to /dev/md2 as 0
mdadm: failed to RUN_ARRAY /dev/md2: Input/output error
apollo13 ~ # mdadm --stop /dev/md2
apollo13 ~ # mdadm --assemble --verbose --run --force /dev/md2 /dev/hdb1
/dev/sd{a,b,c,d}1
mdadm: looking for devices for /dev/md2
mdadm: /dev/hdb1 is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sda1 is identified as a member of /dev/md2, slot 0.
mdadm: /dev/sdb1 is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdc1 is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdd1 is identified as a member of /dev/md2, slot 2.
mdadm: added /dev/sdb1 to /dev/md2 as 1
mdadm: added /dev/sdd1 to /dev/md2 as 2
mdadm: added /dev/sdc1 to /dev/md2 as 3
mdadm: added /dev/hdb1 to /dev/md2 as 4
mdadm: added /dev/sda1 to /dev/md2 as 0
mdadm: failed to RUN_ARRAY /dev/md2: Input/output error
next prev parent reply other threads:[~2006-01-06 12:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd8d0180601050104x15079396h@mail.gmail.com>
2006-01-05 9:06 ` Fwd: Linux MD raid5 and reiser4... Any experience ? Francois Barre
2006-01-05 10:14 ` Daniel Pittman
2006-01-05 11:21 ` Francois Barre
2006-01-05 11:31 ` Gordon Henderson
2006-01-06 6:33 ` Daniel Pittman
2006-01-06 9:47 ` Simon Valiquette
2006-01-06 10:50 ` Francois Barre
2006-01-06 19:28 ` Forrest Taylor
2006-01-06 11:03 ` Kanotix crashed my raid PFC
2006-01-06 12:02 ` PFC [this message]
2006-01-06 12:08 ` PFC
2006-01-06 22:01 ` PFC
[not found] ` <200601090803.03588.mlaks@verizon.net>
2006-01-09 18:30 ` PFC
2006-01-06 19:05 ` Fwd: Linux MD raid5 and reiser4... Any experience ? Mike Hardy
2006-01-08 2:53 ` Daniel Pittman
2006-01-05 11:26 ` berk walker
2006-01-05 11:35 ` Francois Barre
2006-01-05 11:43 ` Gordon Henderson
2006-01-05 11:59 ` berk walker
2006-01-05 13:13 ` Bill Rugolsky Jr.
2006-01-05 13:38 ` John Stoffel
2006-01-05 14:03 ` Francois Barre
2006-01-05 18:55 ` John Stoffel
2006-01-06 9:08 ` Francois Barre
2006-01-06 10:49 ` Andre Majorel
2006-01-09 8:00 ` Molle Bestefich
2006-01-09 8:16 ` Gordon Henderson
2006-01-09 9:00 ` Francois Barre
2006-01-09 9:24 ` Molle Bestefich
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=op.s2yg1vkdcigqcu@apollo13 \
--to=lists@peufeu.com \
--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.