* Failed RAID5
@ 2005-05-12 8:43 janaka
2005-05-12 10:05 ` Neil Brown
0 siblings, 1 reply; 5+ messages in thread
From: janaka @ 2005-05-12 8:43 UTC (permalink / raw)
To: linux-raid
Hey,
I am trying to rebuild a failed raid 5. I have one disk
that's bad, and one disk that, in the confusion, has become
convinced that it is a spare. I don't know where it got
this idea, but I have drive "mdadm --assemble --force
/dev/md2 /dev/hda3 /dev/hdc3 /dev/hde3 /dev/hdg3 /dev/hdi3
/dev/hdk3" as well as "mkraid --force /dev/md2" and my
raidtab hasn't changed except to state that HDA has failed.
Is there anyway for me to force the "spare disk" to
reconsider its purpose in life? Which is presently to make
my data accessable so I can move to raid 10 or some other
more simple raid format.
I mean, I am sure it is some bit in the superblock that is
miss set, but how do I fix that?
Thanks
-fro
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Failed RAID5
2005-05-12 8:43 Failed RAID5 janaka
@ 2005-05-12 10:05 ` Neil Brown
2005-05-12 14:52 ` Mike Tran
0 siblings, 1 reply; 5+ messages in thread
From: Neil Brown @ 2005-05-12 10:05 UTC (permalink / raw)
To: janaka; +Cc: linux-raid
On Thursday May 12, janaka@clanwind.com wrote:
> Hey,
>
> I am trying to rebuild a failed raid 5. I have one disk
> that's bad, and one disk that, in the confusion, has become
> convinced that it is a spare. I don't know where it got
> this idea, but I have drive "mdadm --assemble --force
> /dev/md2 /dev/hda3 /dev/hdc3 /dev/hde3 /dev/hdg3 /dev/hdi3
> /dev/hdk3" as well as "mkraid --force /dev/md2" and my
> raidtab hasn't changed except to state that HDA has failed.
>
> Is there anyway for me to force the "spare disk" to
> reconsider its purpose in life? Which is presently to make
> my data accessable so I can move to raid 10 or some other
> more simple raid format.
>
> I mean, I am sure it is some bit in the superblock that is
> miss set, but how do I fix that?
If you are confident that you know what belongs where, then the best
thing is to recreate the array. Make sure you leave a "missing" device
so that it doesn't do a resync.
e.g.
mdadm --create /dev/md2 -l5 -n6 /dev/hda3 /dev/hdc3 /dev/hde3 \
missing /dev/hdi3 /dev/hdk3
or whatever happens to be right in your situation.
This will rewrite all superblocks but will not touch any data (unless
you try to write to md2).
I suggest that after this you "fsck -n" the make sure the data looks
reasonably OK, and if it does, mount read-only and copy the data off.
If fsck thinks it is trash, then maybe you got the order wrong. Just
"mdadm -S /dev/md2" and try again.
NeilBrown
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Failed RAID5
2005-05-12 10:05 ` Neil Brown
@ 2005-05-12 14:52 ` Mike Tran
0 siblings, 0 replies; 5+ messages in thread
From: Mike Tran @ 2005-05-12 14:52 UTC (permalink / raw)
To: linux-raid
On Thu, 2005-05-12 at 05:05, Neil Brown wrote:
> On Thursday May 12, janaka@clanwind.com wrote:
> > Hey,
> >
> > I am trying to rebuild a failed raid 5. I have one disk
> > that's bad, and one disk that, in the confusion, has become
> > convinced that it is a spare. I don't know where it got
> > this idea, but I have drive "mdadm --assemble --force
> > /dev/md2 /dev/hda3 /dev/hdc3 /dev/hde3 /dev/hdg3 /dev/hdi3
> > /dev/hdk3" as well as "mkraid --force /dev/md2" and my
> > raidtab hasn't changed except to state that HDA has failed.
> >
> > Is there anyway for me to force the "spare disk" to
> > reconsider its purpose in life? Which is presently to make
> > my data accessable so I can move to raid 10 or some other
> > more simple raid format.
> >
> > I mean, I am sure it is some bit in the superblock that is
> > miss set, but how do I fix that?
>
> If you are confident that you know what belongs where, then the best
> thing is to recreate the array. Make sure you leave a "missing" device
> so that it doesn't do a resync.
> e.g.
>
> mdadm --create /dev/md2 -l5 -n6 /dev/hda3 /dev/hdc3 /dev/hde3 \
> missing /dev/hdi3 /dev/hdk3
>
> or whatever happens to be right in your situation.
> This will rewrite all superblocks but will not touch any data (unless
> you try to write to md2).A
> I suggest that after this you "fsck -n" the make sure the data looks
> reasonably OK, and if it does, mount read-only and copy the data off.
>
> If fsck thinks it is trash, then maybe you got the order wrong. Just
> "mdadm -S /dev/md2" and try again.
Also, "mdadm --examine" will give you a good idea of how things were put
together.
eg.
mdadm --examine /dev/hda3
--
Regards,
Mike T.
^ permalink raw reply [flat|nested] 5+ messages in thread
* failed raid5
@ 2013-10-20 18:30 i.mikic
2013-10-21 8:24 ` Mikael Abrahamsson
0 siblings, 1 reply; 5+ messages in thread
From: i.mikic @ 2013-10-20 18:30 UTC (permalink / raw)
To: linux-raid
Hello,
the raid5 on my Iomega Storecenter ix4 is not starting up anymore.
as far as i can see, 2 of the Memberdisks were switched from active to
spare.
configuration: 4x 1TB Harddrive, no changes done, error occured while
running.
the funny thing is, there is an additional raid5 (1GB on each disk) that is
still running.
waht are the chances the data on the drives is still intact, how can i get
the
raid running again and how risky is the process (is it neccesary to get
additional drives for cloning)?
here the mdadm --examine ouput
/dev/sda2:
Magic : a92b4efc
Version : 00.90.00
UUID : 835af38b:cb4edece:860bf3ca:97c28e09
Creation Time : Fri Jul 24 08:04:50 2009
Raid Level : raid5
Used Dev Size : 975742336 (930.54 GiB 999.16 GB)
Array Size : 2927227008 (2791.62 GiB 2997.48 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Fri Oct 18 07:51:35 2013
State : clean
Active Devices : 2
Working Devices : 4
Failed Devices : 2
Spare Devices : 2
Checksum : ecc62357 - correct
Events : 0.1531645
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 2 0 active sync /dev/sda2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 0 0 2 faulty removed
3 3 0 0 3 faulty removed
4 4 8 34 4 spare /dev/sdc2
5 5 8 50 5 spare /dev/sdd2
/dev/sdb2:
Magic : a92b4efc
Version : 00.90.00
UUID : 835af38b:cb4edece:860bf3ca:97c28e09
Creation Time : Fri Jul 24 08:04:50 2009
Raid Level : raid5
Used Dev Size : 975742336 (930.54 GiB 999.16 GB)
Array Size : 2927227008 (2791.62 GiB 2997.48 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Fri Oct 18 07:51:35 2013
State : clean
Active Devices : 2
Working Devices : 4
Failed Devices : 2
Spare Devices : 2
Checksum : ecc62369 - correct
Events : 0.1531645
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 18 1 active sync /dev/sdb2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 0 0 2 faulty removed
3 3 0 0 3 faulty removed
4 4 8 34 4 spare /dev/sdc2
5 5 8 50 5 spare /dev/sdd2
/dev/sdc2:
Magic : a92b4efc
Version : 00.90.00
UUID : 835af38b:cb4edece:860bf3ca:97c28e09
Creation Time : Fri Jul 24 08:04:50 2009
Raid Level : raid5
Used Dev Size : 975742336 (930.54 GiB 999.16 GB)
Array Size : 2927227008 (2791.62 GiB 2997.48 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Fri Oct 18 07:51:35 2013
State : clean
Active Devices : 2
Working Devices : 4
Failed Devices : 2
Spare Devices : 2
Checksum : ecc62379 - correct
Events : 0.1531645
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 4 8 34 4 spare /dev/sdc2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 0 0 2 faulty removed
3 3 0 0 3 faulty removed
4 4 8 34 4 spare /dev/sdc2
5 5 8 50 5 spare /dev/sdd2
/dev/sdd2:
Magic : a92b4efc
Version : 00.90.00
UUID : 835af38b:cb4edece:860bf3ca:97c28e09
Creation Time : Fri Jul 24 08:04:50 2009
Raid Level : raid5
Used Dev Size : 975742336 (930.54 GiB 999.16 GB)
Array Size : 2927227008 (2791.62 GiB 2997.48 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Update Time : Fri Oct 18 07:51:35 2013
State : clean
Active Devices : 2
Working Devices : 4
Failed Devices : 2
Spare Devices : 2
Checksum : ecc6238b - correct
Events : 0.1531645
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 5 8 50 5 spare /dev/sdd2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 0 0 2 faulty removed
3 3 0 0 3 faulty removed
4 4 8 34 4 spare /dev/sdc2
5 5 8 50 5 spare /dev/sdd2
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: failed raid5
2013-10-20 18:30 failed raid5 i.mikic
@ 2013-10-21 8:24 ` Mikael Abrahamsson
0 siblings, 0 replies; 5+ messages in thread
From: Mikael Abrahamsson @ 2013-10-21 8:24 UTC (permalink / raw)
To: i.mikic; +Cc: linux-raid
On Sun, 20 Oct 2013, i.mikic@freenet.de wrote:
> as far as i can see, 2 of the Memberdisks were switched from active to spare.
Check "dmesg" output and see what you find, there should be reason stated
there.
> waht are the chances the data on the drives is still intact, how can i
> get the raid running again and how risky is the process (is it neccesary
> to get additional drives for cloning)?
Stop the array, then do mdadm --assemble --force with all the member
drives. Since your event count is identical on all drives, this should be
safe.
--
Mikael Abrahamsson email: swmike@swm.pp.se
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-10-21 8:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-12 8:43 Failed RAID5 janaka
2005-05-12 10:05 ` Neil Brown
2005-05-12 14:52 ` Mike Tran
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 18:30 failed raid5 i.mikic
2013-10-21 8:24 ` Mikael Abrahamsson
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).