How to remove the hd resync, I've badly assigned /dev/sdb to a raid portion

advapi · 24. August 2018

Hello,
I've replaced a bad sector hd of my Raid5. I've added it to the missing raid using the webUI, but i've wrongly added to /dev/md126 the whole /deb/sdb and not it's portion. now I do

Code

mdadm --manage --set-faulty /dev/md126 /dev/sdb
mdadm --manage /dev/md126 --remove /dev/sdb

And I've to perform a reboot so that I can do after

Code

mdadm --manage /dev/md126 --add /dev/sdb3
mdadm --manage /dev/md13 --add /dev/sdb4
and so on...

But after the reboot the resync automatically start..

Here're the detail you request

cat /proc/mdstat

Code

md9 : active raid1 sda1[0] sdc1[2] sdd1[3]
      530048 blocks [4/3] [U_UU]
      bitmap: 2/65 pages [8KB], 4KB chunk


md126 : active raid5 sdc3[1] sda3[0] sdb[4](F) sdd3[3]
      5855836800 blocks level 5, 64k chunk, algorithm 2 [4/3] [UU_U]


md13 : active raid1 sdc4[2] sda4[0] sdd4[3]
      458880 blocks [4/3] [U_UU]
      bitmap: 2/57 pages [8KB], 4KB chunk


md4 : active (auto-read-only) raid1 sdc2[1] sda2[0] sdd2[2](S)
      530048 blocks [2/2] [UU]

Alles anzeigen

bldk

Code

/dev/sda1: UUID="13ba2058-84c9-b23f-94c3-74d53167e1c2" TYPE="linux_raid_member" PARTUUID="0001af6b-01"
/dev/sda2: UUID="402ffbf8-4ab4-c138-67e6-0d254f4db159" TYPE="linux_raid_member" PARTUUID="0001af6b-02"
/dev/sda3: UUID="604e122c-42eb-5b4e-b015-dd01bc2e42fc" TYPE="linux_raid_member" PARTUUID="0001af6b-03"
/dev/sda4: UUID="97d58847-6b6c-8f4c-b1b2-71e0892c9325" TYPE="linux_raid_member" PARTUUID="0001af6b-04"
/dev/sdd1: UUID="13ba2058-84c9-b23f-94c3-74d53167e1c2" TYPE="linux_raid_member" PARTUUID="7678a671-01"
/dev/sdd2: UUID="402ffbf8-4ab4-c138-67e6-0d254f4db159" TYPE="linux_raid_member" PARTUUID="7678a671-02"
/dev/sdd3: UUID="604e122c-42eb-5b4e-b015-dd01bc2e42fc" TYPE="linux_raid_member" PARTUUID="7678a671-03"
/dev/sdd4: UUID="97d58847-6b6c-8f4c-b1b2-71e0892c9325" TYPE="linux_raid_member" PARTUUID="7678a671-04"
/dev/sdc1: UUID="13ba2058-84c9-b23f-94c3-74d53167e1c2" TYPE="linux_raid_member" PARTUUID="000c94f3-01"
/dev/sdc2: UUID="402ffbf8-4ab4-c138-67e6-0d254f4db159" TYPE="linux_raid_member" PARTUUID="000c94f3-02"
/dev/sdc3: UUID="604e122c-42eb-5b4e-b015-dd01bc2e42fc" TYPE="linux_raid_member" PARTUUID="000c94f3-03"
/dev/sdc4: UUID="97d58847-6b6c-8f4c-b1b2-71e0892c9325" TYPE="linux_raid_member" PARTUUID="000c94f3-04"
/dev/sdb: UUID="604e122c-42eb-5b4e-b015-dd01bc2e42fc" TYPE="linux_raid_member"
/dev/sde1: UUID="b2001418-52fd-4f6b-9e24-8705c8b82ba0" TYPE="ext4" PARTUUID="442a50f5-01"
/dev/sde5: UUID="e7da58b5-173a-45de-9f09-c176dbaefd38" TYPE="swap" PARTUUID="442a50f5-05"
/dev/md4: UUID="1f65288c-4c03-41af-823b-1836cea0a1c3" TYPE="swap"
/dev/md13: UUID="9b3e5a38-f042-4a42-ad3a-5dc6251e7009" TYPE="ext3"
/dev/md126: UUID="05bb45d1-54a9-445c-883f-f20faf53edab" TYPE="ext4"
/dev/md9: UUID="08151ef5-b4ef-4fe4-a950-2e6d088cb72b" TYPE="ext3"

Alles anzeigen

fdisk -l | grep "Disk "

Code

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 0x0001af6b
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 0x7678a671
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 0x000c94f3
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk /dev/sde: 74.5 GiB, 80026361856 bytes, 156301488 sectors
Disk identifier: 0x442a50f5
Disk /dev/md4: 517.6 MiB, 542769152 bytes, 1060096 sectors
Disk /dev/md13: 448.1 MiB, 469893120 bytes, 917760 sectors
Disk /dev/md126: 5.5 TiB, 5996376883200 bytes, 11711673600 sectors
Disk /dev/md9: 517.6 MiB, 542769152 bytes, 1060096 sectors

Alles anzeigen

cat /etc/mdadm/mdadm.conf

Code

# 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.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
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>


# definitions of existing MD arrays
ARRAY /dev/md9 metadata=0.90 UUID=13ba2058:84c9b23f:94c374d5:3167e1c2
ARRAY /dev/md126 metadata=0.90 spares=1 UUID=604e122c:42eb5b4e:b015dd01:bc2e42fc
ARRAY /dev/md4 metadata=0.90 spares=1 UUID=402ffbf8:4ab4c138:67e60d25:4f4db159
ARRAY /dev/md13 metadata=0.90 UUID=97d58847:6b6c8f4c:b1b271e0:892c9325

Alles anzeigen

and the scan

Code

ARRAY /dev/md4 level=raid1 num-devices=2 metadata=0.90 spares=1 UUID=402ffbf8:4ab4c138:67e60d25:4f4db159
   devices=/dev/sda2,/dev/sdc2,/dev/sdd2
ARRAY /dev/md13 level=raid1 num-devices=4 metadata=0.90 UUID=97d58847:6b6c8f4c:b1b271e0:892c9325
   devices=/dev/sda4,/dev/sdc4,/dev/sdd4
ARRAY /dev/md126 level=raid5 num-devices=4 metadata=0.90 UUID=604e122c:42eb5b4e:b015dd01:bc2e42fc
   devices=/dev/sda3,/dev/sdb,/dev/sdc3,/dev/sdd3
ARRAY /dev/md9 level=raid1 num-devices=4 metadata=0.90 UUID=13ba2058:84c9b23f:94c374d5:3167e1c2
   devices=/dev/sda1,/dev/sdc1,/dev/sdd1

What can I do in order to stop the resync and add them manually?
Thanks

Jetzt mitmachen!