It is the same. Not wrong. I will run boot.
grub> linux /boot/vmlinuz-4.19-x86_64 root=UUID=$abc rw
Note
root=UUID=$abc
not
root=UUID=abc
and with 'rw'
Want to try again?
First time I hear of it failing if kernels are there and..
Hey, watch out for kernels and initramfs with a .img at its end.
That's why configfile is easier without typing anything.
Do you have a grub.cfg in it?
Lat time it failed you too.
Try with configfile.
1 Like
@gusbemacbe
looking at your past posts.. sdc3 had a different uuid.
So, instead of using root=UUID=xxxxxxxxxxxxxxxxxx
let's try with root=/dev/sdc3 in the linux line.
Note you may still have to experiment with other to get it right becasue /dev/sdxy is never reliable.
So we need to try, if sdc3 doesn't work, with all of these.. (one at a time)
grub> linux /boot/vmlinuz-4.19-x86_64 root=/dev/sdc3 rw
grub> linux /boot/vmlinuz-4.19-x86_64 root=/dev/sdb3 rw
grub> linux /boot/vmlinuz-4.19-x86_64 root=/dev/sda3 rw
1 Like
Unfortunately no 3 sdXYs are recognised. But what about the configfile?
Here is the full grub.cfg:
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="${saved_entry}"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
set menu_color_normal=light-gray/black
set menu_color_highlight=green/black
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
else
search --no-floppy --fs-uuid --set=root d3b51cb0-3d23-4827-8074-930b75264081
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_GB
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
else
search --no-floppy --fs-uuid --set=root d3b51cb0-3d23-4827-8074-930b75264081
fi
insmod png
background_image -m stretch /usr/share/grub/background.png
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-d3b51cb0-3d23-4827-8074-930b75264081' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
else
search --no-floppy --fs-uuid --set=root d3b51cb0-3d23-4827-8074-930b75264081
fi
echo 'Loading Linux 4.19rc6.1004.gbefad94-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.19-x86_64 root=UUID=d3b51cb0-3d23-4827-8074-930b75264081 rw quiet resume=UUID=1a9ae34a-453b-40ba-843a-201a7911cc49
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-d3b51cb0-3d23-4827-8074-930b75264081' {
menuentry 'Manjaro Linux (Kernel: 4.19rc6.1004.gbefad94-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19rc6.1004.gbefad94-1-MANJARO x64-advanced-d3b51cb0-3d23-4827-8074-930b75264081' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
else
search --no-floppy --fs-uuid --set=root d3b51cb0-3d23-4827-8074-930b75264081
fi
echo 'Loading Linux 4.19rc6.1004.gbefad94-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.19-x86_64 root=UUID=d3b51cb0-3d23-4827-8074-930b75264081 rw quiet resume=UUID=1a9ae34a-453b-40ba-843a-201a7911cc49
echo 'Loading initial ramdisk ...'
initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}
menuentry 'Manjaro Linux (Kernel: 4.19rc6.1004.gbefad94-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19rc6.1004.gbefad94-1-MANJARO x64-fallback-d3b51cb0-3d23-4827-8074-930b75264081' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd1,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
else
search --no-floppy --fs-uuid --set=root d3b51cb0-3d23-4827-8074-930b75264081
fi
echo 'Loading Linux 4.19rc6.1004.gbefad94-1-MANJARO x64 ...'
linux /boot/vmlinuz-4.19-x86_64 root=UUID=d3b51cb0-3d23-4827-8074-930b75264081 rw quiet resume=UUID=1a9ae34a-453b-40ba-843a-201a7911cc49
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-4.19-x86_64-fallback.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
search --fs-uuid --no-floppy --set=root --hint-ieee1275='ieee1275/ (null)/sas/disk@0,gpt3' --hint-bios=hd1,gpt3 --hint-efi=hd1,gpt3 --hint-baremetal=ahci1,gpt3 d3b51cb0-3d23-4827-8074-930b75264081
linux16 /boot/memtest86+/memtest.bin
}
fi
### END /etc/grub.d/60_memtest86+ ###
Maybe are UUIDs' resumes are wrong?
Yes, the resume uuid is wrong.
But we did not use your grub.cfg (configfile) to boot and we did not specify resume.
The problem (error message) uuid is that of your root, not swap.
I'm thinking of asking you to chroot into the partition,
do mkinitcpio and grub-install
BTW, did you change hooks line of /etc/mkinicpio.conf ?
Just asking, becasue I don't think you did.
That may cause some problem.
I'm now tending to think it could be your mac.
Not being truly a 'pc' motherboard and hence not a truly 'pc' bios.
But I'm really not sure.
@AgentS, any idea?
If you want to try chroot, let us know.
Always be careful using chroot and I don't do that often. Rarely, actually. Can't think of the last time I did that.
By the way, do you have any other kernel other than 4.19?
We can try that if you have.
Of course, lastly we can reinstall.
Last time you installed in bios-legacy.
Not sure if your disk (which is gpt) is affected by it.
If we reinstall, suggest we make the disk again. Redo partitioning to gpt (that will wipe whole disk) and make sure we install properly in uefi.
1 Like
Yes, but I have already done it and it did not work. The Live Media does not recognise the command mkinitcpio.
Yes, I added only the btrfs to HOOKS, but since we have done these changes, it seems that mkinicpio.conf also has changed itself. Here is the full mkinicpio.conf and has removed btrfs:
MODULES=""
BINARIES=()
FILES=""
HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
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 
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. 
3 Likes
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.
@gusbemacbe,
Your system is now quite messed up.
Reinstall.
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.
I have just reinstalled from Mac mini.
inxi -SMGpuoxxxz
System:
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
Machine:
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
Graphics:
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
Partition:
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
Unmounted:
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
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.
