On 11/29/11 04:51, Stephen Powell wrote:
On Tue, 29 Nov 2011 01:21:58 -0500 (EST), Marc Shapiro wrote:Well, I just rebooted again, and things are better, but still not quite right. This problem has NOT gone away. I can use 'noresume' but I should not have to and it seems that it would be best not to, so that all power saving routines will work properly.The syntax of your /etc/initramfs-tools/conf.d/resume file is incorrect, if your previous post is accurate. (1) Change /etc/initramfs-tools/conf.d/resume to say RESUME=UUID=xxx... instead of UUID=xxx... (2) Edit /etc/lilo.conf to eliminate the "noresume" option. (3) Issue the command (as root of course) update-initramfs -uk $(uname -r) This will update your initial RAM file system with the updated copy of /etc/initramfs-tools/conf.d/resume and should also run lilo. If update-initramfs does not run lilo after updating the initial RAM file system, then run it manually and let me know that it didn't run automatically; so we can investigate the cause of that problem. Then reboot.
Still no luck. Here are the contents of: /etc/initramfs-tools/conf.d/resume /etc/initramfs-tools/conf.d/driver-policy /etc/lilo.conf :/etc/initramfs-tools/conf.d$ cat resume RESUME=UUID=305ee6c5-c60c-4167-a57c-e13c96ed1e79 :/etc/initramfs-tools/conf.d$ cat driver-policy # Driver inclusion policy selected during installation # Note: this setting overrides the value set in the file # /etc/initramfs-tools/initramfs.conf MODULES=dep :/etc/initramfs-tools/conf.d$ cat /etc/fstab # /etc/fstab: static file system information. ## <file system> <mount point> <type> <options> <dump> <pass>
UUID=5e0d4da4-aba3-4965-8fb4-788501b0fe69 / ext3 errors=remount-ro 0 1 UUID=305ee6c5-c60c-4167-a57c-e13c96ed1e79 none swap sw 00 proc /proc proc defaults 0 0 none /proc/bus/usb usbfs defaults 0 0 /dev/mapper/vg1-tmp /tmp ext3 defaults 0 2 /dev/mapper/vg1-var2 /var ext3 defaults 0 2 /dev/mapper/vg1-usr /usr ext3 defaults 0 2 /dev/mapper/vg1-photos /usr/local/photos ext3 defaults 0 2 /dev/mapper/vg1-home /home ext3 defaults 0 2
I have run 'update-initramfs -uk $(uname -r)' again and lilo DOES run after the initrd is updated, but I still get the message on bootup that it can not stat the resume device and the device that it tries to get is still the OLD swap file on the boot drive (under LVM) that is not mentioned in any of the files above. The new swap file, which is listed in /etc/initramfs-tools/conf.d/resume and /etc/lilo.conf is a primary partition on the new drive.
Could there be a problem with the resume device not being on the boot drive? Marc