Bug 1850288 - Page Missing - v22 - multiboot-guide - "6.3.2.2. Reinstalling GRUB on BIOS systems."
Summary: Page Missing - v22 - multiboot-guide - "6.3.2.2. Reinstalling GRUB on BIOS sy...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: multiboot-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-23 22:44 UTC by Josiah Luscher
Modified: 2024-05-21 09:23 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 09:23:37 UTC
Embargoed:


Attachments (Terms of Use)
I think I found the current BIOS Grub2 installation instructions: https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/ (1.89 KB, text/plain)
2020-06-23 22:55 UTC, Josiah Luscher
no flags Details

Description Josiah Luscher 2020-06-23 22:44:24 UTC
Description of problem:  Entire documentation section missing.  


Version-Release number of selected component (if applicable): v22


How reproducible: Very Easy


Steps to Reproduce:
1. Open the following page with web browser:

https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/GRUB-reinstalling-BIOS.html

Actual results:  Header is displayed with no content.


Expected results: Enlightenment(?)


Additional info:  My server won't boot!  Plasse HALP! [Sad Human]  -- Thanks!

Comment 1 Josiah Luscher 2020-06-23 22:55:28 UTC
Created attachment 1698511 [details]
I think I found the current BIOS Grub2 installation instructions: https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/

This seems to be the information that is missing, or at least it's close:

https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/

Comment 2 Petr Bokoc 2024-05-21 09:23:37 UTC
This guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.


Note You need to log in before you can comment on or make changes to this bug.