Hi, thanks for the quick answer. 2011/2/10 Phil Turmel <philip@xxxxxxxxxx>: > Working from backups is a very good plan! Well, not having a backup has brought me into this problem so I learned form my mistake. > Hmmm. Not enough info here, and further steps destroy it. Good thing you started over. > > Please show "mdadm -E /dev/loop[0-2]" on fresh loop copies *before* trying any "create" or "add" operations. Unfortunately I'm not that familiar the -E option so I don't really understand what all that means. But I think it's interesting that there are sometimes 4 devices although the raid only has 3 in reality. root@backup-server:/media# mdadm -E /dev/loop[0-2] /dev/loop0: Magic : a92b4efc Version : 0.90.00 UUID : 9665c475:31f17aa2:83a3570a:c5b3b84e Creation Time : Thu Nov 19 21:09:37 2009 Raid Level : raid5 Used Dev Size : 1463481216 (1395.68 GiB 1498.60 GB) Array Size : 2926962432 (2791.37 GiB 2997.21 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 2 Update Time : Sun Nov 14 02:08:16 2010 State : active Active Devices : 1 Working Devices : 2 Failed Devices : 2 Spare Devices : 1 Checksum : aa2d9609 - correct Events : 3352465 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 3 8 35 3 spare 0 0 8 19 0 active sync 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed 3 3 8 35 3 spare /dev/loop1: Magic : a92b4efc Version : 0.90.00 UUID : 9665c475:31f17aa2:83a3570a:c5b3b84e Creation Time : Thu Nov 19 21:09:37 2009 Raid Level : raid5 Used Dev Size : 1463481216 (1395.68 GiB 1498.60 GB) Array Size : 2926962432 (2791.37 GiB 2997.21 GB) Raid Devices : 3 Total Devices : 1 Preferred Minor : 2 Update Time : Sun Nov 14 14:12:44 2010 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 2 Spare Devices : 0 Checksum : aa2e3f94 - correct Events : 3352467 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 0 8 19 0 active sync 0 0 8 19 0 active sync 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed /dev/loop2: Magic : a92b4efc Version : 0.90.00 UUID : 9665c475:31f17aa2:83a3570a:c5b3b84e Creation Time : Thu Nov 19 21:09:37 2009 Raid Level : raid5 Used Dev Size : 1463481216 (1395.68 GiB 1498.60 GB) Array Size : 2926962432 (2791.37 GiB 2997.21 GB) Raid Devices : 3 Total Devices : 1 Preferred Minor : 2 Update Time : Sun Nov 14 01:41:40 2010 State : active Active Devices : 1 Working Devices : 1 Failed Devices : 2 Spare Devices : 0 Checksum : aa2d8f80 - correct Events : 3352459 Layout : left-symmetric Chunk Size : 64K Number Major Minor RaidDevice State this 4 8 3 -1 spare 0 0 8 19 0 active sync 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed > Yeah, mdadm was trying to tell you not to do that. "--assume-clean" is really important when trying to recreate an array with existing data. > > [trim /] > > If the problem is just the event counts, "mdadm --assemble --force" is probably what you want, followed by "mdadm --readonly". If pvscan shows your LVM subsystem at that point, try an fsck to see how much trouble you are in. > > Phil > I will try that at some point but not right now because the restore from my backups takes about 15 hours. Thomas -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
