Finally found work around.
Once installer started, I checked mount and mount target mounted ESP on sda.
Unmounted that partition & mounted ESP on sdc.
ubuntu-mate@ubuntu-mate:~$ history
1 mount
2 sudo umount /target/boot/efi
3 sudo mount /dev/sdc1 /target/boot/efi
4 mount
--
Apr 28 18:34:20 fred-Z170N-disco systemd-tmpfiles[615]:
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below
legacy directory /var/run/, updating /var/run/speech-dispatcher →
/run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.
Apr 28 18:34:20
Rebooted and reinstalled.
Using different order for selecting ESP/efi partition it worked without error
on not using sda, but installed to ESP on sda.
Install log showed this:
Feb 15 20:23:36 ubuntu grub-installer: info: Installing grub on '/dev/sdb'
Feb 15 20:23:36 ubuntu grub-installer: info:
Public bug reported:
Installing latest version as of Feb 15, 2019.
I have multiple installs, so using Something Else install option.
I am able to change partition to use to my sdb8 which is previous Disco install.
I tell it not to use swaps that I still have on sda & sdc.
But I want to install
Still an issue in 19.04 Disco.
Just installed again to sdb and just like comment above, said it was installing
to sdb's ESP, but overwrote my main working install's ESP on sda.
I cannot find any reference to installing to sda.
Installer sees sda as an ESP, but also sees sdb as ESP.
** Changed
Just installed 18.04.1 to flash drive sdd.
Installer said this:
Dec 27 19:29:45 ubuntu grub-installer: info: Installing grub on '/dev/sdd'
Dec 27 19:29:45 ubuntu grub-installer: info: grub-install does not support
--no-floppy
Dec 27 19:29:45 ubuntu grub-installer: info: Running chroot /target
Installed 19.04 to sdb drive (internal, but also flash drive as sdc) and
it overwrote my /EFI/ubuntu folder on sda.
I changed combo box which never has done anything with UEFI installs, but it
does then say during install that it is installing grub to sdb/external.
I clicked on ESP on sda, and
With 18.10 using grub to loop mount the ISO.
/tmp/calamares-root-ere7liao/boot/efi
Boost.Python error in job "unpackfs".
Command '['mount', '/cdrom/casper/filesystem.squashfs',
'/tmp/tmp0dld31ld/filesystem', '-t', 'squashfs', '-o', 'loop']' returned
non-zero exit status 32.
None
Traceback:
Resolved my boot issue, I think. Errors on FAT32 ESP, my sda1.
Issue started with no space left on device.
Then I would add new UEFI boot entry for sda's ESP for 18.04, but on reboot
UEFI would not use it, erased it and entries for all the .efi possibilities
were added from boot device, my
I updated UEFI from Asus, but same version I was using since April.
Still only can boot with rEFInd from sdc or flash drive with full
install of Ubuntu.
UEFI does not want to see ESP on sda which is mounted by fstab. It changes
entries to like drive disconnected.
And on reboot all new entries
I have been booting with the same version of UEFI from Asus since April.
But now either UEFI or Ubuntu is deleting all UEFI entries and creating
multiple new UEFI entries from boot device.
I was having issue of UEFI entry not installing at all.
fred@bionic-z97:~$ sudo grub-install
May be similar to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No space left on
May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1787692
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518
Title:
package grub-efi-amd64-signed
May be related to this bug.
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787692
Title:
package grub-efi-amd64-signed
*** This bug is a duplicate of bug 1396379 ***
https://bugs.launchpad.net/bugs/1396379
Just installed 18.10 to external SSD seen as sdc, but hd0 in UEFI/grub.
I unselected the ESP on sda, and selected external's ESP for efi partition.
Also used combo box which I know currently does nothing
Installer only asks for bios_grub if you boot install media in BIOS
mode.
With UEFI systems you want to always boot installer in UEFI boot mode
and then it will use ESP - efi system partition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Seems related to this bug.
Ubuntu 18.10 Cosmic installed /EFI/grub
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1775743
As update during install creates /EFI/grub like in above install.
But some users manually boot into Ubuntu & update grub and it works.
manual boot:
grub> set
Just saw one thread in Ubuntu Forums & one in AskUbuntu where with 18.04
the Boot-Repair output from efibootmgr -v shows no ubuntu entry and only
has a grub entry.
See:
https://ubuntuforums.org/showthread.php?t=2396042
And:
> With which daily image did you see this?
The install of Cosmic has modified date of Mon 11 Jun 2018 07∶55∶53 AM CDT.
Not sure when I downloaded it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure proposed fix is all of issue.
I boot 18.04 by default with UEFI and every test or experimental install in the
past has overwritten my /EFI/ubuntu.
But install of Cosmic did not overwrite my /EFI/ubuntu but created /EFI/grub.
It has a correct /EFI/grub/grub.cfg, but my UEFI is set to
Same issue as posted in #3 with new 18.04.
Install to flash drive, does not use ESP on flash drive, but installs to
ESP on sda. Then system is not bootable without flash drive as it has
overwritten my default boot on sda from /EFI/ubuntu.
I also have changed GRUB_DISTRIBUTOR as defined in
Issue is really that to boot in UEFI mode you should have gpt.
And most systems now have gpt as windows in UEFI mode requires gpt. But if
installing in BIOS/Legacy/CSM boot mode to gpt drive, you must have a bios_grub
partition which is only 1 or 2MB unformatted with bios_grub flag.
Or if
I have same issue with 17.04 full install to flash drive.
It overwrites my main working install's /EFI/ubuntu on sda.
If I then remove flash drive system is unbootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debian says it is fixed in Debian Grub 2.02~beta2-19 Back in Jan 2015.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767037
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746662
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708430
** Bug watch added: Debian Bug tracker #767037
I have tried installing all versions thru 17.04 to sdb and to sdb's ESP.
Every one overwrote my main working installs /EFI/ubuntu folder in sda.
I quickly learned to back that folder up, so I could reset main working
install as default boot.
Same happens when I do a full install to flash drive,
Similar to
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1450783
If distributor was updated by version then you would have different
/EFI/version folders and/or different entries in UEFI.
Other versions of Linux do have different names/versions, so grub2 can
do this.
--
You received
See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746662
** Bug watch added: Debian Bug tracker #746662
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746662
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubiquity even says installing grub to sdb during install but overwrites
my /EFI/ubuntu on sda.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591352
Title:
Ubiquity copies efi boot information to
Grub only installs to sda.
I have created ESP on sdb, told installer to install to sdb, it says
during install in notes at bottom installing grub to sdb, but it
overwrites my default boot /EFI/ubuntu on sda's ESP.
Also issue with full install to flash drive or any external drive as sdb
or higher
See also:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/684280
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155216
See Post #14 by experimancer
Fix is actully here: https://help.ubuntu.com/community/Grub2/ISOBoot
(i.e add "toram" to relevant Grub2 menuentry or manually
This similar bug says to use toram boot paramater, but if installer
offers to unmount partition, it still should do that.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/684280
Post #14 by experimancer
Fix is actully here: https://help.ubuntu.com/community/Grub2/ISOBoot (i.e add
Same issue with 16.04 Xenial.
Installer does ask if you want to unmount, but it does not unmount and hangs or
gives errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155216
Title:
Unable to
Your boot entries with kernel 3.19 would be from your 15.04 install.
All your installs are BIOS based on MBR partitioned drives. So rEFInd
will not work as it is for UEFI systems with gpt partitioned drives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Now getting same issue with UEFI boot and Wily. ISO on sdb, boot is from
sda as that is all the grub allows with UEFI.
And it automounts a partition in sda (random partition?) as /isodevice.
So then it will not let install to another partition on sda.
--
You received this bug notification
I changed GRUB_DISTRIBUTOR so I could tell which install was which.
I have my main working 14.04LTS install on sda, but install other test installs
on sdb.
I try to install grub to ESP - efi system partition on sdb and installer even
says installing to sdb. But it always installs to sda.
I then
Several users in Ubuntu Forum also having same issue, including me.
http://ubuntuforums.org/showthread.php?t=2288589
Manually starting wine server first in terminal worked, but error still
flashed by as I started Picasa.
wineserver -p
--
You received this bug notification because you are a
Have you tried adding this to Windows BCD with Windows bcdEdit?
bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi
Grub only works is secure boot is off. Not sure if shimx64.efi would
work from Windows with secure boot on or not.
Many systems need work arounds as vendors/mfgs violate UEFI
Not a shim issue.
Windows only only installs to NTFS partitions. Or drives with space for NTFS
partition.
Also Windows installer booted in BIOS mode will not install to gpt partitioned
drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It is my understanding that ESP is the correct full Initials (name) for
what we often just call the efi partition.
EFI System Partition (ESP)
Ubuntu installers have referred to the ESP by the name EFI boot partition,
But use of boot partition has confused new users thinking that is
Ubuntu's
Not grub issue.
Windows only has boot files in one NTFS primary partition with boot flag.
It looks like you may have run Boot-Repair which copied boot files from sda1 to
sda2.
But your XP install probably has no boot files in it for os-prober to find.
If all installs of Windows are on primary
I have not read the spec but saw this:
UEFI 2.3 -it is permitted for the firmware to treat the EFI system partition in
the same way as removable media or use bootx64.efi
http://mjg59.dreamwidth.org/4125.html
And many UEFI implementations, all of HP Sony that I have seen in
Ubuntu forums will
LVM install wipes out entire drive.
With alternative installer in 12.04 it clearly said full drive install.
But with 14.04 LVM says easy partitioning so new users choose it and
erase entire drive.
http://ubuntuforums.org/showthread.php?t=2233313
--
You received this bug notification because
This user selected reinstall and it showed just his partitions. But then
it erased all.
http://ubuntuforums.org/showthread.php?t=2231525
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265192
Title:
One more:
http://askubuntu.com/questions/488708/cannot-access-windows-after-re-installing-ubuntu-on-dual-boot-pc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265192
Title:
Reinstallation wipes
Boot-Repair does the rename for 'buggy' UEFI. Many HP Sonys only boot
with one of the fixes as the UEFI is hard coded to only boot Windows.
The rename then lets UEFI think it boots Windows efi file but really
boots to grub menu. But then Windows entry in UEFI only boots grub.
bkpbootmgfw.efi
May be duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1265192
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267204
Title:
Option to remove Ubuntu 12.04 and replace it
In Ubuntu Forums we have seen at least 4 or 5 users with exactly the
same issue.
Installer only offers to reinstall Ubuntu but then overwrites entire hard
drive. First thought it was user issue, but many have reported it and described
consisently what they have done.
On re-install it only sees
Same error with trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155216
Title:
Unable to umount isodevice
To manage notifications about this bug go to:
The issue is not just the 4 primary partitions in use with MBR. We are
seeing the the forums many users over writing UEFI Windows with gpt
partitioning. Again not sure if just user error or why it is occurring
but it is a lot more than one or two accidentally picking wrong choice.
Several have
Orginal error was in ISO itself.
Above error seems to be just when written with certain tools that file
name is too long to be converted from ISO correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It disappeared on me, but then I was able to re-add it. But not on right
side. It is sitting in the middle now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249663
Title:
Trusty gnome flashback
This user found more issues and created a perl script to rename files
correctly.
http://cirrus.ucsd.edu/~pierce/fix_ubuntu_usb/
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Daily's have not worked. Just tried jerrylamos' workaround and it did
not work for me.
Entire contents of installer debug.
Ubiquity 2.15.20
(ubiquity:3886): Pango-WARNING **: error opening config file
'/root/.config/pango/pangorc': Permission denied
Ubiquity 2.15.20
/root does not have read
It now looks like in 12.04.3 that both 6 and 4 are missing from end of file
name. The change from 3.9 to 3.10 added a character, so one more was dropped
from end of file.
Seems like an issue with file name length on ISO.
Original file on server is probably correct.
--
You received this bug
With yesterdays update my work around of using bash instead of sh and
from terminal worked. Updated again today and now I cannot install from
icon nor with terminal bash workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Similar issue. I use grub loop mount to boot ISO, so I did not know if that was
issue. Could not get Ubiquity to start (or seem to). Tried rebooting ISO
several times.
Then tried using commands in Icon's properties at command line and it said
Ubuquity was running, but nothing was happening.
We still see this. I see about one user a week having this issue and I
have to have them use testdisk to restore backup or use Windows repairs
to fix.
It seems to be in several different places. Original install under
Something Else or dpgk reinstall of grub. But in all cases it seems that
** Changed in: linux (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172065
Title:
12.04.2 incorrect file name signed efi amd6.deb
To manage notifications
I like to create flash drives that I can use to boot muliple systems.
I then want my flash drive configured to be able to boot system whether
UEFI or BIOS like the installer flash drive. But the installer uses
syslinux for BIOS and grub for UEFI. I really just want grub for both.
--
You
The live installer boots with syslinux for BIOS and grub for UEFI.
So I think you have to edit grub menu for persistence as with UEFI syslinux is
not used.
Not sure how to do that, as I do not use persistence.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached screenshot here:
http://ubuntuforums.org/showthread.php?t=2138041p=12617434#post12617434
I downloaded copy from this mirror:
http://mirror.anl.gov/pub/ubuntu-iso/DVDs-Ubuntu/12.04.2/
That has a 14-Feb-2013 date.
Many users in Forum said they could not boot liveCD with secure boot on.
I
Public bug reported:
download ISO has wrong nameamd6 should be amd64.
In /pool/main/g/grub2-signed
grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd6.deb
seems like it should be
grub-efi-amd64-signed_1.9~ubuntu12.04.3+1.99-21ubuntu3.9_amd64.deb
See Also
There is no log. It is just a wrong file name in the install ISO.
It is not a file I use as it is UEFI secure boot I only have ISO. But
file is still wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My workaround was to download into my test install of 12.10 and copy
that .deb file into 12.04.
That newer version then worked and I did not have to recompile myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Edit - found reference to the bit that is set, but need to find how to reset
it. It is intended for other efi type partitions like a vendor recovery so
users would not damage a vendor recovery. If HP is setting it on the efi
partition it is wrong. Bug is not really related to current issue.
I do not like suggesting dd to new users.
In this thread just adding a Windows 7 boot stanza to 40_custom worked.
Grub legacy almost never found Windows 7 either and we almost always had
to add the boot stanza for Windows 7 to menu.lst.
http://ubuntuforums.org/showthread.php?t=2088596
See post
After install of 12.10 and reboot, it does not work. Typical black screen.
Added nomodeset to grub parameter on boot line it then does boot.
But for a new user that is a huge issue, that it just does not work.
No pop-up like previous versions on proprietary drivers are available.
--
You
I reported under the wrong bug report. Mine is nVidia.
These all seem related to me:
This one has the most reports:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1068341
https://bugs.launchpad.net/fglrx/+bug/1068456
It used to not create an entry at all, but now creates the standard
BIOS/mbr entry when it needs to be a different UEFI/gpt type entry.
See this:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1024383
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is Ubiquity separate from grub2's installer?
This supposedly was fixed with 10.10 and grub 1.98.
Kansasnoob bug report:
http://art.ubuntuforums.org/showthread.php?t=1475385
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/576724
Ran backtrace
If I run openyahtzee from command line, processor #1 goes to 100%, If I
try running it again then both processors show 100% until I kill the
process. No window ever opens.
** Attachment added: gdb-openyahtzee.txt
Public bug reported:
Using 12.04 with fall-back mode and nVidia proprietary driver.
openyahtzee (1.9-1) unstable; urgency=low
top - 14:40:38 up 1 day, 23:23, 1 user, load average: 0.56, 0.50, 0.44
Tasks: 153 total, 2 running, 151 sleeping, 0 stopped, 0 zombie
Cpu(s): 50.2%us, 0.2%sy,
In my case with fallback mode and 3d the close, min, max buttons totally
disappeared. Only when I changed to 2d mode did icons reappear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982485
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941075
Title:
package cups 1.5.2-5 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit
status
Public bug reported:
Running Update from previous install.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-5
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CupsErrorLog:
Date: Sat
Public bug reported:
Trying to loop mount the alternative installer:
Jan 11 17:53:41 iso-scan: devices found: '/dev/sda1 /dev/sda2 /dev/sda3
/dev/sda4 /dev/sdb1 /dev/sdc1 /dev/sdc2 /dev/sdc5 /dev/sdc6 /dev/sda /dev/sdb
/dev/sdc'
Jan 11 17:53:44 iso-scan: selected_device(s)='/dev/sdb1'
Jan 11
Just installed 12.04. Same issue but worse. Could not get to graphical screens
at all. Alt-f2 gave me command line. Did updates Nov 10, 2011 and still would
not fully boot.
Uninstalled 173, installed nvidia-current , finally got to gui, but it used
default video as it then popped up saying I
The additional drivers now shows three entries. The installed 173,
current and an updated which I gather is the current but will be
updated?
Is this left over from alpha or beta as it seemed then the only driver
was the 173 as there were issues with everything else?
--
You received this bug
Public bug reported:
Binary package hint: grub2
grub-pc installed on gpt drive sdb boots Ubuntu install on sdb but will not
boot windows in sda or other Ubuntu installs in sdc.
Since I was booting directly from sdb I tried changing drive numbers 0,1, 2
in set root with same results.
Windows
I use c and at grub prompt insmod part_msdos.
Both windows and Ubuntu then booted ok (a little slow it seemed in
switching to Ubuntu, windows is always slow so I could not tell any
difference.)
Glad you already had a fix. How would I have found this. I occasionally
review grub errors and
To make this permanent, the simplest option for now is probably to edit
/etc/grub.d/40_custom and add 'insmod part_msdos' at the very end of
that file, after the comments.
I added insmod part_msdos to 40_custom both windows on sda1 and Ubuntu
on sdc5 booted without any issues.
Thanks
Part of the problem is windows refers to drives when they really are
partitions. In windows you have a C: drive and a D: drive when you only have
one hard drive and two partitions. All those windows users that then have not
installed Ubuntu other than the auto installer really do not know about
82 matches
Mail list logo
