>Good morning Michael,
Hello Phil
>On 02/17/2014 08:33 AM, Samer, Michael (I/ET-83, extern) wrote:
>> Greetings to all
>>
>> As my thread from the 6.2.2014 didn't bring any hint or any reply or way out, I need >advise if my way is approved:
>
>I travel a lot, and didn't see your posts. Help from someone usually
>pops up. Sorry it didn't work that way for you.
I'd have asked more frequently and surely the case is not FAQ.
That's the last --examine I did four weeks ago (before I recovered the part/volume table again:
/dev/sda3:
Magic : a92b4efc
Version : 0.90.00
UUID : 52d7d080:5c40de46:bc741f30:65cb5a0d
Creation Time : Sun Jan 27 23:10:25 2013
Raid Level : raid5
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 13663619200 (13030.64 GiB 13991.55 GB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Apr 21 14:14:49 2013
State : active
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 91564c42 - correct
Events : 136
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 51 3 active sync /dev/sdd3
0 0 8 3 0 active sync /dev/sda3
1 1 0 0 1 faulty removed
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
4 4 8 67 4 active sync /dev/sde3
5 5 8 83 5 active sync /dev/sdf3
6 6 8 99 6 active sync /dev/sdg3
7 7 8 115 7 active sync /dev/sdh3
/dev/sdb:
MBR Magic : aa55
Partition[0] : 1060250 sectors at 40 (type 83)
Partition[1] : 1060284 sectors at 1060296 (type 83)
Partition[2] : 3903891386 sectors at 2120584 (type 83)
Partition[3] : 996024 sectors at 3906011976 (type 83)
/dev/sdc3:
Magic : a92b4efc
Version : 0.90.00
UUID : 52d7d080:5c40de46:bc741f30:65cb5a0d
Creation Time : Sun Jan 27 23:10:25 2013
Raid Level : raid5
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 13663619200 (13030.64 GiB 13991.55 GB)
Raid Devices : 8
Total Devices : 8
Preferred Minor : 0
Update Time : Sun Apr 21 14:06:49 2013
State : active
Active Devices : 8
Working Devices : 8
Failed Devices : 0
Spare Devices : 0
Checksum : 91564a57 - correct
Events : 135
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 19 1 active sync /dev/sdb3
0 0 8 3 0 active sync /dev/sda3
1 1 8 19 1 active sync /dev/sdb3
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
4 4 8 67 4 active sync /dev/sde3
5 5 8 83 5 active sync /dev/sdf3
6 6 8 99 6 active sync /dev/sdg3
7 7 8 115 7 active sync /dev/sdh3
/dev/sdd:
MBR Magic : aa55
Partition[0] : 1060250 sectors at 40 (type 83)
Partition[1] : 1060284 sectors at 1060296 (type 83)
Partition[2] : 3903891386 sectors at 2120584 (type 83)
Partition[3] : 996024 sectors at 3906011976 (type 83)
/dev/sde3:
Magic : a92b4efc
Version : 0.90.00
UUID : 52d7d080:5c40de46:bc741f30:65cb5a0d
Creation Time : Sun Jan 27 23:10:25 2013
Raid Level : raid5
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 13663619200 (13030.64 GiB 13991.55 GB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Apr 21 14:14:49 2013
State : active
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 91564c54 - correct
Events : 136
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 4 8 67 4 active sync /dev/sde3
0 0 8 3 0 active sync /dev/sda3
1 1 0 0 1 faulty removed
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
4 4 8 67 4 active sync /dev/sde3
5 5 8 83 5 active sync /dev/sdf3
6 6 8 99 6 active sync /dev/sdg3
7 7 8 115 7 active sync /dev/sdh3
/dev/sdf:
MBR Magic : aa55
Partition[0] : 1060250 sectors at 40 (type 83)
Partition[1] : 1060284 sectors at 1060296 (type 83)
Partition[2] : 3903891386 sectors at 2120584 (type 83)
Partition[3] : 996024 sectors at 3906011976 (type 83)
/dev/sdg:
MBR Magic : aa55
Partition[0] : 1060250 sectors at 40 (type 83)
Partition[1] : 1060284 sectors at 1060296 (type 83)
Partition[2] : 3903891386 sectors at 2120584 (type 83)
Partition[3] : 996024 sectors at 3906011976 (type 83)
/dev/sdh3:
Magic : a92b4efc
Version : 0.90.00
UUID : 52d7d080:5c40de46:bc741f30:65cb5a0d
Creation Time : Sun Jan 27 23:10:25 2013
Raid Level : raid5
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Array Size : 13663619200 (13030.64 GiB 13991.55 GB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Apr 21 14:14:49 2013
State : active
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 91564c8a - correct
Events : 136
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 7 8 115 7 active sync /dev/sdh3
0 0 8 3 0 active sync /dev/sda3
1 1 0 0 1 faulty removed
2 2 8 35 2 active sync /dev/sdc3
3 3 8 51 3 active sync /dev/sdd3
4 4 8 67 4 active sync /dev/sde3
5 5 8 83 5 active sync /dev/sdf3
6 6 8 99 6 active sync /dev/sdg3
7 7 8 115 7 active sync /dev/sdh3
As you can see sdb3/sdf3 and sdg3 is missing it's md superblock ( I already searched for the
Via
"for x in /dev/sd[a-e]2 ; echo -e "\nDevice $x" ; dd if=$x bs=1M |hexdump -C |grep "000 fc 4e 2b a9" ; done"
And did not find any on the three.
My best guess was to reconstruct the header blocks (leaving the framework intact) so mdadm can recognize itself and repair it (in my case a simple dump would be sufficient, so read access would be my goal)
>Anyways, it means I don't have your initial report. Please show "mdadm
>-E /dev/sd[a-z]3".
>
>mdadm --create --assume-clean is a terrible solution, except when its
>the right one. I'd like to make sure.
>
As not even Neil did post any hints I was left on my (BSD based) ZFS knowhow, but I'm usually into (PPC based) hardware RAID Controllers and their reconstruction.
>
> I reconstructed the part table (testdisk import from a working disk) and now I'm only >missing the md superblock on three disks (sdb3/sdf3/sdg3) for my md0 integrity.
>
> I'd do the following:
>
> a) "mdadm --stop /dev/md0"
>
> b) "mdadm --create --assume-clean --verbose --force --run /dev/md0 --level=5 --raid->devices=8 /dev/sda3 missing /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/sdf3 /dev/sdg3 /dev/sdh3"
>
>Device order matters--it must match the device roles in the --examine
>reports. If three devices have no metadata, you might have to do this
>step multiple times with different combinations. (Never writing to the
>array until you find the right one.)
Good to hear advice :-)
I'm open to a "How to"
I have a complete dump of the 8 disks on my SAN, so I'm able to do a full restore (it would take about 14 days but I always have a backup, unfortunately this was no NAS in my administration)
>
> or to include the "most datas available" version
> c) "mdadm --create --verbose --assume-clean /dev/md0 --level=5 --raid-devices=8 >/dev/sd{a,b,c,d,e,f,g,h}3"
> to gather at least the older layout & data
>
>No, leave out the drive that dropped out first.
That would be my last try to get the data lossat a minimum
>
> d) "fsck.ext4 /dev/md0" on the array afterwards
>
>"fsck -n" first to make sure of the device order.
My first doing would be a dd dump of the md0 (tooks about 12 days)
>
>HTH,
>
>Phil
Thanks for the advice!
Michael
��.n��������+%������w��{.n�����{����w��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
