Re: destroyed raid 5 by removing wrong disk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 31.07.2018 um 23:11 schrieb Wol's lists:
On 31/07/18 18:52, Martin Probst wrote:


The disk /dev/sde1 was rebuilding at nearly 40%. I think, this disk is not useful for recovery. Is it possible to get these three disk working again? And how? I removed disk /dev/sdb for maybe 60 seconds. So it should be nearly synced to the both other clean devices. Can someone help me, please?

https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn

In particular "Asking for help" - get the output for lsdrv on all drives.

I'm hoping it's a simple matter of re-assembling the array, and restarting the rebuild. Try an explicit assemble, but DON'T use --force unless advised by someone who knows more than I do -) and then either the rebuild should restart automatically, or there are ways to restart it.

Just don't take the metaphorical hammer to try and force it to continue - that's a sure way to wreck it.

Cheers,
Wol

Hi, thanks for reply. The output of lsdrv is:

[root@tsa lsdrv]# ./lsdrv
PCI [ahci] 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
âscsi 0:0:0:0 ATA      MKNSSDCR60GB-7   {MK1604061001BF2B5}
ââsda 55.90g [8:0] Partitioned (dos)
â âsda1 500.00m [8:1] xfs {e74c6f48-b9d5-4d52-94f5-12ef333cfe89}
â ââMounted as /dev/sda1 @ /boot
â âsda2 55.41g [8:2] PV LVM2_member 55.34g used, 64.00m free {K3VIee-RMMh-jqT5-6lJJ-Mu1i-7SBh-PDcj85}
â  âVG centos <55.41g 64.00m free {f7op90-OJUs-akHP-H7wP-UyPu-MQ7L-wwGbrL}
â   âdm-2 16.32g [253:2] LV home xfs {21acc49d-871c-46bc-8109-f9d0adb1595d}
â   ââMounted as /dev/mapper/centos-home @ /home
â   âdm-0 33.43g [253:0] LV root xfs {a8426998-7dba-4908-9dde-7815fecd6718}
â   ââMounted as /dev/mapper/centos-root @ /
â   âdm-1 5.59g [253:1] LV swap swap {35bdac07-8cae-4c02-bd28-9cc689325423}
âscsi 1:0:0:0 ATA      WDC WD10EFRX-68J {WD-WMC1U9061988}
ââsdb 931.51g [8:16] Partitioned (dos)
â âsdb1 931.51g [8:17] MD raid5 (4) inactive 'tsa.myhome.lan:0' {32da23b1-b44b-51d0-d038-f0e6c38e7b29}
âscsi 2:0:0:0 ATA      WDC WD10EFRX-68F {WD-WCC4J0ENJPNJ}
ââsdc 931.51g [8:32] Partitioned (dos)
â âsdc1 931.51g [8:33] MD raid5 (4) inactive 'tsa.myhome.lan:0' {32da23b1-b44b-51d0-d038-f0e6c38e7b29}
âscsi 3:0:0:0 ATA      WDC WD10EFRX-68F {WD-WCC4J4APX71E}
ââsdd 931.51g [8:48] Partitioned (dos)
â âsdd1 931.51g [8:49] MD raid5 (4) inactive 'tsa.myhome.lan:0' {32da23b1-b44b-51d0-d038-f0e6c38e7b29}
âscsi 4:0:0:0 ATA      WDC WD10EFRX-68P {WD-WCC4J8RH9SF0}
 âsde 931.51g [8:64] Partitioned (dos)
âsde1 931.51g [8:65] MD raid5 (4) inactive 'tsa.myhome.lan:0' {32da23b1-b44b-51d0-d038-f0e6c38e7b29}

I try to assemble, but it doesn't work:
[root@tsa lsdrv]# mdadm --assemble /dev/md0 /dev/sdd1 /dev/sdc1 /dev/sdb1 /dev/sde1 mdadm: /dev/md0 assembled from 2 drives and 2 spares - not enough to start the array.

Is it importent to list the devices in correct order? I put a disk on another computer for backup. This change the order of my devices. But I have documented the correct order.

I didn't use --force at this time. I am current create backups from all disks.

Cheers,
Martin
--
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



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux