Same for me. I can't install kubuntu 20.04.2 with the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error with 20.04-desktop ISO
To manage notifications about th
Me too, Machine: Lenovo Think-book 14-IIL. Win 10 pre-installed. Since a couple
of days I got permanently this error. Installing Ubuntu 20.04.1 anyway my
machine became very unpredictable. Rebooting of either system (Win or Ubuntu)
ended in a lot of error messages. I had to power off and then t
I have also just experienced this same issue when installing xubuntu
20.04.1. Let me know if I can be of any assistance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error wit
Today I had the same exact problem.
I found out that after creating on Windows 10 with win32diskimager an usb boot
stick with Ubuntu 20.04, I had a called "writable" partition on that stick
also. That efi image file you mentioned was the only file with a different
md5sum.
After that I created on
I have double-checked that there is nothing in the boot configuration
that is configured to modify the contents of efi.img (which contains
only the signed EFI executables - modification of which would cause the
image to subsequently fail to boot). Any modification of this image
must be coming from
I just realized Kai has already indirectly referenced the link I
mentioned.
These are two new (old) data points:
https://www.reddit.com/r/debian/comments/aflkdv/strange_error_while_check_the_cdroms_integrity_on/
Affecting ubuntu 18.10 Desktop
https://askubuntu.com/questions/404035/the-boot-grub-ef
This certainly looks like a hardware dependent issue.
Just to add another data point (not 20.04):
https://askubuntu.com/questions/1149958/ubuntu-server-18-04-2-hwe-kernel-boot-grub-efi-img-file-failed-the-md5-checks
@Lau
Since you have the hardware that CAN reproduce the issue, why not do a littl
Initially this was a question
(https://answers.launchpad.net/ubuntu/+question/691933) but I
invalidated it when this was reproduced by someone else and it seemed
like a real bug.
The checksum test were already reported there, but we also came to the
conclusion that it is modified during the boot p
As explained in the thread, the issue is not with the files in the
original iso but with the fact that the efi.img is modified during the
boot process, making the subsequent checksum fail.
This seems marked as invalid without looking at the issue.
--
You received this bug notification because yo
I Don't know real hardware, but on qemu:
qemu-system-x86_64 -bios /usr/share/qemu/OVMF.fd -drive
media=disk,file=ubuntu-20.04.1-desktop-amd64.iso
"-bios will only provide one big read-only ROM. In that case OVMS stores
the EFI variables in /boot/EFI/NvVars."
--
You received this bug notificatio
I have downloaded 20.04.1 desktop media, validated SHA256.gpg signature
and SHA256 checksum, mounted the iso.
The check succeeded for me both using md5sum -c md5sum.txt and using
casper-md5check /mnt /mnt/md5sum.txt.
I also mounted p1 of the iso, and executed the checks again and they too
were su
** Changed in: ubuntu
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error with 20.04-desktop ISO
To manage notificati
It might be helpful to take a closer look to see exactly what has
changed.
For example, do a binary comparison:
$ cmp -bl old/efi.img new/efi/img
Or loop mount the img files and examine the contents:
$ mkdir mntold
$ mkdir mntnew
$ sudo mount -o loop old/efi.img mntold
$ sudo mount -o loop new/ef
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error with 20.04-desktop ISO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
** Changed in: ubuntu-cdimage
Status: New => Confirmed
** Changed in: ubuntu
Status: New => Confirmed
** Changed in: ubuntu
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
maybe duplicate of bug 1832425
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error with 20.04-desktop ISO
To manage notifications about this bug go to:
https://bugs.launchpad.
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888033
Title:
Check error with 20.04-desktop ISO
To manage notifications
There was follow-up in the question (I first created this as a question):
https://answers.launchpad.net/ubuntu/+question/691933
The file efi.img in the USB appears to be modified at boot time (Kai
suggests that it is modified by the BIOS), which leads to a failed check
(different checksum than exp
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Description changed:
-
- When using the ISO for Ubuntu 20.04 Desktop from bootable USB, the following
message appears briefly at the end of the media check during boot.
+ When using the ISO for Ubuntu 20.04 Desktop from bootable USB, the
+ following message appears briefly at the end of the m
20 matches
Mail list logo
