{"id":8660,"date":"2024-11-26T01:07:00","date_gmt":"2024-11-26T06:07:00","guid":{"rendered":"https:\/\/www.both.org\/?p=8660"},"modified":"2024-11-25T11:09:44","modified_gmt":"2024-11-25T16:09:44","slug":"fedora-rescue-mode-fails","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=8660","title":{"rendered":"Fedora rescue mode fails"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

Have you ever noticed the bottom line on the GRUB bootloader menu? Well, you won’t unless you’re looking for it during the very first part of the Linux boot process. So if you have a spare VM to play with, boot it now and when the GRUB menu appears, press any key to stop the countdown timer. That will prevent the boot from proceeding and let you look at the bottom entry. <\/p>\n\n\n\n

There should be at least two entries, and more if you’ve been doing updates like you should. The one I’m talking about is always the bottom entry in the list as in Figure 1.<\/p>\n\n\n\n

\"\"<\/a>
Figure 1: The GRUB boot menu with the rescue mode entry highlighted.<\/figcaption><\/figure>\n\n\n\n

This is intended to be a quick and easy method for entering rescue mode to perform system maintenance that can’t be performed in any other way. For me, this usually turns out to be a self-inflicted problem that prevents the system from completing the boot process to multi-user.target (runlevel 3) or graphical.target (runlevel 5). Rescue mode is supposed to be a minimal but usable working environment for the SysAdmin to perform those types of repairs. <\/p>\n\n\n\n

The problem<\/h2>\n\n\n\n

When I select this entry and press the Enter key, the system boots into graphical.target. Or, when having problems that need to be fixed, it crashes at the same place it did before. That can be aggravating when I’m trying to resolve a problem. <\/p>\n\n\n\n

I’m not sure why this has been neither fixed nor removed from the GRUB menu. <\/p>\n\n\n\n

My solution<\/h2>\n\n\n\n

This is an easy solution. Well, it should be for a SysAdmin who needs to fix a boot problem.<\/p>\n\n\n\n

First, initiate a boot or reboot as the case may be. When the GRUB menu is displayed, press the e<\/strong> key to enter edit mode for the default kernel, which is typically the most recent one and will be highlighted. This allows you to edit the Linux Kernel command line. While that sounds dangerous, and it can be, if you follow these simple directions, it\u2019s not.<\/p>\n\n\n\n

Figure 2 shows the GRUB menu with the default kernel selected. You won\u2019t have more than a few seconds, usually 3 for Fedora, to press the e<\/strong> key. You can also stop the countdown timer by moving the selector bar with the arrow keys, or by pressing any other key that doesn\u2019t perform a function. Don\u2019t press the Enter key or it will just continue to boot.<\/p>\n\n\n\n

\"\"<\/a>
Figure 2: The default kernel is already selected. Press the E key to enter edit mode for this kernel.<\/figcaption><\/figure>\n\n\n\n

In Figure 3, we see the default kernel boot configuration in GRUB. Edit the \u201clinux\u2026\u201d line to add a \u201c1\u201d to the end of the line. The red arrow shows the location where I added \u201c1.\u201d After making the edit, press the F10 key to boot. The \u201c1\u201d we added causes GRUB to boot Linux into the rescue.target.<\/p>\n\n\n\n

\"\"<\/a>
Figure 3: Edit the end of the \u201clinux\u2026\u201d line to add a \u201c1\u201d to boot into rescue.target.<\/figcaption><\/figure>\n\n\n\n

Figure 4 shows the password prompt at the bottom of the screen. Enter the root password to login.<\/p>\n\n\n\n

\"\"<\/a>
Figure 4: Login to Rescue mode.<\/figcaption><\/figure>\n\n\n\n

After entering the root password, you\u2019ll be at a root command prompt and ready to perform your administrative tasks. After resolving the problem, you can reboot and the system should boot to the default target.<\/p>\n\n\n\n

Thoughts<\/h2>\n\n\n\n

I think that this rescue option should be removed from the Fedora GRUB boot menu. It seems a bit lazy to keep an option that hasn’t worked for such a long time. <\/p>\n","protected":false},"excerpt":{"rendered":"

Have you ever noticed the bottom line on the GRUB bootloader menu? Well, you won’t unless you’re looking<\/p>\n","protected":false},"author":2,"featured_media":4599,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[351,5,83],"tags":[657,174],"class_list":["post-8660","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-boot","category-linux","category-problem-solving","tag-grub","tag-linux-boot"],"modified_by":"David Both","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/8660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8660"}],"version-history":[{"count":8,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/8660\/revisions"}],"predecessor-version":[{"id":8669,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/8660\/revisions\/8669"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/4599"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}