After upgrading a server from 10.04 to 12.04 I saw errors on boot about udev trying to use a non-existent vol_id:
failed to execute '/lib/udev/vol_id' 'vol_id --export /dev/md0': No such file or directory
I tracked this down to the following line in /etc/udev/rules.d/65-mdadm.vol_id.rules:
IMPORT{program}="vol_id --export $tempnode"
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541884 mentions this issue and says that we should be using '/sbin/blkid -o udev -p ...' instead. Indeed, checking /lib/udev/rules.d/64-md-raid.rules, it has:
IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
I then updated /etc/udev/rules.d/65-mdadm.vol_id.rules to use this instead, and the errors went away.
After upgrading a server from 10.04 to 12.04 I saw errors on boot about udev trying to use a non-existent vol_id:
failed to execute '/lib/udev/vol_id' 'vol_id --export /dev/md0': No such file or directory
I tracked this down to the following line in /etc/udev/ rules.d/ 65-mdadm. vol_id. rules: program} ="vol_id --export $tempnode"
IMPORT{
http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 541884 mentions this issue and says that we should be using '/sbin/blkid -o udev -p ...' instead. Indeed, checking /lib/udev/ rules.d/ 64-md-raid. rules, it has: program} ="/sbin/ blkid -o udev -p $tempnode"
IMPORT{
I then updated /etc/udev/ rules.d/ 65-mdadm. vol_id. rules to use this instead, and the errors went away.