[opensuse] uefi on the second disk
Hello, On a laptop I have windows (8, then 8.1, then 10) and several openSUSE (right now two leaps and one tw) this laptop have two disks, one of them being a 24Gb internal ssd. Being much faster than the HDD, my main Leap is on it. But I can't make the laptop read the efi partition of the ssd. Is it possible to trick Yast (or grub-install) to write the efi boot file on the hdd (/dev/sda1)? I tested all what I was thinking of, with no result, I even copied the /boot/efi/EFI files to the same folder in the hdd (named open), but the bios don't see them right now I boot from a grub menu from the other Leap install (on hdd) any idea? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon 01 Feb 2016 05:05:19 PM CST, jdd wrote:
Hello,
On a laptop I have windows (8, then 8.1, then 10) and several openSUSE (right now two leaps and one tw)
this laptop have two disks, one of them being a 24Gb internal ssd. Being much faster than the HDD, my main Leap is on it.
But I can't make the laptop read the efi partition of the ssd.
Is it possible to trick Yast (or grub-install) to write the efi boot file on the hdd (/dev/sda1)?
I tested all what I was thinking of, with no result, I even copied the /boot/efi/EFI files to the same folder in the hdd (named open), but the bios don't see them
right now I boot from a grub menu from the other Leap install (on hdd)
any idea? thanks jdd Hi No need to trick anything, just tell the nvram via efibootmgr where the efi file is.... assuming sda1 set to gpt, has a small partition < 500MB, formatted as fat and set to type ef00?
Just boot from a rescue USB (via the system boot menu), then run; efibootmgr -v Where does the existing openSUSE boot from, or even exist? By default efibootmgr uses sda, are your sure it's not sdb? This may be your issue if the ssd is sdb, you need to tell the nvram where it is as it defaults to sda. So assuming it is infact sda and no efi entry for openSUSE, then; efibootmgr -c -L "opensuse-secureboot" -l "\\EFI\\opensuse\shim.efi" If it's sdb, then you need to use -d /dev/sdb in the above as an option. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.25-default up 3 days 14:06, 6 users, load average: 0.33, 0.49, 0.51 CPU AMD A4-5150M @ 2.70GHz | GPU Radeon HD 8350G -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
01.02.2016 19:22, Malcolm пишет:
On Mon 01 Feb 2016 05:05:19 PM CST, jdd wrote:
Hello,
On a laptop I have windows (8, then 8.1, then 10) and several openSUSE (right now two leaps and one tw)
this laptop have two disks, one of them being a 24Gb internal ssd. Being much faster than the HDD, my main Leap is on it.
But I can't make the laptop read the efi partition of the ssd.
Is it possible to trick Yast (or grub-install) to write the efi boot file on the hdd (/dev/sda1)?
I tested all what I was thinking of, with no result, I even copied the /boot/efi/EFI files to the same folder in the hdd (named open), but the bios don't see them
right now I boot from a grub menu from the other Leap install (on hdd)
any idea? thanks jdd Hi No need to trick anything, just tell the nvram via efibootmgr where the efi file is.... assuming sda1 set to gpt, has a small partition < 500MB, formatted as fat and set to type ef00?
Just boot from a rescue USB (via the system boot menu), then run;
efibootmgr -v
Where does the existing openSUSE boot from, or even exist?
By default efibootmgr uses sda,
No, it does not. efibootmgr has no defaults and grub-install by default is using whatever is mounted as /boot/efi. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon 01 Feb 2016 08:12:47 PM CST, Andrei Borzenkov wrote:
01.02.2016 19:22, Malcolm пишет:
On Mon 01 Feb 2016 05:05:19 PM CST, jdd wrote:
Hello,
On a laptop I have windows (8, then 8.1, then 10) and several openSUSE (right now two leaps and one tw)
this laptop have two disks, one of them being a 24Gb internal ssd. Being much faster than the HDD, my main Leap is on it.
But I can't make the laptop read the efi partition of the ssd.
Is it possible to trick Yast (or grub-install) to write the efi boot file on the hdd (/dev/sda1)?
I tested all what I was thinking of, with no result, I even copied the /boot/efi/EFI files to the same folder in the hdd (named open), but the bios don't see them
right now I boot from a grub menu from the other Leap install (on hdd)
any idea? thanks jdd Hi No need to trick anything, just tell the nvram via efibootmgr where the efi file is.... assuming sda1 set to gpt, has a small partition < 500MB, formatted as fat and set to type ef00?
Just boot from a rescue USB (via the system boot menu), then run;
efibootmgr -v
Where does the existing openSUSE boot from, or even exist?
By default efibootmgr uses sda,
No, it does not. efibootmgr has no defaults and grub-install by default is using whatever is mounted as /boot/efi.
Hi I'm not referring to a mount point, or grub-install. My reference is to efibootmgr and the nvram entry which identifies the disk which has the /boot/efi partiton. I can have multiple disks, multiple /boot/efi partitions, I just need to add an entry for which one I wish to have available to boot from. In those cases I need to use the -d flag... -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.25-default up 3 days 16:38, 6 users, load average: 0.54, 0.37, 0.35 CPU AMD A4-5150M @ 2.70GHz | GPU Radeon HD 8350G -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 01/02/2016 18:12, Andrei Borzenkov a écrit :
No, it does not. efibootmgr has no defaults and grub-install by default is using whatever is mounted as /boot/efi.
no. efibootmgr have many defaults (simply looks at the man page), and by the way yast do not seems to use the mounted partition, I also tried that - or not exactly, see below. But I could fix the problem by two means. After a lot of tests, I finally could use efibootmgr efibootmgr do not look at all at the EFI folder if not instructed to do so. It only looks at the nvram variables of the uefi system. To be able to add an entry in the nvram, you have first to get yast to build the boot system, then copy it if necessary in a subfolder of /boot/efi/EFI in the wanted disk. then issue the command line as root (parenthesis are comments, do not write them) - all on the same line: efibootmgr -c (-c to "create") -p 1 (number of the EFI partition on the disk, beginning with 1, which is the default) -d /dev/sdb (default is sda, if you use sda better not write the option at all) -L "jdd" (name of the option in the efi menu) - l "\EFI\opensuse\grubx64.efi" opensuse is the name of the folder, it's a windows thing, so the backslash, the root of the system is the efi partition for us mounted on /boot/efi. As far as I know, this command just add the entry and return the new nvram list, after that you will find it in the efi boot menu and in the UEFI options. It's not necessary to mount anything for this command to work, nothing is verified at this moment, so why testing is so long, any test needs reboot... you can add several entries, with different syntax, for make testing easy. The relevant command for my config booted, but with no grub menu (may be because there is only one config on this disk) BUT. Making all this led me to understand what the UFI asked me to enter in the menu options "add en entry" of my asus s400c laptop. I had to enter a name (no need to quote), choose the disk (very obscure list of two elements, I think some sort of UUID), give a "path". This one was what I could understand after the efibootmgr syntax: the "EFI\opensuse\grubx64.efi" part. and this option gives the same result as the other. YaST yast is not always easy to manage, because it uses in the third tab (choosing the default menu entry) the previous osprober recult, and osprober is only executed after the config is validated, so you have to make a "blank run" to update the boot entry list (the one of the grub menu), before being able to choose one... a bit long, sorry jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
new test time, and I understand better how YaST works. first, for whatever unknown reason I had grub2 selected (and not grub2-efi) on this always efi secureboot computer... didn't help. then YaST write the boot files (*.efi) to /boot/efi and complain if nothing is mounted there (good). I didn't take the time to test all, not sure YaST can keep several versions there. You can manually, simply changing the folder name for anything you want and using efibootmgr not sure neither what YaST do if the opensuse folder already exist, keep or change? probably change. I could test all that moving all the opensuse folder (under EFI) to a backup place then making YaST write them again. I found here: https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_grub2_yas... than for YaST to write every bit of info about boor system, one have to force it, changing the bootloader in the menu to anything else (no need to validate, reloading the menu do the trick) then back to grub2-efi. Changing any other option *is not enough* I think there should be an option "reload" of "force writing", because this trick is specially naked. so far, so good thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
01.02.2016 19:05, jdd пишет:
Hello,
On a laptop I have windows (8, then 8.1, then 10) and several openSUSE (right now two leaps and one tw)
this laptop have two disks, one of them being a 24Gb internal ssd. Being much faster than the HDD, my main Leap is on it.
But I can't make the laptop read the efi partition of the ssd.
Is it possible to trick Yast (or grub-install) to write the efi boot file on the hdd (/dev/sda1)?
grub-install is using partition which is mounted as /boot/efi.
I tested all what I was thinking of, with no result, I even copied the /boot/efi/EFI files to the same folder in the hdd (named open), but the bios don't see them
It is not clear what this means. BIOS does not see filesystem? BIOS sees filesystem but does not see files? They are not present in firmware boot menu? In the latter case you simply need to re-run grub-install after fixing /boot/efi mount point. Otherwise more information is needed.
right now I boot from a grub menu from the other Leap install (on hdd)
any idea? thanks jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 01/02/2016 18:12, Andrei Borzenkov a écrit :
grub-install is using partition which is mounted as /boot/efi.
yes, I understand, but grub is not the problem With UEFI, there is no more boot flag and my uefi simply do not see the second disk may be there is a bug in YaST: I guess YaST is also updating the nvram?? or is it only at install time? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
01.02.2016 22:58, jdd пишет:
Le 01/02/2016 18:12, Andrei Borzenkov a écrit :
grub-install is using partition which is mounted as /boot/efi.
yes, I understand, but grub is not the problem With UEFI, there is no more boot flag and my uefi simply do not see the second disk
So mount ESP from the first disk. Where is the problem?
may be there is a bug in YaST: I guess YaST is also updating the nvram?? or is it only at install time?
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/02/2016 04:17, Andrei Borzenkov a écrit :
So mount ESP from the first disk. Where is the problem?
I did with no better result on yast. But there are many variables, so it may be I forgot something. Experimenting on this subject is very time consuming jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Maybe you should take a look with the rEFInd disk, it let you see exactly what uefi should (could) see. Maybe it gives a idea whats happening. http://sourceforge.net/projects/refind/files/0.10.2/refind-cd-0.10.2.zip/dow... Op 02-02-16 10:23, jdd schreef:
Le 02/02/2016 04:17, Andrei Borzenkov a écrit :
So mount ESP from the first disk. Where is the problem?
I did with no better result on yast. But there are many variables, so it may be I forgot something. Experimenting on this subject is very time consuming
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Hans de Faber -
jdd -
Malcolm