Page 1 of 4 123 ... LastLast
Results 1 to 10 of 37

Thread: Problem with /boot/efi

  1. #1
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    408

    Default Problem with /boot/efi

    A few weeks ago, while still using 42.3, I decided to fix what I felt was an annoying problem (albeit a tiny one).
    Whenever I booted up my system, I would see (I don't use Plymouth) an entry fly by telling me that a particular partition
    was improperly unmounted and I should run fsck to possibly fix it. The contravening partition? /boot/efi (the mount point to my /dev/sda1).


    So, I rebooted with a copy of Parted Magic (a hard disk management system) and ran the gparted app.
    After all was done (you can imagine it, and you'd be right), my system was then unbootable.
    I could access it through Parted Magic's file management software (which alleviated some of my horror), but was unable to boot.


    I took this opprtunity to upgrade my system to Leap 15.0, and went through a "System Installation" rather than an "Upgrade", but
    to no avail. I still could not boot. I then tried booting with the installation medium (usb) still in the usb slot, chose "Boot from HD",
    and was able to easily boot into the newly installed Leap 15.0.


    Hence, if I want to reboot, I must have the usb installer stick in the usb slot in order to boot into Leap 15.0. Obviously (I would think),
    this is not a satisfactory method of booting one's computer and I am now tiring of doing it this way ( ).


    Can anyone guide/help me on fixing this problem?
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 x64 KDE 20170319-lp150.7.1
    Linux Counter #140934

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,025
    Blog Entries
    15

    Default Re: Problem with /boot/efi

    Hi
    I would suggest using a Tumbleweed Live rescue or DE USB in the future, much more compatible

    So, if you get the system booting via USB as you described;

    Is /boot/efi mounted?

    Code:
    lsblk
    Does the /boot/efi/EFI directory have an opesuse directory, in here are there files?

    Do the boot entries exist in the BIOS nvram?

    Code:
    efibootmgr -v
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    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. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    10,839
    Blog Entries
    3

    Default Re: Problem with /boot/efi

    Quote Originally Posted by kerijan2003 View Post
    The contravening partition? /boot/efi (the mount point to my /dev/sda1).
    If you have Windows, then best to use that to fix FAT partitions. You might have to first assign the partition a drive letter, then run "CHKDSK /F". And then unassign the drive letter.

    I've tried to fix broken FAT partition in linux with "fsck", but it is not as successful. Usually the brokenness is small, so it doesn't matter. But for a badly broken partition, Windows does best. Or maybe FREEDOS could be used (not sure of that).

    If that fails, I don't have a good alternative suggestion. I would probably boot from rescue media, reformat the partition, set it to be an EFI partition, then reinstall grub. Ask if you decide to try this and need help.
    opensuse Leap 15.0; KDE Plasma 5;
    opensuse tumbleweed; KDE Plasma 5 (test system);

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    528

    Default Re: Problem with /boot/efi

    Quote Originally Posted by kerijan2003 View Post
    A few weeks ago, while still using 42.3, I decided to fix what I felt was an annoying problem (albeit a tiny one).
    Whenever I booted up my system, I would see (I don't use Plymouth) an entry fly by telling me that a particular partition
    was improperly unmounted and I should run fsck to possibly fix it. The contravening partition? /boot/efi (the mount point to my /dev/sda1).


    So, I rebooted with a copy of Parted Magic (a hard disk management system) and ran the gparted app.
    After all was done (you can imagine it, and you'd be right), my system was then unbootable.
    I could access it through Parted Magic's file management software (which alleviated some of my horror), but was unable to boot.


    I took this opprtunity to upgrade my system to Leap 15.0, and went through a "System Installation" rather than an "Upgrade", but
    to no avail. I still could not boot. I then tried booting with the installation medium (usb) still in the usb slot, chose "Boot from HD",
    and was able to easily boot into the newly installed Leap 15.0.


    Hence, if I want to reboot, I must have the usb installer stick in the usb slot in order to boot into Leap 15.0. Obviously (I would think),
    this is not a satisfactory method of booting one's computer and I am now tiring of doing it this way ( ).


    Can anyone guide/help me on fixing this problem?
    You need install grub2 on your HD: https://doc.opensuse.org/documentati...er.rescue.grub
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  5. #5
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    408

    Default Re: Problem with /boot/efi

    Code:
    lsblk
    Code:
    # lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 931.5G  0 disk  
    ├─sda1   8:1    0   256M  0 part /boot/efi
    ├─sda2   8:2    0   9.8G  0 part [SWAP]
    ├─sda3   8:3    0  72.1G  0 part /
    └─sda4   8:4    0 849.4G  0 part /home
    sdb      8:16   0   4.6T  0 disk  
    └─sdb1   8:17   0   4.6T  0 part /mnt/Multimedia4
    sdc      8:32   0   3.7T  0 disk  
    └─sdc1   8:33   0   3.7T  0 part /mnt/Multimedia2
    sdd      8:48   0   7.3T  0 disk  
    └─sdd1   8:49   0   7.3T  0 part /mnt/Multimedia1
    sde      8:64   0   7.3T  0 disk  
    └─sde1   8:65   0   7.3T  0 part /mnt/Multimedia3
    sdf      8:80   0   4.6T  0 disk  
    └─sdf1   8:81   0   4.6T  0 part /mnt/Multimedia5
    sr0     11:0    1  1024M  0 rom
    

    Does the /boot/efi/EFI directory have an opesuse directory, in here are there files?

    Code:
    # mount
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    devtmpfs on /dev type devtmpfs (rw,nosuid,size=4807040k,nr_inodes=1201760,mode=755)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
    tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
    efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
    cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
    cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
    cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
    cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
    cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
    cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
    cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
    cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
    cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
    cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
    /dev/sda3 on / type ext4 (rw,relatime,data=ordered)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=36,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=969)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    /dev/sdf1 on /mnt/Multimedia5 type ext4 (rw,relatime,data=ordered)
    /dev/sdd1 on /mnt/Multimedia1 type ext4 (rw,relatime,stripe=8191,data=ordered)
    /dev/sdc1 on /mnt/Multimedia2 type ext4 (rw,relatime,data=ordered)
    /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/sde1 on /mnt/Multimedia3 type ext4 (rw,relatime,stripe=8191,data=ordered)
    /dev/sdb1 on /mnt/Multimedia4 type ext4 (rw,relatime,stripe=8191,data=ordered)
    /dev/sda4 on /home type ext4 (rw,relatime,data=ordered)
    tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=963044k,mode=700,uid=1000,gid=100)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
    tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
    gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
    
    Code:
    # ls -la /boot/efi
    total 24
    drwxr-xr-x 3 root root 16384 Dec 31  1969 .
    drwxr-xr-x 4 root root  4096 Nov 10 10:27 ..
    drwxr-xr-x 4 root root  4096 Sep 11  2017 EFI
    # ls -la /boot/efi/EFI/
    total 28
    drwxr-xr-x 4 root root  4096 Sep 11  2017 .
    drwxr-xr-x 3 root root 16384 Dec 31  1969 ..
    drwxr-xr-x 2 root root  4096 Sep 11  2017 boot
    drwxr-xr-x 2 root root  4096 Sep 11  2017 opensuse
    # ls -la /boot/efi/EFI/boot/
    total 1544
    drwxr-xr-x 2 root root    4096 Sep 11  2017 .
    drwxr-xr-x 4 root root    4096 Sep 11  2017 ..
    -rwxr-xr-x 1 root root 1208968 Oct 31 16:05 bootx64.efi
    -rwxr-xr-x 1 root root  358768 Oct 31 16:05 fallback.efi
    # ls -la /boot/efi/EFI/opensuse/
    total 3492
    drwxr-xr-x 2 root root    4096 Sep 11  2017 .
    drwxr-xr-x 4 root root    4096 Sep 11  2017 ..
    -rwxr-xr-x 1 root root 1158688 Oct 31 16:05 MokManager.efi
    -rwxr-xr-x 1 root root      58 Oct 31 16:05 boot.csv
    -rwxr-xr-x 1 root root     155 Oct 31 16:05 grub.cfg
    -rwxr-xr-x 1 root root 1060704 Oct 31 16:05 grub.efi
    -rwxr-xr-x 1 root root  123904 Nov  1 08:48 grubx64.efi
    -rwxr-xr-x 1 root root 1208968 Oct 31 16:05 shim.efi
    
    Do the boot entries exist in the BIOS nvram?

    Not sure how to retrieve that information.

    Code:
    efibootmgr -v
    Code:
    # efibootmgr -v
    BootCurrent: 0001
    Timeout: 2 seconds
    BootOrder: 0000,0001
    Boot0000  opensuse      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
    Boot0001* UEFI: Ut165 USB2FlashStorage0.00      PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(1,MBR,0x6b8b4567,0xa30,0x1e84)..BO
    
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 x64 KDE 20170319-lp150.7.1
    Linux Counter #140934

  6. #6
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    408

    Default Re: Problem with /boot/efi

    Quote Originally Posted by nrickert View Post
    If you have Windows, then best to use that to fix FAT partitions. You might have to first assign the partition a drive letter, then run "CHKDSK /F". And then unassign the drive letter.

    I've tried to fix broken FAT partition in linux with "fsck", but it is not as successful. Usually the brokenness is small, so it doesn't matter. But for a badly broken partition, Windows does best. Or maybe FREEDOS could be used (not sure of that).

    If that fails, I don't have a good alternative suggestion. I would probably boot from rescue media, reformat the partition, set it to be an EFI partition, then reinstall grub. Ask if you decide to try this and need help.

    Nope. No windows on my machine (there hasn't been for a couple decades).

    Reformat? How? From what environment?

    Not sure how one would set it to be an EFI partition.
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 x64 KDE 20170319-lp150.7.1
    Linux Counter #140934

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,025
    Blog Entries
    15

    Default Re: Problem with /boot/efi

    Quote Originally Posted by kerijan2003 View Post
    Code:
    efibootmgr -v
    Code:
    # efibootmgr -v
    BootCurrent: 0001
    Timeout: 2 seconds
    BootOrder: 0000,0001
    Boot0000  opensuse      VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
    Boot0001* UEFI: Ut165 USB2FlashStorage0.00      PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(1,MBR,0x6b8b4567,0xa30,0x1e84)..BO
    
    Hi
    So looks like the nvrm is funky.... So boot from your usb device and as root user run;
    Code:
    efibootmgr -b 0 -B 0
    efibootmgr -c -L "openSUSE" -l "\\EFI\\opensuse\\grubx64.efi"
    First command deletes that funky entry (which may be a hardware BIOS/UEFI issue), the second command creates a new entry. Reboot and go into the BIOS and check the boot order, should have openSUSE in there? If so, system should boot again....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #8
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    408

    Default Re: Problem with /boot/efi

    Quote Originally Posted by karlmistelberger View Post
    Checked out the linked document and have a question. It is mentioned that
    Code:
    > sudo grub2-install /dev/sda
    will reinstall. Should it not be?
    Code:
    > sudo grub2-install /dev/sda1
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 x64 KDE 20170319-lp150.7.1
    Linux Counter #140934

  9. #9
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,025
    Blog Entries
    15

    Default Re: Problem with /boot/efi

    Quote Originally Posted by kerijan2003 View Post
    Checked out the linked document and have a question. It is mentioned that
    Code:
    > sudo grub2-install /dev/sda
    will reinstall. Should it not be?
    Code:
    > sudo grub2-install /dev/sda1
    Hi
    Nooooo, your using efi, you just need to fix the entry in the BIOS....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  10. #10
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    408

    Default Re: Problem with /boot/efi

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Nooooo, your using efi, you just need to fix the entry in the BIOS....
    Not sure how one accesses that part of the BIOS. I've never seen and lists in the BIOS mentioning installed OSes.I'll reboot into the BIOS now to see if I can figure this out. Will return if'n I need help.
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 x64 KDE 20170319-lp150.7.1
    Linux Counter #140934

Page 1 of 4 123 ... LastLast

Posting Permissions

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