Results 1 to 5 of 5

Thread: text mode yast bootloader repair didn't (non-working UEFI grub)

  1. #1
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,207

    Default text mode yast bootloader repair didn't (non-working UEFI grub)

    XPG (Adata) ASX6000LNP-128GT-C nvme stick went bad in annoyingly quick fashion, 25 days after purchase, before I got done with everything and made a fresh backup of the entire stick. I've already got it packed up and in the mail with a return shipping RMA label from the vendor. The NVME was originally a clone from SATA SSD, but thinking the new nvme was OK a few days earlier, I had already pressed the old SSD into service elsewhere.

    I've been trying to piece together as best I can what I had after installing the new ZTC-PCIEG3-128G NVME. Over and over again I've been meeting up with various grub> prompts and grub errors after trying this and that for hours and hours over a period of days and interruptions, including finding and reporting a rescue mode bug. Eventually I decided the restoration of the ESP partition had to be defective, so I reformatted it FAT 32 using the old volume label and 8 character UUID, then:
    Code:
    # mount -t ext4 /dev/sda7 /mnt
    # mount -o bind /dev /mnt/dev
    # mount -o bind /sys /mnt/sys
    # mount -o bind /proc /mnt/proc
    # chroot /mnt
    # mount -a
    I then restored backup content of /boot/grub2/ and /boot/EFI/efi/[opensusetw,BOOT]/, then:
    Code:
    # efibootmgr
    # efibootmgr -b 0 -B
    # efibootmgr -b 0 -c -d /dev/nvme0n1 -L opensusetw -l /efi/opensusetw/grubx64.efi -p1 -v
    # efibootmgr -v
    BootCurrent: 0004
    Timeout: 1 seconds
    BootOrder: 0000,0003,0004
    Boot0000* opensusetw    HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\OPENSUSETW\GRUBX64.EFI)
    Boot0003* UEFI OS       HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
    Boot0004* UEFI: Optiarc DVD RW AD-7200S PciRoot(0x0)/Pci(0x17,0x0)/Sata(3,65535,0)/CDROM(1,0x4e8dd,0x7800)..BO
    I thought it looked good, and the BIOS seemed to match.

    Then I ran ncurses yast > bootloader, changed timeout, exited. Thinking yast surely must have done whatever was needed that I may have overlooked, this was my result from trying to boot TW from its own Grub:
    Code:
    Welcome to GRUB!
    
    error: symbol `grub_file_filters' not found.
    Entering rescue mode...
    grub rescue>
    I'd seen this before, so I tried just typing in from this custom.cfg backup stanza:
    Code:
    menuentry "openSUSE TW defkernel 3 on P07" {
    	load_video
    	set gfxpayload=keep
    	search --no-floppy --set=root --hint-efi=hd0,gpt7 --label sx6stw
    	linux	/boot/vmlinuz root=LABEL=sx6p07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 video=1024x768@60 video=1440x900@60 3 drm.debug=0x1e log_buf_len=1M pci=noaer 
    	initrd	/boot/initrd
    }
    Code:
    grub rescue> load_video
    Unknown command `load_video'.
    grub rescue> set gfxpayload=keep
    grub rescue> search --no-floppy --set=root --hint-efi=hd0,gpt7 --label sx6stw
    Unknown command `search'.
    grub rescue> insmod gzio
    error: symbol `grub_file_filters' not found.
    grub rescue>
    I'm really burned out try to get this back in gear after waiting for ddrescue reaching 99.67% done in 30 hours and forecasting several more days to completion, then searching out all the pieces from which to reconstruct, playing guessing games with a UEFI BIOS that doesn't like to have video output until after it's needed, making me guess if and when to strike DEL or F2 or F8, and insufferably waiting on reboots with various slow boot media that eventually dead end because something I need is missing. I trashed one 15.1 DVD and burned new for TW and 15.1 both. My skill with USB sticks is deficient, so with this PC making me play non-appearing video and keyboard games when I try my 15.1, I just don't like to try.

    Note a "fresh installation" is best avoided. TW's is responsible via custom.cfg for booting other installations on 8 other nvme partitions. There really ought to be a way to fix this that doesn't involve cloning from its sibling PCs NVME and losing those things that make them differ, such as the Fedora installation the other lacks, the RAID sda & sdb configuration unneeded on this, and the different IP, MAC and hostname across multiple partitions.

    What's missing that Grub rescue mode doesn't know needed commands, like search? Grub help is nearly useless, as it scrolls most output over top of screen.

    Any advice or ideas what I may have missed getting my TW grub to work again?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1,TW,15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on 965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  2. #2
    Join Date
    Sep 2012
    Posts
    5,665

    Default Re: text mode yast bootloader repair didn't (non-working UEFI grub)

    [QUOTE=mrmazda;2924719]
    Code:
    Welcome to GRUB!
    
    error: symbol `grub_file_filters' not found.
    Entering rescue mode...
    grub rescue>
    Your core.img (or grubXX.efi) does not match other grub binaries in /boot/grub2, it is much older.
    I tried just typing in from this custom.cfg backup stanza
    You cannot type them in grub rescue environment which supports very limited set of commands (basically it is just insmod and ls). grub interface that you normally use is implemented by normal.mod.

  3. #3
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,207

    Default Re: text mode yast bootloader repair didn't (non-working UEFI grub)

    Thanks arvidjaar!

    Just before seeing your reply I managed to boot the installed system via installation media's grub by going to shell and typing entries used by grub.cfg. Will going into YaST2 bootloader and changing the timeout fix this, or is something more required to get core.img and/or grubx64.efi up to date. Would force reinstalling grub2-x86_64-efi and/or grub2 do it?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1,TW,15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on 965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  4. #4
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,207

    Default Re: text mode yast bootloader repair didn't (non-working UEFI grub)

    Perplexing result from trying harder at the grub rescue> prompt before arvidjaar's response arrived:
    Code:
    grub rescue> set
    cmdpath=(hd1,gpt1)/EFI/OPENSUSETW
    prefix=(hd1,gpt7)/boot/grub2
    root=hd1,gpt7
    grub rescue>ls
    (hd0) (hd1) (hd1,gpt16) (hd1,gpt15) (hd1,gpt14) (hd1,gpt13) (hd1,gpt12) (hd1,gpt11) (hd1,gpt10) (hd1,gpt9) (hd1,gpt8) (hd1,gpt7) (hd1,gpt6) (hd1,gpt5) (hd1,gpt4) (hd1,gpt3) (hd1,gpt2) (hd1,gpt1)
    This is with only one storage device in the PC, empty DVD drive, no USB sticks inserted, only the M.2 NVME stick. Why does it report (hd1) at all, much less owning all the partitions?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1,TW,15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on 965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,207

    Default Re: text mode yast bootloader repair didn't (non-working UEFI grub)

    YaST2 bootloader seems to have been sufficient. All content in /boot/efi/EFI/opensusetw, /boot/grub2/x86_64-efi/ and /boot/grub2/fonts/ has fresh timestamps. /boot/efi/EFI/BOOT/BOOTX64.EFI has one from several hours ago, maybe as a result of something I did in recent hours while booted with the kernel thinking local time was UCT time, which is actually 5 hours behind. /boot/efi/EFI/BOOT/grubx64.efi has one from June 2018.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.1,TW,15.2 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&15.1 on 965P/Radeon
    Tertiary: TW,15.2,15.1,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

Posting Permissions

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