[opensuse-factory] Major boot/gub issue after disk swap
Hi list, today I decided to have a look at the new btrfs layout of Tumbleweed. To be on the safe side I removed the current SDD of my laptop and put an identical, empty one in, and then did a new install of the most recent TW (20180206). Only thing I changed from the default is increase the rootfs size to 80GiB, I just selected 'KDE/Plasma system' and installed. This went fine, I looked around the system, and then shut it down to put my old SDD back in. ¡IT DOESN'T BOOT ANYMORE! Immediately after the POST screens of the BIOS I get a message error: file '/boot/grub/x86_64-efi/normal.mod' not found Entering rescue mode... grub rescue> I checked BIOS, but didn't see obvious places where to change things (and have not changed anything) What did the install do? It must have changed something in the laptop BIOS, but what and where, and how can I revert it back to the old setting? Boot is UEFI, Secure Boot is disabled. Going to look at the two disks from a separate system now, but any guidance is highly welcome... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
maybe the nvram settings that you can change from efibootmgr? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
nicholas cunliffe wrote:
maybe the nvram settings that you can change from efibootmgr?
Ah, good tip - will look into that. What irritates me is that it looks for /boot/grub/..., whereas grub2 should be used. I assume the problem is my old EFI had an entry debian from an earlier testinstall. That one still is in place, looks like the new install did not touch it. Likely the ordering got messed up somehow, and it now tries to load the debian grub (which indeed was grub, not grub2). Guess I'll have to boot from the install stick and hope that one has everything in place for adjusting it to proper settings. Thanks for getting me on track! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
08.02.2018 20:00, Peter Suetterlin пишет:
Hi list,
today I decided to have a look at the new btrfs layout of Tumbleweed.
To be on the safe side I removed the current SDD of my laptop and put an identical, empty one in, and then did a new install of the most recent TW (20180206). Only thing I changed from the default is increase the rootfs size to 80GiB, I just selected 'KDE/Plasma system' and installed.
This went fine, I looked around the system, and then shut it down to put my old SDD back in.
¡IT DOESN'T BOOT ANYMORE!
Immediately after the POST screens of the BIOS I get a message error: file '/boot/grub/x86_64-efi/normal.mod' not found Entering rescue mode... grub rescue>
I checked BIOS, but didn't see obvious places where to change things (and have not changed anything)
What did the install do? It must have changed something in the laptop BIOS, but what and where, and how can I revert it back to the old setting?
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Can you provide "efibootmgr -v" output (from installation media e.g.). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
08.02.2018 20:33, Andrei Borzenkov пишет:
08.02.2018 20:00, Peter Suetterlin пишет:
Hi list,
today I decided to have a look at the new btrfs layout of Tumbleweed.
To be on the safe side I removed the current SDD of my laptop and put an identical, empty one in, and then did a new install of the most recent TW (20180206). Only thing I changed from the default is increase the rootfs size to 80GiB, I just selected 'KDE/Plasma system' and installed.
This went fine, I looked around the system, and then shut it down to put my old SDD back in.
¡IT DOESN'T BOOT ANYMORE!
Immediately after the POST screens of the BIOS I get a message error: file '/boot/grub/x86_64-efi/normal.mod' not found Entering rescue mode... grub rescue>
I checked BIOS, but didn't see obvious places where to change things (and have not changed anything)
What did the install do? It must have changed something in the laptop BIOS, but what and where, and how can I revert it back to the old setting?
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Can you provide "efibootmgr -v" output (from installation media e.g.).
Also ls -lR /boot/efi (assuming it is mounted as ESP) btrfs sub get-default /mount/point/for/SSD/root btrfs sub li /mount/point/for/SSD/root -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov wrote:
08.02.2018 20:33, Andrei Borzenkov пишет:
Can you provide "efibootmgr -v" output (from installation media e.g.).
Also
ls -lR /boot/efi (assuming it is mounted as ESP) btrfs sub get-default /mount/point/for/SSD/root btrfs sub li /mount/point/for/SSD/root
/boot/efi is not mounted, but efibootmgr -v shows the issue. I only have it on screen of the laptop, and won't type everything. Basic: Bootorder is 0001,0000, where 0000 is the old debian install entry, and 0001 is the (new) opensuse entry. But that one now has the entry pointing to the partition ID of the new disk, which isn't in the system. So it falls back to the debian entry. So I'll have to remove both entries, and set up the proper one for the old disk. Should be doable with some manual reading.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Suetterlin wrote:
Andrei Borzenkov wrote:
08.02.2018 20:33, Andrei Borzenkov пишет:
Can you provide "efibootmgr -v" output (from installation media e.g.).
Also
ls -lR /boot/efi (assuming it is mounted as ESP) btrfs sub get-default /mount/point/for/SSD/root btrfs sub li /mount/point/for/SSD/root
/boot/efi is not mounted, but efibootmgr -v shows the issue. I only have it on screen of the laptop, and won't type everything. Basic: Bootorder is 0001,0000, where 0000 is the old debian install entry, and 0001 is the (new) opensuse entry. But that one now has the entry pointing to the partition ID of the new disk, which isn't in the system. So it falls back to the debian entry.
So I'll have to remove both entries, and set up the proper one for the old disk. Should be doable with some manual reading....
Yes! I created a new entry, efibootmgr -c -b 2 -L opensuse -l \\EFI\\opensuse\\grubx64.efi (-d \dev\sda and -p 1 are default) The command automatically put this at the beginning of the bootorder. With that the system boots again :D THANK YOU ALL for saving my sleep tonight -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2018-02-08 19:43, Peter Suetterlin wrote:
Peter Suetterlin wrote:
Andrei Borzenkov wrote:
08.02.2018 20:33, Andrei Borzenkov пишет:
..
So I'll have to remove both entries, and set up the proper one for the old disk. Should be doable with some manual reading....
Yes!
I created a new entry,
efibootmgr -c -b 2 -L opensuse -l \\EFI\\opensuse\\grubx64.efi
(-d \dev\sda and -p 1 are default)
The command automatically put this at the beginning of the bootorder. With that the system boots again :D
THANK YOU ALL for saving my sleep tonight
What I wonder is if there is some way to repair the list from the "bios" itself, something like "scan disks and boot from..." :-? - -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp8sh8ACgkQja8UbcUWM1wlpwD+OvIzrdXFXcov11tTDnGkfp8N JMoar0Gi7O8UfQUAxtEA/iXHzS3SVnz3pGUhARhrgQVU7beDoTdSjvfCcpVJmX/k =Vc6D -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. wrote:
What I wonder is if there is some way to repair the list from the "bios" itself, something like "scan disks and boot from..." :-?
Yes, I also think there should, but I couldn't find one. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 8 Feb 2018 21:07:09 +0000
Peter Suetterlin
Carlos E. R. wrote:
What I wonder is if there is some way to repair the list from the "bios" itself, something like "scan disks and boot from..." :-?
Yes, I also think there should, but I couldn't find one.
Of course, every BIOS is different do such option will be manufacturer-specific. YMMV Thanks Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov wrote:
08.02.2018 20:00, Peter Suetterlin пишет:
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Can you provide "efibootmgr -v" output (from installation media e.g.).
Andrei, you surely know much more about the boot setup and dependencies: Thinking about the issue, it seems the installation has not touched the other entry for debian (although that disk/directory was not available), but it has deleted/overwritten the existing entry for opensuse. I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 8 Feb 2018 18:57:22 +0000
Peter Suetterlin
Andrei Borzenkov wrote:
08.02.2018 20:00, Peter Suetterlin пишет:
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Can you provide "efibootmgr -v" output (from installation media e.g.).
Andrei, you surely know much more about the boot setup and dependencies:
Thinking about the issue, it seems the installation has not touched the other entry for debian (although that disk/directory was not available), but it has deleted/overwritten the existing entry for opensuse.
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
I suppose it writes an entry for openSUSE so if there is a previous entry with the same name it is overwritten. Another thing to consider is that the installer does not see the other openSUSE installation because you removed the disk so it might look OK to remove the entry for known and missing openSUSE system. On the other hand it does not understand the Debian entry so it leaves it alone. Leaving unbound amount of garbage around will eventually lead to issues and cleaning up does sometimes cause issues as well. Nothing satisfies everybody. Thanks Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
08.02.2018 21:57, Peter Suetterlin пишет:
Andrei Borzenkov wrote:
08.02.2018 20:00, Peter Suetterlin пишет:
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Can you provide "efibootmgr -v" output (from installation media e.g.).
Andrei, you surely know much more about the boot setup and dependencies:
Thinking about the issue, it seems the installation has not touched the other entry for debian (although that disk/directory was not available), but it has deleted/overwritten the existing entry for opensuse.
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
Currently there is no provision for it. It will derive location on ESP and menu title from distributor name which defaults to openSUSE. You can go to bootloader settings on summary screen and change distributor name so that the first word is different, like openSUSE-test or similar. It is not so much a bug as missing feature. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov composed on 2018-02-09 06:54 (UTC+0300):
Peter Suetterlin composed:
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
Currently there is no provision for it. It will derive location on ESP and menu title from distributor name which defaults to openSUSE. You can go to bootloader settings on summary screen and change distributor name so that the first word is different, like openSUSE-test or similar.
Is there a corresponding location in YaST2 to do same in an existing installation? Where besides /etc/os-release and /boot/efi/EFI/ is the distributor name present, configured or specified - ID= in /etc/os-release perhaps?
It is not so much a bug as missing feature. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-02-09 05:24, Felix Miata wrote:
Andrei Borzenkov composed on 2018-02-09 06:54 (UTC+0300):
Peter Suetterlin composed:
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
Currently there is no provision for it. It will derive location on ESP and menu title from distributor name which defaults to openSUSE. You can go to bootloader settings on summary screen and change distributor name so that the first word is different, like openSUSE-test or similar.
Is there a corresponding location in YaST2 to do same in an existing installation?
Where besides /etc/os-release and /boot/efi/EFI/ is the distributor name present, configured or specified - ID= in /etc/os-release perhaps?
I think it is "GRUB_DISTRIBUTOR=" in /etc/default/grub
It is not so much a bug as missing feature.
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Andrei Borzenkov wrote:
Andrei, you surely know much more about the boot setup and dependencies:
Thinking about the issue, it seems the installation has not touched the other entry for debian (although that disk/directory was not available), but it has deleted/overwritten the existing entry for opensuse.
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
Currently there is no provision for it. It will derive location on ESP and menu title from distributor name which defaults to openSUSE. You can go to bootloader settings on summary screen and change distributor name so that the first word is different, like openSUSE-test or similar.
It should not depend on the name, as this is (only) a label. I had to specify the exact entry *number* to make changes. efibootmgr even has an option to remove double entries, which implies you can (easily?) create them. Just did that as a test: woodstock:~ # efibootmgr -v BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0004,0003,0002,0001,001A,001B,001C,0017,0018,0019,001D,0022 Boot0001* opensuse-secureboot HD(2,GPT,f8779391-5543-430b-9d17-ef59de3f598c,0xa000800,0xfa000)/File(\EFI\opensuse\shim.efi) Boot0002* opensuse HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\opensuse\grubx64.efi) Boot0003* debian HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\debian\grubx64.efi) Boot0004* debian HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\debian\grubx64.efi) .... In doubt I'd say it is preferable to have a user scratch his head which of the two 'opensuse' entries is the right one, than removing the second without asking... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On vendredi, 9 février 2018 10.38:38 h CET Peter Suetterlin wrote:
Andrei Borzenkov wrote:
Andrei, you surely know much more about the boot setup and dependencies:
Thinking about the issue, it seems the installation has not touched the other entry for debian (although that disk/directory was not available), but it has deleted/overwritten the existing entry for opensuse.
I wonder if that should be regarded as error? Am I only allowed one opensuse install per computer? Shouldn't the installer always create only new entries without touching any older ones?
Currently there is no provision for it. It will derive location on ESP and menu title from distributor name which defaults to openSUSE. You can go to bootloader settings on summary screen and change distributor name so that the first word is different, like openSUSE-test or similar.
It should not depend on the name, as this is (only) a label. I had to specify the exact entry *number* to make changes. efibootmgr even has an option to remove double entries, which implies you can (easily?) create them.
Just did that as a test: woodstock:~ # efibootmgr -v BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0004,0003,0002,0001,001A,001B,001C,0017,0018,0019,001D,0022 Boot0001* opensuse-secureboot HD(2,GPT,f8779391-5543-430b-9d17-ef59de3f598c,0xa000800,0xfa000)/File(\EFI\ opensuse\shim.efi) Boot0002* opensuse HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\ope nsuse\grubx64.efi) Boot0003* debian HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\deb ian\grubx64.efi) Boot0004* debian HD(1,GPT,2bfd8cb4-2c72-4fce-b8d9-3dea01dd9c75,0x800,0x100000)/File(\EFI\deb ian\grubx64.efi) ....
In doubt I'd say it is preferable to have a user scratch his head which of the two 'opensuse' entries is the right one, than removing the second without asking...
I guess You should be able to determine which by crossing information between blkid and efibootmgr blkid /dev/nvme0n1: PTUUID="08be79f4-879c-4830-ab8a-4f0472974f62" PTTYPE="gpt" /dev/nvme0n1p1: SEC_TYPE="msdos" UUID="55EE-42B2" TYPE="vfat" PARTLABEL="primary" PARTUUID="cfe806b5-42f1-4acb-b521-38cdcb4801e0" efibootmgr -v BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0004,0005 Boot0000* opensuse HD(2,GPT,84209ec8-9191-4536-a2cc-f6dd1695458c, 0x1000,0x41800)/File(\EFI\opensuse\grubx64.efi) Boot0001* opensuse-secureboot HD(1,GPT,cfe806b5-42f1-4acb- b521-38cdcb4801e0,0x800,0x4e000)/File(\EFI\opensuse\shim.efi) In my case cfe806b5-42f1-4acb-b521-38cdcb4801e0 is the uid of my efi partition and it seem that I can remove the Boot0000 :-) (the other one are bootable nic) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bruno Friedmann wrote:
In doubt I'd say it is preferable to have a user scratch his head which of the two 'opensuse' entries is the right one, than removing the second without asking...
I guess You should be able to determine which by crossing information between blkid and efibootmgr
Well, I was talking of the EFI boot menu. IIRC you cannot see those details there. Once you have a running system available it's indeed easy :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/02/18 12:00 PM, Peter Suetterlin wrote:
Hi list,
today I decided to have a look at the new btrfs layout of Tumbleweed.
To be on the safe side I removed the current SDD of my laptop and put an identical, empty one in, and then did a new install of the most recent TW (20180206). Only thing I changed from the default is increase the rootfs size to 80GiB, I just selected 'KDE/Plasma system' and installed.
This went fine, I looked around the system, and then shut it down to put my old SDD back in.
¡IT DOESN'T BOOT ANYMORE!
Immediately after the POST screens of the BIOS I get a message error: file '/boot/grub/x86_64-efi/normal.mod' not found Entering rescue mode... grub rescue>
I checked BIOS, but didn't see obvious places where to change things (and have not changed anything)
What did the install do? It must have changed something in the laptop BIOS, but what and where, and how can I revert it back to the old setting?
Boot is UEFI, Secure Boot is disabled.
Going to look at the two disks from a separate system now, but any guidance is highly welcome...
Turn off fast boot also. During the installation access Boot process and set it grub2 to use grub2-efi. When swapping make sure that you run grub2-mkconfig -o /boot/grub2/grub.cfg because each drive will have a different UUID in /etc/fstab. If it's not in fstab it won't boot. Check UUID using blkid. Try adding the UUID of original drive to /etc/fstab using a boot cd and reboot. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Bruno Friedmann -
Carlos E. R. -
Felix Miata -
Michal Suchánek -
nicholas cunliffe -
Peter Suetterlin -
Roman Bysh