Installer doesn't install MBR+GRUB, no startable system

Hello community!

I’m glad I have discovered EndeavourOS after many years with different distros and FreeBSD!
Have installed it on my old ThinkPad T450s, works very well, rrreally fast, I am fan of the minimalistic concept and the terminal-oriented way.

So, based on that excellent experience with endeavourOS I enthusiastically wanted to install it also on my ASUS netbook (Celeron, 2 GB RAM, 30 GB drive).

However: every install I try (same ISO as for the ThinkPad), with no error message the installer runs through, leaves an installed file system on the disk but not MBR + GRUB, so the BIOS of the netbook shows no bootable system. But, when I try the next install, the installer shows a file system on the target disk and identifies it as endeavourOS.

I had fedora, Mint and MX Linux installed before, so principally the HW is OK for Linux.

Any help would be very welcome!

Please send output of these commands:

sudo fdisk -l
efibootmgr -v

here we are

Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 3.75 GiB, 4026531840 bytes, 7864320 sectors
Disk model: UDisk           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e784590

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 3583359 3583296  1.7G  0 Empty
/dev/sda2       3583360 3796351  212992  104M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.61 GiB, 1724010496 bytes, 3367208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[liveuser@eos-2022.09.10 ~]$ 


[liveuser@eos-2022.09.10 ~]$ efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002
Boot0001* UEFI: General UDisk 5.00	PciRoot(0x0)/Pci(0x15,0x0)/USB(0,0)/CDROM(1,0x36ad80,0xd0a6)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 15 / 03 05 06 00 00 00 / 04 02 18 00 01 00 00 00 80 ad 36 00 00 00 00 00 a6 d0 00 00 00 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0002* UEFI: General UDisk 5.00, Partition 1	PciRoot(0x0)/Pci(0x15,0x0)/USB(0,0)/HD(1,MBR,0x1e784590,0x36ad80,0x34000)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 15 / 03 05 06 00 00 00 / 04 01 2a 00 01 00 00 00 80 ad 36 00 00 00 00 00 00 40 03 00 00 00 00 00 90 45 78 1e 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
    data: 00 00 42 4f

However, these are results from the booting USB stick as live system used for install tries…
Is this of value?

here is how it looks on the install target that does not boot after running the installer

image

Terminal output looks incomplete, or there is something really wrong…
Where is /dev/mmcblk0 (disk) and /dev/mmcblk0p2 (partition) info?

Also, you are looking for MBR, which is not correct (MBR is for MSDOS-Legacy type). It seems you are installing on UEFI, so the bootloader is on your ESP (the fat32 partition).

You may need to install a UEFI entry, with efibootmgr.
Have a look at Archwiki, about creating a UEFI entry manually, and/or GRUB.

Hi,

well, how can these outputs be helpful? They are from the live system USB and not from the target system! The target system - as I wrote and is cause of this posting - is not booting after enOS install, so how could I do a fdisk -l and a efibootmgr -v with meaningful output at all? And as I wrote, the target system has a BIOS. Not a UEFI. What was unclear about that info?

For me it seems the installer fails to discover that the traget is a BIOS system.

What can I give you more for analysis?

It’s a secret :stuck_out_tongue_winking_eye: , or… just give them, and I will explain later.

This provides disk info, not only about the booted system.

This already suggests you have booted in UEFI mode, so your system is probably UEFI capable, even if you didn’t think so :person_shrugging:

Apart from the above commands output, post sudo inxi -Faz, and look for your PC user manual, and/or your vendor’s datasheet. Maybe there is some UEFI/BIOS setting that might need configuration.

sorry, I somehow missed to copy the complete output of fdisk, but here is the next try

[liveuser@eos-2022.09.10 ~]$ sudo fdisk -l
Disk /dev/mmcblk0: 29.12 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E8BD9C59-7251-8E49-956E-1FC216935112

Device            Start      End  Sectors  Size Type
/dev/mmcblk0p1     4096   618495   614400  300M EFI System
/dev/mmcblk0p2   618496 52772531 52154036 24.9G Linux filesystem
/dev/mmcblk0p3 52772532 61063064  8290533    4G Linux swap


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 3.75 GiB, 4026531840 bytes, 7864320 sectors
Disk model: UDisk           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e784590

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 3583359 3583296  1.7G  0 Empty
/dev/sda2       3583360 3796351  212992  104M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.61 GiB, 1724010496 bytes, 3367208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
1 Like

[liveuser@eos-2022.09.10 ~]$ sudo inxi -Faz

System:
  Kernel: 5.19.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: initrd=\arch\boot\intel-ucode.img
    initrd=\arch\boot\amd-ucode.img
    initrd=\arch\boot\x86_64\initramfs-linux.img archisobasedir=arch
    archisolabel=EOS_202209 cow_spacesize=10G
    module_blacklist=nvidia,nvidia_modeset,nvidia_uvm,nvidia_drm,pcspkr
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1 nvme_load=yes
  Desktop: Xfce v: 4.16.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm
    v: 4.16.1 dm: LightDM v: 1.32.0 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: E203NA v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: E203NA v: 1.0 serial: <filter>
    UEFI: American Megatrends v: E203NA.304 date: 10/23/2017
Battery:
  ID-1: BAT0 charge: 27.9 Wh (96.9%) condition: 28.8/38.0 Wh (75.7%)
    volts: 7.6 min: 7.6 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: discharging cycles: 7
CPU:
  Info: model: Intel Celeron N3350 bits: 64 type: MCP arch: Goldmont
    level: v3 built: 2016 process: Intel 14nm family: 6 model-id: 0x5C (92)
    stepping: 9 microcode: 0x48
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB
    desc: d-2x24 KiB; i-2x32 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 803 high: 807 min/max: 800/2400 base/boost: 1100/2400
    scaling: driver: intel_cpufreq governor: schedutil volts: 1.2 V
    ext-clock: 100 MHz cores: 1: 807 2: 800 bogomips: 4378
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 500 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
    empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5a85 class-ID: 0300
  Device-2: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:4 chip-ID: 04f2:b54b class-ID: 0e02 serial: <filter>
  Display: server: X.Org v: 21.1.4 compositor: xfwm v: 4.16.1 driver: X:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: eDP-1 mapped: eDP1 model: AU Optronics 0x225c built: 2014
    res: 1366x768 hz: 60 dpi: 133 gamma: 1.2 size: 260x140mm (10.24x5.51")
    diag: 294mm (11.6") ratio: 16:9 modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics 500 (APL 2) v: 4.6 Mesa 22.1.7
    direct render: Yes
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
    vendor: ASUSTeK driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_soc_avs,snd_sof_pci_intel_apl bus-ID: 00:0e.0
    chip-ID: 8086:5a98 class-ID: 0403
  Sound Server-1: ALSA v: k5.19.7-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.57 running: yes
Network:
  Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: ath10k_pci v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0042
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-5:3
    chip-ID: 13d3:3501 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 32.87 GiB used: 0 KiB (0.0%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: HP model: DF4032
    size: 29.12 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> rev: 0x8 scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
  ID-2: /dev/sda maj-min: 8:0 type: USB model: General size: 3.75 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
    rev: 5.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: N/A size: 10 GiB used: 70.3 MiB (0.7%) fs: overlay
    source: ERR-102
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 189 Uptime: 12m wakeups: 1 Memory: 1.8 GiB used: 1.44 GiB
  (80.3%) Init: systemd v: 251 default: multi-user tool: systemctl
  Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 895 libs: 212 tools: yay
  Shell: Bash (sudo) v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.21

[liveuser@eos-2022.09.10 ~]$

Please edit your posts and format the pasted text for better readability.
You can do so by clicking on :pencil2:, highlighting the text and pressing Ctrl-E.

1 Like

I added those backticks (```) to the first of the new outputs.
Now it is easier to read. :wink:

hey, is that what you intended?

thanks a lot for your help

1 Like

You are welcome!

And welcome to EnOS’ community! Hope you enjoy it here!

What does vendor’s info say about UEFI and non-UEFI installation?
In what mode were the other Linux OSes installed?
Does the current ESP include any EndeavourOS bootloader file and in which path?

It is advisable to update your laptop BIOS to the latest version, before going forward.

In any case, do some reading on the previously provided links, to better understand the processes you might need to follow to fix your issue.

this looks like some kind of netbook to me… never saw one like this… it could be that the device uses some kind of boot like uboot or such similar to arm devices?

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

This output makes me think this too…

1 Like

Might be helpful: https://sorashi.github.io/asus-e200ha-arch/

Especially this part:

Installation

Use cfdisk /dev/mmcblk0 to create (in this order)

300M EFI Filesystem
  1G Linux swap
rest Linux filesystem
mkfs.fat -F32 /dev/mmcblk0p1
mkswap /dev/mmcblk0p2
mkfs.ext4 /dev/mmcblk0p3
mount /dev/mmcblk0p3 /mnt
swapon /dev/mmcblk0p2

Actually, in this case I would advise not to update UEFI. It’s possible that new version has even more “safety features” like this.

Indepent OS BIOS - https://drivers.softpedia.com/get/BIOS/Asus/ASUS-E203NA-BIOS-315.shtml

Related: https://askubuntu.com/questions/775498/ubuntu-on-32-bit-uefi-only-based-tablet-pc

Crazy.

1 Like

Hey all,
I thought it might help to install a different Linux distro on my netbook and see what it tells us, as a comparison. Because, if debian, fedora, Mint, MX Linux can be installed, then it must be something that endeavourOS is doing different, right?

So, first here is the gparted screen after a fresh MX Linux install:

image

next, fdisk:

Festplatte /dev/mmcblk0: 29,12 GiB, 31268536320 Bytes, 61071360 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: E9625FAC-A8EA-46CF-BB12-B217838DCAE5

Gerät            Anfang     Ende Sektoren Größe Typ
/dev/mmcblk0p1     2048   526335   524288  256M EFI-System
/dev/mmcblk0p2   526336 57911295 57384960 27,4G Linux-Dateisystem
/dev/mmcblk0p3 57911296 61057023  3145728  1,5G Linux-Dateisystem

axel@mx:~

next, efibootmgr -v

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* MX21	HD(1,GPT,909266f5-c2d1-4065-9621-0116414fdf2e,0x800,0x80000)/File(\EFI\MX21\GRUBX64.EFI)
Boot0001* UEFI OS	HD(1,GPT,909266f5-c2d1-4065-9621-0116414fdf2e,0x800,0x80000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

next, inxi -Faz:

System:    Kernel: 5.10.0-18-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-18-amd64 
           root=UUID=431780db-759f-45b2-a6ec-a16ab5bf976d ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: ASUSTeK product: E203NA v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: E203NA v: 1.0 serial: <filter> UEFI: American Megatrends 
           v: E203NA.304 date: 10/23/2017 
Battery:   ID-1: BAT0 charge: 24.5 Wh (85.1%) condition: 28.8/38.0 Wh (75.7%) volts: 7.6 
           min: 7.6 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Discharging 
           cycles: 8 
CPU:       Info: Dual Core model: Intel Celeron N3350 bits: 64 type: MCP arch: Goldmont 
           family: 6 model-id: 5C (92) stepping: 9 microcode: 48 cache: L1: 112 KiB L2: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 4377 
           Speed: 887 MHz min/max: 800/2400 MHz base/boost: 1100/2400 volts: 1.2 V 
           ext-clock: 100 MHz Core speeds (MHz): 1: 887 2: 875 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass status: Not affected 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 500 vendor: ASUSTeK driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:5a85 class-ID: 0300 
           Device-2: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:3 
           chip-ID: 04f2:b54b class-ID: 0e02 serial: <filter> 
           Display: server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
           s-diag: 414mm (16.3") 
           Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 136 size: 256x144mm (10.1x5.7") 
           diag: 294mm (11.6") 
           OpenGL: renderer: Mesa Intel HD Graphics 500 (APL 2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster 
           vendor: ASUSTeK driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci 
           bus-ID: 00:0e.0 chip-ID: 8086:5a98 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
           vendor: AzureWave driver: ath10k_pci v: kernel modules: wl port: f040 bus-ID: 01:00.0 
           chip-ID: 168c:0042 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-5:2 
           chip-ID: 13d3:3501 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 25a hci-v: 4.2 
           Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 29.12 GiB used: 5.64 GiB (19.4%) 
           ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: HP model: DF4032 size: 29.12 GiB 
           block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 0x8 
           scheme: GPT 
           SMART Message: Unknown smartctl error. Unable to generate data. 
Partition: ID-1: / raw-size: 27.36 GiB size: 26.77 GiB (97.82%) used: 5.63 GiB (21.0%) fs: ext4 
           block-size: 4096 B dev: /dev/mmcblk0p2 maj-min: 179:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) 
           fs: vfat block-size: 512 B dev: /dev/mmcblk0p1 maj-min: 179:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 1.5 GiB used: 7.5 MiB (0.5%) priority: -2 
           dev: /dev/mmcblk0p3 maj-min: 179:3 
Sensors:   System Temperatures: cpu: 43.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 205 Uptime: 27m wakeups: 2 Memory: 1.8 GiB used: 1.54 GiB (85.3%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Packages: note: see --pkg apt: 1952 lib: 979 flatpak: 0 Shell: Bash (sudo) 
           v: 5.1.4 running-in: xfce4-terminal inxi: 3.3.06