I had a similiar problem on upgrading to Feisty. I would get an error similiar to this: "fsck.ext3: No such file or directory while trying to open /dev/.tmp-254-3" and the control-D to continue message, but after the boot process the partitions would mount correctly and appeared error free. in /var/log/fsck/checkfs the log would confirm this error message.
after looking around a bit on the internet, i found this post: http://ubuntuforums.org/archive/index.php/t-25938.html it seems this might be related to udev here's the salient quote from that link : "I had a problem a little like this. There is a known problem regarding timing of events at boot and udev devices not being created quickly enough. I got round it by adding a 5 second sleep at the beginning of the fsck script in /etc/init.d" So I added the line "sleep 5" after the initial comments in /etc/init.d/checkfs.sh , and everything seems to work OK since then. I haven't had the message at all. /var/log/fsck/checkfs confirms that the file systems have all been fully checked. -- Boot interrupted after feisty upgrade--gives a command prompt for no apparent reason https://bugs.launchpad.net/bugs/106565 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
