[질문] apt-get upgrade 이후 mdadm 관련 warning 해결방법

apt-get update 이후 apt-get upgrade 입력하고 나니 처음보는 문구가 있어서 글을 남깁니다.

W: mdadm: the array /dev/md/imsm0 with UUID metadata=imsm
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.

mdadm.conf 설정이 제대로 되어 있는지, 재부팅 해도 되는지 궁금합니다.

아래는 자동 생성된 /etc/mdadm/mdadm.conf 의 내용입니다.

mdadm.conf

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 root

definitions of existing MD arrays

ARRAY metadata=imsm UUID=db9a5594:ad532dc5:2b59cc7f:2b8cacb2
ARRAY /dev/md/Volume1 container=db9a5594:ad532dc5:2b59cc7f:2b8cacb2 member=0 UUID=7a9e6fe2:e13dc08d:cae2770d:26ea8e2d

This file was auto-generated on Thu, 27 Apr 2017 17:21:41 +0900

by mkconf $Id$

그리고 아래는 /usr/share/mdadm/mkconf 의 실행 결과입니다.

mdadm.conf

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 root

definitions of existing MD arrays

ARRAY metadata=imsm UUID=db9a5594:ad532dc5:2b59cc7f:2b8cacb2
ARRAY /dev/md/Volume1 container=db9a5594:ad532dc5:2b59cc7f:2b8cacb2 member=0 UUID=7a9e6fe2:e13dc08d:cae2770d:26ea8e2d

그리고 아래는 mdadm --misc --detail /dev/md 들의 출력 결과입니다.
/dev/md127:
Version : imsm
Raid Level : container
Total Devices : 3

Working Devices : 3

Member Arrays : /dev/md/Volume1

Number   Major   Minor   RaidDevice

   0       8        0        -        /dev/sda
   1       8       16        -        /dev/sdb
   2       8       32        -        /dev/sdc

/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid5
Array Size : 5860528128 (5589.04 GiB 6001.18 GB)
Used Dev Size : 2930264192 (2794.52 GiB 3000.59 GB)
Raid Devices : 3
Total Devices : 3

      State : clean 

Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

     Layout : left-asymmetric
 Chunk Size : 128K


       UUID : 7a9e6fe2:e13dc08d:cae2770d:26ea8e2d
Number   Major   Minor   RaidDevice State
   2       8       16        0      active sync   /dev/sdb
   1       8       32        1      active sync   /dev/sdc
   0       8        0        2      active sync   /dev/sda

/dev/md/Volume1:
Container : /dev/md/imsm0, member 0
Raid Level : raid5
Array Size : 5860528128 (5589.04 GiB 6001.18 GB)
Used Dev Size : 2930264192 (2794.52 GiB 3000.59 GB)
Raid Devices : 3
Total Devices : 3

      State : clean 

Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

     Layout : left-asymmetric
 Chunk Size : 128K


       UUID : 7a9e6fe2:e13dc08d:cae2770d:26ea8e2d
Number   Major   Minor   RaidDevice State
   2       8       16        0      active sync   /dev/sdb
   1       8       32        1      active sync   /dev/sdc
   0       8        0        2      active sync   /dev/sda

/dev/md/imsm0:
Version : imsm
Raid Level : container
Total Devices : 3

Working Devices : 3

Member Arrays : /dev/md/Volume1

Number   Major   Minor   RaidDevice

   0       8        0        -        /dev/sda
   1       8       16        -        /dev/sdb
   2       8       32        -        /dev/sdc

UUID의 형식이 잘 못 되었습니다.
콜론이 정확한지 부터 확인해 보십시오.

정확한 UUID를 체크하시려면 blkid 명령어를 이용해 보십시오.