grub error not an assignment

• Introduction
• Privacy Policy
• Release Information
• Release Engineering
• Porter's Handbook
• Developer's Handbook
• Manual Pages
• Presentations and Papers
• Documentation Project Primer
• All Books and Articles
• Mailing Lists
• User Groups
• FreeBSD Journal
• Q&A (external)
• Project Ideas
• Git Repository
• GitHub Mirror
• Code Review (Phabricator)
• Continuous Integration Service
• Security Information
• Bug Reports
• Submitting Bug Reports
• Monetary Donations
• Hardware Donations

• Search forums

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature currently requires accessing the site using the built-in Safari browser.

• Base System

Solved   Error: Not an Assignment

• Thread starter usakhncit
• Start date Sep 23, 2019

Karma: 34 Posts: 241

• Sep 23, 2019

Hi I have dualbooted FreeBSD and Linux, using GRUB as bootloader. Both OSes are booting fine, except a tiny hiccup. After I select FreeBSD from GRUB, then a new screen appears saying: Code: error: not an assignment. Press any key to continue Although, it is harmless and disappears in few seconds. But I want to fix it and remove this error screen. Kindly guide me in this respect that where this error is coming from and how can I fix it. Please check attached image. Thanks  

Attachments

Administrator

Karma: 18,143 Posts: 45,780

Probably a typo in your Grub configuration.  

• Thread Starter

SirDice said: Probably a typo in your Grub configuration. Click to expand...

I have fixed the problem. SirDice was right. There was a small problem with grub configurations. Following is the correct configuration: Code: #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry "FreeBSD-12.0-RELEASE" { insmod ufs2 set root='hd0,msdos4' chainloader (hd0,4)+1 }  

• This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…

Ubuntu Documentation

• Official Documentation
• Community Help Wiki
• Page History
• Login to edit

Grub2 / Troubleshooting

• GRUB has failed to find even the most basic information, usually contained in the MBR or boot sector.

GRUB 2 Terminal Commands

grub rescue>

General troubleshooting preparation, boot-repair.

• sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update sudo apt-get install -y boot-repair && boot-repair

Search & Set

How & where to search.

• "Tab completion" may work - enter part of the filename and press the TAB key.

Specific Troubleshooting

• The kernel cannot be loaded until the 'linux' module is loaded.
• A Linux kernel and initrd.img must be located and loaded.

Editing the GRUB 2 Menu During Boot

Key Points About Terminal Menu Editing:

• If the menu is displayed, the automatic countdown may be stopped by pressing any key other than the ENTER key.
• In certain circumstances, if holding the SHIFT key method does not display the menu pressing the ESC key repeatedly may display the menu.
• Press the 'e' key to reveal the selection's settings.
• Use the UP/DN/Left/Right cursor keys to navigate to the desired point for editing.
• After starting to type the kernel or initrd name, press TAB.
• If additional characters are not added, look at the bottom of the menu as there may be multiple choices. Add characters until only one entry is visible at the bottom, then TAB again.
• The choices are listed at the bottom of the screen as a reminder.

Menu Editing Examples

Post boot follow up.

• sudo update-grub
• Ensure the paths and kernel/initrd image versions are correct.
• Confirm the UUID numbers.

Fallback mode

Grub 2 errors, selected problems and bugs, external drive installs and ''grub-pc'' updates, external drive installs and mbr selection, boot partition is in logical volume whose volume group contains a snapshot, insmod fails with "error: no such disk".

Grub2/Troubleshooting (last edited 2013-02-27 11:10:09 by fw-tnat )

The material on this wiki is available under a free license, see Copyright / License for details You can contribute to this wiki, see Wiki Guide for details

How-To Geek

How to use grub rescue to fix linux.

Put the boot in.

Quick Links

When your bootloader doesn't boot, using the grub shell, using the grub rescue shell, other possible remedies, key takeaways.

If your GRUB shells shows a "grub>" prompt, you can use the ls , set , linux , and initrd commands to fix your Linux system. If instead you see a "grub rescue>" prompt, use set , insmod , linux , and initrd commands to boot your PC.

If your Linux computer can't boot into its operating system, you're likely to find yourself staring at a prompt in the GRUB shell. Follow these steps to repair your broken boot processes.

There are very few computer problems that make your heart sink as deeply and rapidly as a failure to boot . Without a working operating system, your computer isn't really a computer.

It can be a very opaque problem, with no easy way to drill down into the root cause. Without access to Linux, you can't use any of the usual diagnostic tools and processes you'd use to investigate the problem. And without determining what the issue is, how can you fix it?

On Linux,  GRUB  is the software that controls the boot process. If you have multiple operating systems installed , it let's you pick the one you want to boot into.

GRUB is controlled by its configuration. It relies on other supporting files too, in order to perform its functions. If any of these are missing or become corrupted, GRUB won't work. Changes to the hard drives and partitions of your computer need to be reflected in GRUB's configuration. If this isn't the case, GRUB's instructions won't make sense, and your boot process won't work.

Related: How to Burn an ISO File to a USB Drive in Linux

As a side note, what we all call GRUB is actually GRUB 2. This is an advanced version of GRUB that was released back in 2012. Amongst other changes, it changed the way the "grub.cfg" file was created , and let you boot from removable media.

If GRUB cannot load an operating system , you'll be left staring at a prompt in the GRUB shell. This is a minimalist environment that will let you perform a handful of actions. Done correctly, however, these steps can resurrect your computer.

There are two different GRUB shells. Depending on the root cause of the problem, you might find yourself at a GRUB shell prompt:

or at a GRUB rescue shell prompt:

grub rescue>

The GRUB rescue shell is even more restricted than the GRUB shell, but it still packs enough punch to get your computer to boot. Once your computer has booted, you're in a much better position to cure the root cause.

The GRUB shell is a command line interface that lets you use a small subset of Linux commands. If you find yourself here instead of at your usual login screen, it means your boot process is messed up.

The commands you have access to are not the same as the usual Linux versions. For example, the GRUB shell ls command isn't the Bash ls command. It has very little in common with it. We can see this by using the --help option.

It lists five options only. That's a far cry from the dozens of options supported by ls in Bash. Nevertheless, even with our somewhat muted palette of commands, we can still rectify the situation.

At the prompt, type ls and hit "Enter."

On this computer, it lists three items.

• (hd0)  is the first hard drive.
• (hd0,gpt1)  is the first partition on the first hard drive.
• (hd0,gpt2)  is the second partition on the first hard drive.

The "gpt" label stands for GUID partition table . We need to include the brackets " () " when we reference a partition, but we can omit the label.

To look at the partitions in turn, we'll use ls .

We've found that the second partition has a Linux file system on it. We'll investigate a little further by looking at the root directory of that partition.

ls (hd0,2)/

Clearly, this is the Linux partition , with the boot directory on it. This is where the GRUB files, Linux boot images, and other boot files are stored.

On this computer, we'll need to reference partition (hd0,2)  when we issue our commands. On your computer you'd use whatever partition you find your Linux installation on.

We can use the cat command  to look text files by appending the directory path and filename to the partition name, like this:

cat (hd0,2)/etc/issue

On multi-boot installations, this is a useful way to verify you're on the right partition. It's also great for looking inside configuration files.

Here, we're using the ls command with the -l (long) and -h (human readable sizes) options to list the files in the "/boot" directory.

ls -lh (hd0,2)/boot

To get this computer to boot, we need to tell GRUB that our newly discovered Linux partition holds the boot files.

set root=(hd0,2)

We need to specify which Linux kernel to boot from. We do this with the linux command. Note that we also have to provide the root directory using the usual Linux hard drive and partition naming scheme.

linux /boot/vmlinuz-6.2.0-20-generic root=/dev/sda2

On our example computer, we're using (hd0) which is the first hard drive. This is called  sda in the usual Linux nomenclature. We found that the second partition is the Linux partition, so we need to specify sda2 .

Your machine might be different. For example, if your Linux partition is reported as (hd2,1) that means partition one on the third hard drive, or sdc1 .

We also need to specify which RAM -based file system image to use when the computer boots. This must use the same numerical component as the Linux kernel we're using.

initrd /boot/initrd.img-6.2.0-20-generic

Now, to boot our system, type "boot" and hit "Enter."

This should boot your computer up into Linux. That's got us running again, but we still need to fix GRUB so we don't need to do this every time we start our computer.

We'll run update-grub . This will scan our system, identify operating systems, and create a new GRUB config. We need to run this as the root user.

sudo update-grub

Rarely, you might need to reinstall the GRUB bootloader too, using grub-install .

sudo grub-install /dev/sda

Note you don't need to specify which partition to install on, just which drive. In normal installations, it's the same drive your Linux is on.

The proof of the pudding comes with the next reboot. Your computer should reboot normally.

Related: How to Configure the GRUB2 Boot Loader's Settings

Depending on the nature of the boot problem, you might not get dropped into the GRUB shell. You might be left in the GRUB rescue mode. If that's the case, your prompt will look like this:

The commands we need to issue in this shell are different. We need to use ls to find the Linux partition, just as if you were using the GRUB shell. Having identified the Linux partition, you can go ahead and enter these commands.

Remember to use the drive identifiers and kernel version numbers that are correct for your computer. The insmod command loads kernel modules.

set prefix=(hd0,2)/boot/grub

insmod normal

insmod linux

You can then type "boot" and hit "Enter" to reboot your computer. Once it has rebooted and you have logged in, update GRUB with the update-grub command.

If the issue turns out to be missing boot files, such as the "vmlinuz" and "initrd.img" files, you can boot your computer from a Live DVD or bootable Linux USB flash drive , and copy the missing files into place.

Note that the "vmlinuz" and "initrd.img" files must have the same version numbers in them, because they work as a matched pair.

Related: How to Create a Bootable Linux Live USB on Your Mac

You are not logged in.

• Topics: Active | Unanswered
• »  Installation
• »  [SOLVED] GRUB installation fails - will not proceed with blocklists

#1 2017-04-22 11:51:38

[solved] grub installation fails - will not proceed with blocklists.

I am trying to install Archlinux on VirtualBox. Everything goes fine until the point when I try to install GRUB.

The structure of disk and details are visible here: https://ibb.co/mAfK6Q

Basically I have two partitions only /dev/sda1 - main /dev/sda2 - swap

the first starts on 2048 which should be fine (from what I read here https://bbs.archlinux.org/viewtopic.php?id=169124 )

in SYSTEM settings for this virtual machine I have disabled EFI. partitions were created using gdisk

regards Rafal

Last edited by rafdre (2017-04-22 14:11:11)

#2 2017-04-22 12:05:15

Re: [SOLVED] GRUB installation fails - will not proceed with blocklists

grub-install : error: will not proceed with blocklists

That is not the full error message, please do not crop command output when posting here.

https://bbs.archlinux.org/viewtopic.php?id=57855

IIRC, the full error message explains the source of the problem.

You need to create a BIOS boot partition to house the non-UEFI GRUB bootloader on your GPT disk; select type "ef02" in gdisk.

However, the recommended approach for a non-UEFI system is to use a traditional "MBR-style" (msdos) partition table rather than the GUID type you have created.

To do this, run `sgdisk --zap-all /dev/sdX` to clear the GPT then use `fdisk` to create an "ms-dos" type partition table instead (this is the default option with that program).

Are you infected with Wetiko?

#3 2017-04-22 13:14:06

thanks a lot for quick answer

I have not posted anything else because of the following reason: 1) as I said this is virtual machine, so I cannot simply COPY& PASTE text. Therefore I provided a link to the screenshot 2) actually what I posted is the only ERROR I saw. The rest were WARNINGS. Here I provide more details:

I hope I copied it 1:1 (thats a challenge while manual copy is done)

what I did now is : I started again from scratch, but this time I used fdisk instead of gdisk. I did basically what is described here http://tldp.org/HOWTO/Partition/fdisk_partitioning.html

It worked wonderful. I was able install GRUB without issues, but that's all I could accomplish so far :-(

Now - when I select entry in GRUB system does not start saying "no such device"  followed by UUID

Changing entry (command "e" in GRUB) from UUID to something like /dev/sda1 does not help.

My steps in installation process were quite simple: 1) define partitions 2) pacstrap /mnt base 3) genfstab -p /mnt >> /mnt/etc/fstab

later CHROOT and installation of GRUB

have I missed something? Why GRUB does not recognize hard disk device?

#4 2017-04-22 13:36:44

I see the issue is not new for ARCHLINUX. I found this video on YouTube : https://www.youtube.com/watch?v=2LgdfoN7b2Q

I have checked and indeed the UUID in /etc/fstab is different than this fake one in grub.cfg file

#5 2017-04-22 13:49:09

I see the issue is not new for ARCHLINUX.

Also, please mark the thread [SOLVED]

#6 2017-04-22 14:10:49

I think 'welcome' is not the right word here :-) , but thanks. I am using ArchLinux for quite some time. Right now I have debian/archlinux on one PC (brix) and archlinux on my small home server. I used to have archlinux together with SLES/windows on another laptop , but after nVidia stopped support for drivers (GeForce 360M) I decided to use there openSuse as 3rd system (I am using this laptop basically only with projector to watch movies). SUSE is the distro I used for quite long (still think its a good distro...especially for beginners)

Regarding the issue with GRUB & UUID: the video provides workaround but not good long term solution. They advise to use Ubuntu Live CD only because of gedit tool (they are not familiar with 'vi' :-) ? ). Advice from video is to manipulate grub.cfg

if you open grub.cfg it says clearly that file was generated.

I used better way than advised on that video. I simply regenerated the files using this command:

Lessons learned 1. When you install ArchLinux on VirtualBox is better to user fdisk (and not gdisk) to prepare a disk partitions 2. After GRUB installed - if you see errors like "error: no such device: ad4103fa ", then its good to try to generate new config file with 'grub-mkconfig'

Board footer

Atom topic feed

Powered by FluxBB

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

GRUB2 booting: efidisk read error & prefix is not set

I have a booting USB stick with some iso-image, based on Arch Linux. It loads through efi and then comes to Grub 1.99, where I can choose the iso images. I can load them without any problems, but before I see the menu of the Grub some error messages appear:

error: "prefix" is not set error: efidisk read error

USB stick is formatted in FAT32 and has a partition table msdos.

Here is my /boot/grub/grub.cfg

insmod video insmod font insmod jpeg insmod gfxterm set prefix=/boot/grub/grub.cfg loadfont /boot/grub/unicode.pf2 set gfxmode=auto terminal_output gfxterm background_image /boot/grub/background.jpg set default=0 set timeout=10 set menu_color_normal=white/black set menu_color_highlight=black/light-gray menuentry "image.iso" { set isofile="/images/image.iso" loopback loop $isofile set root=(loop) linux /isolinux/vmlinuz isofile=$isofile splash quiet initrd /isolinux/initrd }

These settings works without any problems. At least, I can see my background image and the styles has been changed.

I also checked from the Grub shell the parameters

root=hd2,msdos1 //means that I have a correct path, otherwise actually it doesn't boot.

I tried different versions of this prefix // /boot/grub/ // /boot/grub/grub.cfg // /efi/boot/

I would be glad to hear what can be the problem:)

p.s. Was reading also that can be sth with GPT partition table, but in this case it doesn't boot with my computer.

Thanks for helping.

You must log in to answer this question.

Browse other questions tagged linux boot grub multi-boot grub2 ..

• The Overflow Blog
• How do you evaluate an LLM? Try an LLM.
• Why configuration is so complicated
• Featured on Meta
• New Focus Styles & Updated Styling for Button Groups
• Upcoming initiatives on Stack Overflow and across the Stack Exchange network
• Google Cloud will be Sponsoring Super User SE

Hot Network Questions

• Is this Python/Pygame that draws a maze well structured?
• Why two um in this sentence
• Is it possible for magical Universities to become powerful political entities, and is my structure for the same sensible?
• For every sequence of nonempty open sets there is a disjoint sequence of nonempty open sets "below" it
• Avoiding throw because we are not sure they will always be caught
• Which consulate should I contact when my country doesn't have one in the destination country?
• Which is the denominator of the Brier score for joint multiple variables predictions?
• Who is the target audience for the $60+ academic books?
• How bright would it be at night on my planet?
• How can I fit a board to walls intersecting at an obtuse angle?
• Why didn't the full logo appear?
• Load balancer with HAProxy
• What was that glowing green thing that soldiers threw in the corridor of the White House in the final battle scene of “Civil War?”
• Success of Aggressive Rebuttal Strategy
• Is it okay for a potential advisor to call a post-doc "pretentious"?
• Why do valence electrons not push each other away?
• Can two interfering light beams create radio waves?
• What does "6" mean in glibc.so.6?
• Does the equivalence principle only apply for the gravitational field of an infinitely sized body?
• In which US states are hush money payments illegal?
• Run function at end of pipe
• Is there no liberal arts "school" that is also a research "school"?
• Science Fiction boardgame.Two players (maybe more possible) Torus shaped spaceship gameboard You control reproducing aliens. Played 1986-1988
• Embarrassment at work caused by a supervisor's reaction due to my shingles disease

Grub error not an assignment

I have an Ubuntu 20.04 on a desktop with 1 hard disk. For the last 2 or 3 months, the boot has slowed down and during bootup, there is an "error: not an assignment" message that flashes and disappears. I checked the questions in this forum from the past, and have checked the syntax of the /etc/grub.d/default file.. it is a very standard file and i don't see any syntax changes.. I have also downloaded grub-customiser and verified the grub config and there are no errors - but the boot is slow, and "error: not an assignment" still persists.

I do not have any custom config under 00_header, or 10_linux or 40_custom.

Is there anything else i need to check?

Update for @ChanganAuto: No errors when running 'sudo update-grub'

@pasmanpasmański, thank you and noted. Updated /etc/default/grub, and ran 'sudo update-grub' and rebooted.. no change, i still get the error:not an assignment message.

Update: Dec 10

Commented out the preload modules, ran sudo update-grub and still no luck.. the error: not an assignment message persists

Update: resolved

After reading through a few more posts, I finally decided to run boot-repair - and it seems to have fixed my problem - the error message has disappeared - though it is a bit sad not knowing exactly what caused it or how it was fixed - boot repair info is below in case it is useful https://paste.ubuntu.com/p/XHZMck23s6

After reading through a few more posts, I finally decided to run boot-repair - and it seems to have fixed my problem - the error message has disappeared - though it is a bit sad not knowing exactly what caused it or how it was fixed - boot repair info is below in case it is useful paste.ubuntu.com/p/XHZMck23s6

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

GRUB Rescue - setting boot and prefix again and again

I almost know nothing about coding in Ubuntu. I am currently dual booting ubuntu 16.04 LTS and Windows 10. Everything was fine . But today an error occured saying

"can't find filesystem"

and then grub rescue begins . After searching for some time I have found out solution that tells to do these:

I know that ls is listing harddrive partitions(let me know if I am wrong) .Then(in set prefix ) I need to select a partition . There came a error when I selected msdos5. After some try I selected msdos6. Then it ran . But the problem is that from another solution to this problem I wrote this code:

I think I messed up . Probably , it involves which partition of the harddisks is going to boot .Now, my laptop is running after writing this code and every time I turn on the laptop the boot stuck at the beginning showing the same error & I need to write the code every time I need to run the laptop . How can I solve this issue? I probably also need to know the partition which is booting (msdos*) & I don't know how to find that.

• partitioning

• So are you typing msdos5 or msdos6, or sda5 or sda6 once booted? You may need fsck on your ext4 partition, but lets see details first. May be best to see details, you can run from Ubuntu live installer or any working install: Post the link to the Create BootInfo summary report. Is part of Boot-Repair: help.ubuntu.com/community/Boot-Info –  oldfred Jan 3, 2017 at 16:29

2 Answers 2

I got a solution for this type of problem if grub rescue> prompt occurs in booting time and you have to write a code like:

After boot Linux/Ubuntu based OS will load then open a terminal and write the command:

then type this command:

after these operation now finally reboot your system.

• 1 Worked on Manjaro as well :) –  Brij Sep 3, 2017 at 17:58
• Worked on Debian Jessie –  ako Mar 14, 2018 at 19:32
• Worked on Linux Mint Sylvia –  Valid Jul 14, 2018 at 2:00
• Worked for ubuntu 19.10 efi, ... had to use (lvm/vgaubuntu-root) ... > normal took me straight to my normal grub screen. Thanks!! –  Keldon Alleyne Feb 2, 2020 at 14:15
• Ends with a "Stage1 not read correctly" error, every single time. After almost an entire day spent on this (three days in all trying to get this disk, which works find in one machine, simply migrated to another so I can copy it), I have concluded there is no fix anywhere on the internet, and that includes rescatux and Super Grub 2 disk, which I have read can both fix just about anything, and can't fix this error. I also tried boot-repair, or rather, I tried to figure out how to install boot-repair, but that doesn't seem to be possible anymore either. –  John Smith Nov 5, 2023 at 3:47

In the above answer by deepak bundela, i think the following line needs to be corrected:

(am repeating the * as bundela put it so as not to distract from the real issue)

i was unable to find a grub environment variable called boot, and as far as i recall it has always been set root=()

i am somewhat confused by all the commenters who said that it worked on their distros. did they do a set boot or a set root ?

at the grub rescue> prompt, if one just types set it lists all the env variables that have been set. in all my grub rescue adventures, i've never seen the boot env variable being listed.

• Very curious that everyone missed that. Good catch, Ram. –  Frobozz Dec 3, 2022 at 18:47

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged boot dual-boot grub2 partitioning grubrescue ..

• The Overflow Blog
• How do you evaluate an LLM? Try an LLM.
• Why configuration is so complicated
• Featured on Meta
• New Focus Styles & Updated Styling for Button Groups
• Upcoming initiatives on Stack Overflow and across the Stack Exchange network
• AI-generated content is not permitted on Ask Ubuntu
• Let's organize some chat workshops

Hot Network Questions

• level shift a 0-20V pulse to +,-10V without deteriorating the rise time
• Measuring the resistance of an LED -> getting conflicting values
• Avoiding throw because we are not sure they will always be caught
• Is a Grey paladin of Asmodeus possible?
• 6-Round Word Search
• Reviewer rejects a paper and then publishes the same results as their own?
• How can I fit a board to walls intersecting at an obtuse angle?
• Why didn't the full logo appear?
• What is this vegetable?
• Science fiction story with a made up religion called Sa'tong
• Enforce contract on burglars
• which refers to what?
• ID a 1930's-40's aircraft
• Can a player cast an instant at anytime during an opponent's turn?
• What was Silk Spectre II's relationship with superheroics?
• I think my MTB chain is modified ( shortened )
• Different estimates of Least Squares and Maximum Likelihood Estimates under non-normality
• Does the equivalence principle only apply for the gravitational field of an infinitely sized body?
• I forgot an item on board an airplane on a regular flight. Who should I contact to get it back?
• Which is the denominator of the Brier score for joint multiple variables predictions?
• Is there a good term for a 'paper trail' that actually consists of e-mail communication?
• Can porcelain tile be stored in an attic which will exceed 100 °F?
• For every sequence of nonempty open sets there is a disjoint sequence of nonempty open sets "below" it
• How to write the metaphor: "Time is like sunlight and habits are like plants. The habits that receive your time will flourish."

• Disk & Data Manager
• Partition Wizard
• Power Data Recovery
• ShadowMaker
• Media Toolkit
• uTube Downloader
• Video Converter
• Download Partition Wizard Free Edition: Download Pro Edition: Try Demo Server Edition: Try Demo
• Partition Manager

How to Fix Error: Unknown Filesystem Grub Rescue in Windows 10?

My one is an uefi bios mode Dell laptop. I dual booted my laptop with kali linux and windows 10. The both operating systems runs smoothly. I can choose any operating from the grub. After going to windows, it says important updates install them. So, I restart my laptop to update. It says in the bottom your pc may restart several times. After 75% when it restarts it says error: file’/grub/x86_64-efi/ normal.mod ‘not found. https://answers.microsoft.com/en-us/windows/forum/all/dual-boot-laptop-entering-to-the-grub-rescue-error/301e095c-1faa-4358-84bd-a0999b2fad0c

Have you ever been stuck in the same situation as stated in the post “Error unknown filesystem grub rescue”? If you encounter this error now, this post is what you need.

Grub Rescue Unknown Filesystem: Meaning and Cause

In this error, GRUB is a boot loader that loads configuration information at boot time and allows modification at boot time which means the computer cannot boot when the error. So, when the error ” grub rescue unknown file system” appears, it means that there is a boot issue on the computer.

Well, what triggers the boot issue? After an investigation, we find the issue appears after people make adjustments to the two operating system partitions (delete the system partition, resize partition or reinstall Ubuntu OS, etc.) on the same hard disk. Any of these operations may cause the boot file missing or dislocating, and GRUB can’t find the original partition where the boot file is located.

You already know the reason, so how to fix the error: unknown filesystem grub rescue in Windows 10? Keep reading to know about it.

Have you ever received the error message “conda is not recognized as an internal or external command, operable program or batch file”? Here is how to solve it.

When this “unknown filesystem grub rescue” error occurs, how should you fix it to ensure that the operating system can start normally? Here are three solutions, you can try them one by one.

Solution 1: Enter Grub Mode

For “unknown filesystem grub rescue” errors, one of the most common methods is to use the command line to fix grub.

Step 1: Find the partition where Linux installs and the grub directory.

• After entering rescue mode , type grub rescue > ls and press the Enter key on your keyboard to list all disks and partitions. For example, (hd0), (hd0, msdos1), (hd0, msdos2) …
• Type grub rescue > ls (hd0) and press  Enter Repeat this step and try each partition one by one until the contents of the partition appear instead of appearing the message:” Filesystem is unknown “.

Assume that when it is (hd0, msdos8), the content appears successfully.

Step 2: Type grub rescue > set root= (hd0, msdos8) and press the Enter key.

Step 3: Type grub rescue > set prefix= (0,8)/boot/grub and press the Enter key.

Step 4: Type grub rescue > insmod normal and press the Enter key. Then you have now exited the grub rescue mode and entered the grub mod that you should be familiar with.

Step 5: Type grub > normal and press the Enter key.

Step 6: Fix grub.

After entering Linux system, you need to update the grub part of the MBR to adapt to the new partition situation, input sudo update-grub in the terminal and press Enter .

Step 7: Type sudo grub-install/dev/sda and press the Enter key. And sda is your boot disk.

In this way, the next time you boot up the computer, there will be a normal grub boot option.

Is Gears of War on PC? What’s the Gears of War 6 PC release date? Now, this post will analyze all information about the Gears of War PC.

Solution 2: Automatic Repair BCD Files Using Windows 10

When Windows 10 fails to start, you can restart the system multiple times and the system will enter WinRE mode. Sometimes the Windows 10 system will automatically enter the Automatic Repair interface. If not, you can use the Windows 10 installation tool to enter this recovery environment.

In WinRE mode, you can follow the step-by-step instructions to repair the system.

Step 1: Boot your PC from Windows 10 installation media.

Step 2: On the Install window, click the Repair your computer option. And then choose the Troubleshoot option.

Step 3: Under the Advanced options , click the Command Prompt option.

Step 4: Type the following commands one by one in the Command Prompt and hit the Enter key after each typing to rebuild the MBR:

bootrec / fixmbr

bootrec / fixboot

bootrec / scanos

bootrec / rebuildbcd

After finishing the commands above, you should be able to successfully boot into your computer.

However, if the problem still exists, you can refer to Solution 3 to rebuild MBR.

In this post, we will introduce you to the information about Xbox One vs Xbox Series X/S. Which one is better? Just keep reading to know the answer.

Solution 3: Rebuild MBR Using a Reliable Software

If you think it is too complicated to rebuild MBR by typing commands one by one, you can use an MBR repair tool — MiniTool Partition Wizard. Compared with the above method, using this software is much easier, with only 2 steps.

MiniTool Partition Wizard Demo Click to Download 100% Clean & Safe

Step 1: Use the bootable disk to start the computer .

Step 2: Please wait for MiniTool Partition Wizard to launch itself.

Step 2: Right click the problematic system disk and select the Rebuild MBR option. Finally, click the Apply button.

In this way, you have known some ways to solve this problem “grub rescue filesystem is unknown”. Give it a try.

In this article, we will discuss what to do if the graphics driver computer does not support Miracast on your Windows 10/11.

If you started your laptop one day, you see a black screen with a message “Unknown File System”. How to deal with that? The detailed and illustrated guide may come to help. Click to Tweet

Bottom Line

Now we have reached the end of this article. In this article, we have introduced to you what the “grub rescue unknown filesystem” error is, the cause of this error, and the detailed solutions to solve it.

After trying so many solutions, you may have successfully solved your problem. If you have any suggestions about this article, you can leave a comment below. If you have any problems about MiniTool Partition Wizard, you are welcome to send us an email at [email protected] . Thank you in advance.

About The Author

Position: Columnist

User Comments :