I'm having the same issue. You may want to check and see if the local-premount script is actually waiting for the right device. I found that my system had an incorrect UUID in the resume configuration file: /etc/initramfs- tools/conf.d/resume This file doesn't appear to have been changed as part of the Hardy upgrade on my system, based on the file modification time, so something else must have also changed due to the upgrade. I'm curious as to when/how this file is created and updated. I've had to reformat my swap partition several times in the past (the kernel kept telling me my swap had an invalid signature), so maybe the resume config file was never updated. Perhaps it is never updated after the first install?
You can check the UUIDs with stuff like this: cat /etc/initramfs-tools/conf.d/resume | cut -b13- cat /etc/fstab | grep swap | head -1 | cut -b6-41 ls -l /dev/disk/by-uuid/ I'm not all that familiar with the initrd stuff, but I am surprised that my system is attempting to look for a resume device, since I had disabled suspend/resume. I removed the "resume=<dev>" boot parameter via the grub configuration file. I glanced over the resume startup script, or at least what I think is the correct startup script (/usr/share/initramfs-tools/scripts/local-premount/resume), and it does not appear to check the kernel command line (/proc/cmdline) for the "resume=" parameter, of course, I'm not even sure if /proc is mounted at that point in time... Does anyone know if there is there a better (more official) way to disable resume? -- Slow boot process on "waiting for resume device" https://bugs.launchpad.net/bugs/206358 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
