As the error message says, you can not install grub in bios booting mode
on a GPT partitioned disk without a bios_grub partition.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: grub-installer
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066325
Title:
F
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066325
Title:
Fail
Have tonight tried with the release version of 12.10 - and the issue is
still there. See attached syslog from the latest installation attempt.
I had to use my workaround of removing my hard disk while installing
12.10 and subsequently re-attaching the hard disk. As a result I now
have 12.10 instal
Aha, a misunderstanding. It is direct on harware. -> o.K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066325
Title:
Failing to install boot loader - 12.10 daily build October 12
To manage notific
I guess a workaround will be to remove the hard disk while installing
onto the SSD then add the hard disk back in afterwards. Just a bit of a
hassle really. Surely there will be many users who have multiple drives
in their machine.
--
You received this bug notification because you are a member of
Sorry, but the only reason I mentioned KVM was that I initially tested
in KVM with no issues what so ever - and that was what caused me to go
ahead with a direct hardware install. The issue above IS a direct
hardware install (no KVM)!
Thus, I hope this can be fixed before Thursday as I would quite
There are only known problems with RAID settups when I remember correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066325
Title:
Failing to install boot loader - 12.10 daily build October 12
T
@ Soren
Just for knowing:
I have looked over the last reports on grub-installer.
There are nearly no issues arround with Ubuntu12.10, which resides on
top of Grub2 2.0. Just reports for Ubuntu12.04, which resides on grub2
1.99.x
May be your report is just caused by the KVM environment. So ,may
With the line you can find above and following
Oct 14 13:34:15 ubuntu grub-installer: error: Running 'grub-install
--force "/dev/sda"' failed.
it is a problem with grub-installer.
I will attach also this package here and keep the report open for grub2
and ubiquity, because I could not decide whi
In Syslog from comment 10 (from error logs 1 tar gz):
Oct 14 13:34:13 ubuntu ubiquity: File descriptor 3 (pipe:[34046]) leaked on
lvdisplay invocation. Parent PID 22139: /bin/sh
Oct 14 13:34:13 ubuntu ubiquity: Volume group "sdb" not found
Oct 14 13:34:13 ubuntu ubiquity: Skipping volume grou
from error logs 1 tar gz
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066325/+attachment/3398165/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
from error log 1 tar gz
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066325/+attachment/3398164/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Attached is a tarball with /var/log/syslog, /var/log/partman, and
/var/log/installer (same as previous attachment, but taken after
subsequently attempting to manually choose the location /dev/sdb and
/dev/sdb1 - both failing.
All logs produced with latest daily build (14th October).
** Attachment
Attached is a tarball of /var/log/syslog, /var/log/partman, and
/var/log/installer taken at the time of the error writing boot loader to
/dev/sda.
** Attachment added: "error_logs_1.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066325/+attachment/3398133/+files/error_logs_1.tg
I have set this for now to ubiquity and grub2, but the problem of the
missing logs is still there.
If you want to help us to investigate further please attach the logs
from
/var/log/syslog
/var/log/partman
/var/log/installer
of a fresh installation try.(May be you can get them to a flash
drive/s
Sorry Soren, but you have hit the wrong package.
This is on the installer itself(ubiquity) or grub2 or on grub-installer.
** Package changed: linux (Ubuntu) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => New
** Also affects: ubiquity
Importance: Undecided
12.10 beta 2 fails in the same way as the 12 October daily build of
12.10: The installer attempts to write the boot loader to the wrong
device (/dev/sda) and fails; manually changing the selection to /dev/sdb
does not produce a bootable system.
Have now re-installed 12.04, which successfully write
Booting off the live image for daily build 12 october does not allow me
to run apport-collect, claiming that a package is missing (or something
similar).
Experienced a hard-freeze right after the error so currently booting
live image of 12.04. Running apport-collect off the 12.04 live image
does n
19 matches
Mail list logo
