0

I have a RAID5 with 3 drives currently running on a 14.04 install. Everything is ok, but the system is a bit underpowered. Therefore I have gathered together some new hardware and installed 18.04 on it. I now want to move the RAID5 to the new system. I have the mdadm.conf file from the old system.

Is it as simple as copying the .conf file to the /etc/mdadm-folder and running a simple command? Or is there more to it?

I have noticed the mdadm.conf file doesn't specify the UUID of the drives currently in the RAID. Should this information be in the .conf-file? In fact, most of it is commented out. I've had some help setting this up, so the commenting out might be left-over from that time.

#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# 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>

# instruct the monitoring daemon where to send mail alerts
MAILADDR my.address@gmail.com

# definitions of existing MD arrays

# This file was auto-generated on Sun, 11 Dec 2016 12:03:25 +0100
# by mkconf $Id$
# ARRAY /dev/md0 uuid=2eb53a1c:a82b7568:44e5e773:527631b2
# /dev/md0:
#         Version : 1.2
#   Creation Time : Mon Dec 12 20:47:10 2016
#      Raid Level : raid5
#      Array Size : 7813770752 (7451.79 GiB 8001.30 GB)
#   Used Dev Size : 3906885376 (3725.90 GiB 4000.65 GB)
#    Raid Devices : 3
#   Total Devices : 3
#     Persistence : Superblock is persistent
# 
#     Update Time : Thu Dec 22 22:03:48 2016
#           State : clean 
#  Active Devices : 3
# Working Devices : 3
#  Failed Devices : 0
#   Spare Devices : 0
# 
#          Layout : left-symmetric
#      Chunk Size : 128K
# 
#            Name : unas14:0  (local to host unas14)
#            UUID : 2eb53a1c:a82b7568:44e5e773:527631b2
#          Events : 374
# 
#     Number   Major   Minor   RaidDevice State
#        0       8       17        0      active sync   /dev/sdb1
#        1       8       33        1      active sync   /dev/sdc1
#        2       8       49        2      active sync   /dev/sdd1

# Text below generated using [mdadm --detail --scan >> /etc/mdadm/mdadm.conf] 17.02.19
ARRAY /dev/md0 metadata=1.2 name=unas14:0 UUID=2eb53a1c:a82b7568:44e5e773:527631b2

Perhaps should I make a fresh mdadm.conf file containing the UUIDs of the drives first?

Any input is greatly appreciated. Thanks. :)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.