BUG in GRUB
- From: Sergey <mafia_rgd@xxxxxxx>
- Date: Sat, 10 Dec 2005 18:26:53 +0500
This is the output of my commands when run from terminal:
---------------------------------------------------
GNU GRUB version 0.95 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> root (hd0,4)
Filesystem type is reiserfs, partition type 0x83
grub> kernel /boot/vmlinuz-2.6.11-1.1369_FC4
[Linux-bzImage, setup=0x1e00, size=0x18e473]
grub> initrd /boot/initrd-2.6.11-1.1369_FC4.img
Possible files are: initrd-2.6.11-1.1369_FC4.img-2
initrd-2.6.11-1.1369_FC4.img-3 initrd-2.6.11-1.1369_FC4.img-4
initrd-2.6.11-1.1369_FC4.img
grub> initrd /boot/initrd-2.6.11-1.1369_FC4.img
[Linux-initrd @ 0x2dc000, 0x113f39 bytes]
grub>
---------------------------------------------------
When the same commands are run in boot grub (when the grub has just been
loaded on system startup), the output is the following:
---------------------------------------------------
GNU GRUB version 0.95 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> root (hd0,4)
Filesystem type is reiserfs, partition type 0x83
grub> kernel /boot/vmlinuz-2.6.11-1.1369_FC4
[Linux-bzImage, setup=0x1e00, size=0x18e473]
grub> initrd /boot/initrd-2.6.11-1.1369_FC4.img
Possible files are: initrd-2.6.11-1.1369_FC4.img-2
initrd-2.6.11-1.1369_FC4.img-3 initrd-2.6.11-1.1369_FC4.img-4
initrd-2.6.11-1.1369_FC4.img
grub> initrd /boot/initrd-2.6.11-1.1369_FC4.img
grub>
---------------------------------------------------
You may notice after specifying "initrd" command the output is nothing. And
system fails to start - apparently because there's no initrd loaded and the
root fs can not be mounted. I have created 3 copies of initrd file
(absolutely the same copies). On boot when asking to load
initrd-2.6.11-1.1369_FC4.img-2 and initrd-2.6.11-1.1369_FC4.img-3 everything
is fine - grub responses: [Linux-initrd @ 0x2dc000, 0x113f39 bytes]. But on
initrd images initrd-2.6.11-1.1369_FC4.img and initrd-2.6.11-1.1369_FC4.img-4
grub tells nothing and system does not load. Why, why is that? How can I
debug grub on boot stage when nothing is loaded? But when grub is run from
terminal, it works just fine... All initrd files are *absolutelly* the same,
same size, no diff, same permissions, timestamps, etc. Inode number only
differ.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Prev by Date: Re: Copying IMAP spool from one server to another
- Next by Date: Re: Gui for configuring NTP
- Previous by thread: Copying IMAP spool from one server to another
- Next by thread: Device for External hard drive not created on bootup
- Index(es):
Relevant Pages
|
|
