Bug 750228
| Summary: | F16 RC2 efidisk.img doesn't boot on ThinkPad T520, older one works | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> |
| Component: | lorax | Assignee: | Martin Gracik <mgracik> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | anaconda-maint-list, awilliam, bcl, dmach, mads, next.little.owl, robatino, satellitgo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-03 17:02:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 713568 | ||
|
Description
Charles R. Anderson
2011-10-31 12:06:02 UTC
I've identified the working efidisk.img as being the one from TC2. Out of these images: -rw-rw-r--. 1 root 101737 140613632 Oct 20 12:47 efidisk-tc2.img -rw-rw-r--. 1 root 101737 140789760 Oct 27 14:05 efidisk-tc3.img -rw-rw-r--. 1 root 101737 140756992 Oct 29 02:53 efidisk-rc1.img -rw-rw-r--. 1 root 101737 140781568 Oct 29 22:21 efidisk-rc2.img ae9c490627be00b5c24a1a2d21d7f54a4a323cfaaa294b95a017bed3d929d493 efidisk-rc1.img 728d09398b6808eb7fe0adbceae20be3b793946f1ec310433139039184ce7392 efidisk-rc2.img 1aaf74fa23ac748a586cd28f8d0e09d9f5bbe59981aa553550cafda269f270eb efidisk-tc2.img fe3e88a5155f99963a6ffad657c67abbefc34379c353bc9dc838610ac8e00466 efidisk-tc3.img RC1 and TC2 have the "mkdosfs" signature: # grep mkdos efidisk-* Binary file efidisk-rc1.img matches Binary file efidisk-tc2.img matches Confirmed that the RC1 image also works fine. So it seems that efidisk.img works only if it has the "mkdosfs" signature in it. TC2 & RC1 work, TC3 & RC2 fail. The last version of lorax is from October 17, and nothing has changed since then, so it's strange that rc1 which is newer that tc3 works, but rc2 doesn't. Perhaps something different in the environment that is running lorax then? Where can one find the logs of the compose that was done for each release? Discussed at 2011-10-31 blocker review meeting. Accepted as a blocker per criterion "Where platform support exists, all dedicated installer images (except efidisk.img, which offers no options) must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout" . Will talk to releng and try and figure out what they did differently in the working/broken composes. We will need an RC3 for one other blocker, so will fix this at the same time. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Well, we're a bit confused about this. Here's the generation log from RC1: http://fpaste.org/wJRS/ and RC2: http://fpaste.org/hDjy/ as you can see, there's almost no difference... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers How does efiboot.img relate to efidisk.img? I wonder when to use one vs. the other. But this bug is about efiDISK.img, so the above fpastes don't help, unless efiboot.img somehow contributes to the contents of efidisk.img. yeah, we just noticed that. hold a sec. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers We've determined that the efidisk.img is almost entirely zeros (140MB of zeros) after the partition table. Something is going wrong when lorax copies the efiboot.img contents into the partition on the newly created efidisk.img, but only sometimes.
def create_efidisk(self, efiboot):
efidisk = joinpaths(self.workdir, "efidisk.img")
if os.path.isfile(efidisk):
os.unlink(efidisk)
...
with open(efiboot, "rb") as f_from:
with open("{0}p1".format(dmdev), "wb") as f_to:
efidata = f_from.read(1024)
while efidata:
f_to.write(efidata)
efidata = f_from.read(1024)
That was /usr/lib/python2.7/site-packages/pylorax/__init__.py As a workaround, I was successful in using: livecd-iso-to-disk --efi --format --reset-mbr boot.iso /dev/sdX to install RC2 in EFI mode on my ThinkPad T520. Charles: You are lucky. $ sudo livecd-iso-to-disk --efi --format --reset-mbr boot.iso /dev/sdb Verifying image... /home/vamo/Downloads/boot.iso: b5c9eb0f10996d3e0cb97e9e776c3d43 Fragment sums: 11466c6aa9c7457a1fb7ed2a4a48ea7cd25ad56dfa4bd384d9177555bc63 Fragment count: 20 Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdb!!! Press Enter to continue or ctrl-c to abort Waiting for devices to settle... mkdosfs 3.0.9 (31 Jan 2010) 1+0 records in 1+0 records out 16 bytes (16 B) copied, 7.4732e-05 s, 214 kB/s /home/vamo/Downloads/boot.iso uses initrd.img w/o install.img ERROR: This live image does not support EFI booting Cleaning up to exit... [root@adam images]# livecd-iso-to-disk --format --reset-mbr --efi Fedora-16-x86_64-netinst.iso /dev/sdd Verifying image... /media/Sea500/images/Fedora-16-x86_64-netinst.iso: b5c9eb0f10996d3e0cb97e9e776c3d43 Fragment sums: 11466c6aa9c7457a1fb7ed2a4a48ea7cd25ad56dfa4bd384d9177555bc63 Fragment count: 20 Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdd!!! Press Enter to continue or ctrl-c to abort 2 bytes were erased at offset 0x438 (ext2) they were: 53 ef Waiting for devices to settle... mkdosfs 3.0.11 (24 Dec 2010) /media/Sea500/images/Fedora-16-x86_64-netinst.iso uses initrd.img w/o install.img Copying DVD image to target device. Updating boot config file Installing boot loader Target device is now set up with a Live image! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers fpasting the logs is not a good idea, they are already expired now, so I can't take a look at them. Can you please attach them? Also the kickstart file with which the composes are made would help. Using F14-i686 livecd-tools, I can create bootable USB *only* if I make it from LiveCD. However, booting from such USB fails (Lenovo Ideapad S205). See: https://bugzilla.redhat.com/show_bug.cgi?id=748272#c28 (In reply to comment #15) > Using F14-i686 livecd-tools, I can create bootable USB *only* if I make it from > LiveCD. However, booting from such USB fails (Lenovo Ideapad S205). You can't expect f14 livecd-tools to be able to create f16 live images. That would require backporting of all new development. So the user, having F14, basically can not create a bootable image to update the system to F16? Does anybody verified, that it works on F15? AFAIK dd should work: http://mjg59.dreamwidth.org/4957.html http://www.zytor.com/pipermail/syslinux-commits/2011-August/001451.html http://markmail.org/message/kvykxy3hx6brlvqw https://www.redhat.com/archives/anaconda-devel-list/2011-August/msg00352.html But it seems like there is evidence that Adam is right that it doesn't ... The F16 livecd-iso-to-disk script is also on the F16 LiveCD image, so if you can loopback mount that, you can get the script to use on an older Fedora release (I didn't test it though). LiveOS/livecd-iso-to-disk Mads Kiilerich: dd works if it is a hybrid image, which is case of all F16 images. It could boot from such USB, but not in *EFI mode*. https://bugzilla.redhat.com/show_bug.cgi?id=748272#c24 Charles R. Anderson: Thanks, I will try it. Can you put the Lenovo BIOS setting to "UEFI-Only" i.e. no Legacy Boot? That might be necessary in order to boot a hybrid image in EFI-mode. I'll be testing that shortly. Charles R. Anderson: No, it would be the first thing I would do. The new Lenovo Ideapad S205 doesn't have a legacy compatible mode, only UEFI is supported (Phoenix SecureCore Tiano). The older Lenovo ThinkPad X120e has it. Charles R. Anderson: regarding the Comment 19 - the loopback mount and the new livecd-iso-to-disk fail, because the F14's parted doesn't support option "legacy_boot on". $ sudo ./livecd-iso-to-disk --format --reset-mbr --efi ../../Fedora-16-x86_64-netinst.iso /dev/sdb Verifying image... ./livecd-iso-to-disk: line 799: checkisomd5: command not found Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdb!!! Press Enter to continue or ctrl-c to abort wipefs: WARNING: /dev/sdb: appears to contain 'gpt' partition table Waiting for devices to settle... mkdosfs 3.0.9 (31 Jan 2010) parted: invalid token: legacy_boot (In reply to comment #12) > /home/vamo/Downloads/boot.iso uses initrd.img w/o install.img > ERROR: This live image does not support EFI booting > Cleaning up to exit... This means that the source image you are using doesn't have EFI support on it. There were some problems with earlier F16 TC's missing EFI due to the change to grub2 for harddrive installs. Try a newer image and make sure it has the /EFI/ directory on it. Also, older livecd-iso-to-disk versions *should* work to make newer media. If it doesn't, file a bug against livecd-tools with the image you used and the livecd-iso-to-disk version you are using and I'll fix it. (In reply to comment #23) > Charles R. Anderson: regarding the Comment 19 - the loopback mount and the new > livecd-iso-to-disk fail, because the F14's parted doesn't support option > "legacy_boot on". The version of parted that supports this is still in testing, if you could grab it, give it a try and leave karma for it in koji I would appreciate it. Brian C. Lane, you say:
"This means that the source image you are using doesn't have EFI support on it."
It was the F14's livecd-iso-to-disk; I use F16 RC2, the same as Adam W., see the checksum.
I will try the new parted, but not sure if if it is everything - the script uses the host's syslinux:
resetMBR() {
...
if [ -f /usr/lib/syslinux/gptmbr.bin ]; then
cat /usr/lib/syslinux/gptmbr.bin > $device
...
In F14 might be too old ... I will see.
RC3's efidisk.img worked in testing for me, anyone else? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Brian C. Lane: parted was patched in F15, not in F14. RC3?! RC3 dd if=efidisk.img of=/dev/sdX works for me if I put BIOS setup into UEFI-only boot mode. dd if=Fedora-16-x86_64-netinst.iso of=/dev/sdX doesn't work in EFI-mode for me, despite mjg59's cool hacks. I tried UEFI-only mode in the BIOS setup, and it just fails to boot at all. If I switch to Legacy-only mode in the BIOS setup, it boots fine but in BIOS-mode with syslinux, of course. An install done that way will end up with a MBR partition table due to the Lenovo blacklist that was implemented in anaconda. So it is good to keep efidisk.img around for Lenovo systems, at least. Please don't deprecate it unless a fix is found for EFI on Lenovo. Of course, we also have the less convenient workaround of using livecd-iso-to-disk --efi --format --reset-mbr Fedora-16-x86_64-netinst.iso /dev/sdX as well. That works to boot the Lenovo in EFI mode. I installed Fedora 14, enabled updates-testing, yum update, and then: yum install livecd-tools livecd-iso-to-disk --efi --format --reset-mbr Fedora-16-x86_64-netinst.iso /dev/sdX (using the livecd-iso-to-disk script from the Fedora 14 install, NOT from 16) The result boots in EFI mode on my Lenovo ThinkPad T520. So it looks like we have covered lots of ways to workaround the issues. cra: it's not really a 'workaround'. the correct way to write an EFI-bootable USB stick in Fedora is to use livecd-iso-to-disk --efi . dd is not recommended for doing it. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Discussed at 2011-11-01 emergency blocker review meeting. dgilmore is fairly sure he knows how to ensure valid efidisk.img gets produced now; RC3's was okay, and RC4's should be too. Leaving open just so we remember to check RC4. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers http://tflink.fedorapeople.org/iso/20111101_preRc4.x64.boot.iso http://tflink.fedorapeople.org/iso/20111101_preRc4.x64.boot.iso.sha256 efidisk.img looks fine, and boots fine to anaconda on ThinkPad T520, didn't do a full install test. (In reply to comment #31) > I installed Fedora 14, enabled updates-testing, yum update, and then: > > yum install livecd-tools > livecd-iso-to-disk --efi --format --reset-mbr Fedora-16-x86_64-netinst.iso > /dev/sdX > > (using the livecd-iso-to-disk script from the Fedora 14 install, NOT from 16) > > The result boots in EFI mode on my Lenovo ThinkPad T520. So it looks like we > have covered lots of ways to workaround the issues. It doesn't work on F14 i686, I am still getting error (Comment 12): ERROR: This live image does not support EFI booting I modified livecd-iso-to-disk in the place, where it detects if it is an EFI disk: if [ -n "$efi" -a ! -d $CDMNT/EFI/boot ]; then # debug begin echo ------------------ grep $CDMNT /etc/mtab echo ------------------ ls -al $CDMNT echo ------------------ if [ -d $CDMNT/EFI ]; then ls -al $CDMNT/EFI/ fi echo ------------------ # debug end echo "ERROR: This live image does not support EFI booting" exitclean fi And I got the following result: ----------------- /home/vamo/not_backupped/fedora-16-RC3/Fedora-16-x86_64-netinst.iso /media/cdtmp.RYOkuX iso9660 ro,loop=/dev/loop0 0 0 ------------------ total 12 dr-xr-xr-x. 5 root root 2048 Nov 1 03:54 . drwxr-xr-x. 4 root root 4096 Nov 1 23:05 .. dr-xr-xr-x. 3 root root 2048 Nov 1 03:54 EFI drwxrwsr-x. 3 root 101737 2048 Nov 1 03:54 images drwxrwsr-x. 2 root 101737 2048 Nov 1 03:54 isolinux ------------------ total 6 dr-xr-xr-x. 3 root root 2048 Nov 1 03:54 . dr-xr-xr-x. 5 root root 2048 Nov 1 03:54 .. drwxrwsr-x. 2 root 101737 2048 Nov 1 03:54 BOOT ------------------ The problem is, that the script tests [ ... -d $CDMNT/EFI/boot ], but the mounted image contains /EFI/BOOT My kernel is "uname -a" is: Linux amulet 2.6.35.14-100.fc14.i686 #1 SMP Fri Oct 21 19:14:19 UTC 2011 i686 i686 i386 GNU/Linux I am going to report it as a bug. did you use the latest f14 updates, including updates-testing? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Václav, please update livecd-tools to the version (14.5) from updates-testing and leave feedback here: https://admin.fedoraproject.org/updates/FEDORA-2011-13515 The problem has been fixed, but since there isn't enough karma it hasn't been pushed to stable yet. Downloaded, tested, it works. It is for the first time, I am able to boot in EFI mode without efidisk.img. I have already filled the bug report, sorry, the next time I will try updates-testing first. this is fixed in RC5 (was fixed in RC3 and RC4 too) and we're almost certainly going to ship that, so closing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |