Skip to contentSkip to conversation

Possible to rescue SW Raid5 with 2 missing Disks

DISCUSSION Dragon 2 participants 2 messages Feb 15, 2013 MD RAID

lore
Share & tools
lore

Dragon

author
#0 lore raw

Hi Mikael and Brad,

and thanks for the information. i appreciate this because i learned a lot. and you are right the internet is full of wrong things and yes i react a bit late because the problem is now, but as an excuse, i have not that time to study such a big subject like raid with all its interessting parts like the hardware, speed, possibilities, e.g. but i learned a lot by solve errors like this ;) and appreciate people like you at mailinglists and forums who helped.

ok now its become difficult for me to follow because of my engl. understanding. what i understand out of your answers is:
- force is not at all a problem
- in the most cases do not use --create --assume-clean, else you know why
--> but what is the problem with this, please explain

In my case the superblock seems to be on all disks persistant, i use the same version and chunk-size.

#1 lore raw
Quoted 1 line · Dragon

In my case the superblock seems to be on all disks persistant, i use the same version and chunk-size.

The problem is that you used --create which just overwrites your old superblocks. So the information on your current superblocks might very well be wrong. The order of the drives might be wrong, you might have wrong chunk size, you might have wrong data offset, you might even have wrong superblock version.

Since you didn't save the superblock information before you did --create, it's hard to give you advice on how to proceed.

If you have old log entries (syslog) from when the raid was successfully started and stopped before you ran into trouble, that might contain some information that might help.

Signature · 1 line
Mikael Abrahamsson    email: [email protected]