This is still an issue in Oneiric. Here is my case:
* a computer with two hard-drives. One of the MBR of these is used to bottup
normally
* I introduced a USB stick with Kubuntu 11.04, booted from USB, and upgraded
to Oneiric (11.10)
After the upgrade, the MBR in the HD of the desktop
Colin: do my logs shed any light? Let me point out that updates to grub
during the life of the distro did not ruin the MBR. It has only (and
consistently) happened when upgrading to a newer distro version.
With that in mind. Why don't we ask the user for confirmation before
writing to the MBR?
Leo:
Exactly how many user level people will understand a disk ordering
other than what they see in their BIOS boot display, assuming they
actually watch that display?
If a user has only one disk, or had no two disks the same size, they
might be able to figure out that BIOS disk 0 is /dev/sdc to
Frank and Leo, could you post the output of 'sudo debconf-show grub-pc',
plus /var/log/installer/syslog and /var/log/installer/partman? I
suspect that at some point something (perhaps the installer) recorded
the wrong disk as the installation target, and that got preserved.
seasoned_geek: please
Colin:
BIOS ordering is NOT a Red Herring. I'm not abusing you, I'm attempting
to educate you since there appears to be a shocking amount of ignorance
on the issue.
FeeDOS, Windows, OpenDOS, PC DOS 2000, and OS/2 all do BIOS ordering and
do it correctly.
When your user base has a second OS
The thing that's needed is consistency, not agreement with BIOS
ordering. The necessary property can be expressed quite simply: once
you choose to install GRUB to a given disk on installing the OS,
upgraded versions should be installed to that disk again on upgrades.
BIOS ordering does nothing
The thing which is needed is agreement with the BIOS because ONLY THAT
CAN PROVIDE CONSISTENCY WITH THE OTHER OPERATING SYSTEMS. They ALL
respect the BIOS, even the boot order changes done in PROM or at boot
time via a hot key.
Claiming BIOS ordering is irrelevant is simply demonstrating a
There are a number of inaccuracies in this comment, but there's no point
discussing this further with somebody who clearly isn't interested in
hearing what we have to say. I'm not prepared to spend any more time
explaining how GRUB works in this bug report. Please allow us to debug
user problems
My statements were and are completely accurate.
I'm using a different OS because this problem has existed for YEARS in
the Ubuntu distribution and I could no longer function with a single
disk computer.
Ubuntu is the ONLY Linux distro having this problem.
--
You received this bug notification
Hi Colin,
I am attaching the required info. Apparently I can only add one at a
time.
Thank you so much for looking into this. Cheers!
Leo
** Attachment added: sudo debconf-show grub-pc grub-pc.txt
** Attachment added: sudo cat /var/log/installer/partman partman.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110797/+files/partman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: sudo cat /var/log/installer/syslog syslog.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110798/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: df -h df-h.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110800/+files/df-h.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/496435
Title:
** Attachment added: sudo blkid blkid.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110801/+files/blkid.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/496435
Ok, I added all the info, I hope it helps. I took the liberty to add a
couple more useful outputs.
My computer boots from /dev/sdb , but I always keep a grub in /dev/sda
just in case. Both of them failed to load grub after the upgrade (I only
run grub-install /dev/sda every once in a while, I
I noticed a reference to a third partition in the grub-pc output:
grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1001FALS-00J7B1_WD-
WMATV1484210-part3
Does this mean that the upgrade is trying to install grub on a partition
instead of the MBR? But, assuming that's the case, why does the old
Leo:
I'm not introducing opinions. I have introduced facts which have been
completely ignored by support because it doesn't fit their opinion of
how things should work.
Ubuntu is the _only_ distro with this problem. Every other distro
acknowledged the facts. Here we have erroneous opinions
I got this problem on upgrade to 10.10 and then again on 11.04. I was
also concerned that when I booted from a usb stick then the stick was
sda and my hard drive(I only have one...windows vista boot as well) was
sdb so I didnt feel confident to do a grub install, so ended up creating
a live dvd
Same here. My desktop system with 2 sata hard drives just rendered
itself unbootable after upgrading Kubuntu 10.10 - 11.04
As far as I can tell, Fix Released is not a proper characterization for this
bug's status, and this is a CRITICAL bug. I really don't mean to flame, but we
can't afford
I had to abandon Ubuntu for OpenSuSE 11.4 which doesn't have this issue.
The root of the problem is that Ubuntu DOES NOT RESPECT BIOS ORDERING
but just about everything else does. What Ubuntu appears to do is
quite stupid, it appears to ASS-U-ME that your largest drive is your
boot drive, rather
To work around this (annoying) bug see [1], specifically Section 13
Reinstalling GRUB 2 from LiveCD
[1] http://ubuntuforums.org/showthread.php?t=1195275
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To work around this (annoying) bug see [1], specifically Section 13
Reinstalling GRUB 2 from LiveCD
[1] http://ubuntuforums.org/showthread.php?t=1195275
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I used update-manager to update from 10.04 to 10.10, and I got the infamous
grub-xputs.
I have two SATA disks and memory card reader.
With 10.04, SATA disks were enumerated before memory card readers (sda, sdb
then sdc, sde, sdd, sdf).
With 10.10, memory card readers are enumerated before SATA
Grub MUST MUST MUST MUST MUST support the BIOS device order.
Why must Grub boot with Unix code? Why cannot Grub boot with whatever
bootstrap IBM used with the boot manager they shipped with OS/2? That boot
manager always respected device order AND it could boot any OS, including
various
@Jordan - I technically have 2 drive controllers. One RAID controller
exposing a single drive, and one PCI ATA-133 controller holding two
optical drives. I'm not sure how this bug could be considered fixed if
grub is still failing to identify the correct drive upon which it
actually needs to
I encountered this bug today upgrading Kubuntu from a clean 10.04
install to 10.10 using the update-manager tool. The machine is 32-bit.
It has no SATA controller at all. It's not a Dell (it's an older Asus-
based dual athlon MP system). There is only one hard drive in the
system. There is no
@Danny Sauer
This bug has been fixed. And as you have only one hard drive it could
not, by definition, have ever affected you.
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Ubuntu
Unless, in its infinite wisdom of not identifying devices in BIOS order, Grub
also decided to identify devices as whatever type it chooses rather than what
they are. It could have identified the RAID controller connected CD/DVD as a
hard drive even though it wasn't and choose to try updating
@Seasoned_geek
Please re-read the bug description, this has nothing to do with how the
BIOS orders devices. Additionally, it is impossible to reliably
determine the BIOS's order from within linux which, among other reasons,
is why grub2 instead identifies filesystems by UUID.
--
upgrades of the
This bug has EVERYTHING to do with how the BIOS orders devices and how Grub
just outright ignores that ordering despite the fact every other PC based OS
can get that information from the BIOS and respect it. They can even honor
the device order selected by the user from the boot menu.
When
I hit the bug also, in Kubuntu AMD 64. However, I have only one hard
drive. No RAID.
Was able to use the LiveCD to chroot in and fix GRUB, but this bug,
lasting this long..very disappointing. Blogged about it:
http://linuxgrandma.blogspot.com/2010/10/grub2-and-chroots-dammit.html
--
I hit the bug upgrading from 10.10 from 10.04 running AMD 64. I have
multiple SATAs and RAID, but only the one operating system. Very
frustrating as I've left my USB key with xubuntu for such moments at
work! So, in short, the bug still exists.
Tim
--
upgrades of the grub-pc package can
** Tags added: iso-testing
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same here, it hit me when upgrading from Kubuntu 10.04 to 10.10beta, on
an amd64 system with multiple sata drives. I had to boot from the live
image and chroot.
Shouldn't that part of a grub/system upgrade ask for user input, since
this is SO critical? This is a killer for non-experts!
--
The problem is that Grub doesn't identify SATA drives in the same order as the
BIOS. It is really easy to see if you have 3 SATA drives and each have
different sizes.
I have argued and argued and argued and argued, but I keep hitting a stone
wall. FreeDOS and Windows both manage to identify
Got the same issue using ubuntu-10.04.1-alternate-amd64.iso. I run a MD
RAID for the root but have a small ext2 partition at the start of the
first drive for /boot.
Was the fix in 10.04? If it was then it did not work for me.
I recovered by live booting a CD, installing mdadm, assembling the
** Changed in: grub2 (Debian)
Status: New = Fix Released
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The problem is that Grub does not respect the BIOS ordering, which
means it doesn't play with Windows, FreeDOS, DR DOS, or any other OS
that does respect BIOS ordering for multi-drive systems.
On Thursday, May 06, 2010 10:45:28 pm you wrote:
Bump. I can attest that this symptom is present in
I installed GRUB 2 already in Karmic. There where several kernel
updates, which implied a GRUB menu update. there was never a problem.
But the update from 9.10 to 10.4 and a reboot produced the error symbol
`grub_puts_' not found.
There are an IDE and a SATA harddisk
neither sudo grub-install
Bump. I can attest that this symptom is present in release Lucid. I performed
an over-the-wire upgrade from 9.10 to 10.04. On reboot, got the symbol
`grub_puts_' not found error. Interestingly, although there are two SATA HDs
in this machine (one spinning media, one solid-state), the BIOS
I upgraded my Karmic to stable Lucid yesterday, today when i rebootet i got
this error to. So to claim it is fixed in Lucid is wrong.
I have two SATA drives. The first with windows (with two NTFS partition) and
Kubuntu Karmic (with / /home /var ext4 partitions) and the second with only
one ext4
Hey all after an hour on Google I found a fix that worked for me for the
Grub_puts_ error.
http://ubuntuforums.org/showthread.php?t=1014708
I am currently dual-booting Windows 7 with Ubuntu 9.10. After upgrading
to 10.04 though I got the grub_puts_ error. I just used my Ubuntu 9.10
disk and
Heads up... the http://ubuntuguide url mentioned in comment#7 links to a
Windows virus downloader. Can someone please remove that url from this
report/issue?
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification
the permanent fix is to remove the Dell Backup Utility.
Rob.
On Sat, Apr 17, 2010 at 9:31 PM, M Pietila
pietila.meg...@comcast.netwrote:
Upgraded from Karmic to Lucid today and am also having the symbol
'grub_puts' not found error described by illbashu; I have the Ubuntu
install on a
This bug might interact with the Dell Backup Utility, but I hit this
bug every time I install Ubuntu with Grub2 on my no-name, custom PC.
My computer uses a SATA DVD, and has lots of hard disks. The BIOS disk
enumeration may change for Grub when the system is running the
installation DVD, then
This bug impacts all who have multiple SATA drives. While DELL may be
corrupting things for _some_ users, my workstation doesn't have a single
Windows partition on it.
Grub DOES NOT HONOR the BIOS drive enumeration.
If you have more than one disk drive, YOU CANNOT INSTALL this or any later
Upgraded from Karmic to Lucid today and am also having the symbol
'grub_puts' not found error described by illbashu; I have the Ubuntu
install on a different drive from sda, so I had to reinstall grub2 for
Karmic also. I haven't rebooted yet after reinstalling grub2, but I
assume I'll run into
symbol 'grub_puts' not found
grub-recover
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/509797
^ bug report told me to post here.
I'm having this prob on 10.04 beta every time grub gets updated. The
only fix I found was to boot into 9.10 (only live cd I have) and restore
grub. Is there
This should fix the core of this problem. I expect that it will need a
few more tweaks, but that's why I'm landing it a couple of months before
release. :-) If you have problems with this, please file them
*separately* rather than following up to this bug, otherwise I'm going
to get very
Pretty sure this bug toasted my Pointsec encrypted primary drive. Karmic
was installed entirely on secondary HD with primary not present (to make
sure I didn't overwrite the mbr and break Pointsec). I then used the
bios menu to switch between drives to boot.
Booting the primary started showing
This bug is exactly what's covered by the foundations-lucid-reliable-
device-id-in-grub specification, so I've linked them.
** Changed in: grub2 (Ubuntu)
Status: New = Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
--
upgrades of the grub-pc package can overwrite
I can confirm this bug. The problem appears to be that Grub2 will include the
line
set root=(hdX,Y)
when installing grub on the external hard drive. In my case I had 3 internal
drives on the machine that I used to configure the external drive. So the line
root=(hd3,1) was included which works
I would welcome some advice on how to post with a more pleasing layout
too.
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Am Mittwoch, den 06.01.2010, 21:15 + schrieb bwallum:
set root=UUID=fd0c6442-dc3d-49ba-8e46-91657460fe52
search --no-floppy --fs-uuid --set
fd0c6442-dc3d-49ba-8e46-91657460fe52
The search --fs-uuid --set line will set $root the device with that
UUID.
There's no need to change
** Bug watch added: Debian Bug tracker #554790
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554790
** Also affects: grub2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554790
Importance: Unknown
Status: Unknown
--
upgrades of the grub-pc package can overwrite
** Changed in: grub2 (Debian)
Status: Unknown = New
--
upgrades of the grub-pc package can overwrite wrong MBR
https://bugs.launchpad.net/bugs/496435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
56 matches
Mail list logo
