grub 0.96 bug

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

 



I'm delving into GRUB bughunting now.

GRUB 0.96 is apparently sensitive to the order in which "device xxx"
commands are entered.  Sounds horrid, aye...

Ie. typing:
grub> device (hd0) /dev/xxx
grub> device (hd0,5) /dev/yyy

Is a completely different thing to typing:
grub> device (hd0,5) /dev/yyy
grub> device (hd0) /dev/xxx

Reproducible: Always.

Here's an example.  (I added "grub_printf" to rawread to try and find
out why the OUTSIDE error happens, never mind the "raw reading"
messages.  Also added # comments.)

========================
GNU GRUB  version 0.96  (640K lower / 3072K upper memory)

# Tell GRUB about devices
grub> device (hd0) /dev/mapper/hpt37x_ehgjaggaf
grub> device (hd0,5) /dev/mapper/hpt37x_ehgjaggaf6

# Tell GRUB where to find it's files
grub> root (hd0,5)/boot
Attempt to open drive 0x80 (/dev/mapper/hpt37x_ehgjaggaf6)
- Raw reading from offset 0
Error 5: Partition table invalid or corrupt

# Refresh GRUB's memory on where device hd0 is.
# _Same_ command as first command entered (above).
grub> device (hd0) /dev/mapper/hpt37x_ehgjaggaf

# Notice the different error message!
grub> root (hd0,5)/boot
Attempt to open drive 0x80 (/dev/mapper/hpt37x_ehgjaggaf)
- Raw reading from offset 0
- Raw reading from offset 0
- Raw reading from offset 0
- Raw reading from offset 0
- Raw reading from offset 0
- Raw reading from offset 41961780
Error 18: Selected cylinder exceeds maximum supported by BIOS

grub>
========================


[Index of Archives]     [Linux RAID]     [Linux Device Mapper]     [Linux IDE]     [Linux SCSI]     [Kernel]     [Linux Books]     [Linux Admin]     [GFS]     [RPM]     [Yosemite Campgrounds]     [AMD 64]

  Powered by Linux