[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

grub2 can't see my linux kernel file

From: j t
Subject: grub2 can't see my linux kernel file
Date: Fri, 8 Jan 2010 23:21:09 +0000

Hi all.

I'm running gnu grub version 1.97.1 on my Thinkpad X31 with a 40GB
hard drive. I've installed the bootloader into the master boot record,
and the bootloader starts OK, but it can't see my linux kernel .

linux (hd0,6)/boot/vmlinuz-2.6.26-2-686 root=/dev/hda6 ro
error: out of disk

Interesingly, tab completion works OK until I reach:
linux (hd0,6)/boot/
and then an extra tab produces no output (but I am certain that my
kernel is in that directory)

In case it helps, here's the info on the drive and partition table:

# hdparm -i /dev/hda


 Model=HITACHI_DK23EA-40B, FwRev=00K3A0B6, SerialNo=KJ2973
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=72008693
 IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-5 T13 1321D revision 3:  ATA/ATAPI-2,3,4,5
 * signifies the current active mode

# fdisk -l /dev/hda

Disk /dev/hda: 40.0 GB, 40007761920 bytes
240 heads, 63 sectors/track, 5168 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Disk identifier: 0x1f253ddf

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           4       30208+  83  Linux
/dev/hda2   *           5        1500    11309760    7  HPFS/NTFS
/dev/hda3            1501        1565      491400   82  Linux swap / Solaris
/dev/hda4            1566        5168    27238680    5  Extended
/dev/hda5            1566        3547    14983888+  83  Linux
/dev/hda6            3548        5168    12254728+  83  Linux

Is this a problem with the bios not being able to reach into that
particular directory because it's beyond some limit? If so, is there
any way that I can prove this for certain? (the drive is only 40GB,
but the latest bios is dated 2005) Also, does it matter if fdisk and
hdparm show different cylinder/head/sector values?

Thank you for your help, Jaime.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]