My GRUB boot loader suddendly gone missing...

valo1234 · 2025-05-19 15:27:18

I was using my arch linux swiftly until I receive the message -

Linux Kernel is out of memory , hence Firefox is closed

.
I thought okay, no problem. But then, my screen froze, my mouse cursor was stuck. No effect of moving here and there on my touchpad. keyboard shortcuts was not working. So, I did force shut down and on power on, found this -

Default boot device Missing or Boot failed. Insert Recovery media and hit key ..........

This clearly shows that my system boot is missing. So, I check my BIOS page, and it was right. I didn't found the my GRUB boot entry.

1) So far, I booted into live USB. and entered command

lsblk

, I was able to see my all partitions(which I had created on my SSD ), but there mount point is missing. I also tried to arch-chroot. It shows,

no chroot is specified

What should I do next or what resources I should refer , Your help is greatly appreciated.

Scimmia · 2025-05-19 15:31:38

valo1234 wrote:

I was able to see my all partitions(which I had created on my SSD ), but there mount point is missing. I also tried to arch-chroot. It shows,
no chroot is specified

What should I do next or what resources I should refer , Your help is greatly appreciated.

You have to mount them and arch-chroot exactly the same way you did when you set the system up.

valo1234 · 2025-05-19 16:35:11

okey, so I have to follow the installation guide exaclty the same way ?
Also, will I need to reinstall firefox , plasma ,etc again ?

Xylerfox · 2025-05-20 00:53:38

valo1234 wrote:

okey, so I have to follow the installation guide exaclty the same way ?
Also, will I need to reinstall firefox , plasma ,etc again ?

You just need to re-mount the partitions before you can arch-chroot again.

Mount your root to /mnt
Mount your home to /mnt/home (if your home is on a different partition)
Mount your boot to /mnt/boot (if that's how you did it)

Once you mount all your mount points like the install guide, you can then chroot into your Arch install and fix what you need to!

I would just rebuild your boot loader first, then see if Plasma and Firefox need a reinstall

valo1234 · 2025-05-20 01:09:07

Okey, as far I remember I have did the partition in the following way,
3 partition of SSD -
1) 1GB for boot - /mnt/efi
2) 4GB for swap - swap partition
3) remaining for root - /mnt

Is this fine ??

valo1234 · 2025-05-20 02:17:07

I am trying to remount the partition as I described in the last post.
After all mount , when i go in arch-chroot /mnt, the mount for EFI partition is not showing.
for root it show - / (as I did /mnt for root )

any idea ??

valo1234 · 2025-05-20 04:25:19

Hi, Problem is resolved. Moslty I believe was not following the right order for mounting. After doing this right way, I can see the mounts in my chroot and yes , I am successfully booted in into my system.
But earlier my system used to take around 12-15 seconds to boot and surprisingly now it is taking 1min 42 seconds, which is huge. So, I ran the systemd commands below are the outputs

Startup finished in 2.642s (firmware) + 2.399s (loader) + 4.089s (kernel) + 1min 31.551s (userspace) = 1min 40.682s 
graphical.target reached after 1min 31.551s in userspace.

2)

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 31.551s
└─sddm.service @1min 31.551s
  └─plymouth-quit.service @1min 31.510s +38ms
    └─systemd-user-sessions.service @1min 31.486s +19ms
      └─network.target @1min 31.483s
        └─wpa_supplicant.service @1min 31.454s +28ms
          └─basic.target @1min 30.714s
            └─dbus-broker.service @1min 30.667s +44ms
              └─dbus.socket @1min 30.652s
                └─sysinit.target @1min 30.650s
                  └─systemd-update-utmp.service @1min 30.622s +27ms
                    └─systemd-tmpfiles-setup.service @1min 30.556s +64ms
                      └─local-fs.target @1min 30.549s
                        └─tmp.mount @1min 30.518s +30ms
                          └─systemd-journald.socket @302ms
                            └─-.mount @268ms
                              └─-.slice @268ms

3) I checked journalctl logs, this is what I found.

May 20 09:36:33 valo systemd[1]: systemd-rfkill.service: Deactivated successfully.
May 20 09:37:57 valo systemd[1]: dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d441e\x2d9426\x2d42c82ff28882.device: Job dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d4>
May 20 09:37:57 valo systemd[1]: Timed out waiting for device /dev/disk/by-uuid/ef322d0b-f2af-441e-9426-42c82ff28882.
May 20 09:37:57 valo systemd[1]: Dependency failed for /dev/disk/by-uuid/ef322d0b-f2af-441e-9426-42c82ff28882.
May 20 09:37:57 valo systemd[1]: Dependency failed for Swaps.
May 20 09:37:57 valo systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
May 20 09:37:57 valo systemd[1]: dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d441e\x2d9426\x2d42c82ff28882.swap: Job dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d441>
May 20 09:37:57 valo systemd[1]: dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d441e\x2d9426\x2d42c82ff28882.device: Job dev-disk-by\x2duuid-ef322d0b\x2df2af\x2d4>
May 20 09:37:57 valo systemd[1]: Mounting Temporary Directory /tmp...
May 20 09:37:57 valo systemd[1]: Mounted Temporary Directory /tmp.
May 20 09:37:57 valo systemd[1]: Reached target Local File Systems.
May 20 09:37:57 valo systemd[1]: Listening on Boot Entries Service Socket.

Major time and time out error occured in my swap partition. Can u guys suggest me further steps .

valo1234 · 2025-05-20 05:02:43

Hi,
Issue has been resolved. I see that my boot had difficulty in finding swap. Probably due to diff in UUId in fstab and actual UUID for the partition.
so, i check and this was the really a issue. So i ran- mkswap, got new UUID for swap partition . and then

swapon

and reboot.
Now, it is back to as it was earlier. 11-14 seconds for boot .

Thank you guys for your support.

Arch Linux

#1 2025-05-19 15:27:18

My GRUB boot loader suddendly gone missing...

#2 2025-05-19 15:31:38

Re: My GRUB boot loader suddendly gone missing...

#3 2025-05-19 16:35:11

Re: My GRUB boot loader suddendly gone missing...

#4 2025-05-20 00:53:38

Re: My GRUB boot loader suddendly gone missing...

#5 2025-05-20 01:09:07

Re: My GRUB boot loader suddendly gone missing...

#6 2025-05-20 02:17:07

Re: My GRUB boot loader suddendly gone missing...

#7 2025-05-20 04:25:19

Re: My GRUB boot loader suddendly gone missing...

#8 2025-05-20 05:02:43

Re: My GRUB boot loader suddendly gone missing...

Board footer