Created attachment 337737 [details] df and fdisk -l Description of problem: After installing from F11-Beta-x86_64-Live.iso and update from menu, then it is not possible to boot. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. boot from cd F11-Beta-x86_64-Live.iso. All default settings. Except time and to only use disk sdc. 2. Finish innstall and then update 3. after update ( installing package) seamed finished, but did not completed. (was using cd ). Then shut down with power button. Actual results: boot into grub Expected results: boot into F11 Additional info: I have also tried to install from Fedora-10-Beta-x86_64-DVD.iso with similar result. In DVD install there was to warnings ( errors ) on something about not to able to figure out computer disks ( if remember right ) the other was some phyton ( ???) warning. I have also tried to install from live cd and reboot after installation and then after reboot was booted into grub. Disk sdc is 500.1 GB but it lokks like that F11 asumes it is about 250 GB.
Created attachment 337741 [details] png from nautilus
So what exactly is the problem here? If anaconda is giving you an error, please attach the complete error message to this bug so we can fix it. If your computer is failing to boot, please fully describe exactly what behavior you are seeing so we can determine what is wrong. Thanks.
Created attachment 337868 [details] resut off booting png
Same problem with Fedora-11-Snap1-x86_64-Live.iso.
Looks like the bootloader was not installed correctly. Once the install is complete but before you reboot, can you attach /tmp/anaconda.log, /tmp/program.log, and /tmp/syslog to this bug report? Thanks.
Created attachment 339553 [details] /tmp/anaconda.log
Created attachment 339555 [details] /tmp/program.log
Created attachment 339556 [details] syslog the only one I can find not in /tmp
Created attachment 339561 [details] /tmp/storage.log
Before installing F11 then I cleaned all partition off install disk sdc with gparted from F10.
I see two potential problems here. First, there's a reference to /mnt/sysimage/mnt/boot which seems wrong. Second, your /boot partition is on /dev/sdc1 and yet the grub command being run in the program.log indicates it's looking for (hd0,0)/grub.conf. That would most certainly explain why you're not getting anything more than the prompt. Martin - can you take a look here and see what might be going on? We could perhaps be constructing the wrong device.map in booty. Thanks.
Can I get the /mnt/sysimage/boot/grub/device.map file too please? And can you please try following command from the grub prompt you have after the instalation and give us the results? find /grub/stage1 Also, can you describe the drives you have? `cat /proc/partitions` will suffice (output of `fdisk -l drive` for all drives would be better though).
Ah sorry, nevermind about the fdisk, i overlooked one of the attachments.
And I see you have choosen to use only sdc, "boot from cd F11-Beta-x86_64-Live.iso. All default settings. Except time and to only use disk sdc." But you have /boot also on the sdb drive (and sda is bootable as well). Did you check that BIOS is using the correct drive to boot? Anyways, try the grub find command and make sure you are booting the correct (sdc) grub.
>But you have /boot also on the sdb drive (and sda is bootable as well). Did you >check that BIOS is using the correct drive to boot? Yes I am quite sure I was botting from scd in bios. I can install F11 on sdc if I use preformated partitions. ( I dont know how to write corectly boot secor on sdc. I boot into F11 form sdb ( F10)) >Anyways, try the grub find command and make sure you are booting the correct >(sdc) grub. I will try later to day.
I can not find i F11 after innstaqll /mnt/sysimage/boot/grub/device.map [liveuser@localhost ~]$ su - [root@localhost ~]# cd /mnt/sysimage/boot/grub -bash: cd: /mnt/sysimage/boot/grub: No such file or directory [root@localhost ~]# from gedit Could not find the file /mnt/sysimage/boot/grub/device.map. [root@localhost /]# cd /mnt/sysimage [root@localhost sysimage]# ll total 16 drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 boot drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 dev drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 proc drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 sys [root@localhost sysimage]# cd boot [root@localhost boot]# ll total 0 [root@localhost boot]# /mnt/sysimage/boot/grub/device.map [liveuser@localhost ~]$ su - [root@localhost ~]# cd /mnt/sysimage/boot/grub -bash: cd: /mnt/sysimage/boot/grub: No such file or directory [root@localhost ~]# F11 after innstall from gedit Could not find the file /mnt/sysimage/boot/grub/device.map. [root@localhost /]# cd /mnt/sysimage [root@localhost sysimage]# ll total 16 drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 boot drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 dev drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 proc drwxr-xr-x. 2 root root 4096 2009-04-16 17:30 sys [root@localhost sysimage]# cd boot [root@localhost boot]# ll total 0 [root@localhost boot]# [root@localhost boot]# pwd /mnt/sysimage/boot [root@localhost boot]# ll total 0 [root@localhost boot]#
Nevermind about the device.map, I found it together with the fdisk output. Just test the find command in grub prompt please.
After install F11 in grub find /grub/stage1 responce (hd2,0)
I believe this was caused by a problem with passing arguments to grub-install that ought to be fixed by 5e184c33a83eedc7dd71c5fc6a8e5586d6639d95. Please test the next preview release and if you are still experiencing problems, let us know. Thanks.
Tested with F11-Preview-x86_64-Live.iso Same problem. same as in #18
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Tested with Fedora-11-x86_64-Live.iso. Same problem. When all disks are unplugged and /dev/sdc: 500.1 GB, 500107862016 bytes is only hard disk ( then as sda) same problem trying to install to disk fdisk -l ( form F10 and disk reconnected ) Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000ea98f Device Boot Start End Blocks Id System /dev/sdc1 * 1 26 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdc2 26 60801 488179201 8e Linux LVM
Tested with Fedora-12-x86_64-DVD.iso rc1 same result.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.