Error messages reported by GRUB 16 : Inconsistent filesystem structur e- Description: This error is returned by the file system code to denote an internal error caused by the sanity checks of the file system structure on disk not matching what it expects. This is usually caused by a corrupt file system or bugs in the code handling it in GRUB. Possible Solution:Start up using your live CD, if you dont have one use the instructions and links on this page: https://help.ubuntu.com/community/LiveCD
Determine you Ubuntu partitions sudo fdisk -lu Run fsck or e2fsck e2fsck -C0 -p -f -v /dev/hda2 (Where: hda2 is put your Ubuntu partition you found running fdisk -lu). **Check your SATA drive cables, especially if you have recently been inside your computer. There have been cases where a loose cable triggered this error. ** 18 : Selected cylinder exceeds maximum supported by BIOS - Description: This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general). Possible Cause: The GRUB error 18 message could be referring to the 137 GB BIOS hard disk size limit. This occurs when a machine was made for an 80 or 120 GB hard disk, and someone fits a 137 GB+ hard disk in thier machine without checking if the BIOS supports it. If you computer was made before 2000 the size limit is much smaller, 8.45 GB. So if you have installed a larger HD recently this could be your problem. Even if you have been using your computer for months with no problem your computer can become unmountable seemingly out of nowhere. Apparently, an operating system that is partly inside the hard drive limit may boot for some time as long as the kernel happens to be located within the part of the disk that the BIOS can 'see', its within the 137/8.45GB Hard Drive limit. After an update, if a newer kernel happens to be placed somewhere outside the limit, the operating system might suddenly become unable to boot (at least by the new kernel), Possible Solution: Check your computer's BIOS date and settings in case your BIOS can be updated. Otherwise you will need reduce the size of your Linux partition or create a boot partition which is probabally the better solution. Additional Information - This link has info on solving both these problems, including checking your BIOS, links to making a boot partition, ect. Follow the link and scroll down, its a long page, until you get to your GRUB error. http://users.bigpond.net.au/hermanzone/p15.htm#16 -- GRUB Error 16 and 18 https://bugs.launchpad.net/bugs/312607 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
