Page 5 of 5 FirstFirst ... 345
Results 41 to 50 of 50

Thread: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

  1. #41

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Can we try non-secure boot, so if you let the system boot, see how it defaults (from the output of efibootmgr) to 0002, change the order to;
    Code:
    efibootmgr -o 0,1,2
    Reboot, does it start up ok and current == 0 for efibootmgr output?

    Then run the os-prober command again, does it se more/less etc?

    Also what release of Tumbleweed are you at...?
    Thanks again for getting back to me on this one. Happy to try this gambit out:, but I did un-check "secure boot" in the Yast Bootloader, and clicking "OK" is what lead to the "failure to find EFI directory error." Other issue, is right now it is "auto-booting" to TW, which is in sda, but the "0000" item seems to be from efibootmgr -v to be in sdb, which is one of the LEAP 42.2 options . . . I prefer to have the TW and/or rolling options that are in sda to be the "default" . . . and even though "0002" is shown as "current" that also seems to be showing an "secure-sdb" listing??

    The TW install is from June '17 possibly LEAP 42.3 and "uname -r" shows kernel is 4.14.1-1-default.

    Got a couple things to do this morning before I can run any console stuff and reboot and so forth; I'd like to keep the TW sda8?? partition has the default boot, and then yes, I'd like os-prober to find and be able to boot sda7--which now it lists in grub, but clicking on it goes to "panic window" . . . .

    Later on,

    n_s

  2. #42
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    23,238
    Blog Entries
    15

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Hi
    So, based on what you have learned, if it seems to be defaulting to 0000, then you can delete all the openSUSE efi entries and re-create to point at which disk and efi file...

    To delete an entry, start at the highest;
    Code:
    efibootmgr -b 2 -B 2
    efibootmgr -b 1 -B 1
    efibootmgr -b 0 -B 0
    
    efibootmgr -c -d /dev/sda -L "openSUSE sda" -l "\\EFI\\opensuse\\grubx64.efi"
    
    efibootmgr -c -d /dev/sda -L "openSUSE-secure sda" -l "\\EFI\\opensuse\\shim.efi"
    
    efibootmgr -c -d /dev/sdb -L "openSUSE sdb" -l "\\EFI\\openSUSE\\grubx64.efi"
    
    efibootmgr -c -d /dev/sdb -L "openSUSE-secure sdb" -l "\\EFI\\openSUSE\\shim.efi"
    
    efibootmgr -o 0,1,2,3
    
    efibootmgr -n 0
    The last one will ensure it does boot 'next' from 0000 entry.
    Last edited by malcolmlewis; 02-Dec-2017 at 09:37.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2 (x86_64) GNOME 3.20.2
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #43

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    So I copied/pasted your last list of items and dumped it into the console and it zipped through the list super quick, pasted it here to show what it did, then I'll shut down and try the reboot.

    Code:
    # os-prober
    /dev/sda7:openSUSE Tumbleweed:openSUSE:linux
    /dev/sdb2:Mac OS X:MacOSX:macosx
    /dev/sdb7:openSUSE Leap 42.2:openSUSE1:linux
    /dev/sdb8:openSUSE Leap 42.2:openSUSE2:linux
    192:/home/Zer0 # efibootmgr -b 2 -B 2
    BootCurrent: 0002
    BootOrder: 0000,0001,0080
    Boot0000* openSUSE sdb
    Boot0001* opensuse
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    192:/home/Zer0 # efibootmgr -b 1 -B 1
    BootCurrent: 0002
    BootOrder: 0000,0080
    Boot0000* openSUSE sdb
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    192:/home/Zer0 # efibootmgr -b 0 -B 0
    BootCurrent: 0002
    BootOrder: 0080
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -c -d /dev/sda -L "openSUSE sda" -l "\\EFI\\opensuse\\grubx64.efi"
    BootCurrent: 0002
    BootOrder: 0000,0080
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    Boot0000* openSUSE sda
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -c -d /dev/sda -L "openSUSE-secure sda" -l "\\EFI\\opensuse\\shim.efi"
    BootCurrent: 0002
    BootOrder: 0001,0000,0080
    Boot0000* openSUSE sda
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    Boot0001* openSUSE-secure sda
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -c -d /dev/sdb -L "openSUSE sdb" -l "\\EFI\\openSUSE\\grubx64.efi"
    BootCurrent: 0002
    BootOrder: 0002,0001,0000,0080
    Boot0000* openSUSE sda
    Boot0001* openSUSE-secure sda
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    Boot0002* openSUSE sdb
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -c -d /dev/sdb -L "openSUSE-secure sdb" -l "\\EFI\\openSUSE\\shim.efi"
    BootCurrent: 0002
    BootOrder: 0003,0002,0001,0000,0080
    Boot0000* openSUSE sda
    Boot0001* openSUSE-secure sda
    Boot0002* openSUSE sdb
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    Boot0003* openSUSE-secure sdb
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -o 0,1,2,3
    BootCurrent: 0002
    BootOrder: 0000,0001,0002,0003
    Boot0000* openSUSE sda
    Boot0001* openSUSE-secure sda
    Boot0002* openSUSE sdb
    Boot0003* openSUSE-secure sdb
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF* 
    192:/home/Zer0 # 
    192:/home/Zer0 # efibootmgr -n 0
    BootNext: 0000
    BootCurrent: 0002
    BootOrder: 0000,0001,0002,0003
    Boot0000* openSUSE sda
    Boot0001* openSUSE-secure sda
    Boot0002* openSUSE sdb
    Boot0003* openSUSE-secure sdb
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF*
    Finger's crossed. : - )))))

  4. #44

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    After running those changes, on cold boot GRUB shows one of the LEAP sdb choices as the top hit, then it shows a "TW" edition in the what we know to be empty "sda6" . . . clicking on that "failed." Shut down and tried the next TW listing, showing "sda7" and that boots to TW GNOME, but I think it's actually a Gecko rolling in that partition . . . and no "sda8" (where TW GNOME actually is) . . . . And, then, a couple OSX partitions, of which there are four . . . .

    Also, before I ran the suggested commands there was a recommended TW upgrade, which I did, new kernel, a few "grub2" packages, but at the end it showed the same "can't find EFI directory" . . . and then I ran these "erase and install" for grub, resulting in a a few listings of the various choices, but not all, and not in right partitions. After that I again ran "efibootmgr -v" and then "os-prober" . . . went to Yast and tried agaiin to click on "OK" to make the TW as the default item--with the same "failure" error.

    So, I am in TW GNOME via the GRUB menu . . . third item . . . but, we're back to it showing the "sda6" partition as housing TW, but, not only is it empty, but it goes into "rescue" mode . . . which of course does . . . not too much. Latest edition of the two commands:

    Code:
    # efibootmgr -v
    BootCurrent: 0000
    BootOrder: 0000,0001,0002,0003
    Boot0000* openSUSE sda    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensuse\grubx64.efi)
    Boot0001* openSUSE-secure sda    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot0002* openSUSE sdb    HD(1,GPT,36faabea-42fb-40d1-b88b-fb254febf542,0x28,0x64000)/File(\EFI\openSUSE\grubx64.efi)
    Boot0003* openSUSE-secure sdb    HD(1,GPT,36faabea-42fb-40d1-b88b-fb254febf542,0x28,0x64000)/File(\EFI\openSUSE\shim.efi)
    Boot0080* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(4,GPT,7420b4c3-007e-4b98-b566-eaa4ebf5e403,0x1d5a9f00,0x1d40da70)
    Boot0081* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(4,GPT,7420b4c3-007e-4b98-b566-eaa4ebf5e403,0x1d5a9f00,0x1d40da70)
    Boot0082*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(4,GPT,7420b4c3-007e-4b98-b566-eaa4ebf5e403,0x1d5a9f00,0x1d40da70)
    BootFFFF*     MemoryMapped(11,0xffd50000,0xfffdffff)/FvFile(2b0585eb-d8b8-49a9-8b8c-e21b01aef2b7)C.D...
    192:/home/Ze # os-prober
    /dev/sda7:openSUSE Tumbleweed:openSUSE:linux
    /dev/sdb2:Mac OS X:MacOSX:macosx
    /dev/sdb7:openSUSE Leap 42.2:openSUSE1:linux
    /dev/sdb8:openSUSE Leap 42.2:openSUSE2:linux

  5. #45

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Ran through a few restarts and trying to tab down into different Grub listed options, and it is getting me to the two LEAP options in sdb, and interestingly it is now showing the sda EFI partition as the "bootloader" for the sdb options. Unfortunately now in TW my GParted app is crashing on launch, so I can't check the various partition and/or EFI bootloader . . . . But, nothing is showing the Gecko MATE "rolling" install on what is actually "sda7" . . . and which is what Grub shows as TW Gnome, rather than sda8 where it actually is.

    Don't know if you have any more tricks up your sleeve on this one, but I'm considering going back to my olde-fashioned "nuke n pave" method as the way to get grub set up again, as well as to get the Gecko partition . . . it's just time consuming getting the rolling system back to where it is now, from the July date, etc. But, since it isn't showing up in grub or SuperGrub2 . . . seems like starting "fresh" is the next step??

    n_s

  6. #46
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    23,238
    Blog Entries
    15

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Hi
    Well, that may be the case, if you want more than two openSUSE releases then you could create another efi partition or use two and do some tweaking with folder names since it uses opensuse for the folder name.... I've run openSUSE, SLED, SLES an winX on one esp since they all use unique folder names.....

    So what is your final end game, some osX, TW and Leap?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2 (x86_64) GNOME 3.20.2
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #47

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Final end game seems to be fleeting . . . but yep, The LEAP GNOME & Gecko on sdb and the TW GNOME & Gecko Rolling on sda . . . and then a couple OSX versions on both HDs . . . .

    Got the Gecko Rolling on sda7 erased via DU in OSX, then went to try to re-install it using a USB flash of the system from July, and since I already used it to do the prior install I know that it did work then, but, something seems to have now been corrupted and the MATE menu doesn't load, and neither does the calamares installer . . . . Finally got to a terminal and tried that to "launch" it . . . which brings a string of data and then to a "segmentation fault" . . . no launch. Same with GParted via the live session . . . can log in, FF launches, LO writer launches . . . couple other things . . . just not the installer . . . or GParted.

    Can't win for losin' on this one . . . good news is that on reboot Grub opens, shows still the "non-existent" "sda6" TW and "sda7" TW (which is in 8 as I just had just erased sda7) . . . and, a moments hesitation in the "plymouth splash" and we're back in TW . . . !!!!

    Have to carry this one to another day or week . . . but, from previous times when the OSX install crushes the grub links, a fresh install of something linux with the "bootloader" pointing to the efi partition should repair all the listings . . . . From the times that I've been able to "nano" the grub.cfg file in the past, OSX for some "unknown" reason really screws with the various settings in the grub file or somewhere else so that the grub file gets "corrupted" . . . .

    Don't know if that is in play on this thread or not . . . but it keeps finding systems that aren't there and so forth . . . .

    I'll post back if & when I've gotten to some new plateau . . . thanks for walking along with me . . . very kind of you. : - )

    n_s

  8. #48
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    23,238
    Blog Entries
    15

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Hi
    You could try adding those bootx64.efi files in EFI/boot on sda and sdb as new entries and see what they fire up...

    The problem is maintenance on an update (user nrickert runs multiple releases and changes folder names) where it want to write to.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2 (x86_64) GNOME 3.20.2
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #49

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Quote Originally Posted by malcolmlewis View Post
    Hi
    You could try adding those bootx64.efi files in EFI/boot on sda and sdb as new entries and see what they fire up...

    The problem is maintenance on an update (user nrickert runs multiple releases and changes folder names) where it want to write to.
    Well, I might get back to you about the exact commands on how to do that, if this fresh install method fails then I will want to know . . . the details . . . .

    n_s

  10. #50

    Default Re: OSX install breaks connection to grub on EFI partition--TW rescue doesn't rescue??

    Latest update: So I got it done . . . the hard way . . . as I've done most of what I've done in life . . . 2.25 hours of downloading and processor time to retrieve and install the 1505 packages needed to bring Gecko Rolling up to date from "July" and that was it . . . . On restart Grub picked up the two OpenSUSE editions in sda . . . and perhaps one in sdb and that is "over" . . . . I'm mainly using sda now and sdb is essentially "back up" disk, so if I need to get into one of the LEAP partitions I know that SuperGrub2 will "find" them, it couldn't find sda . . . .

    It's "OK" for now, until the next OSX upgrade perhaps . . . .

    Thanks to MalcolmLewis for offering his assistance, maybe at some point I'll have the time to go back and study the posts for the kb of it, etc. Now it was just triage to get the sda units boot-able . . . haven't had the chance to try to see if Yast bootloader will "find the EFI partition" now or whether that aspect is "broken." Obviously there are at least 4 editions of Yast spread across the two HDs and perhaps are "in conflict" with each other?? or having themselves set as "default"??



    n_s

Page 5 of 5 FirstFirst ... 345

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •