[Dell Inc. Latitude D620] hibernate/resume failure [non-free: nvidia]

[Stanislav Valasek]

Source package: probably error in kernel?

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu jaunty (development branch)
Release: 9.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
linux-image-generic:
  Installed: 2.6.28.11.14
  Candidate: 2.6.28.11.14
  Version table:
 *** 2.6.28.11.14 0
        500 http://cz.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
I upgraded NB from 8.10 to 9.04. Than I converted ext3 filesystem to ext4. Directions from http://ext4.wiki.kernel.org/index.php/Ext4_Howto#Converting_an_ext3_filesystem_to_ext4.
I thing today I upgraded a system - recomendent updates.
I tried to hibernate. Than I excected to wake up normally.

4) What happened instead
After bios check and menu ubuntu selection I got an error:
error 24: Attempt to access block outside partition.
I need to get live distro, check and correct ext4 partition, chroot and reinstall grub. Directions: http://mapopa.blogspot.com/2009/01/grub-voodoo-error-no-1324-and-how-do-i.html

I have duaboot with MS Windows XP.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: Dell Inc. Latitude D620
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcCmdLine: root=UUID=fefeeaea-5972-4956-bc0a-56609a53ae49 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux

[Chris (chris-yourdreamnet)]

This causes hibernate to stop working with ext4 on Karmic. I am able to boot with another kernel, but unable to unmount the root partition to check it. Checking with "fsck.ext4 -fn /dev/sda1" does a read-only check and reports errors. However, rebooting does not make the filesystem check work.

This also shows the bug that a ext4 partition cannot be remounted read only in single user mode.

To get a system check I ran "touch /forcefsck", but this did not cause it to on boot. I then tried "shutdown -rF now", still no fsck run.

I'm not sure what to try now.

[Chris (chris-yourdreamnet)]

I changed my /etc//fstab line to include "ro" so the root would mount read only. I could then run an fsck on the root filesystem.

I then ran "mount -o remount,rw /" to get write access back. Then I removed the "ro" from the fstab again.

No change to the error message.

I then proceeded to run "update-initramfs -k all -c". This broke all of my kernels. Great...