Rename Existing MDADM RAID5 array

curto · 27. September 2021

Guys,

My two MDADM arrays show as MD126 and MD127, one MD127 was created from the commandline on this box under OMV so it is "native" to the box. The other MD126 was created on this system but under a previous OS - Centos 7. (OMV when installed recognized this and made it available through the GUI)

Both systems use EXT4.

The arrays both use 1.2 of the metadata/superblock.

I am attempting to import another array (4 drives RAID5) created under Centos with EXT4 FS also.

I have a 16 channel LSI controller (in IT mode) and all of the RAID drives hang off it. My Boot drive is on a motherboard SATA port.

When i boot up the new array it deactivates some of the other drives and will not assemble the other 2 arrays - but the newly imported one comes up fine.

I think it might be a naming issue with it trying to take the MD127 name.

So my question is can i rename the existing arrays using standard MDADM tools (and update Initram) without OMV worrying ? I would assume so as it appears to reference them all by UUID ?

Craig

geaves · 27. September 2021

You obviously know what you're doing, but initially I would look at the output from cat /proc/mdstat before running anything else

curto · 16. Oktober 2021

Sorry - Life got in the way and just coming back to this now

It is a little screwy so i wanted to check here before proceeding to make sure this will not have any OMV implications

running

Code

mdadm --detail /dev/*

gives me

/dev/md126:
           Version : 1.2
     Creation Time : Fri Feb 26 02:11:03 2021
        Raid Level : raid5
        Array Size : 3906744064 (3725.76 GiB 4000.51 GB)
     Used Dev Size : 1953372032 (1862.88 GiB 2000.25 GB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Sun Oct 17 04:24:07 2021
             State : clean, reshaping 
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 64K

Consistency Policy : bitmap

    Reshape Status : 5% complete
     Delta Devices : 1, (3->4)

              Name : openmediavault.curtin.home:1
              UUID : b874f36c:6c9de6fe:f670abf0:4e251528
            Events : 15496

    Number   Major   Minor   RaidDevice State
       0       8       34        0      active sync   /dev/sdc2
       2       8       66        1      active sync   /dev/sde2
       3       8       50        2      active sync   /dev/sdd2
       4       8       18        3      active sync   /dev/sdb2
/dev/md127:
           Version : 1.2
     Creation Time : Wed Feb 24 01:01:12 2021
        Raid Level : raid5
        Array Size : 35162339328 (33533.42 GiB 36006.24 GB)
     Used Dev Size : 5860389888 (5588.90 GiB 6001.04 GB)
      Raid Devices : 7
     Total Devices : 7
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Sun Oct 17 04:22:55 2021
             State : clean 
    Active Devices : 7
   Working Devices : 7
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : bitmap

              Name : openmediavault.curtin.home:0
              UUID : 0d7e7347:58823df1:87e5704d:8c86ffe6
            Events : 44324

    Number   Major   Minor   RaidDevice State
       0       8      113        0      active sync   /dev/sdh1
       1       8       97        1      active sync   /dev/sdg1
       2       8       81        2      active sync   /dev/sdf1
       8       8       17        3      active sync   /dev/sdb1
       4       8       33        4      active sync   /dev/sdc1
       6       8       49        5      active sync   /dev/sdd1
       7       8       65        6      active sync   /dev/sde1

Alles anzeigen

and then running

Code

 mdadm -Esv

gives me

ARRAY /dev/md/1  level=raid5 metadata=1.2 num-devices=4 UUID=b874f36c:6c9de6fe:f670abf0:4e251528 name=openmediavault.curtin.home:1
   devices=/dev/sdd2,/dev/sdc2,/dev/sdb2,/dev/sde2
ARRAY /dev/md/0  level=raid5 metadata=1.2 num-devices=7 UUID=0d7e7347:58823df1:87e5704d:8c86ffe6 name=openmediavault.curtin.home:0
   devices=/dev/sdh1,/dev/sdf1,/dev/sdd1,/dev/sdc1,/dev/sdg1,/dev/sdb1,/dev/sde1

So i want to rename /dev/md127 to /dev/md0 and propose to run this command

Code

mdadm --assemble --update=name --name=openmediavault.curtin.home:0 /dev/md0 /dev/sdh1 /dev/sdf1 /dev/sdd1 /dev/sdc1 /dev/sdg1 /dev/sdb1 /dev/sde1

Once the array md126 finishes reshaping i will rename it also

Obviously once this is done i will regenerate the initram and update mdadm.conf

Do you see OMV having any issues with the above ??

Craig

geaves · 16. Oktober 2021

Zitat von curto

Do you see OMV having any issues with the above

TBH I don't know never had anyone attempt this before, but then again your raid setup's have not been created using OMV. OMV does not use partitions to create arrays, there's nothing wrong with how you have set this up, it's just not the norm.

My suggestion would be to ensure you have a backup, just in case

curto · 17. Oktober 2021

This is used as a backup box for all of our media etc so no great drama if something goes wrong.

Craig

curto · 26. Oktober 2021

Just an update on this for anyone else trying this - went perfectly and now have the additional RAID set imported and all of them with set names.

Craig

Jetzt mitmachen!