Hi All, and apologies to those who read my Homer moment earlier. I got the following after running apt-get update on one of my servers (Debian Wheezy with ISPConfig 3.0.5.3): W: mdadm: the array /dev/md/3_0 with UUID d6ef77fc:c2faf3d8:1f51fb89:78ee93fe 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. W: mdadm: the array /dev/md/1_0 with UUID e3f6f7d7:e13f251f:1f51fb89:78ee93fe 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. Now if I go to /etc/mdadm/mdadm.conf I have the following: __________________________________________________ # 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 # This file was auto-generated on Tue, 26 Feb 2013 13:48:51 +0000 # by mkconf 3.2.5-5 ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md3 level=raid1 num-devices=2 devices=/dev/sda3,/dev/sdb3 #ARRAY /dev/md11 level=raid1 num-devices=2 devices=/dev/sdc1,/dev/sdd1 ______________________________________________________ But when I get the output of /usr/share/mdadm/mkconf I get: ______________________________________________________ # 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 /dev/md1 UUID=e3f6f7d7:e13f251f:1f51fb89:78ee93fe ARRAY /dev/md3 UUID=d6ef77fc:c2faf3d8:1f51fb89:78ee93fe # This configuration was auto-generated on Mon, 24 Feb 2014 18:58:54 +0000 # by mkconf 3.2.5-5 ______________________________________________ Any advice as to what to do next. All help greatly appreciated.
Hi Srijan my /etc/fstab entry is as follows: /dev/md1 / ext3 defaults,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 1 1 /dev/sda2 none swap sw /dev/sdb2 none swap sw /dev/vg00/usr /usr ext4 defaults 0 2 /dev/vg00/var /var ext4 defaults 0 2 /dev/vg00/home /home ext4 defaults 0 2 #/dev/hdd/data /data ext4 defaults 0 2 devpts /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /tmp tmpfs defaults 0 0 Just to confirm, If I comment out the original array lines in /etc/mdadm/mdadm.conf and replace them with: ARRAY /dev/md1 UUID=e3f6f7d7:e13f251f:1f51fb89:78ee93fe ARRAY /dev/md3 UUID=d6ef77fc:c2faf3d8:1f51fb89:78ee93fe and then run update-initramfs -u I get no more warnings. I believe this is what I'm meant to do but it would be nice to have it confirmed. Thanks, James
Hi James, This will sort your issue, as the /etc/mdadm/mdadm.conf was not able to read the UUID of the arrays & as you have added this, it resolved your issue. Br// Srijan
Thanks for your help Srijan. Just to confirm I have rebooted and everything came back as normal. Is there any reason I would expect to see this again now I have made the change or is there any further background reading worth looking at? Rgds James
Hi James, If the entries in the /etc/mdadm/mdadm.conf are same then there will be no difficulty in future. Br// Srijan
I have a similar issue. I got the identical error message upon running apt-get update.The difference is that my mkconfig has no info about my raid array. I'm wondering the best way to resolve my issue. So my obvious assumption is to add a line to the mkconf file saying something like: ARRAY /dev/md0 UUID=575d4af5-645a-4b89-8cba-c225722b0fc9 However knconfig is not a config file, but a script and I'm not sure where to place this so that it is recognized by mkconfig. lsblk: jd@FileServer1:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk └─md0 9:0 0 465.7G 0 raid1 /media/Pictures sdb 8:16 0 465.8G 0 disk └─md0 9:0 0 465.7G 0 raid1 /media/Pictures Drive UUID: jd@FileServer1:~$ ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 9 Sep 12 10:11 575d4af5-645a-4b89-8cba-c225722b0fc9 -> ../../md0 My mdadm.conf file: jd@FileServer1:~$ cat /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 DEVICE /dev/sda /dev/sdb ARRAY /dev/md0 devices=/dev/sda,/dev/sdb # 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 ##### MAILFROM FileServer1 - mdadm # definitions of existing MD arrays # This file was auto-generated on Sat, 16 May 2015 21:22:43 -0700 # by mkconf $Id$ mkconf: jd@FileServer1:~$ /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 /dev/sda /dev/sdb # 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 ########## # definitions of existing MD arrays
