That seems to work.
With all the juggling around of the order of things to do in the two guides, have I made any obvious errors in the following commands? This includes redoing the last two sections in the original post in a different order but otherwise continues from there and seems to work other than that I still have to enter the passphrase twice, and it uses a US keymap rather than a Danish one for the first of those prompts, but these are at least obvious problems that are easy enough to work on, I’m more worried about having done something wrong that’s non-obvious.
# Installation guide, Installation, Install the base packages
packstrap /mnt base base-devel vim
# Installation guide, Installation, Configure the system, Fstab
genfstab -U /mnt >> /mnt/etc/fstab
# Installation guide, Installation, Configure the system, Chroot
arch-chroot /mnt
# Installation guide, Installation, Configure the system, Time zone
ln -sf /usr/share/zoneinfo/Europe/Copenhagen /etc/localtime
# Installation guide, Installation, Configure the system, Localization
vim /etc/locale.gen
# Uncomment en_US.UTF-8 UTF-8 and other needed locales in /etc/locale.gen, and generate them with:
locale-gen
# Set the LANG variable in locale.conf(5) accordingly, for example:
vim /etc/locale.conf
# LANG=en_US.UTF-8
# If you set the keyboard layout, make the changes persistent in vconsole.conf(5):
vim /etc/vconsole.conf
# KEYMAP=dk-latin1
# Installation guide, Installation, Configure the system, Network configuration
vim /etc/hostname
# lenovo-u41-70
vim /etc/hosts
# 127.0.0.1 localhost
# ::1 localhost
# 127.0.1.1 lenovo-u41-70.localdomain lenovo-u41-70
pacman -S networkmanager
systemctl enable NetworkManager
# dm-crypt/Encrypting an entire system, Encrypted boot partition (GRUB), Configuring mkinitcpio
vim /etc/mkinitcpio.conf
# Change HOOKS line to:
# HOOKS=(base systemd autodetect keyboard sd-vconsole modconf block sd-encrypt sd-lvm2 filesystems fsck)
# Installation guide, Installation, Configure the system, Initramfs
mkinitcpio -p linux
# Installation guide, Installation, Configure the system, Root password
passwd
# dm-crypt/Encrypting an entire system, Encrypted boot partition (GRUB), Configuring GRUB
pacman -S grub efibootmgr
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB --recheck
grub-install --target=i386-pc --recheck /dev/sda
# Configure GRUB to recognize the LUKS encrypted /boot partition and unlock the encrypted root partition at boot:
vim /etc/default/grub
# GRUB_CMDLINE_LINUX="... rd.luks.name=<sda4-UUID>=cryptlvm" ...
# GRUB_ENABLE_CRYPTODISK=y
grub-mkconfig -o /boot/grub/grub.cfg
# Use workaround if grub-mkconfig hangs: https://bbs.archlinux.org/viewtopic.php?pid=1820949#p1820949
# dm-crypt/Encrypting an entire system, Encrypted boot partition (GRUB), Configuring fstab and crypttab
dd bs=512 count=4 iflag=fullblock if=/dev/random of=/etc/mykeyfile
chmod 600 /etc/mykeyfile
cryptsetup luksAddKey /dev/sda3 /etc/mykeyfile
vim /etc/crypttab
# cryptboot /dev/sda3 none luks
vim /etc/crypttab
# cryptboot UUID=<UUID identifier of crypto_LUKS partition on sda3> /etc/mykeyfile
vim /etc/fstab
# /dev/mapper/cryptboot /boot ext4 defaults 0 2
vim /etc/pacman.conf
# It may be worth considering to add the GRUB bootloader to the ignore list of /etc/pacman.conf in order to take particular control of when the bootloader (which includes its own encryption modules) is updated.
# Installation guide, Installation, Configure the system, Boot loader
pacman -S intel-ucode
grub-mkconfig -o /boot/grub/grub.cfg
# Installation guide, Installation, Reboot
exit
umount -R /mnt
reboot
# TODO:
# Installation guide, Installation, Post-Installation
# Fix keymap for GRUB stage 1 https://bbs.archlinux.org/viewtopic.php?id=240739
# Fix having to enter passphrase twice to boot.
# WiFi https://wiki.archlinux.org/index.php/Network_configuration
# Suspend to disk https://wiki.archlinux.org/index.php/Dm-crypt/Swap_encryption#With_suspend-to-disk_support
# https://wiki.archlinux.org/index.php/General_recommendations
# See tip about cryptboot after install. https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#Encrypted_boot_partition_(GRUB)Last edited by BearerOfHonesty (2019-01-08 03:09:00)
Содержание
- Arch Linux
- #1 2019-10-22 05:29:22
- Grub install not possible [SOLVED]
- #2 2019-10-22 06:44:58
- Re: Grub install not possible [SOLVED]
- #3 2019-10-22 08:20:04
- Re: Grub install not possible [SOLVED]
- #4 2019-10-22 14:52:00
- Re: Grub install not possible [SOLVED]
- #5 2019-10-22 17:40:06
- Re: Grub install not possible [SOLVED]
- #6 2019-10-22 18:29:33
- Re: Grub install not possible [SOLVED]
- Arch Linux
- #1 2019-01-07 21:20:37
- [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- #2 2019-01-07 21:39:39
- Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- #3 2019-01-07 21:43:47
- Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- #4 2019-01-07 22:38:08
- Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- #5 2019-01-08 02:47:15
- Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- #6 2019-01-08 06:52:39
- Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
- Сломал граб
- Arch Linux
- #1 2019-08-16 21:55:37
- [Solved] No operating system found, GRUB2 & GPT/BIOS Legacy Mode
Arch Linux
You are not logged in.
#1 2019-10-22 05:29:22
Grub install not possible [SOLVED]
I have x86_64 PC with Bios without EFI.
I tried to install ArchLinux 2019-10-01.
I followed the wiki install guide.
I have a Windows partition #1
and Linux Partition #2.
I got this error
grub-install: error: failed to get canonical path of ‘airootfs’
I have no clue what airootfs is.
What can I do to get my bootloader installed?
Last edited by PeterOpenSource (2019-10-22 18:31:25)
#2 2019-10-22 06:44:58
Re: Grub install not possible [SOLVED]
there’s not much info to start with.
you say you followed the wiki, but which commands, aside from grub-install, did you issue before getting this error?
this error usually means you’re not running the command from within chroot.
Failure is success in progress.
A.E.
#3 2019-10-22 08:20:04
Re: Grub install not possible [SOLVED]
Please provide more output and information about commands and env
#4 2019-10-22 14:52:00
Re: Grub install not possible [SOLVED]
Particularly this section..
Make sure you have the «which» package installed, along with os-prober and ntfs-3g before you install grub.
Grub gets installed to the drive e.g. «sda» NOT a partition e.g. «sda1″(your actual drive and partition info may vary).
Last edited by Zod (2019-10-22 15:12:42)
#5 2019-10-22 17:40:06
Re: Grub install not possible [SOLVED]
Thanks everybody. Yes, it was a chroot mistake. And thanks, Zod!
#6 2019-10-22 18:29:33
Re: Grub install not possible [SOLVED]
Please remember to mark your thread as solved by editing the first post and amending the topic title.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Источник
Arch Linux
You are not logged in.
#1 2019-01-07 21:20:37
[SOLVED] grub-install: error: failed to get canonical path of `/efi´.
I’m installing from archlinux-2019.01.01-x86_64.iso on an UEFI system and following the Installation guide down to the «Partition the disks» section and expected to pick up these instructions again at the start of the «Installation» section after following dm-crypt/Encrypting an entire system section Encrypted boot partition (GRUB) to set up encryption which goes fine until I get to the «Configuring GRUB» section where I get an error.
I think I have followed the instructions correctly.
Here are all the commands I’ve run so far and some notes on the filesystems.
This is the error the last command spits out:
I was thinking that maybe it was supposed to be /mnt/efi instead but that just gives:
Any idea where I went wrong or is it the wiki that’s wrong?
Last edited by BearerOfHonesty (2019-01-08 07:01:33)
#2 2019-01-07 21:39:39
Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
Apparently, grub-install tries to do something with the root filesystem (airootfs).
Try running the command from within the chroot after having installed base and grub (the package).
Last edited by respiranto (2019-01-07 21:40:44)
#3 2019-01-07 21:43:47
Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
When should I be doing that and is the system even ready for that yet? Comparing the two sets of instructions it doesn’t look like I’ve gotten far enough in the instructions for setting up encryption to where the normal installation instructions expect me to chroot which is why I haven’t tried yet.
#4 2019-01-07 22:38:08
Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
You should be ready to run pacstrap and then arch-chroot.
Don’t forget to change the mkinitcpio.conf inside the chroot.
#5 2019-01-08 02:47:15
Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
That seems to work.
With all the juggling around of the order of things to do in the two guides, have I made any obvious errors in the following commands? This includes redoing the last two sections in the original post in a different order but otherwise continues from there and seems to work other than that I still have to enter the passphrase twice, and it uses a US keymap rather than a Danish one for the first of those prompts, but these are at least obvious problems that are easy enough to work on, I’m more worried about having done something wrong that’s non-obvious.
Last edited by BearerOfHonesty (2019-01-08 03:09:00)
#6 2019-01-08 06:52:39
Re: [SOLVED] grub-install: error: failed to get canonical path of `/efi´.
Great that it works now. Please prepend ‘[SOLVED]’ to your thread’s title by editing the first post, unless you believe there are (serious) issues remaining.
Your list of commands looks generally fine. Some points:
You run grub-mkconfig twice. The second time suffices (though it does not at all harm to run it twice).
You install grub in both UEFI and BIOS mode. I’m not sure if that is what you want. There are good possible reasons though and in fact I had such a setup myself in the past.
You might consider not relying on grub-mkconfig, see [0] and the possibly generated the grub.cfg.
In order to prevent entering the password twice, see [1].
I didn’t know about umount’s -R option. Thanks for that. Unmounting explicitly before rebooting (or shutting down) is not necessary though.
Источник
Сломал граб
Покурил арчвики Уефи, ефи-раздел sda1 Сделал
Перейти на systemd-bood
а разве не /efi в параметре ефи директори?
так а ты попробуй, мож опечатка
Тот же самый результат, та же ошибка, ток вместо esp /efi
как то ты поперёк ман читаешь, там же написано что нужно создать /есп/ефи
я использую refind (тоже арчик), потому точно не подскажу. единственное, что в —efi-directory= , ты должен указать путь к директории с прошивкой. у меня выглядит так:
Да, щас вот допер и сделал все как вы озвучили. Теперь
«esp» там не зря курсивом написан, ты должен вставить вместо него точку монтирования, а не тупо копипастить, в твоём случае это /esp. Вообще esp монтируют обычно не туда, куда ты. См https://wiki.archlinux.org/index.php/EFI_system_partition#Typical_mount_points
При правильном указании директории ошибка та же, только airootfs
Grub-install: error: failed to get canonical path of «airootfs»
Видимо, граб не может получить какие-то переменные окружение. Попробуй всё примонтировать и повторить уже в чруте (сначала arch-chroot).
Ты пытаешься поставить груб не примонтировав корень или не чрутнувшись в него
то есть мне в /esp запихать корневой раздел, потом в /esp/efi запихать ефи и chroot /esp?
Нет, в вики же все расписано. Монтируешь корень в /mnt арчрут в /mnt потом монтируешь ефи раздел в /efi или если так хочешь в /esp и ставишь груб
Запись в ефи есть теперь, но при загрузке minimal bash-like line
Прими пургена, может полегчает
Я просто пишу grub-install /dev/nvme0n1 . ESP смонтирован в /boot/efi.
grub-mkconfig -o /boot/grub/grub.cfg
Ага, только он никакие оси не находит. Просто done и все
Если б так просто. Я уже за вечер весь мозг себе вытрахал этим грабли, самому смешно аж
да чтож такое а. чрут сделал? ефи примонтировал? ядро в бут лежит? как не видит, елки-палки, ты что-то делаешь не так.
забей на груб и всего делов. используй efistub!
А ты оспробер поставил , чтоб он находил? С таким чтением вики ты и ядро мог не поставить. Читай еще раз русскую вики по грубу, там все расписано. И можешь загрузить арч и из своего груба вручную, конечно если ядро поставил. В вики даны команды консоли груба.
os-prober тут при чем?
Чё делал sudo mount /dev/sda5 /mnt Chroot /mnt Sudo mount /dev/sda1 /mnt/efi Sudo grub-install Sudo update-grub С телефа чет коды не работают, сорян за такую пасту
Арчем я уже пользуюсь недели 3, так что ядро там стоит 🙂
короче… надо как-то так:
Ну а конфиг груба кто генерировать будет, еще раз прочти вики. И если не можешь простейшие действия по вики повторить, арч пока рано
Чтоб другие оси находил. Но ТС и основной конфиг не сгенерировал
В арче есть arch-chroot он сам монтирует proc run и прочее
sudo shred /dev/sda тебе поможет, но это не точно.
ну и пусть будет. новичку лучше мотировать все ручками, потом пригодиться.
Да чё рано, как будто если я запорю граб на убунте то его будет проще восстановить. Поставил арч как-то, юзаю, прикольно
Ну так читать тогда и читать вики, установка груба из лайва арча четыре команды подряд. А ты и в них запутался.
Именно так просто работает в Ubuntu и Debian.
Размахивать —rbind ни к чему, это даст только неудобства с отмонтированием /dev/pts/. /sys/firmware тут тоже само подтянется.
У тебя boot не отдельным разделом случайно?
в первом же комменте лучшее решение, чем systemd-boot не подходит?
Я хз как его из под лайва поставить, в Вики ч так понял для рабочей системы
Хм, я когда арч ставил то боялся угрохать все другие записи в ефи разделе и создал отдельный, туда и поставил граб, все работало, однако сейчас поставил граб в ефи и нифига
sudo mount /dev/sda5 /mnt Chroot /mnt Sudo mount /dev/sda1 /mnt/efi
Это совсем плохо.
Если boot отдельным разделом то и его монтировать надо. Смотри русскую вики арча груб, там очень хорошо расписан порядок и действия
chroot и bootctl install, не забудь удалить grub
Источник
Arch Linux
You are not logged in.
#1 2019-08-16 21:55:37
[Solved] No operating system found, GRUB2 & GPT/BIOS Legacy Mode
I am a noob. I’m following the installation guide here: https://wiki.archlinux.org/index.php/Installation_guide
I completed the install with no errors, but when I reboot my machine, it is unable to find an operating system on my drive.
I checked the BIOS to ensure that I am in LEGACY mode, that the hard drive is set to boot before the CD, and that the CD
is no longer in the drive once I rebooted after the install. I am using a Lenovo H50-55.
I started by partitioning the drive like so:
Then, I made the filesystems:
Then, mounted them:
Then, I ran some commands to set up wi-fi. I’ve excluded them here but can provide if need.
Next, I installed the base system:and generated the fstab
Then I set up timezones
Then I edited /etc/locale.conf and ran locale-gen.
After than I added my hostname and set up the hosts file.
Then, i TRIED to run this command:
But I received this error:
grub-install: error: failed to get canonical path of `airootfs´
I did some research online and dicovered I needed to chroot into the system. So i performed:
and was then able to perform these commands successfully:
I then set the root password with passwd.
and ran pacman -Syu to see if i needed to update, but it said «nothing to do».
At this point, I believed that I had completed the install, so I reboot and took the cd out of the disc drive; however,
I now am unable to load an operating system. There is no operating system found on my hard drive so the BIOS drops down to my Realtek Network
and coughs up an error about PXI-E. I know the hard drive is just fine as I had a windows install on there just a few hours ago and have
not messed with the hardware at all. I’m a novice, so I could be way off, but my suspicion is that I did not install grub correctly to point to root.
Thanks in advance for any help!
UPDATE: I discovered that I am apparently able to boot the system if I use the CD and select ‘Exsting OS’ instead of the installation media. But I am not able to boot without the CD
Last edited by pirateprentice (2019-08-21 00:03:00)
Источник
| View previous topic :: View next topic | |||||||||||||||
| Author | Message | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| phirephoto n00b 
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
 |
|||||||||||||||
| Jaglover Watchman  
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| jburns Veteran 
Joined: 18 Jan 2007 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| DONAHUE Watchman 
Joined: 09 Dec 2006 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| DONAHUE Watchman
Joined: 09 Dec 2006 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| DONAHUE Watchman
Joined: 09 Dec 2006 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| Jaglover Watchman
Joined: 29 May 2005 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| DONAHUE Watchman
Joined: 09 Dec 2006 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| DONAHUE Watchman
Joined: 09 Dec 2006 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
| phirephoto n00b
Joined: 23 Sep 2018 |
|
||||||||||||||
| Back to top |
|
||||||||||||||
|
|||||||||||||||
|
|
You cannot post new topics in this forum |