☰

升级到拉伸尝试后 mdadm.conf 为空

tag-icon • tag-icon debian mdadm
升级到拉伸尝试后 mdadm.conf 为空

因为我非常有信心，所以今天我按照以下说明更新了我的杰西以进行拉伸：https://angristan.fr/mettre-a-jour-debian-8-jessie-vers-debian-9-stretch/

一切都很顺利，直到 apt full-upgrade 输出的最后一行：

update-initramfs: Generating /boot/initrd.img-4.9.0-4-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

我在 md0 上有一个数组。我的 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

# This configuration was auto-generated on Mon, 27 Mar 2017 14:34:34     +0200 by mkconf

我的 fstab 是

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc1 during installation
UUID=9b473d0e-84ab-4661-b03f-0ce5b56c215b /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc5 during installation
UUID=bc5f7676-5202-4202-903e-e50e6c4fcaf6 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

#/dev/md0
UUID=b1269cba-ec1b-4d68-b6a6-5f9830b5dfca   /mnt/raid5  ext4    defaults    0   2

我不记得我是如何构建阵列的，有没有办法可以重新生成这个conf文件（不，我没有备份）？我担心如果我重新启动我会丢失阵列（我可以复制文件仅有的291 G 数据）。

我看了这个链接https://serverfault.com/questions/867996/apt-get-install-linux-image-extra-getting-w-mdadm-etc-mdadm-mdadm-conf-defin但答案是针对没有数组的人。

感谢帮助。

答案1

/usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf

确实有效：重新生成了配置文件，重启后一切正常。最后事情变得简单了。

相关内容