You are not logged in.
Pages: 1
I install arch on laptop in UEFI boot mode with Secure Boot disabled.
win 10 is already on a partition of SSD, and I want to install arch on another partition of the SSD.
I mount arch partition on /mnt and win 10 EFI System partition on /mnt/boot,
then genfstab and then chroot to /mnt,
install grub and os-prober,
then grub-mkconfig but no os is listed.
Run os-prober still no os listed. So after reboot shows just"Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions."
Anyone could help?
What information should I paste for help?
Thanks.
Last edited by jhello (2017-10-31 13:00:30)
人道待人
Offline
Which partition did you mount to /mnt/boot?
It's meant to be the existing EFI partition, not the Windows system partition.
Offline
Which partition did you mount to /mnt/boot?
It's meant to be the existing EFI partition, not the Windows system partition.
Sorry, I actually did as you said, that is a mistake of my description...
I will correct it.
人道待人
Offline
maybe the partition you want is not mounted ?
ezik
Offline
Did you chroot or arch-chroot? Please specify the exact commands you use and the output you get. arch-chroot is not the same as chroot. If you use chroot, you need to do additional stuff first.
Were you booted in UEFI mode? Are you sure? If so, how did you check?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Did you chroot or arch-chroot? Please specify the exact commands you use and the output you get. arch-chroot is not the same as chroot. If you use chroot, you need to do additional stuff first.
Were you booted in UEFI mode? Are you sure? If so, how did you check?
In order to record every exact command and other detail, I reinstalled it.
In InsydeH20 Setup Utility:
SATA Controller Mode: AHCI
Boot Mode: UEFI
Secure Boot: Disabled
Fast Boot: Disabled
In boot menu of Udisk OS, select
Arch Linux archiso x86_64 UEFI CD
Connect to my wifi.
# ls /sys/firmware/efi/efivars
shows a lot of things.
# mkfs.ext4 /dev/nvme0n1p4
# mount /dev/nvme0n1p4 /mnt
select a fast mirror
# pacstrap /mnt base
# genfstab -U /mnt >> /mnt/etc/fstab
# arch-chroot /mnt
install os-prober
#os-prober
shows
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
I do not mount win 10 partition so there should be only archlinux probed.
But no archlinux shows, just as each time before with timezone and others configured.
Does the warning matter?
Last edited by jhello (2017-10-30 15:59:39)
人道待人
Offline
In your description of your steps here you didn't show mounting the existing ESP to /mnt/boot. Is that just an omission? If not, that is your problem.
Simple and Open
Offline
In your description of your steps here you didn't show mounting the existing ESP to /mnt/boot. Is that just an omission? If not, that is your problem.
I did not mount it.
I exit arch-chroot,and
# mount /dev/nvme0n1p1 /mnt/boot
# genfstab -U /mnt >> /mnt/etc/fstab
# arch-chroot /mnt
# os-prober
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Still no OS.
Where nvme0n1p1 is the ESP
Last edited by jhello (2017-10-30 15:54:27)
人道待人
Offline
You need to have the EFI partition mounted to /mnt/boot before you run the pacstrap command, as this is where the kernel and bootloader are installed to.
Also the lvmetad warning from os-prober isn't an error, if you're not using LVM then you can safely ignore it. Did you actually install GRUB? I can't see you doing so in your installation notes.
Do you have any particular reason for wanting to use GRUB as your bootloader? If not then I'd suggest using systemd-boot instead, as it's already installed in a base system and the configuration is more user friendly.
Last edited by Slithery (2017-10-30 16:07:45)
Offline
Still some issues there. After you get both the / and ESP partitions mounted, do check to make sure the /etc/fstab on the new root does have both partitions listed and use genfstab again if needed, run arch-chroot and then re-install grub (though there are better and simpler options). Reinstall grub from the start and note that you do not run os-prober itself, it runs from grub-mkconfig. Also verify that the ESP has the ESP and boot flags set.
Simple and Open
Offline
slithery and Blasphemist suggestions make os-prober probes os, that is, an available grub.cfg is made.
Thanks very much!
But only arch, no win 10.
/mnt/etc/fstab does have both partitions listed.
and
# parted /dev/nvme0n1 print
esp and boot flags are there.
Last edited by jhello (2017-10-30 16:43:40)
人道待人
Offline
But only arch, no win 10
Have a look on the EFI system partition for the Windows bootloader.
If the ESP is mounted to /boot in your Arch system then it should be found at /boot/EFI/Microsoft/Boot/bootmgfw.efi
Without that file Windows cannot be booted.
Freedom for Öcalan!
Offline
genfstab -U /mnt >> /mnt/etc/fstab
If you keep doing this, you are adding more and more lines - many duplicates - to fstab. That's not a great idea.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
jhello wrote:But only arch, no win 10
Have a look on the EFI system partition for the Windows bootloader.
If the ESP is mounted to /boot in your Arch system then it should be found at /boot/EFI/Microsoft/Boot/bootmgfw.efi
Without that file Windows cannot be booted.
Yes, bootmgfw.efi is there.
I can boot win10 without GRUB after switching an option in the "InsydeH20 Setup Utility".
Any other possibilities?
人道待人
Offline
genfstab -U /mnt >> /mnt/etc/fstab
If you keep doing this, you are adding more and more lines - many duplicates - to fstab. That's not a great idea.
Thanks!
I will delete those redundance after.
人道待人
Offline
Great news.
When I reboot into the new installed arch and run the grub-mkconfig command,
it find windows.
I do not know why.
Thx everyone here!
人道待人
Offline
Yesterday,I reached the same issue,i found a better way.
If it's first setup,and os-prober don't output anything,try reboot the device and try again.
after reboot,I os-prober again,and it worked,then I regenerate the grub cfg,after a reboot again, Windows Boot Manager is now in the grub menu.
std::cout << "I use Arch BTW" << endl;
Offline
Pages: 1