Hey Thanks for the support,
i tried everything you have mentioned, Here is the complete konsole log.
everything seems to be fine yet i still gets the Issue, (even before grubmenu)
“error: Environment block too small.
error: failure reading sector 0x38a96d80 fron ‘hd2’
error: you need to load the kernel first.
Press any key to continue…
Failed to boot both default and fallback entries.”
sbctl does not do anything on it’s own; without configuration - that is a key and a bundle - it is just sitting there.
If you feel the message is disturbing - remove the package
sudo pacman -Rns sbctl
Or you can leave it and instead run
sudo sbctl create-keys
@stephane already pointed you to the topic that describes how you setup secure boot - but unless you actually create a configuration, sbctl does absolutely nothing.
Let me emphasize - sbctl is not the reason for your woes.
One notice before everything
Basically my root mount point on a disk which is connected via my cd/dvd rom. coz im tryina install this to old lap which doesnt have any extra storage.
As per @stephane’s instructions i booted into live usb (secure boot off) and logged into chroot and tired grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
no issues it passed without error. then did, grub-mkconfig -o /boot/grub/grub.cfg
after executing that is the part where i got that sbctl error yet the execution completes.
Complete log as follows
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
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.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
[manjaro /]# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.21-4-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [kms]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Running post hooks
-> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64-fallback.img -S autodetect
==> Starting build: '6.12.21-4-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [microcode]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Running post hooks
-> Running post hook: [sbctl]
Secureboot key directory doesn't exist, not signing!
==> Post processing done ```
No i havent used any script /git / github just fresh installed and tried to boot
At this point, more information would be needed to allow others to form an opinion. Please provide system information as described (below), as well as the outputs of the following commands;
lsblk -f
cat /etc/fstab
I’m sure someone will help when they are able.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
Update Announcements
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;
Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=52C2-21B4 /boot/efi vfat defaults,umask=0077 0 2
UUID=6d420b87-ae34-413f-a135-5f722a66affb / ext4 defaults
Mod edit:- Corrected minor formatting errors.
Still expecting system information, as requested.
You are having the $esp (EFI System Partition) on one disk and the root on the second disk.
As you say SATA enclosure - I assume it is connected using USB.
This could be the cause of your problem especially if the target - assumed USB connected - disk is not available when you try to boot the entry.
Always keep your $esp and root on the same disk.
Never mix EFI and BIOS boot - grub cannot handle the mix and it is therefore either/or when you are using grub.
IF you use the firmware boot override (like you do with install media) thus skipping the grub boot loader; there is no issues mixing EFI and BIOS - again - only if your $esp is on the same - assumed USB connected - disk.
Thank you everyone for the support—I found the issue.
It was my SATA enclosure. The enclosure was connected using IDE mode, which doesn’t support loading the kernel. Unfortunately, my BIOS doesn’t allow me to force the enclosure to use an AHCI connection. So, I mounted my boot mount point on a disk that is directly connected to the motherboard, which resolved the issue.
