Manjaro xfce couldn't install boot

I got this error when installing Manjaro, it copied it to web, here:
https://termbin.com/w1fo8

What’s up? Why couldn’t it install bootloader?

EDIT: Tried it again, same error:

“Bootloader nije mogao biti instaliran. Instalacijska naredba

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --force
je vratila kod pogreške 1.”

Translation:

Bootloader couldn’t be installed. Installation command (the command up there) returned error code 1.

EDIT2: I ran sudo calamares from the terminal to see what output i’ll get…

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
chcon: failed to get security context of '/': Operation not supported
Create subvolume '/tmp/calamares-root-ydlwqpo6/@'
Create subvolume '/tmp/calamares-root-ydlwqpo6/@home'
Create subvolume '/tmp/calamares-root-ydlwqpo6/@cache'
Create subvolume '/tmp/calamares-root-ydlwqpo6/@log'
umount: /tmp/calamares-root-ydlwqpo6 unmounted
chcon: failed to get security context of '/boot/efi': Operation not supported
chcon: failed to get security context of '/dev': Operation not supported
chcon: failed to get security context of '/proc': Operation not supported
chcon: failed to get security context of '/run': Operation not supported
chcon: failed to get security context of '/run/udev': Operation not supported
chcon: failed to get security context of '/sys': Operation not supported
chcon: failed to get security context of '/sys/firmware/efi/efivars': Operation not supported
17:20:27 [1]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
    ERROR: Installation failed: "Greška prilikom instalacije bootloadera" 

Your log shows:

 Installing for x86_64-efi platform.
Could not delete variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Block device required.

It would be like the boot partition has no space.

Can you show uns how to create partitions?

The boot partition ha 512 Mib of space…

Also, the “primary” monitor is switched lol, i have calamares on the right monitor, but it shows it correctly here haha.

Anyway, that’s the partition scheme…

If i set it to “erase disk” it creates swap at the end, no boot-grub at the start, and a 300Mib /boot/efi partition… So 512 should be more than enough… Maybe i’ll just let it partition the disk itself, see if that works.

EDIT: Also, once i created the partition scheme, “erase disk” option no longer appears.
And unmounting the partitions in gparted becomes impossible, i have to completely restart the live session to try again.

I’ll do that now and select “erase disk”, see if that works. I’m not setting any special partitions anyway.

Nope, same thing, default install wouldn’t complete either:

https://termbin.com/8dbh

Same error…

 Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
2023-02-11 - 18:04:06 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --force' returned non-zero exit status 1." 
2023-02-11 - 18:04:06 [6]: [PYTHON JOB]: "stdout:Installing for x86_64-efi platform.\nCould not prepare Boot variable: No space left on device\ngrub-install: error: efibootmgr failed to register the boot entry: Input/output error." 
2023-02-11 - 18:04:06 [6]: [PYTHON JOB]: "stderr:None" 
2023-02-11 - 18:04:06 [6]: virtual void Calamares::JobThread::run()
    Skipping non-emergency job "postcfg" 
2023-02-11 - 18:04:06 [6]:     ..  Skipping non-emergency job "Unmount file systems." 
2023-02-11 - 18:04:06 [1]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
    ERROR: Installation failed: "Bootloader installation error" 
2023-02-11 - 18:04:06 [6]:     .. - message: "Bootloader installation error" 
2023-02-11 - 18:04:06 [6]:     .. - details: The bootloader could not be installed. The installation command <pre>grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --force</pre> returned error code 1.
2023-02-11 - 18:04:06 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
    Calamares will quit when the dialog closes. 
2023-02-11 - 18:04:06 [6]: void Config::doNotify(bool, bool)
    Notification not sent; completion: failed 

Is the NVME failing?

I mean, write errors (contained to KDE, but still…), now there’s a “not enough space” error…

There’s a “sanitize” option on my bios for nvme drives, should i try that?
And if it IS failing. how do i tell? How can i prove it’s failing to get a refund? The drive is new, not even 2, 3 months old…

Can you check this Manjaro XFCE ISO with sha1sum if it is correct?

sha1 of manjaro-xfce-22.0.2-230203-linux61.iso is:

cc874bcc207ad747cb5bd4ebe8f4c7a9784440ff
  • If it matches sha1 correctly, the hardware might be the problem.

  • If no, try downloading Manjaro XFCE ISO again and copying it into USB using ventoy

can you report , from live USB iso

inxi -Fza 
sudo parted -l 

The ISO is gone. I just flashed it with Balena Etcher, and now the nvme is deleted with prtitioning, i saw no reason to put the iso on my backup drive.

I will however, download a new one, check the sum, use ventoy this time and then try to install.
Thank god for linux live environments lol.

inxi -Fza

System:
  Kernel: 6.1.9-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_XFCE_2202 quiet
    systemd.show_status=1 splash apparmor=1 security=apparmor driver=free
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: B550M Pro4 serial: <superuser required>
    UEFI: American Megatrends LLC. v: P2.30 date: 02/24/2022
CPU:
  Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1614 high: 2983 min/max: 1400/4464 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2983 2: 1400
    3: 1400 4: 2388 5: 1400 6: 1400 7: 1400 8: 1400 9: 1400 10: 1400 11: 1400
    12: 1400 bogomips: 93460
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  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 mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm)
    built: 2018-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: DP-1,HDMI-A-1 empty: DP-2 bus-ID: 05:00.0
    chip-ID: 1002:1638 class-ID: 0300 temp: 28.0 C
  Display: x11 server: X.Org v: 21.1.6 compositor: xfwm v: 4.18.0 driver: X:
    loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1354x381mm (53.31x15.00")
    s-diag: 1407mm (55.38")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left
    model: AOC Q3279WG5B serial: <filter> built: 2020 res: 2560x1440 hz: 60
    dpi: 90 gamma: 1.2 size: 725x428mm (28.54x16.85") diag: 842mm (33.1")
    ratio: 15:9 modes: max: 2560x1440 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: right model: AOC Q3279WG5B
    serial: <filter> built: 2020 res: 2560x1440 hz: 60 dpi: 90 gamma: 1.2
    size: 725x428mm (28.54x16.85") diag: 842mm (33.1") ratio: 15:9 modes:
    max: 2560x1440 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 3-2.2:4 pcie: gen: 3 chip-ID: 1235:8200 class-ID: 0103
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 05:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-3: Focusrite-Novation Scarlett 2i4 USB type: USB
    driver: snd-usb-audio
  Sound API: ALSA v: k6.1.9-1-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.21 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 3-2.1:3 chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 706.1 GiB used: 152.83 GiB (21.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S500G
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: SBI02102 temp: 34.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 1B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Kingston model: DT101 II
    size: 7.46 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A gpu: amdgpu temp: 29.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 308 Uptime: 1h 25m wakeups: 0 Memory: 30.73 GiB
  used: 3.71 GiB (12.1%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
  pkgs: 1145 libs: 317 tools: pamac pm: flatpak pkgs: 0 Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.24

sudo parted -l

Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  250GB  250GB  btrfs


Model: Kingston DT101 II (scsi)
Disk /dev/sdb: 8006MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      4085MB  4090MB  4194kB  primary               esp


Model: KINGSTON SNV2S500G (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   491GB  490GB   btrfs           root
 3      491GB   500GB  9449MB  linux-swap(v1)        swap

I’m trying to install it on the nvme drive.

This happens when booting from ventoy.

Any other usb creators i can use?

Update:
I tried to to install Endeavor just to test if itll have the same problem, it installed no problem.

Ill keep testing it dor now to see if the nvme is failing.

The last question, had you experienced these issues 3 months ago with your old drive and Btrfs in your same computer?

Not exactly, i first had Windows 10 on the SSD. Then i bought the nvme and installed PopOS on it with ext4. I didn’t use it for very long because it was pretty troublesome to set up audio on it, so i installed Manjaro and set up everything pretty easily.

More or less from the start, KDE has been exhibiting strange behaviour at times, and pretty early in, the error where the KDE files changed ownership occured. I even posted a thread about it here.
Meanwhile, Windows 10 became completely laggy, unusable, and later crashed completely (cause Manjaro set up dual boot for it, so i could still enter that installation). It behaved similar to how manjaro did later, it’s desktop became unusable, frozen, and just overall it stuttered before the crash.
I didn’t think much of it at the time. But Windows 10 was on a different SSD.
Things on Manjaro only became more frequent as time went on.

And now - EndeavourOS is exhibiting the same things Manjaro was. It installed normally as opposed to Manjaro, but pretty soon, the login screen from KDE disappeared, and while i was able to log in because the screen on the second monitor was fine - i though hey, it’s probably KDE being buggy.
So i switched to xfce EndeavourOS to try, and nope:

326275318_4269556463270523_3939477981732448144_n

On both Manjaro and Endeavour, browser tabs (and browsers themselves) keep crashing constantly, Firefox, Brave, VIvaldi, no matter which one i tried, tabs crash constantly.
And then all the folders on xfce endeavour became locked with this error.
Searching it, seems like some network thing, but i was triyng to browse local folders on the nvme.

I even tried to install balena etcher to make a memtest iso for further testing, and it too gave me I/O errors!

So it’s probably not linux, it’s probably my hardware…

I believe the USB stick is the issue. Try to use other USB stick with USB 3.0+

Yes, I thought so too.

1 Like

No, on the installed OS. The USB stick is fine. It won’t even install balena from AUR, cause installing it gave errors that it couldn’t write to disk, not that Balena couldn’t write to USB.

I already sent emails to the nvme manufacturer and the Motherboard manufacturer, i’m waiting for their response. All the stuff is new, so i should get a replacement if needed… Hopefully…

Be careful, we do not trust the USB stick why Ventoy failed to boot, why can’t /dev/loop1 be mounted before installation. See your photo:

Ventoy with Manjaro XFCE ISO should work fine in my test.

I suspect the faulty USB could cause multiple corruptions in your system after intallation.

1 Like

No the ventoy thing didn’t even boot, i installed the system from an usb created with balena etcher.

Here’s what i’m thinking… Just to test if it’s the hardware.
I’m going to use a completely new USB stick, created with something else than balena or ventoy.
Install Fedora (so not arch based) with default GNOME (so neither KDE or xfce to rule those out), with a different file system (to rule out btrfs).

If the system STILL experiences instability, in the same or similar way it does here - then it’s definitely a hardware issue on my computer.

I suspect it will, but this will just confirm it. Because, if a completely different based linux, with different DE, different file system also behaves the same, that confirms a hardware error.

And if it doesn’t behave this way, yeah i know i will have changed too many variables to pin it down, but at least i’ll know some of that is at fault. I think it’s hardware though, i suspect it’ll be the same instability. We’ll see…

have you checked your memory ?

He did. See here:

:white_check_mark: Memtest passed

:question: mprime test

:white_check_mark: Copy any large file from other partition to the partition and verify it with sha1sum

:question: Test USB connection

:question: Switch to other hard drive if it has a same issue

memtest failed , I/O errors …

Memtest passed but, yeah, unexplained i/o errors.

Edit:
Just to dismiss memory problems altogether - im running memtest on each individual stick separately again. This will take time, but it should guve me a definitive answer.