<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Grub on Kenno&#39;s Open Note</title>
    <link>https://blog.khmersite.net/tags/grub/</link>
    <description>Recent content in Grub on Kenno&#39;s Open Note</description>
    <image>
      <title>Kenno&#39;s Open Note</title>
      <url>https://blog.khmersite.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://blog.khmersite.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.154.0</generator>
    <language>en</language>
    <lastBuildDate>Tue, 10 Sep 2019 01:14:12 +1000</lastBuildDate>
    <atom:link href="https://blog.khmersite.net/tags/grub/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>grub2-editenv: error environment block too small</title>
      <link>https://blog.khmersite.net/p/grub2-editenv-error-environment-block-too-small/</link>
      <pubDate>Tue, 10 Sep 2019 01:14:12 +1000</pubDate>
      <guid>https://blog.khmersite.net/p/grub2-editenv-error-environment-block-too-small/</guid>
      <description>&lt;p&gt;As the title says when I tried to generate grub on a machine running Fedora 31 using UEFI, I was presented with this error:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-console&#34; data-lang=&#34;console&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Generating grub configuration file ...
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;grub2-editenv: error: environment block too small.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;...
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;I didn&amp;rsquo;t know what had caused it. However, it seemed like an easy fix was to remove the &lt;code&gt;grubenv&lt;/code&gt; file.&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-console&#34; data-lang=&#34;console&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;# rm /boot/efi/EFI/fedora/grubenv
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;# grub-editenv /boot/efi/EFI/fedora/grubenv create
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Generating grub configuration file ...
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Adding boot menu entry for EFI firmware configuration
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;done
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;By the way, as a word of caution, if you have a similar problem, please don&amp;rsquo;t just copy and paste the command above and run it. It may make your sitution worse.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Install Grub on GPT</title>
      <link>https://blog.khmersite.net/p/install-grub-on-gpt/</link>
      <pubDate>Mon, 25 Sep 2017 16:45:37 +0000</pubDate>
      <guid>https://blog.khmersite.net/p/install-grub-on-gpt/</guid>
      <description>&lt;p&gt;I came across a problem with grub being broken recently on a system running Ubuntu 16.04. This happened after the grub2 package got upgraded. This post will explain how I solved the problem. If you have similar issues, please do not just copy and paste the commands and execute on your machine. First read on, and try to understand it.&lt;/p&gt;
&lt;p&gt;Usually, when this happened in the past, we just need to chroot into the system and reinstall grub. On Ubuntu, assuming you’ve chrooted into the system, and the boot disk is &lt;code&gt;/dev/sda&lt;/code&gt;, this could be done by running:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restore Grub Boot Loader</title>
      <link>https://blog.khmersite.net/p/restore-grub-boot-loader/</link>
      <pubDate>Sat, 08 Aug 2009 14:56:24 +0000</pubDate>
      <guid>https://blog.khmersite.net/p/restore-grub-boot-loader/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Warning&lt;/strong&gt;: this guide is only a personal note to remind myself when I have to restore Grub again.&lt;/p&gt;
&lt;p&gt;In my previous post, I had just installed Windows 7 as a dual boot with Debian on my Toshiba laptop. The following describe the steps taken to restore the Grub boot loader so that Debian can be started again.&lt;/p&gt;
&lt;p&gt;I booted the laptop with Ubuntu Live CD, then open a Terminal. To get the partition tables, as a root execute the &lt;strong&gt;fdisk&lt;/strong&gt; command:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
