Boot EFI stopped working in a removable external HDD on Mac mini

I have only 4.19

Last week, I had this issue when I have published this topic, because I have reinstalled from my laptop and my external HD could not boot in my Mac mini after the dangerous command sudo pacman -Rscn gnome, which acted like Thanos, having killed the half of OS, but some KDE packages (pacman-mirrors, pacman, etc.) were part of that killed half and another survived half were KDE parts.

But I understood what happened. For my HD to work on my Mac mini, I have to install from Mac mini.

I installed from Mac mini, appying GPT and /boot/efi and it worked everything and everywhere until yesterday I made an upgrade, running the command sudo pacman -Syyu and typed reboot via terminal. Now I remember that Anbox and anbox-bridge [session] were not turned off during the upgrade. They may have caused hibernation error.

At this point, I'd suggest reinstall.
This would be the best.
Good luck.

1 Like

OK, I am going to format. But when I can and can not update for avoiding breaking the bootloader? I fear every update or every upgrade break the bootloader because my external HDD is removable.

Better I purchase a new computer with an internal SSD with Linux, then I will discard the Mac mini and the external HDD, to escape of broken bootloader nightmare.

On My laptop with an internal SSD with Manjaro, every update or upgrade I did, the bootlooader has never been broken since August.

That's because you need a "--removable" for your grub-install for a removable disk.

That's because it is an internal disk and don't need a "--removable"

Too difficult to read all posts together :face_with_thermometer:

OP did not say what errors after each boot test failure.
I saw both intel and amd ucodes in grub.cfg.
Depending actual HW needs, this gives errors sometimes.
It worth trying remove un-needed ucode.

inxi -SMGpuoxxxz
pacman -Qs ucode
journalctl -b -1 -p3

from the Manjaro installation, not LiveMedia.

Perhaps the Avengers can rescue you from this horrific installation. Where's Bruce Banner and Tony stark when you need them. :superhero:


Each every update, I have to run sudo install-grub --removable --recheck` every time, right?

I did not format yet.

Do I remove them or do I format the HDD?

Do you mean the installed OS into the external HDD? I did not format yet.

Unfortunately the Avengers could not rescue me from the horrific update, because with a snap of fingers of Pacman the Mad Titan, the folders /boot and /etc ceased to exist.

Your system is now quite messed up.

If you never remove it, even if that is a external disk, then there's no need to use "--removable"
But if you do, even if just occasionally, you must.

As I experimented here, I have no problem.

@gusbemacbe, Reinstall.
We cannot (& will not) proceed further with your system now.

Hi @gohlip and @AgentS!

I have just reinstalled from Mac mini.

  • inxi -SMGpuoxxxz
  Host: gusbemacbe-mac Kernel: 4.19.0-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.13.5 tk: Qt 5.11.1 
  wm: kwin_x11 dm: sddm Distro: Manjaro Linux 
  Type: Laptop System: Apple product: Macmini5,1 v: 1.0 serial: <filter> 
  Chassis: type: 16 v: Mac-8ED6AF5B48C039E1 serial: <filter> 
  Mobo: Apple model: Mac-8ED6AF5B48C039E1 v: Macmini5,1 serial: <filter> 
  UEFI: Apple v: MM51.88Z.0080.B00.1804091930 date: 04/09/2018 
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Apple driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 
  Display: x11 server: X.Org 1.20.1 driver: intel unloaded: modesetting 
  alternate: fbdev,vesa compositor: kwin x11 resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.1.8 
  compat-v: 3.0 direct render: Yes 
  ID-1: / size: 392.72 GiB used: 6.12 GiB (1.6%) fs: ext4 dev: /dev/sdc3 
  uuid: 990a0c87-17d0-480b-a1e4-ae07765bcae8 
  ID-2: /boot/efi size: 300.4 MiB used: 264 KiB (0.1%) fs: vfat 
  dev: /dev/sdc1 uuid: 8F94-6CB4 
  ID-3: /home size: 56.83 GiB used: 154.6 MiB (0.3%) fs: ext4 
  dev: /dev/sdc4 uuid: eab07c54-a16e-4109-b185-f35145188360 
  ID-4: swap-1 size: 7.47 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc2 
  uuid: e667bca2-99fe-47fa-8c53-a1d6e17d1796 
  ID-1: /dev/sda1 size: 200.0 MiB fs: vfat label: EFI uuid: 67E3-17ED 
  ID-2: /dev/sda2 size: 464.96 GiB fs: hfsplus label: High Sierra 
  uuid: 0ad0d00c-4782-3d2c-a629-5acbd1792bc1 
  ID-3: /dev/sda3 size: 619.9 MiB fs: hfsplus label: Recovery HD 
  uuid: 01cb061d-937b-3aba-943c-0ba15f417b93 
  • pacman -Qs ucode
local/amd-ucode 20180825.fea76a0-1
    Microcode update files for AMD CPUs
local/intel-ucode 20180807.a-1
    Microcode update files for Intel CPUs
  • journalctl -b -1 -p3
journalctl -b -1 -p3
Data from the specified boot (-1) is not available: No such boot ID in journal

As I have just reinstalled, do I must run the command sudo grub-install --removable --recheck?

I have partitioned two partitions - one for / (root) and another for /home. If something goes wrong, if I reinstall and format only the partitions /boot/efi and /root, will I lose the partition /home?

It seems it also has affected my laptop. I have check the informations about the packages intel-ucode and amd-ucode: [Testing Update] 2018-10-01 - Linux419, Grub-Quiet, Systemd, Pamac-Dev

@gohlip and @AgentS

It is 9th, 10th and 11th times I formatted the HDD. I conclude the ISOs of Manjaro 18 Beta 6 and of Manjaro 18.0 Release Candidate 1 break the boot and the grub.

I fear I reinstall with the ISO of latest stable version of Manjaro because I saw the informations in the Announcements about having to install amd-ucode and remove intel-ucode, and to run sudo grub-install.

@tbg, can I report it to the developers?

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

Forum kindly sponsored by