This problem is solved by upgrading to linux-image-2.6.24-8. Adding solved to title. Please close bug report.
** Summary changed: - [hardy] linux-image-2.6.24-7-generic - fsck.ext3: No such file or directory while trying to open /dev/sda1 + [SOLVED] [hardy] linux-image-2.6.24-7-generic - fsck.ext3: No such file or directory while trying to open /dev/sda1 ** Description changed: Upgraded from 2.6.24-5 to 2.6.24-7 and during the boot process I get: [code] fsck.ext3: No such file or directory while trying to open /dev/sda1 /dev/sda1: The superblock could not be read or does not describe correct ext2 filesystem. If the devices is valid and ti really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock: e2fsck -b 8193 <device> ..... fsck died with exit status 8 ... fail! * File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. - [code] + [/code] /var/log is not writable nor is anything mounted besides tmpfs. Unfortunately this is all the information I currently have due to me not being able to write everything down from my laptop to paper and back to my laptop. This has only occurred with the latest kernel in the hardy repository (2.6.24-7) and not with any of the previous versions. -- [SOLVED] [hardy] linux-image-2.6.24-7-generic - fsck.ext3: No such file or directory while trying to open /dev/sda1 https://bugs.launchpad.net/bugs/191712 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
