Hi, before we start, please note that im not a pro at mdadm or lvm, and dont now the full terminology neither the full how it works. 1 week ago, 1 of my raid6 went wrong. it didnt have any superblock anymore. I know all the drives that belongs to that raid but i dont know the right order of the drives. I tried a python script with assemble and permutation all combination possible. it then checks the header and do a e2fsck -n to check errors. Everytime i run the script i get several and different results on each run. Some say that the order of the drives doesnt matter, i agree but withotuh superblock its another story. I got another raid6 which is fine and on top of those 2 raid6, there is a lvm. if you have any question or output you want to see, please tell me and i will provide further informations as soon as i can if you dont understand me, i apologize, im trying to be better at english everyday. Thanks William sudo cat /dev/.mdadm/map md0 1.2 85c93553:f5707fc9:b777b1e6:a0427190 /dev/md0 md1 1.2 32d61f75:647daf4b:c1ee26ec:bc926504 /dev/md1 cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid6 sdd1[5] sda1[4] sdi1[3] sdh1[2] sdj1[1] sdc1[0] 7809854976 blocks super 1.2 level 6, 128k chunk, algorithm 2 [6/6] [UUUUUU] md1 : active raid6 sdk1[0] sdg1[7] sde1[6] sdf1[5] sdm1[8] sdb1[1] 7809855488 blocks super 1.2 level 6, 128k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/15 pages [0KB], 65536KB chunk mount -r /mnt/data0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgRAID60-data0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so cat /etc/mdadm/mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # instruct the monitoring daemon where to send mail alerts MAILADDR jeromepoulin@xxxxxxxxx # definitions of existing MD arrays #ARRAY /dev/md/0 metadata=1.2 UUID=d2349636:b4a0cb67:2af3246a:c7d72c9c name=BILLSSHACK:0 ARRAY /dev/md1 UUID=b52df561:301f043c:b5a7b1ab:9d934878 spares=1 #ARRAY /dev/md/3 metadata=1.2 UUID=751fd632:4baf7d64:ec26eec1:046592bc name=billsshack:3 #ARRAY /dev/md/2 metadata=1.2 UUID=cf2450e4:bc7a9cea:cb5ccda9:6f3ec87c name=billsshack:2 # This file was auto-generated on Wed, 15 Jun 2011 08:57:49 -0400 # by mkconf $Id$ -- 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
