* QNAP 8 port RAID5 md0 unmountable defective md superblocks
@ 2014-01-07 12:47 Michael Samer
2014-02-06 11:16 ` QNAP 8 port RAID5 md0 recovery of missing MBR and " Samer, Michael (I/ET-83, extern)
0 siblings, 1 reply; 10+ messages in thread
From: Michael Samer @ 2014-01-07 12:47 UTC (permalink / raw)
To: linux-raid
Hello list
Currently I've the a mdadm system here with unmountable volume due to
disk (timeout and badblocks) failures. I transfered the disk already to
new HDs.
Question: for this is a RAID5 the only redundant disk was lost to a
timeout sometime in the past and the second (/dev/sdf) had tons of
BadBlocks in the first and last 5MBs. I reconstructed the partition
table (as all 8 disks are build the same way), but how could I glue the
mdadm system together again. After that I'd start an integrity check of
the mdadm volume and afterwards an fsck. I attach the "mdadm --examine
/dev/sd*" so you might consider looking upon my problem
the md0 is found, but the md superblocks are missing on four of the 8
disks.
Question: Where is this superblock located so I can see if it was damaged
(badBlock). Is there a way to reconstruct this md superblock?
A "cat /proc/mdstat"give md0 a inactive (because of the lost redundancy)
The inability to mount the md0 is the main problem; the other md arrays
are uninteresting so far. The md0 consists of 8 disks combined into a
RAID5 Array; sometimes in the past one disk seems to be spilled out
(timeout which is quite a common problem with the WD Caviar Green
Editions due to their missing TLER feature). At 21.4 the /dev/sdf had
BadBlocks in the MBR/PT section and the array collapsed. The contact
with QNAP brought a few hints, but mainly: bring the backup into action
and rebuild. That's as much as I know about. All other actions have been
readonly to analyze. I've been the first to transfer the data to
Nearline Storage disks and looking a bit more into the system. In the
month waiting it seems two other disks seems to have badblocks gathered
as I could not explain the missing md superblocks with anything else.
Hitting such a critical area with such a low amount of BadBlocks puzzles
me somehow.
Here's the mdadm --examine /dev/sd*:
/dev/sda:
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/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 5
Preferred Minor : 9
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3e2e7326 - correct
Events : 763
Number Major Minor RaidDevice State
this 2 8 1 2 active sync /dev/sda1
0 0 0 0 0 removed
1 1 8 17 1 active sync /dev/sdb1
2 2 8 1 2 active sync /dev/sda1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sda2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 126
Update Time : Mon Dec 16 14:46:37 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be161f0b - correct
Events : 59
Number Major Minor RaidDevice State
this 4 8 2 4 spare /dev/sda2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 98 2 spare /dev/sdg2
3 3 8 82 3 spare /dev/sdf2
4 4 8 2 4 spare /dev/sda2
/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/sda4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e299b3 - correct
Events : 4355
Number Major Minor RaidDevice State
this 5 8 4 5 active sync /dev/sda4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/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/sdb1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 5
Preferred Minor : 9
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3e2e7334 - correct
Events : 763
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1
0 0 0 0 0 removed
1 1 8 17 1 active sync /dev/sdb1
2 2 8 1 2 active sync /dev/sda1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sdb4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e299c5 - correct
Events : 4355
Number Major Minor RaidDevice State
this 6 8 20 6 active sync /dev/sdb4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/dev/sdc:
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/sdc1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 8
Preferred Minor : 9
Update Time : Sun Apr 21 14:00:12 2013
State : clean
Internal Bitmap : present
Active Devices : 8
Working Devices : 8
Failed Devices : 0
Spare Devices : 0
Checksum : 3cf34b80 - correct
Events : 440
Number Major Minor RaidDevice State
this 0 8 17 0 active sync /dev/sdb1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 49 1 active sync /dev/sdd1
2 2 8 1 2 active sync /dev/sda1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 81 5 active sync /dev/sdf1
6 6 8 113 6 active sync /dev/sdh1
7 7 8 97 7 active sync /dev/sdg1
/dev/sdc2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 8
Preferred Minor : 8
Update Time : Thu Mar 7 09:42:20 2013
State : clean
Active Devices : 2
Working Devices : 8
Failed Devices : 0
Spare Devices : 6
Checksum : bc9f6dd7 - correct
Events : 31
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 8 114 2 spare /dev/sdh2
3 3 8 98 3 spare /dev/sdg2
4 4 8 82 4 spare /dev/sdf2
5 5 8 66 5 spare /dev/sde2
6 6 8 50 6 spare /dev/sdd2
7 7 8 34 7 spare /dev/sdc2
/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/sdc4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e299c9 - correct
Events : 4355
Number Major Minor RaidDevice State
this 0 8 36 0 active sync /dev/sdc4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/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/sdd1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 6
Preferred Minor : 9
Update Time : Tue Sep 17 12:47:24 2013
State : active
Internal Bitmap : present
Active Devices : 6
Working Devices : 6
Failed Devices : 2
Spare Devices : 0
Checksum : 3db7a8d2 - correct
Events : 723
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1
0 0 8 1 0 active sync /dev/sda1
1 1 8 33 1 active sync /dev/sdc1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sdd2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 126
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be1615ae - correct
Events : 59
Number Major Minor RaidDevice State
this 0 8 50 0 active sync /dev/sdd2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 98 2 spare /dev/sdg2
3 3 8 82 3 spare /dev/sdf2
4 4 8 2 4 spare /dev/sda2
/dev/sdd4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e299dd - correct
Events : 4355
Number Major Minor RaidDevice State
this 2 8 52 2 active sync /dev/sdd4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/dev/sde:
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/sde1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 5
Preferred Minor : 9
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3e2e7368 - correct
Events : 763
Number Major Minor RaidDevice State
this 3 8 65 3 active sync /dev/sde1
0 0 0 0 0 removed
1 1 8 17 1 active sync /dev/sdb1
2 2 8 1 2 active sync /dev/sda1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sde2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 8
Update Time : Fri Dec 13 12:02:41 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be1203d3 - correct
Events : 57
Number Major Minor RaidDevice State
this 3 8 66 3 spare /dev/sde2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 2 2 spare /dev/sda2
3 3 8 66 3 spare /dev/sde2
4 4 8 98 4 spare /dev/sdg2
/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/sde4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e299f1 - correct
Events : 4355
Number Major Minor RaidDevice State
this 4 8 68 4 active sync /dev/sde4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/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/sdf1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 9
Update Time : Sun Apr 21 14:50:18 2013
State : active
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3cf355e6 - correct
Events : 449
Number Major Minor RaidDevice State
this 5 8 81 5 active sync /dev/sdf1
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 1 2 active sync /dev/sda1
3 3 8 33 3 active sync /dev/sdc1
4 4 0 0 4 faulty removed
5 5 8 81 5 active sync /dev/sdf1
6 6 8 113 6 active sync /dev/sdh1
7 7 8 97 7 active sync /dev/sdg1
/dev/sdf2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 126
Update Time : Mon Dec 16 14:46:37 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be161f59 - correct
Events : 59
Number Major Minor RaidDevice State
this 3 8 82 3 spare /dev/sdf2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 98 2 spare /dev/sdg2
3 3 8 82 3 spare /dev/sdf2
4 4 8 2 4 spare /dev/sda2
/dev/sdf4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Wed Apr 24 14:30:56 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 61ab5765 - correct
Events : 1178
Number Major Minor RaidDevice State
this 5 8 84 5 active sync /dev/sdf4
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 4 2 active sync /dev/sda4
3 3 8 36 3 active sync /dev/sdc4
4 4 0 0 4 faulty removed
5 5 8 84 5 active sync /dev/sdf4
6 6 8 116 6 active sync /dev/sdh4
7 7 8 100 7 active sync /dev/sdg4
/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/sdg1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 5
Preferred Minor : 9
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3e2e738a - correct
Events : 763
Number Major Minor RaidDevice State
this 4 8 97 4 active sync /dev/sdg1
0 0 0 0 0 removed
1 1 8 17 1 active sync /dev/sdb1
2 2 8 1 2 active sync /dev/sda1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sdg2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 126
Update Time : Mon Dec 16 14:46:37 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be161f67 - correct
Events : 59
Number Major Minor RaidDevice State
this 2 8 98 2 spare /dev/sdg2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 98 2 spare /dev/sdg2
3 3 8 82 3 spare /dev/sdf2
4 4 8 2 4 spare /dev/sda2
/dev/sdg4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e29a0f - correct
Events : 4355
Number Major Minor RaidDevice State
this 3 8 100 3 active sync /dev/sdg4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/dev/sdh:
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/sdh1:
Magic : a92b4efc
Version : 0.90.00
UUID : 05105cec:26fef0b4:bf3f9508:05f7c111
Creation Time : Sun Jan 27 18:38:01 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 8
Total Devices : 5
Preferred Minor : 9
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 5
Working Devices : 5
Failed Devices : 2
Spare Devices : 0
Checksum : 3e2e739e - correct
Events : 763
Number Major Minor RaidDevice State
this 6 8 113 6 active sync /dev/sdh1
0 0 0 0 0 removed
1 1 8 17 1 active sync /dev/sdb1
2 2 8 1 2 active sync /dev/sda1
3 3 8 65 3 active sync /dev/sde1
4 4 8 97 4 active sync /dev/sdg1
5 5 0 0 5 faulty removed
6 6 8 113 6 active sync /dev/sdh1
7 7 0 0 7 faulty removed
/dev/sdh2:
Magic : a92b4efc
Version : 0.90.00
UUID : 39e8ca2f:3cfff703:4de89223:ac2a0c13
Creation Time : Thu Mar 7 09:41:55 2013
Raid Level : raid1
Used Dev Size : 530048 (517.71 MiB 542.77 MB)
Array Size : 530048 (517.71 MiB 542.77 MB)
Raid Devices : 2
Total Devices : 5
Preferred Minor : 126
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Active Devices : 2
Working Devices : 5
Failed Devices : 0
Spare Devices : 3
Checksum : be1615f0 - correct
Events : 59
Number Major Minor RaidDevice State
this 1 8 114 1 active sync /dev/sdh2
0 0 8 50 0 active sync /dev/sdd2
1 1 8 114 1 active sync /dev/sdh2
2 2 8 98 2 spare /dev/sdg2
3 3 8 82 3 spare /dev/sdf2
4 4 8 2 4 spare /dev/sda2
/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
/dev/sdh4:
Magic : a92b4efc
Version : 0.90.00
UUID : 4bfc2d50:283e9f67:803faac1:21814c31
Creation Time : Sun Jan 27 18:38:10 2013
Raid Level : raid1
Used Dev Size : 458880 (448.20 MiB 469.89 MB)
Array Size : 458880 (448.20 MiB 469.89 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 13
Update Time : Mon Dec 16 14:05:54 2013
State : clean
Internal Bitmap : present
Active Devices : 7
Working Devices : 7
Failed Devices : 1
Spare Devices : 0
Checksum : 62e29a1b - correct
Events : 4355
Number Major Minor RaidDevice State
this 1 8 116 1 active sync /dev/sdh4
0 0 8 36 0 active sync /dev/sdc4
1 1 8 116 1 active sync /dev/sdh4
2 2 8 52 2 active sync /dev/sdd4
3 3 8 100 3 active sync /dev/sdg4
4 4 8 68 4 active sync /dev/sde4
5 5 8 4 5 active sync /dev/sda4
6 6 8 20 6 active sync /dev/sdb4
7 7 0 0 7 faulty removed
/dev/sdj:
MBR Magic : aa55
Partition[0] : 4320 sectors at 32 (type 83)
Partition[1] : 484608 sectors at 4352 (type 83)
Partition[2] : 484608 sectors at 488960 (type 83)
Partition[3] : 34048 sectors at 973568 (type 05)
/dev/sdj4:
MBR Magic : aa55
Partition[0] : 16608 sectors at 32 (type 83)
Partition[1] : 17408 sectors at 16640 (type 05)
Any hints? My first thought was restoring/copying/generating the md
superblock on all missing four member disks.
Hope anyone got some better insight and inspiration than me :-)
Cheers
Michael Samer
^ permalink raw reply [flat|nested] 10+ messages in thread* QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-01-07 12:47 QNAP 8 port RAID5 md0 unmountable defective md superblocks Michael Samer
@ 2014-02-06 11:16 ` Samer, Michael (I/ET-83, extern)
2014-02-17 13:33 ` AW: " Samer, Michael (I/ET-83, extern)
0 siblings, 1 reply; 10+ messages in thread
From: Samer, Michael (I/ET-83, extern) @ 2014-02-06 11:16 UTC (permalink / raw)
To: linux-raid@vger.kernel.org; +Cc: Samer, Michael (I/ET-83, extern)
Hi all
As my thread from the 7.1.2014 didn't bring any hint or any reply or way out, I tried to figure out which might get me started again:
As five disks show no md superblock and four didn't see a partition layout (to contain a superblock) I'd like to (re)create a fitting partition and then (re)create a new md superblock info on all disks.
A) should I use parted (manual) or testdisk (export/import)? As I could read the structure from any of the three working disks as all should be the same.
B) my first try would be to (temper with md ...) create a plain 1:1 system like before
"mdadm --create --assume-clean /dev/md0 --level=5 --raid-devices=8 /dev/sd{a,c,d,e,f,g,h}3 missing"
(as the sdb was spilled out some weeks before, so outdated)
When this doesn't work I'd try
"mdadm --create --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 week old layout & data
C) "fsck.ext4 /dev/md0" on the array afterwards
D) "mdadm --detail --scan --verbose > /etc/mdadm.conf"
[which is a missing function in the QNAP md implantation]
Cheers
Michael Samer
^ permalink raw reply [flat|nested] 10+ messages in thread* AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-06 11:16 ` QNAP 8 port RAID5 md0 recovery of missing MBR and " Samer, Michael (I/ET-83, extern)
@ 2014-02-17 13:33 ` Samer, Michael (I/ET-83, extern)
2014-02-17 13:47 ` Phil Turmel
2014-03-13 10:43 ` AW: " Samer, Michael (I/ET-83, extern)
0 siblings, 2 replies; 10+ messages in thread
From: Samer, Michael (I/ET-83, extern) @ 2014-02-17 13:33 UTC (permalink / raw)
To: 'linux-raid@vger.kernel.org'
Cc: Samer, Michael (I/ET-83, extern), 'philip@turmel.org'
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 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"
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
d) "fsck.ext4 /dev/md0" on the array afterwards
Does anyone has something better in mind?
Cheers
Michael
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-17 13:33 ` AW: " Samer, Michael (I/ET-83, extern)
@ 2014-02-17 13:47 ` Phil Turmel
2014-02-17 19:10 ` AW: " Samer, Michael (I/ET-83, extern)
2014-03-13 10:43 ` AW: " Samer, Michael (I/ET-83, extern)
1 sibling, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2014-02-17 13:47 UTC (permalink / raw)
To: Samer, Michael (I/ET-83, extern),
'linux-raid@vger.kernel.org'
Good morning Michael,
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.
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.
> 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.)
> 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.
> d) "fsck.ext4 /dev/md0" on the array afterwards
"fsck -n" first to make sure of the device order.
HTH,
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread* AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-17 13:47 ` Phil Turmel
@ 2014-02-17 19:10 ` Samer, Michael (I/ET-83, extern)
2014-02-17 19:21 ` Phil Turmel
0 siblings, 1 reply; 10+ messages in thread
From: Samer, Michael (I/ET-83, extern) @ 2014-02-17 19:10 UTC (permalink / raw)
To: 'Phil Turmel', 'linux-raid@vger.kernel.org'
>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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-17 19:10 ` AW: " Samer, Michael (I/ET-83, extern)
@ 2014-02-17 19:21 ` Phil Turmel
2014-02-18 12:16 ` AW: " Samer, Michael (I/ET-83, extern)
0 siblings, 1 reply; 10+ messages in thread
From: Phil Turmel @ 2014-02-17 19:21 UTC (permalink / raw)
To: Samer, Michael (I/ET-83, extern),
'linux-raid@vger.kernel.org'
On 02/17/2014 02:10 PM, Samer, Michael (I/ET-83, extern) wrote:
>> 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
Ok. Stop here. This report shows /dev/sda3 where the metadata thought
it was /dev/sdd3. So your device names have been changing.
Please redo the --examine operation on all of the /dev/sdX3 partitions
and report again.
Also report an excerpt of "ls -l /dev/disk/by-id/" that shows the device
name vs. serial number for all of the drives involved.
Also report kernel and mdadm versions. The report format is an older style.
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread
* AW: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-17 19:21 ` Phil Turmel
@ 2014-02-18 12:16 ` Samer, Michael (I/ET-83, extern)
2014-02-18 12:59 ` Phil Turmel
0 siblings, 1 reply; 10+ messages in thread
From: Samer, Michael (I/ET-83, extern) @ 2014-02-18 12:16 UTC (permalink / raw)
To: 'Phil Turmel', 'linux-raid@vger.kernel.org'
Here's the actual examine of the target machine (I'm using a different one so disk designation is different as the target machine has only V2.6.3 available):
/dev/sda3:
Magic : a92b4efc
Version : 00.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 : 91564c0c - correct
Events : 0.136
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 3 0 active sync /dev/sda3
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/sdb3:
Magic : a92b4efc
Version : 00.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 : 0.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/sdd3:
Magic : a92b4efc
Version : 00.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 : 0.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/sde3:
Magic : a92b4efc
Version : 00.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 : 0.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/sdh3:
Magic : a92b4efc
Version : 00.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 : 0.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
@Phil: do you think there's a chance with my crude way or is there a better one?
Cheers
Sam
On 02/17/2014 02:10 PM, Samer, Michael (I/ET-83, extern) wrote:
>> 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
Ok. Stop here. This report shows /dev/sda3 where the metadata thought
it was /dev/sdd3. So your device names have been changing.
Please redo the --examine operation on all of the /dev/sdX3 partitions
and report again.
Also report an excerpt of "ls -l /dev/disk/by-id/" that shows the device
name vs. serial number for all of the drives involved.
Also report kernel and mdadm versions. The report format is an older style.
Phil
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-18 12:16 ` AW: " Samer, Michael (I/ET-83, extern)
@ 2014-02-18 12:59 ` Phil Turmel
0 siblings, 0 replies; 10+ messages in thread
From: Phil Turmel @ 2014-02-18 12:59 UTC (permalink / raw)
To: Samer, Michael (I/ET-83, extern),
'linux-raid@vger.kernel.org'
Hi Michael,
[Please don't top post. Trim & reply inline or bottom.]
On 02/18/2014 07:16 AM, Samer, Michael (I/ET-83, extern) wrote:
> Here's the actual examine of the target machine (I'm using a
> different one so disk designation is different as the target machine
> has only V2.6.3 available):
[trim /]
We'll need more information on the new platform, w/ all disks involved.
Please start with "lsdrv >tree.txt" [1] and then "gdisk -l" for all
disks. Consider including "smartdrv -x" for all as well.
Phil
[1] https://github.com/pturmel/lsdrv
^ permalink raw reply [flat|nested] 10+ messages in thread
* AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
2014-02-17 13:33 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-17 13:47 ` Phil Turmel
@ 2014-03-13 10:43 ` Samer, Michael (I/ET-83, extern)
1 sibling, 0 replies; 10+ messages in thread
From: Samer, Michael (I/ET-83, extern) @ 2014-03-13 10:43 UTC (permalink / raw)
To: Samer, Michael (I/ET-83, extern),
'linux-raid@vger.kernel.org'
Cc: 'philip@turmel.org'
Greetings to all
Phil solved my problem with his help
A bit diffusing was the problem of my partedMagic different /dev/sdx sorting:
QNAP Original:
sda=ZXT
sdb=S13
sdc=P3E
sdd=ZB6
sde=GJN
sdf=PSN
sdg=WD
sdh=1NH
Parted Order=rebuildversion:
sda=ZB6
sdb=P3E
sdc=S13
sdd=ZXT
sde=GJN
sdf=PSN
sdg=WD
sdh=1NH
so:
mdadm --create --assume-clean --verbose /dev/md0 --chunk=64 --metadata=0.9 --level=5 --raid-devices=8 /dev/sdd3 missing /dev/sd{b,a,e,f,g,h}3
mdadm --assemble /dev/md0 --uuid=30358eff:ac9e6122:004291dc:e0ebbc5e
mdadm --detail --scan >> /etc/mdadm.conf
dd /dev/md0 /BACKUP/Pallmert.bin
worked and did the job and is currently saving the image for further inspection.
Thanks a lot!
Michael
^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <A2EC67620EC7424F9EC3DD49243E9060466EE037@AUDIINSX0328.audi.vwg>]
end of thread, other threads:[~2014-03-13 10:43 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-07 12:47 QNAP 8 port RAID5 md0 unmountable defective md superblocks Michael Samer
2014-02-06 11:16 ` QNAP 8 port RAID5 md0 recovery of missing MBR and " Samer, Michael (I/ET-83, extern)
2014-02-17 13:33 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-17 13:47 ` Phil Turmel
2014-02-17 19:10 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-17 19:21 ` Phil Turmel
2014-02-18 12:16 ` AW: " Samer, Michael (I/ET-83, extern)
2014-02-18 12:59 ` Phil Turmel
2014-03-13 10:43 ` AW: " Samer, Michael (I/ET-83, extern)
[not found] <A2EC67620EC7424F9EC3DD49243E9060466EE037@AUDIINSX0328.audi.vwg>
2014-02-24 12:36 ` Phil Turmel
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).