Grub downloads
Author: c | 2025-04-24
Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Ice Walkers. Sign in with Facebook. Login. Linux Software. GRUB 2.12. Submit New Release; Edit GRUB Information; Submit a New Software; Multiboot boot loader. Friday, Decem.
grubs/boot/grub/grub.cfg.sample at master dwarmstrong/grubs
Try opening a terminal and runningsudo chmod +x /etc/grub.d/20_memtest86+sudo update-grubCheck to see if it's theregrep memtest /boot/grub/grub.cfgJust done the same as I had it disabled$ cat /boot/grub/grub.cfg | grep memtest$ sudo chmod +x /etc/grub.d/20_memtest86+[sudo] password for hob: $ sudo update-grubGenerating grub.cfg ...Found linux image: /boot/vmlinuz-3.2.0-24-genericFound initrd image: /boot/initrd.img-3.2.0-24-genericFound linux image: /boot/vmlinuz-3.2.0-23-genericFound initrd image: /boot/initrd.img-3.2.0-23-genericFound memtest86+ image: /boot/memtest86+.binFound Ubuntu 11.10 (11.10) on /dev/sda6Found Trisquel 5.5 (5.5) on /dev/sda8Found Ubuntu 12.04 LTS (12.04) on /dev/sda9done$ cat /boot/grub/grub.cfg | grep memtest### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test (memtest86+)" { linux16 /boot/memtest86+.binmenuentry "Memory test (memtest86+, serial console 115200)" { linux16 /boot/memtest86+.bin console=ttyS0,115200n8### END /etc/grub.d/20_memtest86+ ###You could try creating the file if it's not there, using nano in a terminalsudo nano /etc/grub.d/20_memtest86+or with a gui editorgksudo gedit /etc/grub.d/20_memtest86+Fill it with#!/bin/shset -eif [ -f /usr/lib/grub/grub-mkconfig_lib ]; then . /usr/lib/grub/grub-mkconfig_lib LX=linux16elif [ -f /usr/lib/grub/update-grub_lib ]; then . /usr/lib/grub/update-grub_lib LX=linuxelse # no grub file, so we notify and exit gracefully echo "Cannot find grub config file, exiting." >&2 exit 0fi# We can't cope with loop-mounted devices here.case ${GRUB_DEVICE_BOOT} in /dev/loop/*|/dev/loop[0-9]) exit 0 ;;esacprepare_boot_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/")"if test -e /boot/memtest86+.bin ; then MEMTESTPATH=$( make_system_path_relative_to_its_root "/boot/memtest86+.bin" ) echo "Found memtest86+ image: $MEMTESTPATH" >&2 cat &2# cat Make sure to run the chmod +x command on it afterwards.I'd be a bit concerned that it's missing though - do you have everything else in grub.d ?$ ls /etc/grub.d/00_header 10_linux.bak 20_memtest86+ 41_custom05_debian_theme 10_linux.dpkg-old 30_os-prober README10_linux 20_linux_xen 40_custom One of the issues I encountered after dual booting Windows with Linux is the missing Windows entry from the grub menu.Here's the scenario. Windows was present on the computer. I installed CachyOS alongside Windows. I selected to install the Grub bootloader that allows booting into Linux, Windows (and any other OS present on the system) along with the option to access UEFI.Only this time, Grub did not show Windows in the menu 😔Missing Windows from Grub bootloaderThat was disappointing but not surprising because I am aware that this is a feature.Let me show you how you can fix this by enabling os-prober feature in Grub and then updating it.Step 1: Enable os-prober in grubGrub config file is located at /etc/default/grub. If you open it via Nano or some editor, you'll see at the end of this file that os-prober is disabled by default sighting security reasons.If you are familiar with any terminal-based text editor, use it to uncomment the line # GRUB_DISABLE_OS_PROBER=false by removing the # at the beginning of the line.However, if you are absolutely new to the command line, you can use this command in the terminal:echo "GRUB_DISABLE_OS_PROBER=false" | sudo tee -a /etc/default/grubIt will ask for your password. It should be the same account password you use to log in to the system.🚧When you type the password in Linux terminal, nothing is reflected on the screen. It feels as if your system is hanged, as there is no visible feedback. Don't worry. It's a security feature and most Linux terminals won't even show asterisks (*) as you enter the password. Just type it in and enter.With os-prober enabled, Grub will look for the presence of other operating systems in EFI folder and will add them in the bootloader menu.There is one little problem. The config changes won't take place unless you update grub.Step 2: Update grubOn Ubuntu and some other distributions, there is a dedicated command to update grub:sudo update-grubHowever, on Arch and some other distributions, you'll end up with update-grub command not found error.That's because update-grub is not a standard command. It is just la stub for this command:sudo grub-mkconfig -o /boot/grub/grub.cfgRun the above command if your system doesn't have update-grub.It should show an output like this:And as you can see in the above output, grub is probing for other OS and has found Windows boot manager. This is an indication that when you reboot the system, grub should show Windows in the available option.And Windows is back in GrubStill no Windows boot manager?See, this method only works when dual boot succeeded properly and you have all EFI settings located in the same folder under the same ESP partition.If that's not the case, you could try accessinggrub project files : grub - Launchpad
The No Such Partition Grub Rescue error is also known as the ‘Death Screen of Linux’. And this error mainly occurs when your grub configuration is messed up for some reason. In this article, we will try to solve this problem of ours using a live CD image of the same OS and try to fix your installation.Pre-requisitesYou have a live CD/DVD/USB of the Operating System (must be of the same version).You have a stable internet connection.And you do not have a Wubi (Ubuntu inside Windows) installation on your system.Let’s get started!6 Easy Steps to Fix No Such Partition Grub Rescue ErrorWe need to re-install grub because it is either deleted or corrupt. And to re-install, we will copy the grub file from the live USB to your grub directory. Note that this will remove any custom configuration you have made to the grub file. Follow these steps to fix your grub file.1. Locate your Root/boot partitionBoot from the Live USB stick and, in the terminal, type the following commands to gain administrative privileges :Now, type the following commands to know your disk partitioning structure :Output Of Fdisk CommandIn the output, you will see text like /dev/sda1 or /dev/sda2 etc. If you have a separate Boot partition (EFI filesystem), note its location (usually it is 500 MB). And, if you don’t have a separate boot partition, then locate your root (/) partition. If you don’t know where your root is located, then you have to guess. Typically, it’s 30-50 GB in size.2. Mount the Root/Boot PartitionTo modify the changes in our root/boot partition, we will have to mount it first. To do that, type the following commands in your terminal :sudo mkdir /mnt/tempsudo mount /dev/sda2 /mnt/tempYour sdX number can be different from mine, use the number where your root partition is located. And for separate boot partition, mount it as follows :sudo mkdir /mnt/temp /mnt/temp/bootsudo mount /dev/sdXY /mnt/temp # Mount the main partition.sudo mount /dev/sdXZ /mnt/temp/boot # Mount the /boot partition.3. Be CHROOTNow that we have mounted the partition, we will have to mount several items in preparation of the chroot, run the following commands :for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt/temp$i; donesudo cp /etc/resolv.conf /mnt/temp/etc/resolv.confsudo chroot /mnt/tempIf everything went well, you will see ‘root’ in the terminal prompt.4. Update apt and Purge GRUB2 packagesRun the following commands as chroot to update apt :Now, purge the old damaged grub files using these commands :apt-get purge grub grub-pc grub-commonSelect yes in the promptA prompt will appear asking for your confirmation to remove GRUB2 press and then press enter.5. Re-install GRUB bootloaderWe need to keep a few things in our mind before we we-install GRUB :While installation, it will ask you to add extra kernel options, if you don’t know about it then you probably don’t need it too. Just press the Tab key to navigate to Ok and press Enter.Installation notes will appear before your screen. Again, press Ok to continue.It will now ask you. Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Ice Walkers. Sign in with Facebook. Login. Linux Software. GRUB 2.12. Submit New Release; Edit GRUB Information; Submit a New Software; Multiboot boot loader. Friday, Decem.grubs/boot/grub/grub.cfg.sample at master
Up now that we are able to:Time zone and clock syncMeaning sync to the hardware clock (for me this is UK, but you can select yours from the appropriate folder)ln -sf /usr/share/zoneinfo/GB /etc/localtimehwclock --systohcSet the LocaleLet’s set the system locale – first we will need an editor (I chose VIM)pacman -S vimvim /etc/locale.genI simply un-commented the line I needed. Then you run:locale-gento generate your localeSet the languageLet’s set the languagevim /etc/locale.confSet the keyboard layoutLet’s now set the default keyboard layoutvim /etc/vconsole.confSet the hostnameLet’s do the hostname next – put in the Ipv4 localhost address and Ipv6 localhost address, and also the hostname (you can fully qualify this if you need a search suffix, or are in an environment with a domain etc.)vim /etc/hostnamevim /etc/hostsPassword set for root accountLet’s set the password nextpasswdBootloader ConfigNow the majority of the config is done and will persist.Next we need to choose a bootloader. There are an abundance of these available, and there is a nice comparison chart here to allow you to make the best choice: usually go for GRUB as it does everything that I need. I have been known to use LILO in the past, but this doesn’t support UEFI. I find GRUB works for me now, and I know how to customise it to how I like.For this tutorial I will be using GRUB. As we are using a UEFI, this bit can be quite tricky. Full concentration required here!I will suggest that you have a look at the Arch documentation here: implement UEFI differently which may change the way that you proceed.I will also go through how we will get it working for this virtual machine. So we need to install grub and efibootmgr.Install the bootloaderpacman -S grub efibootmgrConfigure grubNext we need to install grub based on our efi mount point location for our UEFI system (/efi)grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUBGenerate grub configNow let’s generate the config file for grubgrub-mkconfig -o /boot/grub/grub.cfgRemove install media and rebootOK now – time to remove the install media, and try this out!If you are lucky this will work first time Let’s exit our changeroot environment ExFAT isn't the most widely adopted file system. I wouldn't expect it to work with UEFI. As Bob wrote: Try FAT32.Then again, you shouldn't need to save those keys, nor to disable secure boot (although neither will hurt you).Generally, the boot process on a dual boot system with UEFI looks like this:UEFI loads a bootloader, with linux that's usually GRUB. GRUB looks at it's config, finds an entry for linux and one for windows. The linux entry will load the kernel and possibly the initramfs. The windows entry will just start the windows bootloader.With secure boot, UEFI will check, if the bootloader (in the above example: GRUB) was signed by a key it can verify. That is the case with the windows bootloader, but not with grub. So, in order to boot non windows systems, Microsoft has published a mini bootloader called Shim. Shim is signed by Microsoft and can thus be booted with UEFI with secure boot active. But Shim can't check the integrity of GRUB, nor the integrity of linux or the windows bootloader, if loaded by grub. Therefore, as soon as you use dual boot, secure boot basically becomes ineffective.On the other hand, Ubuntu should boot fine, whether from USB or once you have installed it (I say should, because even though all documentation I ever read says "will", I have had to disable secure boot in the past to run linux). If secure boot would prevent that, it would prevent GRUB from loading. In that caseGrub: Grub 1.99 needed or grub_divmod64_full
Terms and rules Privacy Security You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. Home Forums General Development Phoenix OS Phoenix OS News, Q&A & Development Apr 29, 2018 #1 So I currently have Win10 and Ubuntu installed each on a separate partition. I installed Phoenix OS through windows and it didn't add up on grub. I have to select Win10 through grub and then when Win10 boots up I have to start Phoenix OS through shortcut which reboots my system to Phoenix OS. What I want is to install Phoenix OS on Ubuntu's partition and add it to grub menu. Anyone kind enough to help me with this? Note that made a bootable Phoenix OS USB but it didn't work (didn't work as it doesn't boot at all, doesn't even detect it). Apr 30, 2018 #2 So I currently have Win10 and Ubuntu installed each on a separate partition. I installed Phoenix OS through windows and it didn't add up on grub. I have to select Win10 through grub and then when Win10 boots up I have to start Phoenix OS through shortcut which reboots my system to Phoenix OS. What I want is to install Phoenix OS on Ubuntu's partition and add it to grub menu. Anyone kind enough to help me with this? Note that made a bootable Phoenix OS USB but it didn't work (didn't work as it doesn't boot at all, doesn't even detect it). Used Rufus ? If Rufus can't made live boot possible ,i doubt any other will make .For Ubuntu installation ,check there are various guides around to put Phoenix Os files on root of Ubuntu in seperate folder and edit 40custom to point kernel and initrd Similar threads Home Forums General Development Phoenix OS Phoenix OS News, Q&A & Development Top Liked Posts There are no posts matching your filters. So I currently have Win10 and Ubuntu installed each on a separate partition. I installed Phoenix OS through windows and it didn't add up on grub. I have to select Win10 through grub and then when Win10 boots up I have to start Phoenix OS through shortcut which reboots my system to Phoenix OS. What I want is to install Phoenix OS on Ubuntu's partition and add it to grub menu. Anyone kind enough to helpGRUB/Restore the GRUB Bootloader - Manjaro
Options.Select UEFI Firmware Settings.Click Restart to restart the system and enter UEFI (BIOS) setup utility.F10 BIOS setup -> System Configuration tab ->Boot Options -> OS Boot Manager ->Ubuntu -> (select the Ubuntu option and move this option up to the top of the list) ->F10 Save and Exit (press F10 to save Ubuntu as the default boot option) ->F10 (press F10 again to save the changes to the BIOS/UEFI setup utility)When the computer restarts, the Ubuntu boot menu will be shown. karel121k129 gold badges294 silver badges324 bronze badges answered Dec 1, 2018 at 1:45 abchen2015abchen2015911 silver badge3 bronze badges 2 Live boot Ubuntu and select try Ubuntu option from the GRUB menu that appears and then install boot repair by typing in following commands. sudo add-apt-repository ppa:yannubuntu/boot-repairsudo apt-get updatesudo apt-get install -y boot-repair && boot-repair answered Jan 10, 2019 at 14:59 arnavarnav1092 bronze badges There is a setting in /etc/default/grub called GRUB_TIMEOUT_STYLE=hidden which prevents the GRUB menu from showing during the timeout period unless you press the Esc key. Check to see if this setting is enabled by GRUB_TIMEOUT_STYLE=hidden, and if it is enabled open the /etc/default/grub file for editing in nano text editor and disable it.sudo nano /etc/default/grubComment out the line that says GRUB_TIMEOUT_STYLE=hidden by preceding it with a # character. Make sure that the GRUB_TIMEOUT value there is set to a value larger than zero, for example GRUB_TIMEOUT=10. Save the file. Then run the update-grub command and reboot:sudo update-grub sudo rebootNano text editor keyboard shortcutsUse the keyboard combination Ctrl + O and after that press Enter to save the file to its current location.Use the keyboard combination Ctrl + X to exit nano. Other useful linksHow to repair GRUB2 when Ubuntu won't boot Using EasyBCD to boot to GRUB from Windows boot menu Installing GRUB2 Ubuntu documentation wiki answered Jan 4, 2019 at 10:50 karelkarel121k129 gold badges294 silver badges324 bronze badges 1 I'm presuming GRUB successfully installed, but something is clearly amiss. I know you said you already tried bcdedit, but here's the command to set it: bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi. If you set this and could not boot, as you have indicated already, don't forget to rescind the change you made using bcdedit /deletevalue {bootmgr} path \EFI\ubuntu\grubx64.efi.Try following the steps detailed in Enkouyami's answer (i.e. chrooting into your installed Ubuntu system from the live CD and then reinstalling grub manually).If the above fail, you could try installing grub2win. This allows you to boot grub2 from your Windows EFI firmware by making edits to the boot code. Be sure to follow the instructions carefully on the project's page if taking choosing method.Another method instead of grub2win is Super Grub2 Disk, which is a live CD that allows you to boot into a variety of operating systems. I would try this first instead of grub2win, as there is less risk involved if something goes awry. I have not used Super Grub2 Disk personally, but I hear it is an incredibly useful tool. Using this tool, you can restore. Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Download GRUB - GRUB 2.12, GNU GRUB is a Multiboot boot loader. Ice Walkers. Sign in with Facebook. Login. Linux Software. GRUB 2.12. Submit New Release; Edit GRUB Information; Submit a New Software; Multiboot boot loader. Friday, Decem. Posted in Blog, General and tagged Grub Config, Grub Error, Super Grub Disk 2 Iso Download, Super Grub Disk Tutorial, Super Grub Repair Disk, Super Grub Rescue, SuperGNU GRUB Manual 2.12: Installing GRUB using grub-install
What if you’re dealing with an active grub infestation? Another side of lawn grub control comes into action: the curative methods. These are ways you can deal with active infestations. Here’s how you can treat the grubs in your lawn: Curative chemical insecticides. Carbaryl and trichlorfon are considered curative treatments. You apply them once you’ve noticed grubs in the grass. They are short-lived products that are effective immediately. Treated grubs turn yellow or brown within a week, so reevaluate the turf the week after that to see if the chemicals have succeeded. Milky spore disease. Another grub treatment for your lawn is to fight grubs with milky spore disease. “The commercial milky spore disease is only for Japanese beetles,” Shetlar says. “Even then, milky spore disease is a weak pathogen that results in 20% to 25% infection at best.” Neem oil is your ally. Neem oil is an effective pesticide against grubs while also being safe for pollinators. For a DIY solution, mix neem oil and water according to label instructions. Spray your yard with the solution using a pump sprayer or a hose-end sprayer. Apply in late summer or early fall. Turn to natural enemies. Naturally occurring pathogens (fungi, bacteria, protozoa) kill or weaken grubs; they already exist in the soil, but chemicals you apply will kill them, so you might want to hold off any other chemical grub treatment and let the pathogens do their work.Ground beetles and ants are beneficial insects that feed on eggs and young grubs. Parasitic wasps and flies go after older grubs. Consider beneficial nematodes. Shetlar says, “There’s a very steep learning curve to using the insect parasitic nematodes.” They can only be effective as a lawn grub treatment when used curatively, and even then, only on small affected areas. However, Shetlar did let on that the most experienced organic lawn care professionals may have the knack for using beneficial nematodes as an effective lawn grub killer. “In that case, they work quite well,” he said. “You can typically get 60% to 100% control with the nematodes when they’re used at the right time in the right way.” When to Treat Your Lawn for Grubs The best time to apply preventative grub control products is from mid-April to mid-June, or as a general rule, in summer or early fall, when the eggs have not hatched yet or the grubs are still small. If you missed this time window, apply a curative treatment for grubs into the lawn as soon as the first signs of grub damage begin to appear. When to Call Pest Control Pros If in doing the tally, you find more than six grubs per square foot, it’s a good timeComments
Try opening a terminal and runningsudo chmod +x /etc/grub.d/20_memtest86+sudo update-grubCheck to see if it's theregrep memtest /boot/grub/grub.cfgJust done the same as I had it disabled$ cat /boot/grub/grub.cfg | grep memtest$ sudo chmod +x /etc/grub.d/20_memtest86+[sudo] password for hob: $ sudo update-grubGenerating grub.cfg ...Found linux image: /boot/vmlinuz-3.2.0-24-genericFound initrd image: /boot/initrd.img-3.2.0-24-genericFound linux image: /boot/vmlinuz-3.2.0-23-genericFound initrd image: /boot/initrd.img-3.2.0-23-genericFound memtest86+ image: /boot/memtest86+.binFound Ubuntu 11.10 (11.10) on /dev/sda6Found Trisquel 5.5 (5.5) on /dev/sda8Found Ubuntu 12.04 LTS (12.04) on /dev/sda9done$ cat /boot/grub/grub.cfg | grep memtest### BEGIN /etc/grub.d/20_memtest86+ ###menuentry "Memory test (memtest86+)" { linux16 /boot/memtest86+.binmenuentry "Memory test (memtest86+, serial console 115200)" { linux16 /boot/memtest86+.bin console=ttyS0,115200n8### END /etc/grub.d/20_memtest86+ ###You could try creating the file if it's not there, using nano in a terminalsudo nano /etc/grub.d/20_memtest86+or with a gui editorgksudo gedit /etc/grub.d/20_memtest86+Fill it with#!/bin/shset -eif [ -f /usr/lib/grub/grub-mkconfig_lib ]; then . /usr/lib/grub/grub-mkconfig_lib LX=linux16elif [ -f /usr/lib/grub/update-grub_lib ]; then . /usr/lib/grub/update-grub_lib LX=linuxelse # no grub file, so we notify and exit gracefully echo "Cannot find grub config file, exiting." >&2 exit 0fi# We can't cope with loop-mounted devices here.case ${GRUB_DEVICE_BOOT} in /dev/loop/*|/dev/loop[0-9]) exit 0 ;;esacprepare_boot_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/")"if test -e /boot/memtest86+.bin ; then MEMTESTPATH=$( make_system_path_relative_to_its_root "/boot/memtest86+.bin" ) echo "Found memtest86+ image: $MEMTESTPATH" >&2 cat &2# cat Make sure to run the chmod +x command on it afterwards.I'd be a bit concerned that it's missing though - do you have everything else in grub.d ?$ ls /etc/grub.d/00_header 10_linux.bak 20_memtest86+ 41_custom05_debian_theme 10_linux.dpkg-old 30_os-prober README10_linux 20_linux_xen 40_custom
2025-04-13One of the issues I encountered after dual booting Windows with Linux is the missing Windows entry from the grub menu.Here's the scenario. Windows was present on the computer. I installed CachyOS alongside Windows. I selected to install the Grub bootloader that allows booting into Linux, Windows (and any other OS present on the system) along with the option to access UEFI.Only this time, Grub did not show Windows in the menu 😔Missing Windows from Grub bootloaderThat was disappointing but not surprising because I am aware that this is a feature.Let me show you how you can fix this by enabling os-prober feature in Grub and then updating it.Step 1: Enable os-prober in grubGrub config file is located at /etc/default/grub. If you open it via Nano or some editor, you'll see at the end of this file that os-prober is disabled by default sighting security reasons.If you are familiar with any terminal-based text editor, use it to uncomment the line # GRUB_DISABLE_OS_PROBER=false by removing the # at the beginning of the line.However, if you are absolutely new to the command line, you can use this command in the terminal:echo "GRUB_DISABLE_OS_PROBER=false" | sudo tee -a /etc/default/grubIt will ask for your password. It should be the same account password you use to log in to the system.🚧When you type the password in Linux terminal, nothing is reflected on the screen. It feels as if your system is hanged, as there is no visible feedback. Don't worry. It's a security feature and most Linux terminals won't even show asterisks (*) as you enter the password. Just type it in and enter.With os-prober enabled, Grub will look for the presence of other operating systems in EFI folder and will add them in the bootloader menu.There is one little problem. The config changes won't take place unless you update grub.Step 2: Update grubOn Ubuntu and some other distributions, there is a dedicated command to update grub:sudo update-grubHowever, on Arch and some other distributions, you'll end up with update-grub command not found error.That's because update-grub is not a standard command. It is just la stub for this command:sudo grub-mkconfig -o /boot/grub/grub.cfgRun the above command if your system doesn't have update-grub.It should show an output like this:And as you can see in the above output, grub is probing for other OS and has found Windows boot manager. This is an indication that when you reboot the system, grub should show Windows in the available option.And Windows is back in GrubStill no Windows boot manager?See, this method only works when dual boot succeeded properly and you have all EFI settings located in the same folder under the same ESP partition.If that's not the case, you could try accessing
2025-04-15The No Such Partition Grub Rescue error is also known as the ‘Death Screen of Linux’. And this error mainly occurs when your grub configuration is messed up for some reason. In this article, we will try to solve this problem of ours using a live CD image of the same OS and try to fix your installation.Pre-requisitesYou have a live CD/DVD/USB of the Operating System (must be of the same version).You have a stable internet connection.And you do not have a Wubi (Ubuntu inside Windows) installation on your system.Let’s get started!6 Easy Steps to Fix No Such Partition Grub Rescue ErrorWe need to re-install grub because it is either deleted or corrupt. And to re-install, we will copy the grub file from the live USB to your grub directory. Note that this will remove any custom configuration you have made to the grub file. Follow these steps to fix your grub file.1. Locate your Root/boot partitionBoot from the Live USB stick and, in the terminal, type the following commands to gain administrative privileges :Now, type the following commands to know your disk partitioning structure :Output Of Fdisk CommandIn the output, you will see text like /dev/sda1 or /dev/sda2 etc. If you have a separate Boot partition (EFI filesystem), note its location (usually it is 500 MB). And, if you don’t have a separate boot partition, then locate your root (/) partition. If you don’t know where your root is located, then you have to guess. Typically, it’s 30-50 GB in size.2. Mount the Root/Boot PartitionTo modify the changes in our root/boot partition, we will have to mount it first. To do that, type the following commands in your terminal :sudo mkdir /mnt/tempsudo mount /dev/sda2 /mnt/tempYour sdX number can be different from mine, use the number where your root partition is located. And for separate boot partition, mount it as follows :sudo mkdir /mnt/temp /mnt/temp/bootsudo mount /dev/sdXY /mnt/temp # Mount the main partition.sudo mount /dev/sdXZ /mnt/temp/boot # Mount the /boot partition.3. Be CHROOTNow that we have mounted the partition, we will have to mount several items in preparation of the chroot, run the following commands :for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt/temp$i; donesudo cp /etc/resolv.conf /mnt/temp/etc/resolv.confsudo chroot /mnt/tempIf everything went well, you will see ‘root’ in the terminal prompt.4. Update apt and Purge GRUB2 packagesRun the following commands as chroot to update apt :Now, purge the old damaged grub files using these commands :apt-get purge grub grub-pc grub-commonSelect yes in the promptA prompt will appear asking for your confirmation to remove GRUB2 press and then press enter.5. Re-install GRUB bootloaderWe need to keep a few things in our mind before we we-install GRUB :While installation, it will ask you to add extra kernel options, if you don’t know about it then you probably don’t need it too. Just press the Tab key to navigate to Ok and press Enter.Installation notes will appear before your screen. Again, press Ok to continue.It will now ask you
2025-04-02Up now that we are able to:Time zone and clock syncMeaning sync to the hardware clock (for me this is UK, but you can select yours from the appropriate folder)ln -sf /usr/share/zoneinfo/GB /etc/localtimehwclock --systohcSet the LocaleLet’s set the system locale – first we will need an editor (I chose VIM)pacman -S vimvim /etc/locale.genI simply un-commented the line I needed. Then you run:locale-gento generate your localeSet the languageLet’s set the languagevim /etc/locale.confSet the keyboard layoutLet’s now set the default keyboard layoutvim /etc/vconsole.confSet the hostnameLet’s do the hostname next – put in the Ipv4 localhost address and Ipv6 localhost address, and also the hostname (you can fully qualify this if you need a search suffix, or are in an environment with a domain etc.)vim /etc/hostnamevim /etc/hostsPassword set for root accountLet’s set the password nextpasswdBootloader ConfigNow the majority of the config is done and will persist.Next we need to choose a bootloader. There are an abundance of these available, and there is a nice comparison chart here to allow you to make the best choice: usually go for GRUB as it does everything that I need. I have been known to use LILO in the past, but this doesn’t support UEFI. I find GRUB works for me now, and I know how to customise it to how I like.For this tutorial I will be using GRUB. As we are using a UEFI, this bit can be quite tricky. Full concentration required here!I will suggest that you have a look at the Arch documentation here: implement UEFI differently which may change the way that you proceed.I will also go through how we will get it working for this virtual machine. So we need to install grub and efibootmgr.Install the bootloaderpacman -S grub efibootmgrConfigure grubNext we need to install grub based on our efi mount point location for our UEFI system (/efi)grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUBGenerate grub configNow let’s generate the config file for grubgrub-mkconfig -o /boot/grub/grub.cfgRemove install media and rebootOK now – time to remove the install media, and try this out!If you are lucky this will work first time Let’s exit our changeroot environment
2025-04-12