Created attachment 888490 [details] emerge --info, grub and kernel version It only prints "GRUB " and stop. Numlock, and also Ctrl+Alt+Del is works. Bug appears on system with quite old m/board only when I switch internal SATA controller to RAID mode (actually not configuring the RAID, just pass the drives "as is"). Booting from Gentoo Linux Minimal Installation CD causes no problem, so I can chroot into installed Gentoo, and also get related info. The RAID controller is: # lspci |grep RAID 00:1f.2 RAID bus controller: Intel Corporation 5 Series/3400 Series Chipset SATA RAID Controller (rev 05) Any advices about how to debug an unbug this are appreciated.
It's new installation, all done following handbook. The system boots fine with SATA controller in the IDE mode, but I prefer it boot with SATA controller in the RAID mode. Already tried to add to grub.cfg: set pager=1 set debug=all But without luck - GRUB hangs up at boot with no addidional info.
Is this a BIOS or UEFI based system? Have you tried re-running grub-install while booted with with the controller in RAID mode?
Is this a BIOS or UEFI based system? > 1st try it was BIOS mode. Now also tested in UEFI mode (recompiled grub w/support both, re-formatted /boot as FAT16, rebooted, switched BIOS to UEFI, booted to MinCD, chrooted, installed GRUB in UEFI mode, rebooted) and.. nothing. Same hang up, but even without "GRUB " text. Have you tried re-running grub-install while booted with with the controller in RAID mode? > yes, I was More info: 1. I have M.2 drive connected via adapter. M/board is not support NVME, so (when in BIOS boot mode) when installing OS, I mount M.2 partition drive to (/mnt/gentoo)/, and usb flash stick partition to (/mnt/gentoo)/boot. Yes, flash stick permanently connected to internal m/board connector inside system unit as /boot. 2. There is _6_ HDDs connected to m/b - there will be ZFS array later, when problems gone. So, I think, because of unsupported NVME, that M.2 drive seen always as last when I booted Windows OS, something like PHYSICALDRIVE6 (with connected flash stick, M.2 drive may be with increased index, I presume), so GRUB getting from BIOS M.2 also as "last", just in case. But all of this is not prevent GRUB from boot when SATA controller in ATA mode, so... 3. File system of /boot partition does't play role - grub hangs when /boot is btrfs, and also hangs when /boot is FAT16. 4. Also, I've noticed the BIOS was not updated for ages and now I have the update files. So, we have 2 paths: I can try to update it and problem may gone so we will loose ability to catch possible bug. Or, we can struggle, find the source of problem and improve the GRUB to work with, maybe, buggy BIOSes or what else causing that hangup. I have the time to debug the bug. So, if you help me with some patch to sys-boot/grub and few words like place it there, emerge grub..., we can make it. The grub hangs up after printing "GRUB " before it prints something else, so, please make the patch making grub to increase the verbosity at that moment. P.S. I prefer to boot in BIOS, non-UEFI mode.
This is really beyond my expertise. I would suggest you contact the GRUB developers upstream for assistance.
