Bug 116739 - No data written to /boot/efi?
Summary: No data written to /boot/efi?
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 2
Hardware: IA64 All
: P5 - None : Critical
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 11:47 UTC by Holger Sickenberg
Modified: 2005-10-26 07:32 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
elilo.conf (570 bytes, text/plain)
2005-09-14 14:41 UTC, Holger Sickenberg
Details
YaST2.tgz (173.50 KB, application/x-gzip)
2005-09-14 14:42 UTC, Holger Sickenberg
Details
YaST2.tgz (216.98 KB, application/x-gtar)
2005-09-14 14:45 UTC, Holger Sickenberg
Details
dcon's YaST2 logs (168.69 KB, application/x-gzip)
2005-09-15 05:33 UTC, Dennis Conrad
Details
dcon's hwinfo (90.57 KB, text/plain)
2005-09-15 05:33 UTC, Dennis Conrad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Sickenberg 2005-09-13 11:47:41 UTC
I choosed a "/" and an extra "/boot/efi" partition. After reboot I recognized
that there was not data written to "/boot/efi".

-> Booting failed
Comment 1 Raymund Will 2005-09-13 15:52:35 UTC
Holgi, would you mind attaching '/etc/elilo.conf' (and
maybe the usual YaST log-files)?

Jiri, would it be possible, that only 'efibootmgr' is called
by the new bootloader-code?
(Provided the conf-file is OK, this looks like '/sbin/elilo'
isn't run at all...)
Comment 2 Raymund Will 2005-09-14 09:37:09 UTC
Later today I'll try this myself, but I would appreciate, if you
could speed up things in providing what you have, Holgi.
(This is assuming, that Jiri has time to fix it... ;)
Comment 4 Holger Sickenberg 2005-09-14 14:41:24 UTC
Created attachment 49911 [details]
elilo.conf
Comment 5 Holger Sickenberg 2005-09-14 14:42:42 UTC
Created attachment 49912 [details]
YaST2.tgz
Comment 6 Holger Sickenberg 2005-09-14 14:43:06 UTC
OK, needed info is now attached
Comment 7 Holger Sickenberg 2005-09-14 14:45:45 UTC
Created attachment 49914 [details]
YaST2.tgz
Comment 8 Dennis Conrad 2005-09-14 15:08:53 UTC
Same on my test machine.  Will attach logs etc. tomorrow.
Comment 9 Raymund Will 2005-09-14 15:20:07 UTC
Well, at least the necessary directory 'efi/SuSE' in '/boot/efi'
is *not* created!  Therefore the current version of '/sbin/elilo'
fails to detect the where to place the files...
Comment 10 Dennis Conrad 2005-09-15 05:18:51 UTC
As SLES8 was installed previously on my machine (and YaST2 crashed when I tried
to create a new fat partition) I already had and still have an untouched boot
partition:

fs0:\> ls efi
Directory of: fs0:\efi

  06/06/05  02:11p <DIR>            512  .
  06/06/05  02:11p <DIR>              0  ..
  06/06/05  02:40p <DIR>            512  SuSE
          0 File(s)           0 bytes
          3 Dir(s)


fs0:\> ls efi\SuSE
Directory of: fs0:\efi\SuSE

  06/06/05  02:11p <DIR>            512  .
  06/06/05  02:11p <DIR>            512  ..
  10/31/03  02:17a              326,144  elilo.efi
  06/06/05  02:28p                  329  elilo.conf
          2 File(s)     326,473 bytes
          2 Dir(s)


fs0:\>

I will attach installation logs and hwinfo from my machine in a second.
Comment 11 Dennis Conrad 2005-09-15 05:33:36 UTC
Created attachment 49985 [details]
dcon's YaST2 logs
Comment 12 Dennis Conrad 2005-09-15 05:33:56 UTC
Created attachment 49986 [details]
dcon's hwinfo
Comment 13 Dennis Conrad 2005-09-15 05:41:09 UTC
Update:

I chroot'ed into the installed system and let YaST2's bootlader module propose a
new configuration and install it.  The system boots nowm so it's not a generic
YaST2 problem.
Comment 14 Gerald Pfeifer 2005-10-03 19:45:58 UTC
Jiri, what's the status of this?  
Comment 17 Raymund Will 2005-10-11 11:04:05 UTC
FWIW, this sequence of commands
  chroot /mnt
  mount /boot/efi
  mkdir -p /boot/efi/efi/SuSE
  /sbin/elilo
  umount /boot/efi
  exit
with "stopped" reboot-countdown fixed it for me.

Actually I've made that directory during package installation
hoping, that 'elilo' would eventually be called and thus allow
an easy work-around.  Unfortunately it's not!