I'm marking the udev task as invalid, because this is not a udev bug.
Something else on the system is overwriting /dev/null (removing the device node udev creates), and obviously is also creating those .1, .2, etc. files
This will be quite difficult to debug, you'll need to first establish whether /dev/null exists before the system is booted. Try booting with init=/bin/bash on the kernel command line and check "stat /dev/null" - is it a file there or a device node?
I'm marking the udev task as invalid, because this is not a udev bug.
Something else on the system is overwriting /dev/null (removing the device node udev creates), and obviously is also creating those .1, .2, etc. files
This will be quite difficult to debug, you'll need to first establish whether /dev/null exists before the system is booted. Try booting with init=/bin/bash on the kernel command line and check "stat /dev/null" - is it a file there or a device node?