On 3 June 2012 19:38, Krzysztof Adamski <k@xxxxxxxxxxx> wrote: > On Mon, 2012-06-04 at 02:32 +0800, Igor M Podlesny wrote: >> On 4 June 2012 01:31, Krzysztof Adamski <k@xxxxxxxxxxx> wrote: >> […] >> > The cat /proc/mdstat is: >> > Personalities : [raid1] [raid6] [raid5] [raid4] >> > md7 : active raid6 sdd2[0] sdab2[11] sdaa2[10] sdz2[9] sdy2[8] sde2[7] sdh2[6] sdf2[5] sdg2[4] sdb2[3](F) sdc2[2] sda2[1] >> > 29283121600 blocks super 1.2 level 6, 32k chunk, algorithm 2 [12/11] [UUU_UUUUUUUU] >> > [=============>.......] check = 65.3% (1913765076/2928312160) finish=44345.9min speed=381K/sec >> > bitmap: 1/22 pages [4KB], 65536KB chunk >> > >> > I don't really want to wait 30 days for this to finish, what is correct >> > thing to do before I replace the failed drive? >> > > -- > 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 Don't quote me on this, But since you are running a RAID6 with 1 degraded drive you could stop the check (echo idle > /sys/block/mdX/md/sync_action , I believe). Then you could manually fail the broken HDD, remove it, then physically replace it. However, it looks like MD already did that for you ([UUU_UUUUUUUU]). If possible I'd unmount any filesystems on the array first just in case. Kind regards, Mathias -- 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
