Grub rescue after dual boot installation

Hello!

I have a dual boot system with windows on a primary drive, and manjaro on a partition on my secondary. I recently decided to replace my existing manjaro partition (on /dev/sdb2) with the i3 community edition (18.1.0). During the installation I chose the replace a partition option, and the installation continued seemingly successfully. However, when trying to boot into manjaro I get thrown into grub rescue after the following errors:

error: no such device: e9454db2-2a2c-485a-8651-f6c1ea6e0f84
error: unknown filesystem

Windows boots fine fwiw

My system info:

System:    Host: gawkat-laptop Kernel: 5.2.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 
           Desktop: i3 4.17.1 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Acer product: Aspire VN7-592G v: V1.07 serial: <filter> 
           Mobo: Acer model: Aspire VN7-592G v: V1.07 serial: <filter> UEFI: Insyde v: 1.07 
           date: 01/07/2016 
Battery:   ID-1: BAT0 charge: 41.0 Wh condition: 41.0/52.5 Wh (78%) model: LGC AC14A8L 
           status: Not charging 
CPU:       Topology: Quad Core model: Intel Core i7-6700HQ bits: 64 type: MT MCP arch: Skylake-S 
           rev: 3 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41488 
           Speed: 1000 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 1000 2: 1000 3: 954 4: 956 
           5: 996 6: 954 7: 953 8: 1000 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Acer Incorporated ALI driver: i915 v: kernel 
           bus ID: 00:02.0 
           Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: Acer Incorporated ALI driver: nouveau 
           v: kernel bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.5 driver: intel,nouveau unloaded: modesetting 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 19.1.5 
           direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.2.11-1-MANJARO 
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Lite-On 
           driver: ath10k_pci v: kernel port: 4000 bus ID: 07:00.0 
           IF: wlp7s0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 
           IF: enp8s0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.03 TiB used: 5.25 GiB (0.5%) 
           ID-1: /dev/sda vendor: LITE-ON model: CV1-8B128 size: 119.24 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD10JPVX-22JC3T0 size: 931.51 GiB 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer size: 3.75 GiB 
Partition: ID-1: / size: 155.30 GiB used: 5.20 GiB (3.4%) fs: ext4 dev: /dev/sdb2 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A gpu: nouveau temp: 54 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 209 Uptime: 3m Memory: 15.55 GiB used: 446.4 MiB (2.8%) Init: systemd 
           Compilers: gcc: 9.1.0 Shell: bash v: 5.0.9 inxi: 3.0.36 

efibootmgr -v

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0003,2001,2002,2003
Boot0000* Manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Manjaro\grubx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...}................
Boot0002* USB HDD: SanDisk Cruzer	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x0,0x3d09bc,0x2000)RC
Boot0003* Linpus lite	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Boot\grubx64.efi)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

sudo parted -l

Model: ATA LITEON CV1-8B128 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  106MB  105MB   fat32        EFI system partition          boot, esp
 2      106MB   123MB  16,8MB               Microsoft reserved partition  msftres
 3      123MB   127GB  127GB   ntfs         Basic data partition          msftdata
 4      127GB   128GB  980MB   ntfs                                       hidden, diag


Model: ATA WDC WD10JPVX-22J (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size   File system  Name                  Flags
 1      1049kB  830GB   830GB  ntfs         Basic data partition  msftdata
 2      830GB   1000GB  171GB  ext4


Model: SanDisk Cruzer (scsi)
Disk /dev/sdc: 4022MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2048MB  2052MB  4194kB  primary               esp

sudo blkid

/dev/sda1: LABEL="ESP" UUID="081F-D157" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="4aa29696-f870-4d5d-abc7-9ab01869f334"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="e52a2765-e499-4a0f-93db-bb8f2539abe0"
/dev/sda3: UUID="284822FD4822CA00" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="45436fa4-e767-452c-91a0-c6dac3686d64"
/dev/sda4: UUID="A2DED2CDDED2993D" TYPE="ntfs" PARTUUID="037c72eb-bea4-4cd3-9f23-2d13c0306f45"
/dev/sdb1: LABEL="Data" UUID="2A2C29872C294F5F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7cf1cec9-af72-4eb9-ab60-22712ba3c00d"
/dev/sdb2: UUID="260f7a00-715c-4463-b1b6-b2b7a7f91979" TYPE="ext4" PARTUUID="49ee5805-6fb7-4034-aea5-65de5d3a4ad2"
/dev/sdc1: UUID="2019-09-12-22-12-24-00" LABEL="MJRO1810" TYPE="iso9660"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="1346-AA43" TYPE="vfat"

findmnt -s

TARGET    SOURCE                                    FSTYPE OPTIONS
/boot/efi UUID=081F-D157                            vfat   umask=0077
/         UUID=260f7a00-715c-4463-b1b6-b2b7a7f91979 ext4   defaults,noatime

findmnt /boot/efi

TARGET    SOURCE    FSTYPE OPTIONS
/boot/efi /dev/sda1 vfat   rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname

What I have tried:

Using the guides I am able to both boot and chroot into the installed system, and grub-install and update-grub seem to run fine, however when rebooting I still run into the same issue as before.

Nothing seems to work and at this point I have no idea what to try. Does anyone have a possible solution for this?

From the link, did you do ?

sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/sda -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

ps: there will be a warning that there is already an existing 'manjaro' efibootentry in the second command. Proceed nevertheless. Print out 'efibootmgr -v' before and after reboot. Commands above done.

ps: in Manjaro installations, I'd suggest you format out beforehand the partition you want to use rather than do an installation over an existing manjaro partition. Somehow that doesn't clear out the old data in it. Hopefully, that's not the problem you face. You can check whether you still have old kernels from the old replaced OS.

2 Likes

This is odd. A device with UUID e9454db2-2a2c-485a-8651-f6c1ea6e0f84 doesn't show in the output of your blkid. Have a look at /etc/fstab of your installed Manjaro system.

1 Like

Good point! That could be his old UUID of the replace partition, But he did say he install over it.
And he did say he used the first link: so he did not do all the commands there which is 'grub-install' and 'update-grub' which would use the new UUID (if it has a new UUID). {fstab and blkid shows correct UUID}.

ps: note too this manjaro entry 0000 is not in the bootorder, meaning that could be from the old manjaro install and the new manjaro install is not in any efibootmgr, so he didn't do grub-install nor 'efibootmgr -c -d /xx/xxx/xxx/ xxxxxxxx"

Since he's here, perhaps a good suggestion to use grub-vanilla.
So when booted and after 'pacman-mirrors and pacman -Syu', first do 'pacman -S grub-vanilla'

3 Likes

Thanks for the input guys. I have per gohlip's suggestion formatted the partition and reinstalled to it. Afterwards I followed your guide, this time using grub-vanilla and the uefi commands.

efibootmgr -v before

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0000,0001,0003,2001,2002,2003
Boot0000* manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...}................
Boot0002* USB HDD: SanDisk Cruzer	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x0,0x3d09bc,0x2000)RC
Boot0003* Linpus lite	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Boot\grubx64.efi)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

efibootmgr -v after

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0003,2001,2002,2003
Boot0000* manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...}................
Boot0002* USB HDD: SanDisk Cruzer	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x0,0x3d09bc,0x2000)RC
Boot0003* Linpus lite	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Boot\grubx64.efi)RC
Boot0004* manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Manjaro\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

So this is my fstab:

fstab:
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=081F-D157                            /boot/efi      vfat    umask=0077 0 2
UUID=260f7a00-715c-4463-b1b6-b2b7a7f91979 /              ext4    defaults,noatime 0 1

The UUID thing makes me wonder if I am starting the right boot option. I don't have an option named manjaro when entering the boot menu, and I have no idea what the Linpus Lite option is for. Is it possible they are hidden from the boot menu for some reason? Would it be possible/safe to remove the linpus boot option and changing the boot order to contain the manjaro boot options?

Something's still not right.
At new installation, you've formatted sdb2, and the UUID remains unchanged?
260f7a00-715c-4463-b1b6-b2b7a7f91979

Your bootorder still does not show manjaro entry after reboot.

before
BootOrder: 0000,0001,0003,2001,2002,2003
after
BootOrder: 0001,0003,2001,2002,2003
Boot0000* manjaro	

Confirm you did..(at manjaro OS after installation and booted into it using first link - not chroot)

sudo grub-install 
sudo update-grub
sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi 
sudo efibootmgr -c -d /dev/sda -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

Show input command and output terminal message..PRINT

Sorry if I'm being unclear. After the initial install didn't work i did format the partition and created a fresh install, which gave the same error. The output in OP is from after that point.

Running the commands booted into installation:

[gawkat@gawkat-laptop ~]$ sudo grub-install
Installing for x86_64-efi platform.
Installation finished. No error reported.
[gawkat@gawkat-laptop ~]$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.2-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.2-x86_64.img
Found initrd fallback image: /boot/initramfs-5.2-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[gawkat@gawkat-laptop ~]$ sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
[gawkat@gawkat-laptop ~]$ sudo efibootmgr -c -d /dev/sda -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"
efibootmgr: ** Warning ** : Boot0000 has same label manjaro
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0004,0000,0001,0003,2001,2002,2003
Boot0000* manjaro
Boot0001* Windows Boot Manager
Boot0002* USB HDD: SanDisk Cruzer
Boot0003* Linpus lite
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Boot0004* manjaro
[gawkat@gawkat-laptop ~]$

However, after rebooting the output from efibootmgr -v is still the following:

[gawkat@gawkat-laptop ~]$ efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0003,2001,2002,2003
Boot0000* manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...}................
Boot0002* USB HDD: SanDisk Cruzer	PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x0,0x3d09bc,0x2000)RC
Boot0003* Linpus lite	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Boot\grubx64.efi)RC
Boot0004* manjaro	HD(1,GPT,4aa29696-f870-4d5d-abc7-9ab01869f334,0x800,0x32000)/File(\EFI\Manjaro\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

Reboot without your install usb.
The (your) system will always try to boot from your usb first.
You set it up that way.

Restart your computer twice (without usb), (so your firmware can register your harddrive efibootentry and hopefully your manjaro grubx.efi efibootentry 0004)

Print out 'efibootmgr' after rebooting.
Let's take a look at it.

So, I think I managed to fix it. I assumed (very much incorrectly) that since I previously never had to change any boot settings in the bios on this machine when dual booting, it was the same this time. After finding and following the acer-specific part in your guide, it now boots correctly. Thank you so much for the help and I'm sorry for wasting your time. Hope you have a great day!

1 Like

Typing ahead

ls /boot/efi/efi/
ls /boot/efi/efi/boot/
sudo rm  /boot/efi/efi/boot/grubx64.efi
sudo efibootmgr -b 0003 -B

Oh you replied.
So tell... what did you do exactly (probably you will need screen shots of your bios screens) to boot.
Acer can be tough to fix at the bios level and it can help someone else with this.
See above, you may want to print out so you can remove linpus entry and directory. and its grubx64.efi from there as well. It should always be /boot/bootx64.efi and not /boot/grubx64.efi
I did not mention this earlier as this is not important to fix your problem.
Now that's fixed, you can clean those out.

But tell us your Acer bios setup how you fix it.
This is important for others.
That's how we help and become better.
Linux is not a one way street. Nor should be.

Absolutely.

Here is what I did to fix it:

  1. Enter bios
  2. In Boot tab, enable secure boot
    20191001_124236
  3. In Security tab, enter Select an UEFI file as trusted for executing
    20191001_124350
  4. Choose manjaro efi file. In this case mine was located under HDD0/EFI/Boot/bootx64.efi
    20191001_124657
  5. It will now appear in the Boot tab as a boot option. Mine was at the bottom, and I just moved it to the top. Then just save and exit, and reboot.
    20191001_124804

Also, I ran your commands, which removed the linpus entry. There was no directory, so maybe it got removed somewhere along the way. Again, thanks for the help.

2 Likes

Thanks. I've also put your post above to a link in this topic here , under [If problem Persists] --> Acer so others who have an Acer and a similar problem can get help from your solution here.

Good of you, Gawkat.
Welcome to Manjaro.
Cheers.

3 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by