I suspect you may need to rebuild your initrd image by running
update-initramfs to reflect any changes in the mdadm.conf that may involve
md2.
Also check your DEVICE entry in mdadm.conf that it includes the correct
wildcard.
Good luck
Patrick
On Mon, Feb 27, 2017 at 12:59 PM, deloptes wrote:
>
basti wrote:
> ARRAY /dev/md0 metadata=1.2 name=srv01:0
> UUID=42c30af1:e6986757:2c6bf608:34582a76
> ARRAY /dev/md1 metadata=1.2 name=srv01:1
> UUID=05b45cf9:2bf2dae8:8b4ea488:8cb4c214
> # this line dones not start on boot
> ARRAY /dev/md2 metadata=0.90 UUID=63226122:8d9b97bb:99109359:8e81e636
>
Hi basti,
On Mon, Feb 27, 2017 at 10:21:51AM +0100, basti wrote:
> on one of my debian machine i have a error with one md raid.
>
> There are
> md0 => /
> md1 => /backup
> md2 => /samba
>
> md2 is not start/assemble after reboot,
I had a similar issue when I did not include the driver for some
Hello,
on one of my debian machine i have a error with one md raid.
There are
md0 => /
md1 => /backup
md2 => /samba
md2 is not start/assemble after reboot, my mdadm.conf looks like
ARRAY /dev/md0 metadata=1.2 name=srv01:0
UUID=42c30af1:e6986757:2c6bf608:34582a76
ARRAY /dev/md1 metadata=1.2 name=
4 matches
Mail list logo