Comment 38 for bug 495370

It seems that the file "65-mdadm.vol_id.rules" in "/lib/udev/rules.d/" was used by mdadm in Karmic (http://packages.ubuntu.com/karmic/i386/mdadm/filelist), and changed in Lucid to "65-mdadm-blkid.rules" with the fixing of Bug #493772.

I'm guessing your package is based on the Karmic version of mdadm?

Installing your package, this file is called "65-vol_id.rules", and is identical to both the file installed with Lucid's version of mdadm (2.6.7.1-1ubuntu15), called "65-mdadm-blkid.rules", and Karmic's version of mdadm ("65-mdadm.vol_id.rules").

It seems the above error comes from the initramfs hook script that your package places in "/usr/share/initramfs-tools/hooks/mdadm", which contains the following code:

    # copy the udev rules
    for rules in 65-mdadm.vol_id.rules 85-mdadm.rules; do
     cp -p /lib/udev/rules.d/$rules ${DESTDIR}/lib/udev/rules.d
    done

When the installation script runs "update-initramfs" (and when update-initramfs is run subsequently, independantly of the installation script), the error appears:

    rune@runescomp:~/Desktop/mdadm-new$ sudo update-initramfs -u
    update-initramfs: Generating /boot/initrd.img-2.6.32-23-generic
    cp: cannot stat `/lib/udev/rules.d/65-mdadm.vol_id.rules': No such file or directory

In "/usr/share/initramfs-tools/hooks/mdadm", changing "65-mdadm.vol_id.rules" to "65-vol_id.rules" in the above line from the hook script, the error disappears.

So unless something more is lurking beneath the surface - I don't know enough about the inner workings of either mdadm of Linux in general to assess that - the fix seems to be fairly simple. Changing the above line in "/usr/share/initramfs-tools/hooks/mdadm". Or, alternatively, to follow Lucid's naming convention of the file, rename the file to "65-mdadm-blkid.rules" and change this accordingly in the hook script.