[arch-dev-public] [signoff] udev-170-1
snowmaniscool at gmail.com
Fri May 20 21:42:01 EDT 2011
On Fri, May 20, 2011 at 4:41 PM, Tom Gundersen <teg at jklm.no> wrote:
> On Fri, May 20, 2011 at 8:44 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
>> While the kernel is booting, I'm getting error messages like these:
>> udevd: failed to execute '/sbin/mdadm' '/sbin/mdadm --incremental
>> /dev/sdb2' : No such file or directory
>> udevd: failed to execute '/sbin/mdadm' '/sbin/mdadm --detail --export
>> /dev/md1' : No such file or directory
>> and similar for the other hard disk and raid devices. From a quick
>> check, they seem to come from the udev rules from the mdadm package.
>> I don't know if it's the udev rules in mdadm that need to be updated
>> to work with the new udev or if it's a problem with the new udev
>> and/or kernel26 packages.
>> Despites these error messages, the raid array has assembled itself
>> correctly and everything seem to work fine.
>> Later today, I'll try to downgrade udev and or the kernel to see if it
>> helps. BTW, that's on x86_64.
> When you downgrade, could you manually change udev_log to "err" in
> /etc/udev/udev.conf? I enabled error printing again as of udev-170, so
> it could be that the error was always there, just never printed.
> Thanks for testing!
I'm not able to reproduce that anymore. The error went away during my
tests. Either it is a racing issue or it fixed itself with the
numerous upgrade/downgrade of udev and kernel.
More information about the arch-dev-public