Page 1 of 1

Grub crash and No bootable device

Posted: Sat Jul 10, 2021 4:28 pm
by MrAxolotl
When installing Mxlinux everything is fine and I have 2 problems.

1.- If I choose to install GRUB, upon reaching 96% of the installation, the pc freezes completely, and if I reboot, I get this:

Image

2.-If I decide not to install it, everything continues as normal, but when restarting, it tells me "No bootable device".

My computer is an Acer ES 1-533. I have already read many forums about possible solutions and with none I have been able to solve it, the installer is updated to the latest version and I do it through LiveCD, and i'm not trying dual boot

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 4:42 pm
by Huckleberry Finn
Just boot live session again and before clicking "install" , "Quick System Info" from Menu please :)

P.S. Till then: Especially if it's an SSD , change "sata mode" to Ahci in Bios settings.

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 5:24 pm
by MrAxolotl
Huckleberry Finn wrote: Sat Jul 10, 2021 4:42 pm Just boot live session again and before clicking "install" , "Quick System Info" from Menu please :)

P.S. Till then: Especially if it's an SSD , change "sata mode" to Ahci in Bios settings.

Code: Select all

System:    Host: <filter> Kernel: 4.19.0-16-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo March 31  2021 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: Acer product: Aspire ES1-533 v: V1.07 serial: <filter> 
           Mobo: Acer model: Stego_AP v: V1.07 serial: <filter> UEFI: Insyde v: 1.07 
           date: 11/14/2016 
Battery:   ID-1: BAT1 charge: 6.8 Wh condition: 27.8/37.3 Wh (75%) volts: 10.6/11.4 
           model: COMPAL 0033314234314341 type: Li-ion serial: <filter> status: Discharging 
CPU:       Topology: Dual Core model: Intel Celeron N3350 bits: 64 type: MCP arch: Goldmont 
           family: 6 model-id: 5C (92) stepping: 9 microcode: 40 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 4377 
           Speed: 2361 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 2362 2: 2288 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:5a85 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster 
           vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:0e.0 
           chip ID: 8086:5a98 
           Sound Server: ALSA v: k4.19.0-16-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 1000 bus ID: 01:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel 
           port: 1000 bus ID: 02:00.0 chip ID: 8086:24fb 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 480.18 GiB used: 25.0 MiB (0.0%) 
           ID-1: /dev/sda vendor: Western Digital model: WD5000LPCX-21VHAT0 size: 465.76 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 1A01 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 size: 14.42 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: GPT 
Partition: ID-1: / raw size: N/A size: 2.90 GiB used: 25.0 MiB (0.8%) fs: overlay 
           source: ERR-102 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 194 Uptime: 2m Memory: 3.68 GiB used: 501.9 MiB (13.3%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
The bios does not allow me to change a SATA, it's a hdd

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 5:36 pm
by Huckleberry Finn
MrAxolotl wrote: Sat Jul 10, 2021 4:28 pm 2.-If I decide not to install it, everything continues as normal, but when restarting, it tells me "No bootable device".
So, when you skip Grub installation, the installation finishes successfully (100 % ) .. And the message is normal as you have no Grub. So you can simply start "MX Boot Repair" on live session from Menu... "Reinstall Grub" ..

https://ibb.co/Gc8M7DC

Install on: ESP

Location: Your ESP partition (fat32 / vfat)

Select ... location: Your MX's partition.
________________________________________________

P.S. Also on GParted check (or do if required) if your ESP partition has both flags: boot (and) esp

Re: Grub crash and No bootable device  [Solved]

Posted: Sat Jul 10, 2021 5:40 pm
by MrAxolotl
Huckleberry Finn wrote: Sat Jul 10, 2021 5:36 pm
MrAxolotl wrote: Sat Jul 10, 2021 4:28 pm 2.-If I decide not to install it, everything continues as normal, but when restarting, it tells me "No bootable device".
So, when you skip Grub installation, the installation finishes successfully (100 % ) .. And the message is normal as you have no Grub. So you can simply start "MX Boot Repair" on live session from Menu... "Reinstall Grub" ..

https://ibb.co/Gc8M7DC

Install on: ESP

Location: Your ESP partition (fat32 / vfat)

Select ... location: Your MX's partition.

P.S. Also on GParted check (or do if required) if your ESP partition has both flags: boot (and) esp
I'll try

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 5:41 pm
by fehlix
MrAxolotl wrote: Sat Jul 10, 2021 4:28 pm When installing Mxlinux everything is fine and I have 2 problems.

1.- If I choose to install GRUB, upon reaching 96% of the installation, the pc freezes completely, and if I reboot, I get this:

2.-If I decide not to install it, everything continues as normal, but when restarting, it tells me "No bootable device".

My computer is an Acer ES 1-533. I have already read many forums about possible solutions and with none I have been able to solve it, the installer is updated to the latest version and I do it through LiveCD, and i'm not trying dual boot
Unfortunately I cannot view the external hosted image...

But anyway.. here we go
Some of those Acer 1-533 and also Acer ES1-132, do freeze, when trying to setup EFI boot loader, b/c they seem to have a readonly "NVRAM", which is normally writeable to store UEFI boot loader entries.

You may have already tried this, but if not please do proceed within this order:

* Do boot from MX LiveUSB/DVD and install without enabling the GRUB installation.

* Do take away the "tick" to reboot on the last Installer-window. Close the installer after installation finished,
don't reboot. If you have already installed, do boot again with MX LiveUSB/DVD

* Search in Whisker Menu for " Chroot Recue Scan"
or open terminal and run

Code: Select all

sudo chroot-rescue-scan
* Select the found MX Linux entry. It will open a "chroot"ed terminal within the MX Linux installation

Now within the chroot terminal do this step by step:

** first create the missing efi folder:

Code: Select all

mkdir /boot/efi
** next mount the efi-folder to the ESP (EFI System partition )

Code: Select all

mount -a
** Now two tricky parts:
first: install EFI-GRUB without writing into NVRAM ( b/c this would otherwise freeze)

Code: Select all

grub-install --no-nvram --bootloader-id=MX19  --force-extra-removable
** next an Acer 1-xxx special step:

Code: Select all

cp -a /boot/efi/EFI/BOOT /boot/efi/EFI/Linux
The last step is needed as the readonyl NVRAM holds a couple of preset EFI entries burned into the NVRAM by the manufacture. One of those entries is /EFI/Linux/Bootx64.efi, which is create by the last copy command.

** Disable UEFI-firmware setup access from GRUB (this step may not be needed, but to be safe to avoid a hanger we do it here):

Code: Select all

chmod -x /etc/grub.d/30_uefi-firmware

** Generate the GRUB menu:

Code: Select all

update-grub
That's it.
Now type: exit
and close and reboot, and with some luck and it may boot in MX Linux.
HTH
:puppy:
+++EDIT+++: to mention you may need to turn secure boot off within UEFI firmware setup.
+++EDIT2+++: added the generation of the GRUB menu :happybday:

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 6:11 pm
by MrAxolotl
fehlix wrote: Sat Jul 10, 2021 5:41 pm
MrAxolotl wrote: Sat Jul 10, 2021 4:28 pm When installing Mxlinux everything is fine and I have 2 problems.

1.- If I choose to install GRUB, upon reaching 96% of the installation, the pc freezes completely, and if I reboot, I get this:

2.-If I decide not to install it, everything continues as normal, but when restarting, it tells me "No bootable device".

My computer is an Acer ES 1-533. I have already read many forums about possible solutions and with none I have been able to solve it, the installer is updated to the latest version and I do it through LiveCD, and i'm not trying dual boot
Unfortunately I cannot view the external hosted image...

But anyway.. here we go
Some of those Acer 1-533 and also Acer ES1-132, do freeze, when trying to setup EFI boot loader, b/c they seem to have a readonly "NVRAM", which is normally writeable to store UEFI boot loader entries.

You may have already tried this, but if not please do proceed within this order:

* Do boot from MX LiveUSB/DVD and install without enabling the GRUB installation.

* Do take away the "tick" to reboot on the last Installer-window. Close the installer after installation finished,
don't reboot. If you have already installed, do boot again with MX LiveUSB/DVD

* Search in Whisker Menu for " Chroot Recue Scan"
or open terminal and run

Code: Select all

sudo chroot-rescue-scan
* Select the found MX Linux entry. It will open a "chroot"ed terminal within the MX Linux installation

Now within the chroot terminal do this step by step:

** first create the missing efi folder:

Code: Select all

mkdir /boot/efi
** next mount the efi-folder to the ESP (EFI System partition )

Code: Select all

mount -a
** Now two tricky parts:
first: install EFI-GRUB without writing into NVRAM ( b/c this would otherwise freeze)

Code: Select all

grub-install --no-nvram --bootloader-id=MX19  --force-extra-removable
** next an Acer 1-xxx special step:

Code: Select all

cp -a /boot/efi/EFI/BOOT /boot/efi/EFI/Linux
The last step is needed as the readonyl NVRAM holds a couple of preset EFI entries burned into the NVRAM by the manufacture. One of those entries is /EFI/Linux/Bootx64.efi, which is create by the last copy command.
That's it.
Now type: exit
and close and reboot, and with some luck and it may boot in MX Linux.
HTH
:puppy:
++EDIT+++: to mention you may need to turn secure boot off within UEFI firmware setup.
I get this

https://img.superdanova.com//file/1625955006c84f652.jpg

(if I put it in [img] it doesn't show)

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 6:20 pm
by fehlix
MrAxolotl wrote: Sat Jul 10, 2021 6:11 pm
I get this

(if I put it in [img] it doesn't show)
Yes, b/c I have forgotten to write the last steps (I'll update the post above):
Do boot again with LiveUSB/DVD and in the chrooted terminal: Do this

Code: Select all

mount -a
Disable UEFI-firmware setup access from GRUB (this step may not be needed, but to be safe to avoid a hanger we do it here):

Code: Select all

chmod -x /etc/grub.d/30_uefi-firmware

Generate the GRUB menu:

Code: Select all

update-grub
Done!
Reboot

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 6:53 pm
by Stevo
Many Acer laptops with Insyde UEFI from that era required that you set a password to access the setup utility before it unlocked some crucial settings. This was undocumented with anything that came with the machine. I just wanted to install MX, not have to solve some dungeon crawler game puzzle to do so! :frown: Not to mention that BIOS or Windows updates would set everything in the BIOS back to defaults except the password.

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 7:05 pm
by MrAxolotl
fehlix wrote: Sat Jul 10, 2021 6:20 pm
MrAxolotl wrote: Sat Jul 10, 2021 6:11 pm
I get this

(if I put it in [img] it doesn't show)
Yes, b/c I have forgotten to write the last steps (I'll update the post above):
Do boot again with LiveUSB/DVD and in the chrooted terminal: Do this

Code: Select all

mount -a
Disable UEFI-firmware setup access from GRUB (this step may not be needed, but to be safe to avoid a hanger we do it here):

Code: Select all

chmod -x /etc/grub.d/30_uefi-firmware

Generate the GRUB menu:

Code: Select all

update-grub
Done!
Reboot
Thank you very much, I was already desperate, I was already 2 weeks like this, you are my hero and I will be eternally grateful

Re: Grub crash and No bootable device

Posted: Sat Jul 10, 2021 7:30 pm
by fehlix
OK, here for the record, were I got this magic information mainly from:

* A post early this year within this MX Linux forum where @hamak reported about "Acer ES1-132 No Bootable Device" viewtopic.php?f=107&t=62554

* Another post by a user "spektro37" within an Acer forum, where this was mentioned a bit earlier
https://community.acer.com/en/discussio ... ent_490737

* An even earlier post in Russian
https://www.linux.org.ru/forum/linux-i ... d=13169511
by user V1KT0P, who wrote:
В общем нашел причину того что невозможно загрузиться. Все дело в рукожопии тех кто писал UEFI прошивку. Эти *удаки не нашли ничего лучшего чем захардкорить пути по которым возможен запуск, я вытянул из прошивки вот такие данные:
which translates into English using DeepL.com:
In general, I found the reason why it is impossible to boot. It's all about the handiwork of those who wrote the UEFI firmware. These *mistakes* couldn't find anything better than to hardcode the paths that can be used for startup, so I pulled these data out of the firmware:

and shows this list of hardcoded entries within the readonly NVRAM:

Code: Select all

\EFI\Linux\BOOTX64.efi (Linux)
\EFI\Microsoft\Boot\bootmgfw.efi (Windows Boot Manager)
\EFI\ubuntu\shim.efi (ubuntu SECURE)
\EFI\ubuntu\shim$cpu$.efi (ubuntu SECURE)
\EFI\ubuntu\grub.efi (ubuntu NORMAL)
\EFI\fedora\shim.efi (Fedora)
\EFI\android\bootx64.efi (Android)
\EFI\opensuse\grubx64.efi (topenSUSE)
\EFI\redhat\grub.efi (Red Hat Linux)
\EFI\SuSE\elilo.efi (SuSE Linux)
\EFI\ubuntu\grub$cpu$.efi (ubuntu NORMAL)
So all thanks to these guys finding and posting a way to boot into those Acer's.
:puppy: