On 12/07/2013 11:52 AM, jdd wrote:
Le 07/12/2013 16:45, Lew Wolfgang a écrit :
hot-swap chassis configured as two 11-disk RAID-6 arrays with two global hot spares.
good
The RAID controllers will initiate "Patrol Reads" all on their own to look for hidden sector-read issues.
that is.
11 1Tb HDD - a dream :-)
very nice solution for High availability system :-)
I don't have such requirement, and I only make redundant archives
but I see too many people relying on two disks nats pretending to make raid.
backup/archive/availability is (are?) an intersting topic, but a never ending discussion :-)
thanks jdd
OK jdd, Lew, JA, All (sorry jdd - you get 2 copies) I need your help. I need to make sure I don't screw anything up attempting to remedy the situation. I have booted the box with the 11.0 DVD and entered Recovery Console. I have 3 mdraid partitions on this box: /dev/md0 sda1/sdb1 /boot /dev/md1 sda5/sdb5 / /dev/md2 sda7/sdb7 /home After booting the 11.0 install dvd and booting Recovery Console, mdraid found and assembled all arrays, md0 and md2 are fine, its is just md1 that is the problem: # cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sda7[0] sdb7[1] 221929772 blocks super 1.0 [2/2] [UU] bitmap: 0/424 pages [0KB], 256KB chunk md1 : inactive sda5[0] sdb5[1] 41945504 blocks super 1.0 md0 : active raid1 sda1[0] sdb1[1] 104376 blocks super 1.0 [2/2] [UU] bitmap: 0/7 pages [0KB], 8KB chunk I don't think there is anyway I can guess which of sda5 or sdb5 has the latest bitmap. I really don't think it matters, but I thought I would check. I just need to know the best way to go about fixing it so I do not lose the data. So is there a way I can use the --fail and --remove to then test which disk to keep as the good one before doing --zero-superblock on the other, and then --add to recreate the array and force a rebuild. Or is this just a case where you have to stop the array, and then recreate it using one of the drives and 'missing' and then re-add the other drive back after the array is up and running? I believe you have to use the --force to cause it to run with a missing device? The array information on disk for both disks (sda5/sdb5) shows the exact same Update Time, (Tue Nov 19 15:28:38 2013) the only difference between the output is the checksums (both shown correct) and the Events : 148/149, thus the reported error: md1: bitmap file is out of date (148 < 149) I have the complete output of: # mdadm --examine /dev/sd[ab]5 here: (1.7 Meg) http://www.3111skyline.com/dl/screenshots/suse/mdadm-examine.jpg What is the best way to do this? It seems simple, but I would rather look before I leap here. If there is a better way to attempt to get these partitions to re-sync, I am more than happy to give it a try. Thanks. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org