Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

  1. #11
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    I might download a new copy of Ubuntu ISO and install it fresh to a flash drive.

    Also link on how to create a bootable DVD or USB flash drive, using Windows or Ubuntu, Min hardware requirements
    http://www.ubuntu.com/download/desktop
    http://www.ubuntu.com/download
    Direct link to downloads page, most want ubuntu-18.04-desktop-amd64.iso
    http://releases.ubuntu.com/18.04/
    Create UEFI only bootable flash drive
    http://ubuntuforums.org/showthread.php?t=2299040
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  2. #12
    Join Date
    Jun 2019
    Beans
    12

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Hi oldfred,

    Already tried that many times already.
    I guess I;ll try install 18.04 instead of 16.04.

  3. #13
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    You may also need nomodeset boot parameter until you install the nVidia proprietary driver.
    Very newest versions of Ubuntu will install that also when you check to install proprietary drivers during install.

    At grub menu you can use e for edit, scroll to linux line and replace quiet splash with nomodeset.
    How to set NOMODESET and other kernel boot options in grub2 - both BIOS liveCD & grub first boot ( also UEFI with grub)
    How to add boot parameters, grub menu after install (also grub when UEFI)
    https://wiki.ubuntu.com/Kernel/KernelBootParameters &
    https://help.ubuntu.com/community/Grub2
    http://ubuntuforums.org/showthread.php?t=1613132
    https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter


    Asus Zenbook UX433FN with nVidia
    https://askubuntu.com/questions/1146...enbook-ux433fn
    Asus x541ua Update of UEFI & SSD firmware solved issues
    https://ubuntuforums.org/showthread.php?t=2414431
    How to install Ubuntu on ASUS F556U, JournalError error? add pci=nomsi
    https://askubuntu.com/questions/1079...081221#1081221
    Asus X541UV [SOLVED] How to partition my ssd in order to install ubuntu 17.10 / 16.04.4
    https://ubuntuforums.org/showthread.php?t=2392861
    Asus Vivobook S15
    https://ubuntuforums.org/showthread.php?t=2375408

    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  4. #14
    Join Date
    Jun 2019
    Beans
    12

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Hi oldfred,

    I was able to fix the error by turning off fast start-up and hibernation in Windows 10 which was making the EFI partition read-only.

    However, I am failing at the 'update-grub' stage. For some reason, before running grub-install or update-grub, /target/boot/grub is read-writable, but after running, /target/boot/grub is changed to read-only and it complains that it cannot remove /boot/grub/grub.cfg.new because the partition is read-only.

    Any ideas how to fix this, or what could be causing this? The partitions are all OK (fsck returns no errors), and mount -o remount,rw / doesn't work.

    Thanks.
    Last edited by dethrone; June 17th, 2019 at 06:27 AM.

  5. #15
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Back with 14.04 Ubuntu's default parameter for the ESP was defaults. The since changed to 0077 which means it is mounted with no permissions to write. So Boot-Repair automatically changes it and I change mine manually by commenting out original entry with #.
    It probably is a good idea to change it back as preventing writes is a secuity issue and Windows formats like NTFS & FAT32 have only permissions set at mount.

    But you should never have /boot/grub/grub.cfg.new as that is only written when you have a typo somewhere in either the scripts or parameters that grub uses to build grub.cfg.
    Check /etc/default/grub and if you edited any scripts in /etc/grub.d.

    Code:
    # /boot/efi was on /dev/sda1 during installation
    #UUID=FD76-E33D  /boot/efi       vfat    umask=0077      0       1
    UUID=F626-A4D4  /boot/efi       vfat    defaults      0       1
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  6. #16
    Join Date
    Jun 2019
    Beans
    12

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Hi oldfred,

    Again, super grateful for the help.
    I'm not at home right now so I can't check, but if I am understanding correctly, i just need to comment out the first line (UUID=FD76-E33D) of this file before I run the installer?

    Code:
    # /boot/efi was on /dev/sda1 during installation
    #UUID=FD76-E33D  /boot/efi       vfat    umask=0077      0       1
    UUID=F626-A4D4  /boot/efi       vfat    defaults      0       1
    Which file is this?

    Actually, since the installer mounts the partitions, I would need to edit this file during the installation when the partitions are mounted, but before grub is being installed? Either that or I do it all manually.

  7. #17
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Is error writing into ESP - efi system partition /boot/efi/EFI/ubuntu/grub.cfg or really in /boot/grub/grub.cfg? The grub.cfg in ESP is just 3 lines to load the full grub.cfg in your install.

    I think real issue must be some configuration setting as you should not have /boot/grub/grub.cfg.new, any install should be overwriting /boot/grub/grub.cfg.


    If booted it is /etc/fstab, but that is the grub.cfg for UEFI boot and is just a 3 line configfile entry to boot full grub.cfg in your install.

    If in live installer you have to mount partition, so depends on mount.

    I normally edit it after install, and do not have issues during install, but only when manually changing settings in UEFI. New install always overwrites /EFI/ubuntu but I have a main working install using 18.04LTS and always want that as default. So I typically boot, edit fstab, or booting my 18.04 from new install's grub and edit /boot/efi/EFI/ubuntu/grub.cfg to change to correct install.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  8. #18
    Join Date
    Jun 2019
    Beans
    12

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Hi oldfred,

    Some updates. Ran the installer manually in live mode so I could debug... when I got to this step:

    Code:
    ubuntu@ubuntu:~$ sudo grub-install --no-nvram --root-directory=/target
    Installing for x86_64-efi platform.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    
     Installation finished. No error reported.
    and

    Code:
    ubuntu@ubuntu:~$ sudo chroot /target
    root@ubuntu:/# update-grub
    Sourcing file `/etc/default/grub'
    Generating grub configuration file ...
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    error: cannot read `/dev/sda': Input/output error.
    cat: write error: Read-only file system
    cat: write error: Read-only file system
    In the file /etc/fstab:

    Code:
    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    # / was on /dev/sda6 during installation
    UUID=7b59cef1-ec97-493a-aac3-6b658543fa3b /               ext4    errors=remount-rw 0       1
    # /boot/efi was on /dev/sda2 during installation
    #UUID=22E9-8C35  /boot/efi       vfat    umask=0077      0       1
    # swap was on /dev/sda5 during installation
    UUID=c033c24d-7af5-4022-ba79-6bde9b16899c none            swap    sw              0       0
    I did comment out that line "/boot/efi". But I think that is not the problem? The problem is that /target/boot/grub somehow always gets remounted as "ro".
    Just to be safe, I also changed the first line from "errors=remount-ro" to "errors=remount-rw".

    1. There were no "grub.cfg.new" file generated this time. There isn't even a grub.cfg since the grub stuff failed.
    2. The main culprit seems to be the line "cannot read `/dev/sda': Input/output error.".
    3. Maybe we can get some insight on this if we can somehow run grub-install or update-grub in verbose mode. Is there such a setting?
    4. I believe if we can generate a grub.cfg, then the problem is solved. Maybe there is a filesystem on /dev/sda that is somehow not readable?

  9. #19
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Change back to ro as that lets you boot recovery mode and run fsck if needed as partition is not mounted.

    It seems strange that it says it cannot read sda, as it should be working with partitions like sda2 for ESP and sda6 for /.

    May be best to see details, use ppa version with your live installer (2nd option) or any working install, not older Boot-Repair ISO:
    Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues.
    https://help.ubuntu.com/community/Boot-Repair &
    https://sourceforge.net/p/boot-repair/home/Home/
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  10. #20
    Join Date
    Jun 2019
    Beans
    12

    Re: Dual Boot: The 'grub-efi-amd-64-signed' package failed to install into /target/

    Quote Originally Posted by oldfred View Post
    May be best to see details, use ppa version with your live installer (2nd option) or any working install, not older Boot-Repair ISO:
    Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues.
    https://help.ubuntu.com/community/Boot-Repair &
    https://sourceforge.net/p/boot-repair/home/Home/
    Thanks, I will try that in a bit.

    I read online (https://ubuntuforums.org/showthread.php?t=2246824) that it could be due to bad sectors on disk.
    I'm currently running "badblocks" and I'm 10% finished with 751 bad sectors so far...
    Would you recommend me try and zero out those sectors? (https://askubuntu.com/questions/7511...sectors-on-hdd)
    I think the hard drive should be fine... startctl status is PASS and I can run windows just fine. But maybe Ubuntu is complaining because it can't read some of the sectors?

    EDIT:
    Running grub-install in verbose mode, I see a ton of messages being logged as "adding a relocation entry for xxx". So maybe this is a case of too many bad sectors on the disk.
    Last edited by dethrone; June 18th, 2019 at 06:14 AM.

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •