On Tue, 2011-02-01 at 14:52 +0100, martin f krafft wrote: > also sprach Rain Maker <rainmake...@gmail.com> [2011.02.01.1438 +0100]: > > > This is the correct fix. Remove the DEVICE line. > > > > Will I be able to implement this fix? If so, how? > > As root, run > > /usr/share/mdadm/mkconf force-generate > sed -i -e 's,^DEVICE,#&,' /etc/mdadm/mdadm.conf > update-initramfs -u >
Thanks. Not sure if it is important or not, but update-iniramfs -u gives me an error: root@Medusa:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 mdadm: cannot open /dev/md/BootEnBackup: No such file or directory mdadm: cannot open /dev/md/Data: No such file or directory root@Medusa:~# ls -l /dev/md/ total 0 lrwxrwxrwx 1 root root 8 Feb 1 21:06 BootEnBackup_0 -> ../md125 lrwxrwxrwx 1 root root 8 Feb 1 21:06 Data_0 -> ../md126 lrwxrwxrwx 1 root root 8 Feb 1 21:06 imsm0 -> ../md127 The initram seems to have been generated fine though, and works as expected :) Again, thanks. Roel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
