Comment 31 for bug 523484

So, if ureadahead is not the guilty party, who is?

I have a few 10.04 LTS servers which I have configured with separated /var and they have been working fine so far <knock on wood>.

I have another 10.04 LTS machine in which I created a separate partition for /var but forgot to configure it during install. No problem, I thought, I just had to boot in single user mode (rescue mode in Linux?), edit fstab, move /var to /var.old, and create a new /var. So far I am wrong: if I try to reboot I too get the same error message. So, I deleted the pack files located in /var/lib/ureadahead/, added "console output" to /etc/init/ureadahead.conf and tried again. This is what I got:

udevd-work [298] open /dev/null failed: no such file or directory
udevd-work [300] open /dev/null failed: no such file or directory
udevd [108] : worker [199] did not accept message -1 (connection refused), kill

udevd-work [118]: inotify_add_watch (6, /dev/sda3, 10) failed: no such device or directory
init: ureadahead-other main process (309) terminated with status 5

Don't ask me why it can't find /dev/null. It could be completely unrelated to this. FYI, sda3 is the lVM device; inside it is /var. / is sda2 and /boot sda1. Also, after I restarted the machine using the /var that is on the root filesystem, I did get to see the

udevd-work [118]: inotify_add_watch (6, /dev/sda3, 10) failed: no such device or directory

message during boot time but it did not stop the boot.