You are not logged in.
That command should give you a lot of output (with the --debug flat) which should help you pin down the error.
Sometimes, the diagnostic output can actually make it harder to find the source of an error though. In at least one case, I've removed --debug to get simpler output which made it easier to spot the problem.
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
I think this was the error ...
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
Offline
See the wiki page on chrooting. Or the instructions for installing grub EFI which tells you how to do this. You need to make sure these things show up in the right places before you chroot and then it should work.
https://wiki.archlinux.org/index.php/Ch … nging_Root
Last edited by cfr (2012-07-27 23:32:28)
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
I think this was the error ...
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
I think it may not be /dev/sda.
Check with "fdisk -l" if sda is your USB drive. Because you may need to use /dev/sdb.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
It is because you haven't boot in efi mode. You have boot in grub mode. But all about is to tell to BIOS|EFI firmaware what bootloader launch.
You can try boot in efi mode by F-10 (or like) to boot menu, or by another distribution that boot in efi mode as cd media, usb...(need to go to menu boot too, generally show a efi boot). Then chroot and start again to grub-install.
If you can't, then, do the next.
If EFI doesn't know nothing about what bootloder must launch, it launchs bootloader founded in /boot/efi/EFI/BOOT/bootx64.efi. So, move there the grub_arch.efi and change the name to bootx64.efi.
Later you can do grub_config to acces efivars and launch properly from grub_arch.efi
Last edited by Alber (2012-07-27 10:12:59)
Because not all of us are native English speakers, try no to use slang or abbreviations, thank you.
Offline
sml, don't just run "grub-install --recheck". Specify a fricken device, and THEN generate a .cfg:
# grub-install /dev/sda # grub-mkconfig -o /boot/grub/grub.cfg
@DSpider: There is no need to specify a device for grub-efi-x86_64 uefi installation (and is ignored by grub-install even if specified, in case of --target=x86_64-efi). It is needed only for grub-bios (--target=i386-pc). You got confused between grub-bios and grub-efi-x86_64, thinking both are similar.
The style of booting and the requirements for each firmware are different. See https://bbs.archlinux.org/viewtopic.php … 5#p1137825 .
Last edited by the.ridikulus.rat (2012-07-28 03:54:49)
Offline
sml wrote:I think this was the error ...
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.I think it may not be /dev/sda.
Check with "fdisk -l" if sda is your USB drive. Because you may need to use /dev/sdb.
Offline
# grub-install --directory=/usr/lib/grub/i386-pc --target=i386-pc --boot-directory=/boot --recheck --debug /dev/sda
is for the 32 bit version. Which version are you trying to use? /usr/lib/grub/i386-pc isn't _supposed_ to exist for the 64 bit version and the target isn't supposed to be i386-pc.
@cfr: In GRUB(2), i386-pc target denotes PC BIOS, x86_64-efi target is for 64-bit UEFI (grub-efi-x86_64) and i386-efi is for 32-bit UEFI (grub-efi-i386). I think you mixed up i386-pc and i386-efi .
Offline
@cfr: In GRUB(2), i386-pc target denotes PC BIOS, x86_64-efi target is for 64-bit UEFI (grub-efi-x86_64) and i386-efi is for 32-bit UEFI (grub-efi-i386). I think you mixed up i386-pc and i386-efi .
So i386-pc is (1) 32 bit; and (2) BIOS? (So it would be doubly mistaken in this case.)
Or i386-pc is (1) 32/64 bit BIOS? (Because a 32 bit start works for BIOS booting even on a 64 bit system?)
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
the.ridikulus.rat wrote:@cfr: In GRUB(2), i386-pc target denotes PC BIOS, x86_64-efi target is for 64-bit UEFI (grub-efi-x86_64) and i386-efi is for 32-bit UEFI (grub-efi-i386). I think you mixed up i386-pc and i386-efi .
So i386-pc is (1) 32 bit; and (2) BIOS? (So it would be doubly mistaken in this case.)
Or i386-pc is (1) 32/64 bit BIOS? (Because a 32 bit start works for BIOS booting even on a 64 bit system?)
Non-UEFI BIOS (legacy) firmware is always 16-bit, irrespective of whether the underlying processor is 32/64-bit. grub-bios always runs as a 32-bit program. Hence the target being i386-pc. i386In 64-bit systems, its the linux kernel that switches to 64-bit, not the bootloader.
There is no 32/64-bit BIOS. There are only 32/64-bit UEFI.
Offline
this is hard work ... still stuck using ubuntu
Offline
sml : I was in a similar situation with the same message.
Did you check the boot priority in your bios (well uefi setup utility)?
There should be an option to switch to uefi. It worked for me.
I used a cd to install, I don't know if it work the same with an usb stick.
Offline
If you are booting Ubuntu in EFI mode, you can chroot to your arch install and install grub2 EFI from there. Just make sure to modprobe efivars before you chroot.
But you need to set up the chroot correctly for it to work so that sysfs and procfs *are* available in the chroot. See the wiki page on chroot/grub2 installation etc.
Last edited by cfr (2012-08-17 01:06:56)
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