[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/574883
Ti
I'm not able to reproduce this on a current release, are you?
** 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.
https://bugs.launchpad.net/bugs/574883
Title:
Grub
grub-pc1.99~rc1-1ubuntu2 in natty doesn't want to go in PBR, not in a
primary partition.
"blocklists are not recommended" and no grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/574883
Ti
As I just reviewed this, I wanted to add, that the line
"/usr/sbin/grub-setup: info: »/boot/grub/device.map« kann nicht
geöffnet werden."
in attachment grub-install.log would be
"/usr/sbin/grub-setup: info: »/boot/grub/device.map« cannot be opened"
in English. Usually the file really doesn't
Interesting: unknown boot code (?) on sda2 ??
** Attachment added: "RESULTS.txt"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/574883/+attachment/1811806/+files/RESULTS.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
$ sudo grub-install --force --debug /dev/sda6 > grub-install.log 2>&1
$ sudo fdisk -l 2>/dev/null | egrep "Disk /|/dev/" | sed "s#^/dev/#Part /dev/#"
| awk '{print $2}' | sed 's/://' | xargs -n1 -IX sudo sh -c "hexdump -v -s 0x80
-n 2 -e '2/1 \"%x\" \"\\n\"' X | xargs -n1 -IY sh -c \"case \"Y\"
Okay, I'll give it a try later this day.
In another discussion on this topic in a forum, I was advised to check
the exit code. The grub-install command as stated above produces exit
code 0.
To speed things up: Would you like to have any other information than
the output of grub-install, the booti
Hmm, how odd. I'll see if I can set up a few virtual machines to test
this out. In the meantime, could you please add the --debug option to
grub-install and post the output? That might speed things up for me.
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: grub2
In a next attempt, I tried to install SliTaz3.0 into sda1, which brought
its bootloader grub-legacy (installed to MBR of sda). I intended to use
Slitaz for maintainig the main bootloader which would be grub-legacy
then.
Installing grub2 into the PBR of sda6 failed again, exactly the same
results a
The above described obviously does only write parts of GRUB to the
designated PBR.
Performing
start code
insmod chain
chainloader (hd0,6)+1
end code
in order to chainload the partition prepared in the above mentioned way
produces an error message
"Booting a command list" aft
I continued to search for a solution and found:
http://www.gnu.org/software/grub/manual/grub.html#Installing-GRUB-using-grub_002dinstall
The I tried, what the manual proposes for some USB devices (last paragraph of
the refered section):
start code
caelinux@caelinux:~$ sudo -i
root@caeli
I can reproduce exactly the same behaviour.
I installed the bootloader of my choice to MBR and intended to chainload
several other OS from that.
Two of those OS should be Mint10-64bit (based on Ubuntu 10.10 64bit) and
CAELinux (based on Ubuntu 10.04 bit). Installing GRUB2 to their
respective part
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47720597/Dependencies.txt
--
Grub doesn't install to partition boot record (PBR)
https://bugs.launchpad.net/bugs/574883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
13 matches
Mail list logo
