Help!!! Error 18 - Selected cylinder exceeds maximum supported by BIOS

Asked by Ludmil on 2009-12-12

Help!!! Error 18 - Selected cylinder exceeds maximum supported by BIOS

--------------------------------------------------------------------------------

Hi,

I am running Jaunty Jackalope on a new machine and after a recent update I got the following message when trying to reboot:

Error 18 - Selected cylinder exceeds maximum supported by BIOS

After reading some of the info on Grub error 18 I decided to create a separate boot partition, as suggested. However, when trying to use Gparted from the live CD to create some space ahead of /sda1, Gparted would run for a while and then crash. The crash message says:

"e2fsck crashed with SIGSEGV in qsort"
So now I am stuck, unable to boot from HDD and unable to create new partitions (the other partitions on the disk work fine with Gparted). Could all of this be due to corrupt /sda1 partition?

Since I am pretty new at this I would appreciate any help. Thanks in advance!

Ludmil

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu grub Edit question
Assignee:
No assignee Edit question
Last query:
2009-12-12
Last reply:
2009-12-12
Ludmil (ludmil) said : #2

Hi,

I ran fdisk and here's what it shows:

ubuntu@ubuntu:~$ sudo fdisk -lu

Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors

Units = sectors of 1 * 512 = 512 bytes

Disk identifier: 0x000adb2d

   Device Boot Start End Blocks Id System

/dev/sda1 * 63 799442594 399721266 83 Linux

/dev/sda2 953040060 976768064 11864002+ 5 Extended

/dev/sda5 953040123 976768064 11863971 82 Linux swap / Solaris

ubuntu@ubuntu:~$ sudo umount /dev/sda1

umount: /dev/sda1: not mounted

ubuntu@ubuntu:~$ sudo fsck -y /dev/sda1 /mnt

fsck 1.41.3 (12-Oct-2008)

e2fsck 1.41.3 (12-Oct-2008)

e2fsck 1.41.3 (12-Oct-2008)

fsck.ext2: Is a directory while trying to open /mnt

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it 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 alternate superblock:

    e2fsck -b 8193 <device>

/dev/sda1: Attempt to read block from filesystem resulted in short read while reading block 59507202

/dev/sda1: Attempt to read block from filesystem resulted in short read reading journal superblock

fsck.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /dev/sda1

ubuntu@ubuntu:~$ nautilus mnt &

[1] 7827

ubuntu@ubuntu:~$

I still don't know what to do. I already checked the post http://users.bigpond.net.au/hermanzone/p15.htm#18 and that's how I got stuck with Gparted while trying to create a separate boot partition.

Ludmil

Yep sounds like your data needs fscking. Boot to live cd and check the partitions. There are errors on the data

use:

sudo fsck -a /dev/sda1

This will automatically fix stuff. When it finishes, reboot and remove the CD and see if it boots ok.

Ludmil (ludmil) said : #4

Hi,

I ran fsck -a and here's what happens:

ubuntu@ubuntu:~$ sudo fsck -a /dev/sda1

fsck 1.41.3 (12-Oct-2008)

/dev/sda1: Attempt to read block from filesystem resulted in short read while reading block 59507202

/dev/sda1: Attempt to read block from filesystem resulted in short read reading journal superblock

fsck.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /dev/sda1

Now if I try to boot from the Hard drive I get a message "Operating system not found". More ominously the BIOS does not recognize the hard disk drive any more!

Best regards

Ludmil

If the BIOS doesnt see the drive then its a hardware issue. Check the connectors are in good (Power OFF the system before playing around)

Sounds like the IDE has failed in some way to me, if all cables are connected then the drive has probably died

Can you help with this problem?

Provide an answer of your own, or ask Ludmil for more information if necessary.

To post a message you must log in.