Linux grub error no such device

Arch Linux

You are not logged in.

#1 2010-07-26 17:05:42

[Solved]GRUB error: No such device

I have a bit of a confusing problem and my efforts to find a solution of the Arch Wiki and elsewhere have not worked. The problem I’m having is simply that right after install, everything went fine on install, I reboot, and I cannot get past Grub. I have reinstalled the whole base system twice. Still the same error:

error: no such device: 8f2e32e6-7d21-4f4d-8661-6f1ec6e658ee
Grub Rescue>

Edit: I just noticed that the UUID grub is giving me does not match any of my partitions.

It just leaves me at that.

I have two hard drives. One is a brand spankin’ new SSD that I know works perfectly fine (I test installed Ubuntu on it to be sure), the other the regurlar old hard drive that came with the computer many years ago.

sda is the hard drive
sdb is the SSD

I have the SSD with swap and / on it in two partitions
the hard drive is /home

Because of the inherent speed increase on my SSD and the fact that /boot is on there, I decided to install Grub on sdb. The installer offered the following options:

sda
sda1
sdb —>I hit enter to install Grub here, because I read that you have to install it to the MBR and not a partition.
sdb1
sdb5

Because of the inconsistent naming by Linux and Grub, I set Grub to boot by UUID, so that kernel updates cannot change the drive naming.(Hence the UUID error)

Here is my /etc/fstab

Here is my /boot/grub/menu.lst

To clarify I do not have a seperate /boot partition

Any help is appreceated, I hope I provided enough information.

Last edited by Scotty (2010-07-27 05:41:44)

Источник

How to fix GRUB error no such device on Linux

Updated — September 14, 2018 by Arnab Satapathi

Sometime you may encounter error messages like Error: no such device: xxxxx-xxxx-xxxx-xxxx-xxxxx right after powering up the PC.

Such problems are caused by misconfigured GRUB, unable to load any operating system.

Usually happens when you resize, rename or shrink the disk partitions. Or may be even if you transfer a perfectly working hard drive from one PC to another.

But there’s an easy solution to deal with such problems, and here we’ll discuss about it.

Why this is happening?

This grub no such device problem usually happens when the boot drive’s UUID is changed somehow.

Like if you convert a disk drive with MBR partition table to GPT partition table. Another reason of UUID change is if you resize, merge, shrink or extend the linux root partition.

Here GRUB is present as bootloader, but it can’t find the proper modules and configuration file due to changed partition UUID.

How to fix the Error no such device GRUB rescue ?

To fix this problem, you’ve to determine three things.

First which one is the linux root( / ) partition, second how the system is booted, i.e. in UEFI mode or in legacy BIOS mode.

Third, if it’s booted in UEFI mode, then which is the EFI system partition?

You can use the parted command to determine the ESP partition, which is a FAT32 filesystem of around 100MB.

Now the actual steps to fix the error no such device problem.

1. Use the ls command on the grub rescue prompt to list all the partitions.
2. Then you can use the ls command again to check the contents of each partitions to be sure.

The linux root partition will contain /bin , /boot , /lib etc. etc directories.

If you’re sure about the linux root partition, then type the commands listed below one by one. In my case, the partition is (hd0,msdos5) .

Then you should be able to access the GRUB boot menu like before, select the linux distro and boot to it.

After booting, you must be asked to login to your user account.

Next login to the account and open up a terminal window.

Then determine if the system is booted with UEFI mode or legacy BIOS mode, use the one liner script below.

To reinstall GRUB for legacy BIOS use this command.

To re install GRUB on a UEFI based system, use this.

If grub installation reports no problem, then update the GRUB configuration file.

Finally reboot the PC or laptop to check the if it worked at all or not.

Also don’t just copy-paste the commands, your EFI system partition could be different, most probably /dev/sda1 .

Conclusion

It’s not a very well described tutorial to fix the grub rescue no such device issue. But I hope you’ve got basic the idea to deal with the error no such device issue.

First you need to boot linux somehow then reinstall the GRUB bootloader and update the GRUB configuration. Here’s the detailed GRUB rescue tutorial.

If you’ve any question or suggestion, leave comments below.

Octavian Paun says

Please help : I have one Asus X543MA-GO929 with EndlessOS, recently purchased. For about a week, the system does not start. It looks like this: «error no such device ostree». Do you have any suitable suggestions for this error?

Very interesting.
I had to change my tower and the new one is an EUFI one with W10. After putting the new tower in both modes (UEFI and legacy) the «old» Ubuntu SSD boots up to the CLI interface but cannot enter the graphical mode.
I built a new Ubuntu SSD from a DVD. Boots stops with «no such device : 39760. ). I disconnected from SATA an HDD used in the old tower and inserted in the new one.
Without this old HDD, Ubuntu boot was perfect.
I think the id of old HDD changed under W10 (I tried so many things. ).
How can I solve the problem.
According to your

[ -d /sys/firmware/efi ] && echo «UEFI boot» || echo «Legacy boot»

I booted in legacy mode.
Best regards

That’s a tricky situation, every PC needs a different approach.

If you think the old disk’s UUID is changed, it’s better to reinstall GRUB.

First you should check the partition table of your old HDD, if it’s MBR, install GRUB for legacy BIOS, if it’s GPT, install GRUB in UEFI mode.

The best way is to disconnect all other disk to avoid confusion, then boot from a Live USB, then chroot into the old HDD, and reinstall GRUB.

February 24, 2020

Fails horribly for 4 disk install:

$ sudo parted /dev/sda print
Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 524MB 523MB ntfs Basic data partition hidden, diag
2 524MB 629MB 105MB fat32 EFI system partition boot, esp
3 629MB 646MB 16.8MB Microsoft reserved partition msftres
4 646MB 249GB 249GB ntfs Basic data partition msftdata
5 249GB 250GB 605MB ntfs hidden, diag

$ sudo parted /dev/sdb print
[sudo] password for me:
Model: ATA SSD2SC240G1LC709 (scsi)
Disk /dev/sdb: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 240GB 240GB primary ext4 boot

$ sudo parted /dev/sdc print
Model: ATA WDC WD20EZRX-00D (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ext4

$ sudo parted /dev/sdd print
Model: ATA WDC WD20EZRX-00D (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 1682GB 1682GB primary ext4 boot
2 1682GB 2000GB 318GB extended
5 1682GB 2000GB 318GB logical ext4

Heads up for a situation not covered here.
If you have multiple drives and the one giving this problem is attached to an add-in controller card, you might have to connect it to the motherboard main controller instead.
It seems this can happen if the add-in controller needs a special driver which is not yet available when booting.

I bought a laptop with EndlessOS in it. I want to install Kubuntu as the main OS, so I split into partition, but accidentally format the first partition and so I install Kubuntu in that partition. After installation finished, it rebooted and I found the problem link this article. I simply go to BIOS and change boot order, made the partition which has an OS as the first boot. I exited BIOS, the laptop rebooted and thankfully it booted.

February 6, 2019

Do not give these commands consequitvely, like 8th and 9th steps are alternatives of each other, do not put them in a sequence.

September 28, 2018

Thank you very much. It did smoothly

Georg Salomon says

September 19, 2018

Thanks, very helpfull, probably not for all, but somebody has any linux knowhow, no problem to use.

Thanks so much! Very usefull.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Grub rescue problem (no such device+unknown file system)

[SOLVED] Grub rescue problem (no such device+unknown file system)

Post by Manny_F » Fri Sep 06, 2019 1:27 pm

Hello everyone! I’m a first timer installing Linux and I seem to have screwed up big time at some point. A

I have a PC with Windows 7 Ultimate installed and two hard drives («C:», where Win 7 is installed and «Z:», which I used for storage).

My idea was to set up a dual boot system. Using Windows Disk Management, I partitioned «Z», creating a volume, «L», with empty space that would be used for the Linux install.

Having downloaded Mint’s latest release from its website (64 bit version for my 64 bit machine), I «burned» it into a USB drive using Rufus and proceeded to install on the newly created volume, choosing the «something else» option and making sure to create the «root», «swap» and «home» partitions.

Install went smoothly, but, when reboting, I notice the machine says «Loading Operative System. » for a while, and then I’m greeted by two separate errors «No such device» and «Unknown filesystem» then «Grub Rescue». I saw some people could get through this screen with the «ls» command, but in my case it was to no avail, none of the options offered allowed me to continue any further.

I tried installing Linux again, overwriting the previous install, to see if things would just set themselves right (fat chance, I know), but it changed nothing. So I was basically screwed because I had two OS in my computer but I was unable to access none of them.

I eventually stumbled upon Super Grub2 Disc, which at least allowed me to access Windows 7 again. but to my surprise, Super Grub doesn’t seem to register any Linux installation on the computer, at all (if I try to install Linux again, though, the setup recognizes the existence of Linux on my computer)

Any idea on how to solve this? I would really like to take this as a learning opportunity and any help offered would be greatly appreciated. Sorry if grammar is a bit off but I’m not a native English speaker.

Re: Grub rescue problem (no such device+unknown file system)

Post by Larry78723 » Fri Sep 06, 2019 4:13 pm

What format did you use for the linux partitions? It’s best to format them as ext4. Please post the following report. This will give us a concise overview of your partitions.

Here is how to generate the report and post it:

Boot from your installation media (USB/DVD)
Open a terminal window (Ctrl-Alt-t). Make it fullscreen to avoid unneeded linebreaks or chopped lines. Execute the command

exactly as it has been typed here.

Mark the complete text output which the command will display with your mouse.
Press the keyboard shortcut C to copy the marked text into the clipboard.
Enclose the results between the code markers by selecting from the mini toolbar above the textbox where you type your reply then paste V them in your reply between the code markers.

The results will help us to help you.

Re: Grub rescue problem (no such device+unknown file system)

Post by Manny_F » Sun Sep 08, 2019 11:06 pm

Hi Larry. Sorry for the late reply, I work on weekends away from home.

I’m pretty sure I chose ext4 as format during (both) installations, but of course I could have messed up unknowingly. Here’s what your requested

Re: Grub rescue problem (no such device+unknown file system)

Post by fabien85 » Mon Sep 09, 2019 6:04 am

Hum, you seem to have done it correctly, and you may be hitting a delicate problem.

Is your windows installed in Legacy/BIOS mode ?
If you do not know, see this page to find out.

Another thing that can confirm is to boot again the live USB, launch the following command

and report the result here.
The output should show the same partitions that you got with lsblk (unless the naming of the drives changed) and should also show the type of partition table.
If the drive is partitioned in MBR/msdos, then that’s very probably the problem.

MBR/msdos partition tables only work up to 2TB. Your Linux partitions are located past the 2TB mark, so grub cannot find them.
When grub cannot find the files it needs to load (the modules located in /boot/grub), it drops in «grub rescue» mode.

Also there are 5 partitions on this disk, while MBR can only accomodate 4 primary partitions. So either I’m wrong and your disk is formatted as GPT (which is not usual for windows 7), or some partition(s) are probably invalid.
I’m wondering what /dev/sdb1 is, lsblk does not give the filesystem type of this partition.

Re: Grub rescue problem (no such device+unknown file system)

Post by Spearmint2 » Mon Sep 09, 2019 8:58 am

Re: Grub rescue problem (no such device+unknown file system)

Post by pbear » Mon Sep 09, 2019 11:21 am

Seems to me likely sdb1 is the Windows Z: partition. Doesn’t explain, though, why it doesn’t have a format. Anyhoo, Manny, let’s try another command which should resolve this and a few other questions. Please run sudo parted -l (that’s an «L») and report the output.

Also, do you recall what location you specified for installation of the bootloader?

Re: Grub rescue problem (no such device+unknown file system)

Post by Manny_F » Mon Sep 09, 2019 4:52 pm

Hum, you seem to have done it correctly, and you may be hitting a delicate problem.

Is your windows installed in Legacy/BIOS mode ?
If you do not know, see this page to find out.

Another thing that can confirm is to boot again the live USB, launch the following command

and report the result here.
The output should show the same partitions that you got with lsblk (unless the naming of the drives changed) and should also show the type of partition table.
If the drive is partitioned in MBR/msdos, then that’s very probably the problem.

MBR/msdos partition tables only work up to 2TB. Your Linux partitions are located past the 2TB mark, so grub cannot find them.
When grub cannot find the files it needs to load (the modules located in /boot/grub), it drops in «grub rescue» mode.

Also there are 5 partitions on this disk, while MBR can only accomodate 4 primary partitions. So either I’m wrong and your disk is formatted as GPT (which is not usual for windows 7), or some partition(s) are probably invalid.
I’m wondering what /dev/sdb1 is, lsblk does not give the filesystem type of this partition.

Re: Grub rescue problem (no such device+unknown file system)

Post by Manny_F » Mon Sep 09, 2019 5:00 pm

Seems to me likely sdb1 is the Windows Z: partition. Doesn’t explain, though, why it doesn’t have a format. Anyhoo, Manny, let’s try another command which should resolve this and a few other questions. Please run sudo parted -l (that’s an «L») and report the output.

Also, do you recall what location you specified for installation of the bootloader?

If memory serves me right, the bootloader was installed in /dev/sda both times. but I can’t truly assure it.

Thanks for the continued support of all of you.

Re: Grub rescue problem (no such device+unknown file system)

Post by Spearmint2 » Mon Sep 09, 2019 5:29 pm

sda is in legacy mode, sdb is in UEFI GPT mode.

If linux is on sda, then probably have to use Legacy mode in BIOS to boot from it.

Re: Grub rescue problem (no such device+unknown file system)

Post by pbear » Mon Sep 09, 2019 11:46 pm

Reading a little more carefully, I notice a few things and suggest the following path forward.

1. Obviously sdb2 is the Windows Z: partition. Now we know sdb1 is a Windows reserved partition and not an EFI partition.

2. Neither sdb3 nor sdb5 have mount points, where they’re supposed to be root and home respectively.

3. IMHO, 20 GB is too small for root. Moreover, assuming this is Mint 19.2 (indeed, any version of 19.x), there’s no need for a swap partition (unlike 18.x, which was the version in play when the Installation Guide was written). So, I’d recommend redoing the installation, leaving out swap and giving root at least 30 GB. Be aware that if you are doing separate root and home partitions, it’s imperative you set up Timeshift to save snapshots in /home.* Otherwise, there’s a significant risk your root partition will fill up and the system will cease booting. I always set up my partitions with GParted (mentioned above by Spearmint2) before starting the installer.

* Timeshift is to Mint what System Restore is to Windows. It’s a utility to return your system to a prior state if an update causes a problem. Setting up Timeshift is one of the first things you do post-installation. One of the options is designating where to store snapshots. Default is root. You want to change that to the home partition.

4. To clarify, once you’re in the installer and have selected Something Else, here’s what you’re supposed to do. Select partition planning to use for root, here, sdb3; click Change; Use as: Ext4 system (but don’t tick format box) and select mount point as root (“/”) (annoyingly, you can’t see the mount point option until you’ve selected “use as”). Same steps to select sdb4 (its number will change once swap is removed) and define mount point as /home. As before, designate sda (not sda1) as destination for the bootloader.

5. Assuming all that works, you may find when you boot for the first time that Windows isn’t listed in Grub. Not to worry. This is a common problem, easily solved. All you need to do is boot Mint, open Terminal and run sudo update-grub . As part of the update, the system will run something called os-prober, which should recognize the Windows bootloader and add it to Grub. Reboot. Windows should now be listed. Let us know if not.

6. Before you do any of this, I’d strongly recommend you boot Windows and create a System Repair Disk. You’ll find that option in Control Panel under Backups. That’s the tool you use to restore the Windows bootloader if you’re unable to complete the installation or decide later to undo it. Frankly, you should have had one before you started. Let’s get it done now.

Feel free to ask if you want anything clarified before you give the installation another go.

Источник