# after installing most recent kernel: /boot/grub disappeared?

**URL:** <https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899>\
**Category:** SLES Configure-Administer\
**Created:** [November 4, 2016, 11:11pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899 "2016-11-04T23:11:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![berndgsflinux](https://avatars.discourse-cdn.com/v4/letter/b/6a8cbe/32.png) [@berndgsflinux](https://forums.suse.com/u/berndgsflinux)\
**Post date:** [November 4, 2016, 11:11pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/1 "2016-11-04T23:11:20Z")

</div>

Hi,  
i have a system with SLES 11 SP4 64bit. I installed the most recent kernel because of the dirty-cow bug: 3.0.101-84.1  
The installation was complaining about some missing files in the /boot/grub directory:

```auto
Perl-Bootloader: 2016-11-04 21:11:03 <3> pbl-4528.2 FileIO::ReadFile.90: Error: Failed to open /boot/grub/menu.lst: No such file or directory
Perl-Bootloader: 2016-11-04 21:11:03 <3> pbl-4528.2 FileIO::ReadFile.90: Error: Failed to open /boot/grub/device.map: No such file or directory
Perl-Bootloader: 2016-11-04 21:11:03 <3> pbl-4528.2 Core::GRUB::GrubDev2UnixDev.476: Error: did not find a match for hd0 in the device map
Perl-Bootloader: 2016-11-04 21:11:03 <3> pbl-4528.2 Core::GRUB::GrubDev2UnixDev.476: Error: did not find a match for hd0 in the device map
```

While checking for the missing files i found out that i don’t have a /boot/grub directory !!! I can’t remember deleting it. Why should i ?  
In the history i don’t find anything like "rm -rfv /boot/grub or something similar.

I didn’t check if the directory is available _before_ the installation of the new kernel.  
So i’m not sure if the update removed it.

I’d like to ask if someone else experienced this ?

What i’m sure of is that last week i did several reboots which went fine. Without /boot/grub they surely wouldn’t have gone fine.  
So last week /boot/grub must have been available. /boot is not on a seperate partition.  
I did some testing with OCFS2 and tried to install some packages related to libvirt last week  
I don’t see a relation to a deleted /boot/grub.

Bernd

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 5, 2016, 3:32am UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/2 "2016-11-05T03:32:55Z")

</div>

> [@](#):
>
> On Fri 04 Nov 2016 09:14:01 PM CDT, berndgsflinux wrote:
> 
> Hi,  
> i have a system with SLES 11 SP4 64bit. I installed the most recent  
> kernel because of the dirty-cow bug: 3.0.101-84.1  
> The installation was complaining about some missing files in the  
> /boot/grub directory:
> 
> ## Code:
> 
> Perl-Bootloader: 2016-11-04 21:11:03 \<3\> pbl-4528.2  
> FileIO::ReadFile.90: Error: Failed to open /boot/grub/menu.lst: No such  
> file or directory Perl-Bootloader: 2016-11-04 21:11:03 \<3\> pbl-4528.2  
> FileIO::ReadFile.90: Error: Failed to open /boot/grub/device.map: No  
> such file or directory Perl-Bootloader: 2016-11-04 21:11:03 \<3\>  
> pbl-4528.2 Core::GRUB::GrubDev2UnixDev.476: Error: did not find a match  
> for hd0 in the device map Perl-Bootloader: 2016-11-04 21:11:03 \<3\>  
> pbl-4528.2 Core::GRUB::GrubDev2UnixDev.476: Error: did not find a match  
> for hd0 in the device map --------------------
> 
> While checking for the missing files i found out that i don’t have a  
> /boot/grub directory !!! I can’t remember deleting it. Why should i ?  
> In the history i don’t find anything like "rm -rfv /boot/grub or  
> something similar.
> 
> I didn’t check if the directory is available _before_ the installation  
> of the new kernel.  
> So i’m not sure if the update removed it.
> 
> I’d like to ask if someone else experienced this ?
> 
> What i’m sure of is that last week i did several reboots which went  
> fine. Without /boot/grub they surely wouldn’t have gone fine.  
> So last week /boot/grub must have been available. /boot is not on a  
> seperate partition.  
> I did some testing with OCFS2 and tried to install some packages related  
> to libvirt last week  
> I don’t see a relation to a deleted /boot/grub.
> 
> Bernd

Hi  
Fire up YaST bootloader and check, it should create them again…

Not a UEFI booting system?

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default  
If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below… Thanks!

---

<div class="post-metadata">

**Author:** ![berndgsflinux](https://avatars.discourse-cdn.com/v4/letter/b/6a8cbe/32.png) [@berndgsflinux](https://forums.suse.com/u/berndgsflinux)\
**Post date:** [November 5, 2016, 2:27pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/3 "2016-11-05T14:27:45Z")

</div>

Hi Malcom,  
that’s clear. But the question is how could it dissapear ?  
How can i recognize if it is an UEFI system ?

Bernd

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 5, 2016, 4:21pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/4 "2016-11-05T16:21:00Z")

</div>

> [@](#):
>
> On Sat 05 Nov 2016 12:34:01 PM CDT, berndgsflinux wrote:
> 
> Hi Malcom,  
> that’s clear. But the question is how could it dissapear ?  
> How can i recognize if it is an UEFI system ?
> 
> Bernd

Hi  
If it’s UEFI booting (run the command efibootmgr) then it’s using elilo  
and not grub. It should show whats being used in YaST Bootloader.

What file system in use, btrfs?

What partitions are present?

```auto
lsblk
```

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default  
If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below… Thanks!

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [November 5, 2016, 4:41pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/5 "2016-11-05T16:41:56Z")

</div>

> [@](#):
>
> On Sat 05 Nov 2016 02:21:00 PM CDT, malcolmlewis wrote:
> 
> > [@](#):
> >
> > On Sat 05 Nov 2016 12:34:01 PM CDT, berndgsflinux wrote:
> > 
> > Hi Malcom,  
> > that’s clear. But the question is how could it dissapear ?  
> > How can i recognize if it is an UEFI system ?
> > 
> > Bernd
> 
> Hi  
> If it’s UEFI booting (run the command efibootmgr) then it’s using elilo  
> and not grub. It should show whats being used in YaST Bootloader.
> 
> What file system in use, btrfs?
> 
> What partitions are present?
> 
> ```auto
> lsblk
> ```

Hi  
Another thought, was the system all up to date with patches etc, I  
wonder if you missed a perl-bootloader update?

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default  
If you find this post helpful and are logged into the web interface,  
please show your appreciation and click on the star below… Thanks!

---

<div class="post-metadata">

**Author:** ![berndgsflinux](https://avatars.discourse-cdn.com/v4/letter/b/6a8cbe/32.png) [@berndgsflinux](https://forums.suse.com/u/berndgsflinux)\
**Post date:** [November 5, 2016, 9:16pm UTC](https://forums.suse.com/t/after-installing-most-recent-kernel-boot-grub-disappeared/28899/6 "2016-11-05T21:16:11Z")

</div>

```auto
sunhb58820:~ # mount

/dev/mapper/vg1-lv_root on / type ext3 (rw,strictatime,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
configfs on /sys/kernel/config type configfs (rw)
ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw)
/dev/dm-5 on /images type ocfs2 (rw,_netdev,heartbeat=local)
none on /var/lib/ntp/proc type proc (ro,nosuid,nodev)
```

```auto
sunhb58820:~ # efibootmgr -v
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
Try 'modprobe efivars' as root.

Loading the module didn't suceed.
```

```auto
sunhb58820:~ # rpm -qa|grep -iE 'grub|lilo'
elilo-3.14-0.38.1
grub-0.97-162.172.1
```

```auto
sunhb58820:~ # elilo -tv
elilo: /etc/elilo.conf: failed to open: No such file or directory
```
