[SOLVED] Can't access linux, grub not load, only works with intramfs.

rufusreal · 2023-03-09 00:18:19

For some reason after doing chroot with a live environment and reinstall grub, I am stocked with grub startup.

Grub does not load directly I have to choose the seconf option of GRUB (not Arch Linux) and then select intramfs.

I would like to fix Arch instead of reinstalling again the system and another problem the boot loader does not load my usb with Garuda Linux for installing Arch in case I can't fix grub. Someone can help me.

Last edited by rufusreal (2023-03-09 23:58:26)

jonno2002 · 2023-03-09 01:33:44

how is your system setup ? do you have /boot on the efi partition ? if so make sure you mount that AFTER /root before chrooting.

rufusreal · 2023-03-09 01:55:41

jonno2002 wrote:

how is your system setup ? do you have /boot on the efi partition ? if so make sure you mount that AFTER /root before chrooting.

Yes I have /boot partition, and I booted into the live environment and I mounted /(root) and then /boot, but I don't if it is conflicting with /boot/efi because for some reason I cant mount that directory (EFI), and my motherboard is UEFI.

I notice I have zram partition but it is not used as swap, and the only thing that may cause that error is some line on grub configuration. But I'm very new configuring GRUB.

This is the only line I have changed on "/etc/default/grub"

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset systemd.zram=0"

Last edited by rufusreal (2023-03-09 01:57:56)

jonno2002 · 2023-03-09 02:24:19

remove these and try again:

nomodeset systemd.zram=0

and why are they even there ? what made you think they were needed ?

as for the efi thing it again depends how you set it up, how did you install arch ?

rufusreal · 2023-03-09 02:34:04

I have removed those parameters from Grub line but same issue at starting the computer.

I installed Arch with archinstall and have two partitions one with /boot (fat32) and other / (btrfs with subvolumes created by default).

I think the system was created with zram swap but trying to fix the suspend mode to wake up properly (because the screen goes black after waking up) I try to remove the zram and create a swapfile with the memory of the RAM.

Then I break Grub and tried to fix it doing Chroot from a live environment. I could start one time but the rest of the time only works from intramfs.

Last edited by rufusreal (2023-03-09 02:36:02)

jonno2002 · 2023-03-09 03:03:15

did you run grub-mkconfig after removing those entries ?
i cant help with suspend issues as i dont use it sorry.
have a read of this page: https://wiki.archlinux.org/title/Swap

rufusreal · 2023-03-09 03:14:35

jonno2002 wrote:

did you run grub-mkconfig after removing those entries ?
i cant help with suspend issues as i dont use it sorry.
have a read of this page: https://wiki.archlinux.org/title/Swap

Yes, I updated grub with "sudo grub-mkconfig -o /boot/grub/grub.cfg" but same error.

The thing was that using Arcolinux before installing Arch I can suspend nicely the system. And the difference is that I was using ext4, swap partition and now I am on btrfs without swap.

rufusreal · 2023-03-09 03:17:09

If can't fix this problem with grub, I will reinstall the system with Garuda or Arcolinux.

I'm tired of facing issues with grub.

And next time I would do a snapshot from the beginning, but I have to learn how to use properly.

jonno2002 · 2023-03-09 03:30:05

have you changed anything in /etc/mkinitcpio.conf ? if so remove that and run:

mkinitcpio -P

in the chroot
if you didnt make changes run it anyway and see if that fixes your problem

EDIT: arch requires you to know your system inside out so you can maintain it correctly and fix problems if they arise, if thats not your thing then best to switch to something else.

Last edited by jonno2002 (2023-03-09 03:32:33)

rufusreal · 2023-03-09 03:42:26

jonno2002 wrote:

have you changed anything in /etc/mkinitcpio.conf ? if so remove that and run:
mkinitcpio -P
in the chroot
if you didnt make changes run it anyway and see if that fixes your problem
EDIT: arch requires you to know your system inside out so you can maintain it correctly and fix problems if they arise, if thats not your thing then best to switch to something else.

I haven't touched mkinitcpio.conf

In the Chroot, do you mean booting from a live environment right?

I think EFI has some problem because I cannot mounted, (I mounted only /boot) when I reinstalled grub from the live environment.

jonno2002 · 2023-03-09 03:51:54

i guess if you can boot the fallback initramfs which i think is what you mean then just do it there.
whats the output of:

lsblk -f
fdisk -l
cat /etc/fstab
ls /boot
ls /boot/EFI

do these while booted from the fallback initramfs

rufusreal · 2023-03-09 04:06:18

lsblk -f
fdisk -l
cat /etc/fstab
ls /boot
ls /boot/EFI

Okey I'll do it tomorrow.

And Idk why fallback intramfs works fine but not the rest.

rufusreal · 2023-03-09 14:25:04

### lsblk -f
NAME        FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                     
└─sda1      ext4   1.0   ssd-backup 1b06c83a-f4fb-4cc5-bc92-d05000f5dd12                
zram0                                                                                   [SWAP]
nvme0n1                                                                                 
├─nvme0n1p1 vfat   FAT32            E623-2873                             435.1M    15% /boot
└─nvme0n1p2 btrfs                   a1a0d266-8841-4091-aab7-bc29a05292d1  892.1G     4% /var/log
                                                                                        /var/cache/pacman/pkg
                                                                                        /home
                                                                                        /.snapshots
                                                                                        /
nvme1n1     ext4   1.0              e2db7ead-a4e1-4dae-a3c1-b2e00398db63  290.4G    63% /0

#### sudo fdisk -l
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: KINGSTON SKC2000M81000G                 
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: F1F7390E-F8B0-4A86-85E4-F180EAFD8483

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    2048    1048575    1046528  511M EFI System
/dev/nvme0n1p2 1050624 1953523711 1952473088  931G Linux filesystem

Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WD Blue SN570 1TB                       
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/zram0: 4 GiB, 4294967296 bytes, 1048576 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Tech            
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 64ECCD06-C01D-4BEE-B40F-9C8577AF67FF

Device     Start        End    Sectors   Size Type
/dev/sda1   2048 1953523711 1953521664 931.5G Linux filesystem

#### cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
UUID=a1a0d266-8841-4091-aab7-bc29a05292d1       /               btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@ 0 0

# /dev/nvme0n1p1
UUID=E623-2873          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro       0 2

# /dev/nvme0n1p2
UUID=a1a0d266-8841-4091-aab7-bc29a05292d1       /.snapshots     btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=260,subvol=/@.snapshots       0 0

# /dev/nvme0n1p2
UUID=a1a0d266-8841-4091-aab7-bc29a05292d1       /home           btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home     0 0

# /dev/nvme0n1p2
UUID=a1a0d266-8841-4091-aab7-bc29a05292d1       /var/cache/pacman/pkg   btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@pkg      0 0

# /dev/nvme0n1p2
UUID=a1a0d266-8841-4091-aab7-bc29a05292d1       /var/log        btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@log      0 0

# /dev/nvme1n1
UUID=e2db7ead-a4e1-4dae-a3c1-b2e00398db63 /0       ext4     noatime   0  2

# swapfile
# /swapfile none swap sw 0 0

#### ls /boot
amd-ucode.img  EFI  grub  initramfs-linux-fallback.img  initramfs-linux.img  vmlinuz-linux

#### ls /boot/efi
BOOT  EFI  GRUB

Last edited by rufusreal (2023-03-09 14:27:59)

jonno2002 · 2023-03-09 15:45:36

that all looks fine, your /boot partition is also your EFI partition so it is mounted.
did you run mkinitcpio yet ?

rufusreal · 2023-03-09 18:27:40

jonno2002 wrote:

that all looks fine, your /boot partition is also your EFI partition so it is mounted.
did you run mkinitcpio yet ?

No, I haven't run mkinitcpio. Did need to run mkinitcpio from Chroot or I can run inside the terminal from my main archlinux?

jonno2002 · 2023-03-09 23:22:25

run it from the fallback boot, the arch-chroot is only when you cant boot into your system at all, but since the fallback is working you can use that.

rufusreal · 2023-03-09 23:56:40

jonno2002 wrote:

run it from the fallback boot, the arch-chroot is only when you cant boot into your system at all, but since the fallback is working you can use that.

It works, thank you very much. I just execute "sudo mkinitcpio -p linux" and backup the intramfs-linux.img before.

I rebooted the system and left the PC and when I came out it was the screen login of KDE (SDDM) and not stuck on grub.

I haven't tried to suspend and wake up but the load of kernel with grub seems to work fine again.

Last edited by rufusreal (2023-03-09 23:59:18)

Arch Linux

#1 2023-03-09 00:18:19

[SOLVED] Can't access linux, grub not load, only works with intramfs.

#2 2023-03-09 01:33:44

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#3 2023-03-09 01:55:41

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#4 2023-03-09 02:24:19

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#5 2023-03-09 02:34:04

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#6 2023-03-09 03:03:15

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#7 2023-03-09 03:14:35

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#8 2023-03-09 03:17:09

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#9 2023-03-09 03:30:05

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#10 2023-03-09 03:42:26

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#11 2023-03-09 03:51:54

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#12 2023-03-09 04:06:18

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#13 2023-03-09 14:25:04

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#14 2023-03-09 15:45:36

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#15 2023-03-09 18:27:40

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#16 2023-03-09 23:22:25

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

#17 2023-03-09 23:56:40

Re: [SOLVED] Can't access linux, grub not load, only works with intramfs.

Board footer