Bug 753672 - Installing Fedora 16 on second drive on laptop does not set up boot loader correctly
Summary: Installing Fedora 16 on second drive on laptop does not set up boot loader co...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-14 04:25 UTC by Richard Sharpe
Modified: 2011-12-06 15:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 15:15:57 UTC
Type: ---


Attachments (Terms of Use)
anaconda-ks.cfg (1.84 KB, application/octet-stream)
2011-11-14 05:24 UTC, Richard Sharpe
no flags Details
install.log (74.40 KB, application/octet-stream)
2011-11-14 05:25 UTC, Richard Sharpe
no flags Details
install.log.syslog (10.88 KB, application/octet-stream)
2011-11-14 05:26 UTC, Richard Sharpe
no flags Details
/tmp/program.log (34.00 KB, application/octet-stream)
2011-11-14 06:02 UTC, Richard Sharpe
no flags Details
/tmp/storage.log (116.02 KB, application/octet-stream)
2011-11-14 06:03 UTC, Richard Sharpe
no flags Details

Description Richard Sharpe 2011-11-14 04:25:11 UTC
I installed Fedora 16 on the second drive of my laptop. I chose a custom layout, but it included a partition for a BIOS target (or whatever). However, it does not boot, rather the laptop says "Installation System not found"

How reproducible: Very reproducible. Two installs, same result.


Steps to Reproduce:
1. Boot installation DVD.
2. Select custom partition layout but force second drive to have boot stuff
3. Let it finish and reboot
  
Actual results:

   Fails to boot with "Installation System not found" Also, cannot boot from 
   rescue mode. That is, if I select Troubleshooting and then "Boot from local 
   drive" I get the following as well:

   Boot failed: press a key to retry...

Expected results:

    Should boot without problems.

Comment 1 Chris Lumens 2011-11-14 05:01:41 UTC
Please include /tmp/program.log and /tmp/storage.log from the end of installation in this bug report.

Comment 2 Richard Sharpe 2011-11-14 05:23:47 UTC
Hmmm, those files do not seem to exist, but /root/anaconda-ks.cfg, /root/install.log, /root/install.log.syslog do exist, which I am attaching.

I will try the install again to see if I can get /tmp/program.log and /tmp/storage.log.

Comment 3 Richard Sharpe 2011-11-14 05:24:39 UTC
Created attachment 533429 [details]
anaconda-ks.cfg

Comment 4 Richard Sharpe 2011-11-14 05:25:21 UTC
Created attachment 533430 [details]
install.log

Comment 5 Richard Sharpe 2011-11-14 05:26:10 UTC
Created attachment 533431 [details]
install.log.syslog

Comment 6 Richard Sharpe 2011-11-14 05:27:31 UTC
There is an error at the end of the install.log:

grubby fatal error: unable to find a suitable template
grubby: doing this would leave no kernel entries. Not writing out new config.
*** FINISHED INSTALLING PACKAGES ***

Perhaps that is my problem.

Comment 7 Richard Sharpe 2011-11-14 05:47:16 UTC
I should point out that the drive I am trying to install on is a 512GB Crucial SSD. I don't expect that to be a problem, though.

Comment 8 Richard Sharpe 2011-11-14 06:00:23 UTC
Well, same result on this latest install.

No files in /tmp (/mnt/sysinstall/tmp) and it is not bootable.

Ahhh, OK, I found them in the real /tmp.

I will attach them.

Comment 9 Richard Sharpe 2011-11-14 06:02:20 UTC
Created attachment 533437 [details]
/tmp/program.log

Comment 10 Richard Sharpe 2011-11-14 06:03:36 UTC
Created attachment 533438 [details]
/tmp/storage.log

Comment 11 Richard Sharpe 2011-11-19 05:24:23 UTC
Hmmm, additional information. The same happens if I swap the two drives so that the SSD is drive 1 and the hard disk is drive 2.

This is getting frustrating.

Any recovery steps that I should try?

Comment 12 Richard Sharpe 2011-11-20 00:35:44 UTC
Well grub2-install /dev/sdb does not seem to fix things.

Comment 13 Vratislav Podzimek 2011-12-06 14:53:21 UTC
Sorry, but I don't understand whether you can boot into grub or cannot boot from the SDD at all.
If you can boot into grub, can you check the configuration of the items (by hiting 'e') in it's menu?

Comment 14 Richard Sharpe 2011-12-06 15:01:24 UTC
(In reply to comment #13)
> Sorry, but I don't understand whether you can boot into grub or cannot boot
> from the SDD at all.
> If you can boot into grub, can you check the configuration of the items (by
> hiting 'e') in it's menu?

The BIOS on the DELL XPS17 will not load even the primary boot sector from the SSD.

I should have updated this earlier. I now suspect that the issue is some poor interaction between the DELL XPS 17 BIOS and the SSD.

I will take the issue up with Dell soon.

In the meantime I used a spare 500GB drive I had laying around and it works fine, although as the first drive.

Comment 15 Vratislav Podzimek 2011-12-06 15:15:57 UTC
(In reply to comment #14)
> (In reply to comment #13)
> > Sorry, but I don't understand whether you can boot into grub or cannot boot
> > from the SDD at all.
> > If you can boot into grub, can you check the configuration of the items (by
> > hiting 'e') in it's menu?
> 
> The BIOS on the DELL XPS17 will not load even the primary boot sector from the
> SSD.
> 
> I should have updated this earlier. I now suspect that the issue is some poor
> interaction between the DELL XPS 17 BIOS and the SSD.
> 
> I will take the issue up with Dell soon.
> 
> In the meantime I used a spare 500GB drive I had laying around and it works
> fine, although as the first drive.

Thanks for the update, I'm closing this bug now. If you find out it's not a BIOS--SSD interaction issue, please reopen it.


Note You need to log in before you can comment on or make changes to this bug.