*** This bug is a duplicate of bug 1090829 ***
https://bugs.launchpad.net/bugs/1090829
I solved this by disabling secure boot. I have an HP Spectre 360. You
have to disable secure boot and clear all secure boot keys in the BIOS
SETUP UTILITY.
--
You received this bug notification because
** Changed in: grub2 (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot install on locked ESP (read-only error)
To manage
@Eric: thanks for your feedback. I attach your Boot-Info in text file just in
case the pastebin expires.
Your Read-Only error is:
cp: cannot create regular file '/boot/efi/EFI/ubuntu/grubx64.efi': Read-only
file system
(eg line 1979)
@Phillip:
his dosfsck is from line 1262
his dmesg is from
*** This bug is a duplicate of bug 1090829 ***
https://bugs.launchpad.net/bugs/1090829
It is read only because it is corrupted, the question is why?
** This bug has been marked a duplicate of bug 1090829
grub-efi fails to install with Input/output error
--
You received this bug
Same bug here on Asus N550JV. Tried to use Boot-repair. Had the same
'Locked-ESP detected' message.
My post on Ubuntu forum: http://ubuntuforums.org/showthread.php?t=2184383
More info: http://paste.ubuntu.com/6332633/
Pressing ESC at start, I can see ubuntu (which was automatically added
to that
I solved my case today, thanks to your comments too.
On my HP Sleekbook 15, the EFI partition was read only because there were
errors on it. Therefore it was impossible to make any change to it.
I found out the files under the EFI/ubuntu directory were totally
garbled, the names themselves were
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Phillip, here is what you asked:
http://paste.ubuntu.com/1562554/
Line 1088 shows the bug.
Then lines and 1112 show a fsck on the ESP with no error.
Then line 1113 shows the bug is still here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
dosfsck was not run there. The -M switch to fsck tells it to skip
mounted filesystems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot install on locked ESP (read-only
Hi, I seem to have this one. I am willing to try to what you ask in
comment #8, but I want to be sure that I have the procedure down. When I
tried to install Ubuntu, it took a couple tries and I did not record
notes about what happened when. I do recall that I may have seen an I/O
error at one
ok, i'll try to provide that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot install on locked ESP (read-only error)
To manage notifications about this bug go to:
Another case: http://askubuntu.com/questions/244261/how-do-i-get-my-hp-
laptop-to-boot-into-grub-from-my-new-efi-file
(See from line 902 of http://paste.ubuntu.com/1418009/ )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
More anecdotes or me toos aren't helpful. What we need is for someone
to fsck the fs to a known good state and then try again. If you can do
that, and then installing causes the error to come back, that would
point to a bug in the kernel that someone could try to reproduce and
track down,
fyi, I updated Boot-Repair so that it will show dmesg and syslog next
time a user meets one of these 2 bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot install on
How is this any different?
** Changed in: grub2 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot install on locked ESP
Here grub-install returns a read-only error.
# grub-install --efi-directory=/boot/efi --target=x86_64-efi
cp: cannot create regular file `/boot/efi/EFI/ubuntu/shimx64.efi': Read-only
file system
cp: cannot create regular file `/boot/efi/EFI/ubuntu/grubx64.efi': Read-only
file system
cp: cannot
An IO error will lead to the fs being mounted read-only. Check
/var/log/syslog for errors.
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please read
http://ubuntuforums.org/showthread.php?p=12409846#post12409846 : the
partition is not entirely read-only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091477
Title:
grub-efi cannot
Barring some rootkit like setup that is actually running Ubuntu under
virtualization, it is not possible to write protect part of the disk
like this, so I'm looking for some kernel log messages that might shed
some more light on the situation.
--
You received this bug notification because you
19 matches
Mail list logo
