Tugger the SLUGger!SLUG Mailing List Archives

Re: [SLUG] mdadm


... snip
>> update-initramfs -k all -u
>>
> 
> 
> Lots of warnings (see below). I sort of think these are not problems,
> because I don't have any raid devices but I'm still bothered that I
> might reboot and die! Some of the messages are pretty cryptic if you
> don't actually know. God help a beginner. Maybe I shouldn't worry so
> much - just re-boot and hope.
> 
> I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as
> suggested, but I'm not a lot wiser. At least I've got a vague idea what
> initramfs IS now. I still can't guess what md is administering.Multi
> Device?

so you have

rm -f /var/lib/mdadm/CONF-UNCHECKED

got rid of the errors for me.. on a system running software raid, not
that it should matter.


> 
> david@test:~/test $ sudo update-initramfs -k all -u
> Password:
> update-initramfs: Generating /boot/initrd.img-2.6.20-16-386
> W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
> W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
> W: mdadm: no arrays defined in configuration file.
> W: mdadm: falling back to emergency procedure in initramfs.
> update-initramfs: Generating /boot/initrd.img-2.6.20-15-386
> W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
> W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
> W: mdadm: no arrays defined in configuration file.
> W: mdadm: falling back to emergency procedure in initramfs.
> update-initramfs: Generating /boot/initrd.img-2.6.17-10-386
> W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
> W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
> W: mdadm: no arrays defined in configuration file.
> W: mdadm: falling back to emergency procedure in initramfs.
> update-initramfs: Generating /boot/initrd.img-2.6.15-23-386
> W: udev hook script requires at least kernel version 2.6.17
> W: not generating requested initramfs for kernel 2.6.15-23-386
... snip

--
Steve

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________