- Печать
Страницы: [1] Вниз
Тема: grub-efi-amd64-signed [Решено] (Прочитано 1947 раз)
0 Пользователей и 1 Гость просматривают эту тему.
кандыба
Подскажите пожалуйста, почему в конце установки программ, выдаёт вот это в терминале?
При обработке следующих пакетов произошли ошибки:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
обновления встают, ноутбук прекрасно работает, но ошибка в конце установки в логах. Всегда такое появляется.
« Последнее редактирование: 03 Мая 2020, 05:48:14 от zg_nico »
Lex Alexov
# apt purge grub*
# apt autoremove
# apt install grub-efi
# update-grub
Samsung NP-530U4b-S01; Intel i3-2367M (4) @ 1.44GHz; 8Gb DDR3 1333 МГц; AMD Radeon HD 7550M; Intel HD Graphics 4000; KDE-Neon 5.21 x64;
The Green Side
И иметь под рукой флешку с boot-repair при выполнении операции
Debian 11, Debian 11 Server
кандыба
# apt purge grub*
Огромная благодарность Вам. После этих команд запись перстала выскакивать. Золотые команды. В закладки.
# apt autoremove
# apt install grub-efi
# update-grub
Тема закрыта.
« Последнее редактирование: 14 Февраля 2020, 15:13:02 от zg_nico »
- Печать
Страницы: [1] Вверх
Edited and modified original answer, AFTER further 20+ experiments on both of my machines.
To make it short answer, I will remove all incorrect assumptions and conclusions in the old answer.
—————-My computers ARE
1. Fujitsu LIFEBOOK-LH532, which UEFI BIOS in the mainboard was destroy by ubuntu EFI ubiquity version 12.04, in 2012
https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1082418
Obviously I choose manual BIOS installation on my NoteBook UEFI LH532.
SINCE I DON’T WANT TO open MY NOTEBOOK TO SHORT CIRCUIT JUMPER cl1&cl2 ON THE MAINBOARD again SINCE I «THE BUG» IS STILL THERE.
***I forced manual BIOS mode by not provide EFI partion on any hard disk.
BUT ALL INSTALLATIONS WILL DETECT UEFI MAINBOARD AND WILL TRY TO INSTALL EFI UBUNTU «FIRST».
- Old Gigabyte xenon server non UEFI mainboard.
Which has no errors at all.
The errors exactly as the topic is,
resulted in problems with «UEFI»NOTEBOOK ONLY.
- NON botable UEFI notebook(LH532). Ubiquity Destroy the existing UBUNTU GRUB.
- «OR IF LUCKY» will just use the old Bios grub installed by 16.04 and boot into new 18.04 (in the old 16.04 partitions) with some error at the beginning of the booting time.
I FIXED THE BOOTING BY
- Pain?? complex?
Using Boot-Repair (failed to use grubcustomiser) installed into existing ubuntu installation on other partitions
or BOOTED Live usb.
And follow instructions which were different from one time to the others depend on the configuration of hard disks in the systems as well as the flavour of ubuntu 18.04 used.
https://help.ubuntu.com/community/Boot-Repair
- Easy and Excellent «most of the time».
I used 16.04 of UBUNTU OR LUBUNTU do a new installaion on other partitions of hard disk in that same computer,
that you have installed «18.04» and failed to install grub with this ERROR.
So that 16.04 will make your system boot.
And yes, you can access to Great 18.04 versions from that 16.04 grub.
And YES, I use UBUNTU 18.04 to write this answer, after LUBUNTU 16.04 INSTALLed NEW GRUB FOR my LH532 notebook with the correct option to choose 18.04.
Reasons for the error of this topic is
you don’t provide EFI partitions for the manual «something else» installation mode.
So if you purposely, like me, not to have EFI partition. you will have this error.
But 16.04 versions, have a smarter UBIQUITY or ? whatever? than 18.04.
It will found that you install with BIOS installation (no efi partition in the hard disk) and let you chose to «GO BACK» to install ubuntu with BIOS mode.
But the 18.04 will do installation with out any choice in my case and possible yours.
I will call those poorer quality in these circumstances of 18.04 as «BUG».
But it could be the programmers intention to force us to use only proper clean automation only???, which they should have remove «something else» option.
- I have correct the issues by completely REFORMAT my SSD.
Install Windows 10 UEFI mode. Which it automatically create EFI partition.
Then install UBUNTU 18.04 with no errors, though it jealously prohibit me to boot into MANJARO LINUX which I installed after Windows 10 with no issues too.
And of course, UBUNTU 18.04 destroy my BIOS F12.
JEALOUSELY PROHIBIT me to install any other OS, and I have to open the notebook case to short circuit jumper CL1 and CL2 to get F12 to choose boot media back.
I did report this to lunchpad as the link I provide above.
Sorry off the topic a bit but let you all knows there are more bugs in ubiquity or installation process more than this issue.
Have you ever found yourself in a situation when your machine fails to boot after upgrading to a new version of Ubuntu? It can be quite frustrating when your device gets stuck in an installation loop and is unable to get to the login screen. This type of issue is often caused by the «grub-efi-amd64-signed failed to install» error. Luckily, this type of issue has a simple fix and can be resolved quickly.
In this guide, we will explain how to solve the «grub-efi-amd64-signed failed to install» error. We will explain what this problem is, which tools you need to fix it and provide a step-by-step guide on how to do so.
What is the “grub-efi-amd64-signed Failed to Install” Error
The «grub-efi-amd64-signed Failed to Install» error occurs when you try to install or upgrade Ubuntu from an external drive, such as a USB flash drive. This issue is known to occur on both 64-bit and 32-bit versions of Ubuntu.
The reason for this issue is the lack of a valid Grub bootloader on the installation drive. If your device does not recognize the Grub bootloader, it will prevent the installation from continuing.
What You Need to Fix the “grub-efi-amd64-signed Failed to Install” Error
To fix the «grub-efi-amd64-signed Failed to Install» error, there are a few things you need before you start.
- An external drive with a valid Grub bootloader
- A computer with an internet connection
- Download the Boot Repair Tool
- A software that can mount the external drive containing the Grub bootloader
Step-by-Step Guide to Fix the “grub-efi-amd64-signed Failed to Install” Error
- Download and install the Boot Repair Tool on your computer. This tool will help you repair your installation drive.
- Mount the external drive containing the Grub bootloader to your computer.
- Run the Boot Repair Tool and follow the instructions to fix the «grub-efi-amd64-signed Failed to Install» error.
- When the repair process is complete, try to re-install or upgrade Ubuntu again.
FAQs
Q: What is the “grub-efi-amd64-signed Failed to Install” Error?
A: The “grub-efi-amd64-signed Failed to Install” error occurs when you try to install or upgrade Ubuntu from an external drive, such as a USB flash drive, when the installation drive does not contain a valid Grub bootloader.
Q: What do I need to fix the “grub-efi-amd64-signed Failed to Install” Error?
A: To fix the “grub-efi-amd64-signed Failed to Install” error, you need an external drive with a valid Grub bootloader, a computer with an internet connection, the Boot Repair Tool, and software that can mount the external drive containing the Grub bootloader.
Q: How can I fix the “grub-efi-amd64-signed Failed to Install” Error?
A: To fix the “grub-efi-amd64-signed Failed to Install” error, you need to download and install the Boot Repair Tool, mount the external drive containing the Grub bootloader, and then run the Boot Repair Tool. Once the repair process is complete, try to re-install or upgrade Ubuntu again.
Q: What happens if I can’t get the Boot Repair Tool to work?
A: If you cannot get the Boot Repair Tool to work, you can try manually reinstalling Grub by using a Live CD. This option requires more technical knowledge and experience and is considered more difficult than using the Boot Repair Tool.
Q: Will the “grub-efi-amd64-signed Failed to Install” Error occur again?
A: This type of error is typically caused by a lack of a valid Grub bootloader on the installation drive. If you have resolved the issue by installing a valid Grub bootloader, the error should not occur again.
- https://www.youtube.com/watch?v=zna0xbJPBXM
- https://askubuntu.com/questions/1251265/the-grub-efi-amd64-signed-package-failed-to-install-trying-to-dual-boot-kali
- Печать
Страницы: [1] Вниз
Тема: grub-efi-amd64-signed [Решено] (Прочитано 1382 раз)
0 Пользователей и 1 Гость просматривают эту тему.
кандыба
Подскажите пожалуйста, почему в конце установки программ, выдаёт вот это в терминале?
При обработке следующих пакетов произошли ошибки:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
обновления встают, ноутбук прекрасно работает, но ошибка в конце установки в логах. Всегда такое появляется.
« Последнее редактирование: 03 Мая 2020, 05:48:14 от zg_nico »
Lex Alexov
# apt purge grub*
# apt autoremove
# apt install grub-efi
# update-grub
Samsung NP-530U4b-S01; Intel i3-2367M (4) @ 1.44GHz; 8Gb DDR3 1333 МГц; AMD Radeon HD 7550M; Intel HD Graphics 4000; KDE-Neon 5.21 x64;
The Green Side
И иметь под рукой флешку с boot-repair при выполнении операции
Debian 11, Debian 11 Server
кандыба
# apt purge grub*
Огромная благодарность Вам. После этих команд запись перстала выскакивать. Золотые команды. В закладки.
# apt autoremove
# apt install grub-efi
# update-grub
Тема закрыта.
« Последнее редактирование: 14 Февраля 2020, 15:13:02 от zg_nico »
- Печать
Страницы: [1] Вверх
i have upgraded ubuntu 18.4.4 to 20.4 but i’am wrong to located the grub into /boot/efi partition i can’t change it
`sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) …
mount: /var/lib/grub/esp: /dev/sdb already mounted or mount point busy.
dpkg: error processing package grub-efi-amd64-signed (—configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Errors were encountered while processing:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
can help me to fix this ?
the picture not want to disable /boot/efi when i choose grub install device
asked Apr 24, 2020 at 7:19
1
Try purging grub and reinstall. Worked for me!
sudo apt-get purge grub*
sudo apt-get install grub-efi
sudo apt-get autoremove
sudo update-grub
answered Dec 8, 2020 at 7:30
pip1726pip1726
1311 gold badge1 silver badge12 bronze badges
0
I’m having problems when Iḿ trying ¿to install any package or software.
My OS is Ubuntu 20.04.
I’ve already tried all the solutions mentioned in this post https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1871963, including configure the UEFI, following the next comand lines:
# sudo apt-get purge grub*
# sudo apt-get install grub-efi
# sudo apt-get autoremove
# sudo update-grub
etc.
The error message appears even when the upgrades and is installed an app from the «Ubuntu Software» application…
Errors were encountered while processing:
grub-efi-amd64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks!
asked Sep 23, 2020 at 1:47
5
I had this same problem the last few days. Months ago I installed Ubuntu 20.04 alongside Win10 I had to switch the BIOS to AHCI from RAID as it wouldn’t allow install. Then after install I could switch back to RAID to allow Win10 dual boot. However along some update it messed it up and I had to switch back to AHCI and reinstalled grub as above. It sorted the problem.
answered Oct 14, 2020 at 21:25
1
[UPDATE 07-18-2018] It seems that some people still get the same error message after unchecking “Install the third party software” option. If that is the case for you, you can try the following:
1. Reboot your computer with Live USB and start Ubuntu (or Linux Mint) installation again
2. At the “Installation type” step, choose “Something else”
3. Delete all partitions (since you already have trouble installing Ubuntu, I don’t think you need to worry about losing data)
4. Manually create partitions. You will need at least three partitions as follows:
- Main partition for Ubuntu: ext4 type with mount point “/”
- Swap partition: swap type with partition size equaling to the size of your physical RAM. If you computer has 16GB RAM, then your swap partition needs to be at least 16GB.
- EFI partition with size about 200MB – 500MB. I use 500MB for my computer
5. Continue the installation. Remember you still need to disable third-party software installation.
If you still get the same error message, then you will need to boot into your BIOS and turn off “Secure Boot”, then follow the above steps to try again.
Let me know if this helped you.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
No matter if you try to install the latest Ubuntu 18.04 LTS, or Linux Mint 19 (based on Ubuntu 18.04 LTS), you may encounter the following error:
GRUB Installation Failed. The ‘grub-efi-amd64-signed’ package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.
This error is not new and it happens in computers that support UEFI mode, so many people usually recommend to enable the Legacy Support in your BIOS settings to solve this problem. However, based on my experience of dozes of trial-and-errors, I found a simple fix for this error and would like to share with you.
Based on my experiment, I think the culprit of the error is when you allow the installer to install third-party software during the installation, although I don’t know why it causes the error.
So the obvious fix is to leave “Install this third-party software” unchecked when installing Ubuntu, or leave “Install third-party software for graphics and Wi-Fi hardware, Flash, MP3 and other media” unchecked when installing Linux Mint, and you don’t need to enable the Legacy Support in your BIOS settings.
There you have it and I hope it helped you. If it did, please let me know in the comments.
1.3
13
votes
Article Rating
I encountered the infamous “‘grub–efi–amd64–signed‘ package failed to install into /target/.” error when installing ubuntu 20.04 along with preinstalled windows 10 in my desktop. Here are the setting environments
- gigabyte mainboard
- one SSD, one HDD
- windows 10 already installed on SSD
I wanted to install ubuntu 20.04 on the HDD so I partitioned the HDD to have one EFI partition(500MB) and the rest set to ‘/’ with ext4 format.
I created a ubuntu 20.04 install usb stick using the image downloaded from the official ubuntu website and Rufus. At the time, I selected ‘BIOS or UEFI’ for “target system” option when creating the usb stick.
With the above settings, no matter what I do I always ended up with the same error at the last moment of the installation.
Solution
After pouring over numerous googling results on this error and failing with all suggested solutions, I still managed to get out some sense of the situation.
And after a lot of fidgeting, I finally found my own solution.
In my case, the problem lied in the process of creating a booting usb stick. When using Rufus, I tried out “UEFI(non CMS)” for “target system” option instead of “BIOS or UEFI”.
Then I booted into the live usb stick and carried on with the same partitioning scheme as I did previously, and this time the installation did not give me the error.
BTW, although it said “(non CMS)” in the select option in Rufus, I still managed to boot into the usb stick even when CMS was enabled in my mainboard settings. I guess it actually meant that it doesn’t support legacy boot modes rather than “CMS must be disabled when booting to a usb stick created with this option!”.
My own understanding of why this method worked is that by creating a live usb stick with the “UEFI(non CMS)” option somehow forces the live usb stick to install ubuntu UEFI mode and not in legacy mode, which installs bootloader on MBR.
Previously when I used the “BIOS or UEFI” option, although the name gives a sense that both modes will be supported, I think it was actually working only on BIOS mode. Therefore, it was installing the boot loaders in legacy mode which did not abide well with the pre-existing windows 10 which was installed in UEFI mode.
My explanation may not be technically accurate, so don’t take my word for granted but as a supplementary advice.
Как правильно задавать вопросы
Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz
в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
10 июл 2018, 14:23
В Cinnamon x64. в Биосе стоит uefi+legacy.
Установка Mint идет по следующей разметки:
HDD — / , /home и swap, флэшка идет под загрузчик (роли не играет, пробывал без неё — тоже мимо), разметка GPT.
На попытку установки выдает ошибку grub-efi-amd64-signed через target выдает ошибку релиза (нет у него файла такого у 19 версии).
Куда копать и что делать?
-
rogoznik
- Сообщения: 9424
- Зарегистрирован: 27 июн 2017, 13:36
- Решено: 118
- Откуда: Нижний Тагил
- Благодарил (а): 705 раз
- Поблагодарили: 1813 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#2
10 июл 2018, 18:44
Anonim19992, загрузка в live-сессию происходит так
или так
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#3
12 июл 2018, 06:21
2 вариант
-
rogoznik
- Сообщения: 9424
- Зарегистрирован: 27 июн 2017, 13:36
- Решено: 118
- Откуда: Нижний Тагил
- Благодарил (а): 705 раз
- Поблагодарили: 1813 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#4
12 июл 2018, 06:41
Тогда тебе еще нужно создать раздел efi в начале диска. Файловая система FAT32, размер 200-300 МБ. Поставить флаги esp, boot
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#5
12 июл 2018, 06:56
в самом начале было сделано,, тоже мимо.
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#6
12 июл 2018, 06:59
[Решение]
Во время установки размечаем диск либо автоматом либо вручную по инструкции.
После получения этой ошибки не выходим из системы.
1.НЕ закрываем установщик.
2.Открываем терминал и пишем:
sudo chroot /target
apt update
apt install grub-efi-amd64-signed
3.Ждем когда установиться.
4.Выходим из chroot
exit
5.Перегружаем систему.
Попробуй)
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#7
12 июл 2018, 07:17
etamax
и читаем мой самый первый пост=)) система не видит файл релиза при apt update и следовательно и установить она не может
-
svtv1
- Сообщения: 278
- Зарегистрирован: 26 дек 2017, 15:27
- Решено: 2
- Благодарил (а): 39 раз
- Поблагодарили: 23 раза
grub-efi-amd64-signed при установке 19 Корицы
#8
12 июл 2018, 07:43
Какой прогой iso-образ ставишь?
«Если достаточно долго сидеть возле реки — мимо проплывет труп твоего врага»
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#10
12 июл 2018, 08:26
Вставил скриншот
- Вложения
-
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#11
12 июл 2018, 08:37
Anonim19992, кстати вопрос svtv1 натолкнул на мысль — может действительно при записи образа недописывается. В Руфусе есть различия записей для мбр и прочего . Правда это в качестве предположения.
И покажи что выдаст — dpkg -l | grep -i grub
Последний раз редактировалось пользователем 1 symon2014; всего редактировалось раз: 12
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#12
12 июл 2018, 08:45
etamax тоже мимо. ошибка релиза ушла, однако данный пакет не установился((
Код: Выделить всё
apt install grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
grub-efi-amd64-signed is already the newest version (1.93.2+2.02-2ubuntu8.1).
0 upgraded, 0 newly installed, 0 to remove and 209 not upgraded.
записывал руфусом, до этого записывал ультраисо
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#13
12 июл 2018, 08:47
Anonim19992 писал(а): ↑
12 июл 2018, 08:45
and 209 not upgraded.
наверно апгрейд надо для начала сделать. И я добавил предыдущий пост.
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#14
12 июл 2018, 08:50
etamax уже делался, не помогло. все остается в таком же состоянии. репа менялась как в /target, так и в просто etc/apt
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#15
12 июл 2018, 08:52
etamax писал(а): ↑
12 июл 2018, 08:37
И покажи что выдаст — dpkg -l | grep -i grub
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#16
12 июл 2018, 09:12
до установки с учетом ваших советов.
- Вложения
-
- лист
-
- разметка диска
-
- dpkg -l | grep -i grub
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#17
12 июл 2018, 09:19
По поводу скрина . Есть сомнения — сдд1 нужно указать как загрузочный эфи — а системный загрузчик ставится на сдд. И на 3 скрине — груб-эфи таки нет — есть писи))
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#18
12 июл 2018, 09:22
1 раз пробовал просто на сдд, фыхлопа было 0.
-
symon2014
- Сообщения: 5136
- Зарегистрирован: 16 дек 2017, 21:59
- Решено: 29
- Откуда: Феодосия
- Благодарил (а): 31 раз
- Поблагодарили: 646 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#19
12 июл 2018, 09:24
Anonim19992 писал(а): ↑
12 июл 2018, 09:22
фыхлопа было 0.
В смысле выхлопа? Установка не продолжалась?
-
Anonim19992
- Сообщения: 132
- Зарегистрирован: 16 ноя 2016, 11:53
- Благодарил (а): 18 раз
- Поблагодарили: 6 раз
- Контактная информация:
grub-efi-amd64-signed при установке 19 Корицы
#20
12 июл 2018, 09:24
И на 3 скрине — груб-эфи таки нет — есть писи)) — и что делать? образ скачен через официал репу, установлен на флэшку разными загрузчиками без результатно((
В смысле выхлопа? Установка не продолжалась? — да, та же ошибка была.
сейчас мучу вариант с upgrade
The ‘grub-efi-amd64-signed’ package failed to install into /target/ error message, shown in Figure 1, is one I got when attempting to install KDE Neon alongside Windows 10 on a friend’s HP 15-ba009dx notebook. This post offers the solution.
Figure 1: Error message when GRUB failed to install
In instances when an installer crashes, you usually get more detailed messages on the bug report screen, but not in this case. So in an attempt to find a clue why GRUB failed to install, I restarted the installer from the command line, hoping that some messages will be printed on the command line when the installer crashes. But that didn’t happen.
Figure 2: No additional information provided why the install crashed
After several attempts of the above, I finally decided to look in the system log file, that is, in /var/log/syslog. Grep-ing for anything related to GRUB returned lines like the ones below:
# Broken grub-efi-amd64-signed:amd64 Depends on grub-efi-amd64 Considering grub-efi-amd64:amd64 1 as a solution to grub-efi-amd64-signed:amd64 grub-efi-amd64-signed : Depends: grub-efi-amd64 (= 2.02~beta2-36ubuntu3.7) but it is not going to be installed Investigating (0) shim-signed Broken shim-signed:amd64 Depends on grub-efi-amd64-bin #
That gave me a clue. The installer needed to install something that was not on the installation image. But it couldn’t. And the reason it couldn’t was because the computer I was installing it on was not connected to the Internet. If it did, the installer would have been able to find the package it needed from a remote repository, provided I selected the options shown in Figure 3.
Figure 3: Option to download updates while installing KDE Neon
So that’s the solution to the The ‘grub-efi-amd64-signed’ package failed to install into /target/ error message. Make sure that the target computer is connected to the Internet, and that you enabled the option (shown in Figure 3) to download updates during the installation.
Share:
Related posts
- The EU’s GDPR is even more relevant to Linux systems, and here is why
- The best Markdown editors for Linux
- How to install Linux Mint 10 on a btrfs file system
- How to set up a Debug Server using Nginx
- How to install Lekture on Fedora 19 KDE
Partner links
- Join a huge party for NFT frens at NFT South
- Reasons to use control panel for your server
- DHgate Computers Electronics, Cell Phones & more
- Axo Finans
Newsletter: Subscribe for updates
Inline Feedbacks
View all comments
It’s work for me.
OS: Ubuntu Desktop 18.10
1. During Live-OS, must do some delete default route and setting default route.
2. And make sure can ping 8.8.8.8 and can ping http://www.google.com
3. Click installer then to install OS.
But in my PXE Server, it’s not Non-Internet environment.
So, I need to find another methods to solve the problem.
It’s work for me.
OS: Ubuntu Desktop 18.10
1. During Live-OS, must do some delete default route and setting default route.
2. And make sure can ping 8.8.8.8 and can ping http://www.google.com
3. Click installer then to install OS.
But in my PXE Server, it’s not Non-Internet environment.
So, I need to find another methods to solve the problem.
Nope, machine is connected to the internet, I can bring up webpages, etc. STILL fails with this message.
Reply to
jelabarre
2 years ago
same here. I’m connected to both WIFI and ethernet cable.
both times i tried to install, i had updates checked. first time i had the second box (3-rd party software) installed, too.
This error message has occurred since Ubuntu 12.0 all the way through 19.10. WHY?!!!
Also, Ubuntu didn’t show up in MS Windows’ Disk Manager, but sda8 and 9 did show up (as Ubuntu being installed) in the installation (software) the second time- I selected to reinstall over it.
Reply to
jelabarre
2 years ago
same here. I’m connected to both WIFI and ethernet cable.
both times i tried to install, i had updates checked. first time i had the second box (3-rd party software) installed, too.
This error message has occurred since Ubuntu 12.0 all the way through 19.10. WHY?!!!
Also, Ubuntu didn’t show up in MS Windows’ Disk Manager, but sda8 and 9 did show up (as Ubuntu being installed) in the installation (software) the second time- I selected to reinstall over it.
Solve the problem perfectly for 18.04.01 on i7-8700K with Samsung 860 EVO. It seems to be a driver problem?
Solve the problem perfectly for 18.04.01 on i7-8700K with Samsung 860 EVO. It seems to be a driver problem?
Thank you for your post. It worked for me.
I am trying to install ubuntu 18.04 on an asus x200la laptop. ubuntu 14.04 worked without any hitches.
I am trying to install ubuntu 18.04 on an asus x200la laptop. ubuntu 14.04 worked without any hitches.
Reply to
vidyadhara b
4 years ago
So what error are you getting with Ubuntu 18.04?
This did not work for me. I am connected to the internet as you can see that I have posted a comment here. But that does not solve the problem.
This did not work for me. I am connected to the internet as you can see that I have posted a comment here. But that does not solve the problem.
No, this isn’t a general solution. I have been trying to install Ubuntu for long but haven’t been able to do so despite having all those options checked.
Thank you 🙂
This post helped me…
Thank you 🙂
This post helped me…
thanks man!!! you save me!
This solved the same problem while installing Kde Neon, thank you.
This solved the same problem while installing Kde Neon, thank you.
Reply to
Andrea
5 years ago
You’re welcome.
Many thanks for posting this solution.
I have clicked the download updates, but this didn’t fix the problem…
I am a little confused Catching_On_Slowly as to how to install mint-meta-codecs into a non-booting system?
Many thanks for posting this solution.
I have clicked the download updates, but this didn’t fix the problem…
I am a little confused Catching_On_Slowly as to how to install mint-meta-codecs into a non-booting system?
I was installing mint 18.2 and had the same issue when installing via a usb. I didn’t read the release notes (link seen on first page of install process) when I started the first time, but I read it the 2nd time around since I couldn’t get anything to work from what I saw on line. As you said it has to be online to receive the codec directory, so I had to go to the Konsole and type in without quotes “apt download mint-meta-codecs”. It works perfectly now, thanks for your thread in getting me to think differently and solving my problem.
Reply to
Catching_On_Slowly
5 years ago
You’re welcome.
Forum rules
There are no such things as «stupid» questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
ScotSeaNow
- Level 1
- Posts: 4
- Joined: Fri Nov 30, 2018 8:25 pm
[Solved] grub-efi-amd64-signed package failed to install
I am trying to install cinnamon mint 19.0 on an HP desktop. I am getting very frustrated as it keeps saying «grub-efi-amd64-signed package failed to install into /target/.»
Does it on both a brand new drive and a drive that had cinnamon mint 18.2 on it. Not dual boot. I told it to erase the 18.2 version and install 19.2.
If I put the Win10 drive back in, it boots and runs OK.
I tried to re-install without re-booting, I get the message «ubi-partman failed with exit code 10. Further information may be found in /var/log/syslog.»
I found the syslog file, but it is quite large.
Anyone know what I am doing wrong?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
Reply toCatching_On_Slowly
5 years ago
You’re welcome.
Forum rules
There are no such things as «stupid» questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
ScotSeaNow
- Level 1
- Posts: 4
- Joined: Fri Nov 30, 2018 8:25 pm
[Solved] grub-efi-amd64-signed package failed to install
I am trying to install cinnamon mint 19.0 on an HP desktop. I am getting very frustrated as it keeps saying «grub-efi-amd64-signed package failed to install into /target/.»
Does it on both a brand new drive and a drive that had cinnamon mint 18.2 on it. Not dual boot. I told it to erase the 18.2 version and install 19.2.
If I put the Win10 drive back in, it boots and runs OK.
I tried to re-install without re-booting, I get the message «ubi-partman failed with exit code 10. Further information may be found in /var/log/syslog.»
I found the syslog file, but it is quite large.
Anyone know what I am doing wrong?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
michael louwe
- Level 10
- Posts: 3288
- Joined: Sun Sep 11, 2016 11:18 pm
Re: grub-efi-amd64-signed package failed to install
Post
by michael louwe » Sat Dec 01, 2018 4:17 am
ScotSeaNow wrote: ↑
Fri Nov 30, 2018 8:47 pm
I am trying to install cinnamon mint 19.0 on an HP desktop. I am getting very frustrated as it keeps saying «grub-efi-amd64-signed package failed to install into /target/.»
.
Have you disabled Secure Boot, Fast Boot and boot the Live LM 19 USB/DVD in UEFI mode of the Boot menu in System BIOS.?
Was the downloaded LM 19 ISO file version 2 or v2, ie not v1.?
Otherwise, try installing with the Internet disconnected.
-
messier09
- Level 1
- Posts: 1
- Joined: Sat Dec 01, 2018 5:34 am
Re: grub-efi-amd64-signed package failed to install
Post
by messier09 » Sat Dec 01, 2018 7:33 am
I would be interested if OP made any progress on the issue? Did installing without internet connection make a difference?
There are a couple of similar threads on here where people managed to install in offline mode — However, this has worked only for some, not everyone, and I have yet to see a post offering ‘the one’ solution to what appears to be a frequent issue.
I am faced with the (possibly exact) same problem on a bunch of brandnew HP workstations myself. Currently, not a chance to move past the grub-efi-amd64-signed error when installing most recent releases of mint, ubuntu or openSUSE in UEFI mode.
Just to save OP some time, here is what I tried so far (without success):
— Fast Boot On/Off
— Secure Boot On/Off
— Legacy Mode On/Off
— Tried several of the more obscure BIOS settings (ROM launch policy etc).
— Used different software on different OS (Rufus in Win7/Etcher in OSX Mojave) to copy the ISO-files to DVDs and different USB sticks. Always ran the checksums. Net-install produces the same error.
— Format/partition disks beforehand (fdisk etc) or during installation
— Install with/without network connection
The issue seems to be related to some GRUB packages and/or directories not being put in the right place when installing in UEFI mode, so there may be a problem with either the bootloader included on the ISO or the combination of bootloader and HP architecture — I can’t help but noticing that people affected tend to be on HP…
-
ScotSeaNow
- Level 1
- Posts: 4
- Joined: Fri Nov 30, 2018 8:25 pm
Re: grub-efi-amd64-signed package failed to install
Post
by ScotSeaNow » Sat Dec 01, 2018 11:13 am
michael louwe wrote: ↑
Sat Dec 01, 2018 4:17 am
.
Have you disabled Secure Boot, Fast Boot and boot the Live LM 19 USB/DVD in UEFI mode of the Boot menu in System BIOS.?Was the downloaded LM 19 ISO file version 2 or v2, ie not v1.?
Otherwise, try installing with the Internet disconnected.
Did disable secure boot. I don’t know about the Boot menu in system bios.
The down loaded version is what is pointed to on this website. It is on a DVD.
How do I load the third party software if installed with the internet disconnected?
I would like to find a way to install grub from a terminal at this point.
In looking at some ways others got this installed does not seem to be an option. When I select the other way to install, it does not give me the option to install a boot sector.
Thanks, Scot
-
ScotSeaNow
- Level 1
- Posts: 4
- Joined: Fri Nov 30, 2018 8:25 pm
Re: grub-efi-amd64-signed package failed to install
Post
by ScotSeaNow » Sat Dec 01, 2018 11:56 am
michael louwe wrote: ↑
Sat Dec 01, 2018 11:39 am
https://sites.google.com/site/easylinuxtipsproject/6 — Bootloader Grub for computers with Windows 8.x or 10 (EFI and UEFI): how to re-install it
In a UEFI computer, the Boot menu in System BIOS gives the user the choice to boot the Live LM USB/DVD in UEFI or Legacy BIOS mode, eg «EFI Ubuntu», instead of just «Ubuntu» for Legacy BIOS mode.
This PC came with windows 7, so I used their WIn7 advice:
mint@mint:~$ sudo mount /dev/sda1 /mnt
mint@mint:~$ sudo grub-install /dev/sda —root-directory=/mnt
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won’t be possible.
grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.
mint@mint:~$
Why the i386?
-
michael louwe
- Level 10
- Posts: 3288
- Joined: Sun Sep 11, 2016 11:18 pm
Re: grub-efi-amd64-signed package failed to install
Post
by michael louwe » Sat Dec 01, 2018 2:06 pm
ScotSeaNow wrote: ↑
Sat Dec 01, 2018 11:56 am
This PC came with windows 7, so I used their WIn7 advice:
.
The error message «grub-efi-amd64-signed package failed to install into /target/.» very likely means your HP desktop has been setup in UEFI mode in System BIOS. So, you need to manually reinstall Grub-efi and not Grub of Legacy BIOS mode.
NB: For dual-booting Windows and Linux on the same internal hard-drive, both OS should be in the same mode, in order to have the Grub menu displayed after startup.
-
JeremyB
- Level 21
- Posts: 12625
- Joined: Fri Feb 21, 2014 8:17 am
-
pbear
- Level 16
- Posts: 6560
- Joined: Wed Jun 21, 2017 12:25 pm
- Location: San Francisco
Re: grub-efi-amd64-signed package failed to install
Post
by pbear » Sat Dec 01, 2018 2:24 pm
ScotSeaNow wrote: ↑
Sat Dec 01, 2018 11:56 am
This PC came with windows 7, so I used their WIn7 advice:
Looks to me like you’re installing in BIOS to a GPT partition table. This can be done, but you have to clear space at the beginning of the drive to make room for the bootloader. See this tutorial by austin.texas. It’s a good strategy if you want more than four partitions, as GPT lets you have up to 128 primary partitions with no mucking about with extended and logical. Or, if you have no use for GPT, start over using an msdos
partition table.
-
JeremyB
- Level 21
- Posts: 12625
- Joined: Fri Feb 21, 2014 8:17 am
Re: [Solved] grub-efi-amd64-signed package failed to install
Post
by JeremyB » Sat Dec 01, 2018 5:32 pm
It could have been a quicker fix if you had posted results for sudo parted -l
as it is fairly easy and quick after knowing how the partitions are set up. In a simple Linux Mint only installed on a single drive can be fixed using the ISO by doing
Code: Select all
sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
sudo apt-get update
sudo apt-get install ubuntu-system-adjustments
apt install --reinstall grub-efi-amd64-signed
sudo update-grub
exit