In an MD-RAID1 system the rebuild process does not begin automatically without re-add the disk to MD-RAID1

Solution Verified - Updated -

Issue

  • When a RAID leg is removed, the resync of MD-RAID1 does not begin automatically when the exiting disk re-add or new disk inserted.
  • Need to re-add the disk once removed from the MD-RAID1 setup using #mdadm --manage command.
# mdadm -D /dev/md1
/dev/md1:
           Version : 1.2
     Creation Time : Thu Jul 27 10:11:02 2023
        Raid Level : raid1
        Array Size : 103808 (101.38 MiB 106.30 MB)
     Used Dev Size : 103808 (101.38 MiB 106.30 MB)
      Raid Devices : 2
     Total Devices : 1
       Persistence : Superblock is persistent

       Update Time : Tue Aug 29 10:11:47 2023
             State : clean, degraded 
    Active Devices : 1
   Working Devices : 1
    Failed Devices : 0
     Spare Devices : 0

Consistency Policy : resync

              Name : rhel8-3:1  (local to host rhel8-3)
              UUID : bd47b8a3:22dc9a21:dbfb4b28:91f3c70a
            Events : 38

    Number   Major   Minor   RaidDevice State
       2       8      112        0      active sync   /dev/sdh
       -       0        0        1      removed

Environment

  • Red Hat Enterprise Linux
  • md-raid

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content