/@/boot/vmlinuz-5.10-x86_64’ not found

Hello, i have a trouble with booting my system after updating.

error: /@/boot/vmlinuz-5.10-x86_64’ not found,
error: you need to load the kernel first.

When i try to use chroot on the live iso:

grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
==> ERROR: No Linux partitions detected!

Help me pls :slight_smile:

Hi @say8hi, and welcome!

From the live ISO, please provide the output of:

sudo lsblk

and

sudo fdisk -l

Ok

sudo lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0  71.3M  1 loop /run/miso/sfs/livefs
loop1    7:1    0 877.9M  1 loop /run/miso/sfs/mhwdfs
loop2    7:2    0   1.8G  1 loop /run/miso/sfs/desktopfs
loop3    7:3    0 770.9M  1 loop /run/miso/sfs/rootfs
sda      8:0    0 232.9G  0 disk 
├─sda1   8:1    0   100M  0 part /mnt
├─sda2   8:2    0    16M  0 part 
├─sda3   8:3    0 150.3G  0 part 
├─sda4   8:4    0   520M  0 part 
├─sda5   8:5    0     8G  0 part 
└─sda6   8:6    0    65G  0 part /run/media/manjaro/0dc34ae4-3bca-4c22-940a-41672b8b6d78
sdb      8:16   0 931.5G  0 disk 
├─sdb1   8:17   0   128M  0 part 
├─sdb2   8:18   0 491.3G  0 part 
└─sdb3   8:19   0 418.3G  0 part 
sdc      8:32   1  28.9G  0 disk /run/miso/bootmnt
├─sdc1   8:33   1   3.6G  0 part 
└─sdc2   8:34   1     4M  0 part

sudo fdisk -l:

Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WDS250G2B0A 
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: 356896D9-3355-4BD2-830B-34426A392D7E

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    206847    204800   100M EFI System
/dev/sda2     206848    239615     32768    16M Microsoft reserved
/dev/sda3     239616 315346943 315107328 150.3G Microsoft basic data
/dev/sda4  315346944 316411903   1064960   520M Windows recovery environment
/dev/sda5  452726784 469503999  16777216     8G Linux swap
/dev/sda6  316411904 452726783 136314880    65G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DL002-9TT1
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: CE29F822-E4F5-11EA-9FC1-18C04D28920F

Device          Start        End    Sectors   Size Type
/dev/sdb1        2048     264191     262144   128M Microsoft reserved
/dev/sdb2      264192 1030522879 1030258688 491.3G Linux filesystem
/dev/sdb3  1030522880 1907795967  877273088 418.3G Microsoft basic data


Disk /dev/loop0: 71.34 MiB, 74805248 bytes, 146104 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/loop1: 877.87 MiB, 920514560 bytes, 1797880 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/loop2: 1.81 GiB, 1940754432 bytes, 3790536 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/loop3: 770.86 MiB, 808308736 bytes, 1578728 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/sdc: 28.9 GiB, 31029460992 bytes, 60604416 sectors
Disk model: DataTraveler 3.0
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: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdc1  *         64 7469523 7469460  3.6G  0 Empty
/dev/sdc2       7469524 7477715    8192    4M ef EFI (FAT-12/16/32)

How? What command?
We generally use the automagic tool:

manjaro-chroot -a

Yeah, i used it:

    ~  sudo manjaro-chroot -a                                                                         ✔ 
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
==> ERROR: No Linux partitions detected!

It seems to me, that perhaps there is a hard drive missing from the listing. Or something. Because something doesn’t quite look right to me.

Do you have just the two hard drives in your computer?

Basically, that error, from the subject, looks like a Btrfs path to me, and I don’t see any Btrfs file systems…

I have 1 SSD that contains Manjaro and Windows 10, and i have 1 HDD for games, pictures and videos.
And i’m using btrfs for manjaro

That’s what I figured.

But, unfortunately I know nothing of Btrfs so won’t be able to help you further.

:sob:

However, please see [HowTo] Provide System Information and, if applicable, [HowTo] post screenshots and links.

You may take a look here:
https://wiki.manjaro.org/index.php?title=GRUB/Restore_the_GRUB_Bootloader#Manual_chroot

Whether or not you actually need to ‘restore grub’ … that guide should help you manually chroot.

Oh, i’ve tried it, but had this error:

mount: /mnt: special device /dev/sdyC does not exist.

Ok, thank you for your try

Well its true that it does not.
The wiki shows examples … it is not meant to be simply copied.
According to your output I think your linux filesystem is sda6 … and since you are using btrfs you need an extra flag as shown in the wiki …

su -
mount -o subvol=@ /dev/sda6 /mnt 

Oh, it works, and then i need to do the same with boot and efi:

mount -o subvol=@ /dev/sda6 /mnt/boot

and

mount -o subvol=@ /dev/sda6 /mnt/boot/efi

Like this?

Not quite.
Again, it is applicable to the variables of your system makeup…
(again from root, within su, as above)

 mount -o subvol=@ /dev/sda1 /mnt/boot/efi

That should be it … you can exit root (su) with command exit.
(the same for exiting chroot when you are finished)
Now you should be able to do what needs to be done - double check your updates and packages and all that.

Ok, i’ll try it, thank you very much!

Cheers.

PS - One of my first steps would probably be going to look in /var/log/pacman.log for any clues.

Meh … heres a one-liner for the last 2 days of transactions:

lnglastx=$(tail -n1 /var/log/pacman.log | awk '{print $1}'); lastx=${lnglastx:1:10}; lastlastx=$(grep -B1 "$lastx" /var/log/pacman.log | head -n1 -c11 | cut -c 2-); printf '\n\nWhat you did the time before:\n\n'; grep -n "$lastlastx" /var/log/pacman.log; printf '\n\nWhat you did last time:\n\n'; grep -n "$lastx" /var/log/pacman.log; printf '\n'