Well, that was was 5 years ago
and that report have lost all meaning
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571893
Title:
It doesn't mean anything.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571893
Title:
Unable to access non-Ubuntu loaders from G
Dino99, just what does this status change from «Confirmed» to
«Incomplete» mean ?...
Henri
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571893
Title:
Unable to access non-Ubuntu loaders from GRUB2
** 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/571893
Title:
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
To mana
Takkat, thanks a million!! I was desperate, you have saved me so much time and
trouble! I followed your advice and in 5 minutes everything is back to normal!
I can use XP and Ubuntu!
Thank you, thank you!
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.n
Adding my voice to the grub2 boot issues after installing Lucid.
1. As above, the grub2 install script automatically overwrote the boot
sector of sda1 (XP) on install. Had to use Testdisk to restore the
backup.
2. It also failed to detect the presence of Puppy in /dev/sda8 by
itself. However, i
sharing info between forums
i finally got a xp w/ recovery console cd to boot...the STOP problem did
have to do with the fact that the XP was so old ..what was going on was
the controller for the HD was AHCI, i switched that in BIOS to IDE and
success the CD booted (apparently able to see th
does anyone have any idea how one could manually get rid of the grub2
from the partitions and also what it was doing when it installed grub2
that was so odd.it kept saying not recommended
also i may add that i used gparted off a bootable cd and deleted the
ubuntu/xubuntu partitions and reabsor
you can see my trials and tribulations over here
http://ubuntuforums.org/showthread.php?p=9383155 if interested.
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which
by the way I should mention that the XP CD disk upon booting gotos STOP: and
gives a location
I do believe it thinks there is a virus due to the odd thing its seeing i.e.
'grub2' and halts
Others have reported being able to use the XP CD disk to boot and repair
startup but I have had no such luc
I have the same problem -- the misleading update tricked me into installing
grub into the partitions.
This is on a new system that has only windows xp home and a recovery partition.
ultimatebootcd has a utliity called GUJIN which shows you the bootloaders --
both say GRUB
I have tried to boot fro
Agree with you dino99 ; that comment is a doozy ! Helpful to the nth
degree !...
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this installer have to take care of the ubuntu partition installation
and install grub on it, nowhere else. Cant understand the actual design
dropping the newcomers and others too into breakages with this crappy
comment: "if you dont known where to install grub, install it
everywhere" AWESOME
--
Hullo Erick and thanks for posting ! Interesting to see that you also
include a Swedish reference ! I'm hoping that enough people will sign
off on being affected by this problem so that the developers will take
it seriously - if we want, as I do, «every-day users» to consider Ubuntu
as an alternati
@ M Henri Day, I just realized we've crossed paths before:
http://ubuntuforums.org/showpost.php?p=9020807&postcount=385
I'm kansasnoob on the forums, at that time I'd not yet discovered this:
http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Boot_Sector
Apologie
My recent report is likely a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/576724
I'll also mention that there. I also subscribed to this bug and marked
"effects me too", even though it's only effected me as far as having to
help dozens of people get things straightened
Thanks for posting, mgcarley ! It's a pity that this bug, which
certainly affects more than three users (!) has not yet been assigned,
and that the problem and its relatively simple solution (for most of us)
is not mentioned on the Lucid release-notes page
(http://sourceforge.net/apps/mediawiki/boo
This problem also affects 32-bit upgrades from Karmic to Lucid
(release). The testdisk solution works fine though.
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, whi
@Henri: no my problem is not really solved. It appears that I
accidentally installed grub in the Windows partition. This eventually
messed up the MBR/Partition block. So far we were unable to restore it
indicating that some additional problem exists, maybe unrelated to grub.
The Grub update would
But note, Takkat, that the Sourceforge testdisk app did in fact solve
the problem I describe in this thread, whereas it didn't resolve yours.
Has the latter now been resolved after the update to GRUB2
(1.98-1ubuntu6) ?...
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
http
Maybe this issue is related to bug #508173, fixed today
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
As from this thread in the german ubuntu forum:
http://forum.ubuntuusers.de/topic/windows-7-bootet-nach-ubuntu-update-nicht/
there is evidence that this is not really a bug from grub but from the way the
installer performs the upgrade.
If Grub2 is already installed on your system:
* keep the cur
Hope that all those affected by this bug do indeed click the «This bug
affects you» button, so that developers will realise that this bug
deserves to be taken seriously
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received t
@Maik Messerschmidt:
Thank you for pointing at this. I am not sure if it matters here, because swap
is and was always fine and devices were not renamed during the upgrade process.
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received
Hi
I think this has something to do with the bug, I just send in:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/573858
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of
To add to troubles: Fixing the MBR using bootfix from the Windows-CD
resulted in a totally corrupted partition table. Too bad as /home was on
the same hard disk. Luckily using testdisk I was able to restore the
partitions.
However Windows still won't boot from GRUB2.
--
Unable to access non-Ubun
Ironic, Takkat, that the procedure you suggested that was so helpful to
Westson and myself, didn't suffice to help you ! In any event, we are
agreed that this is something which the developers would be advised to
look at closely
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in
@Wetson, @Henri: your're welcome.
Unfortunately on my system testdisk says that backup and boot sectors
are identical thus refusing to correct the problem. No idea of how this
broken MBR found it's way to the backup. I definitely did nothing else
before trying testdisk. It seems I need to rebuild
Takkat, thank you very much indeed ! The Sourceforge testdisk app did
the trick for me on both my Ubuntu computers - when I came to «Boot», I
was informed that the «Boot sector» was not identical to the «Backup
boot sector». When this anomaly had been corrected and I exited, I found
that I could bo
I experienced this same problem, with two harddrives installed (one with
windows only and one with ubuntu and some ntfs storage space) after an
upgrade to 10.04 through the update manager i could see windows 7 in the
grub listing however it would not boot, i got the blinking cursor
screen. The wor
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I agree, there are more and mroe reports on this bug around. For some
people there is a workaround by fixing the MBR with testdisk (as
decsribed here:
http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Boot_Sector).
However this does not work for me. BTW I can mount
To save interested parties from the need to check out the link I
provided in my initial posting above, here below /boot/grub/grub.cfg
from my main box :
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/
Unfortunately, this bug remains unassigned. The affected package would
seem to be grub2 rather than ubiquity, so I have now changed the bug
description accordingly. Hope someone competent will take an interest in
this matter as the bug does not seem to affect only my machines ; for my
part, however
Same issue here after update from Karmic to Lucid. A FreeDOS partition
is also affected.
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Thanks for your speedy response, Jeff ! As a matter of fact, on both
machines, Windows was completely shut down before I upgraded from Karmic
to the respective Lucid betas. Both machines have two HDD, on one of
which Windows OS, on the other of which Ubuntu is installed. To provide
an example, here
Meh... I should amend that first sentence to say "Not that I have any
idea if this is the cause of your issue or not,. . ."
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Not that I have any idea if this is an issue or not, but on those
machines, was Windows shut down properly before you installed, or was
Windows Hibernated?
I'm not sure, in cases of hibernation in Windows, that the partition is
mountable, which may be an issue here. I'll try to recreate this thou
38 matches
Mail list logo
