*** This bug is a duplicate of bug 549756 ***
https://bugs.launchpad.net/bugs/549756
Linux is on USB drive, and hard drive is on windows, a pc on which I do
not have right to write MBR (company policy) or install anything;
I have grub2 writing on a hard drive MBR automatically sometimes
*** This bug is a duplicate of bug 549756 ***
https://bugs.launchpad.net/bugs/549756
Omer. Yes, 549756 is a duplicate of this bug, which as you can see from
David's post is still an issue in Maverick.
I agree, this is more likely to be a ubiquity issue than grub2, as it
has to do with the
*** This bug is a duplicate of bug 549756 ***
https://bugs.launchpad.net/bugs/549756
** This bug has been marked a duplicate of bug 549756
[Regression] Installing to USB drive, proposes MBR to be written to internal
disk
--
[karmic] grub re-writes boot sector on wrong drive on fresh
is this still an issue? I wonder the problem might actually be in
ubiquity. bug 549756 might be related
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because you are a member of Ubuntu
Bugs, which
Now I have two problems.
1) how do I get Windows on my laptop to boot again I need my work data!
2) how do I make my mythbuntu USB front-end install bootable?
Oh yes, I did face that problem sometime back, and though I love Ubuntu,
GRUB needs to improve. I follow the brute force approach
I can confirm that this still applies to Maverick Alpha 2.
Recap:
- I burned an Mavrick Alpha 2 CD.
- booted from the CD
- for the installation I choose an USB-Stick as the installation partition
- installation was successful
- rebooting without the USB Stick failed
Even worse: the /boot
Opps sorry I was mislead! /boot was not wiped!
The boot partition wasn't mounted when I was recovering... so the
situation is the same as before. (My bad.)
Grub2 merely gets installed on the wrong device.
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
Another update... I just tried checking the installer on my other laptop
(Dell Vostro V13); the hard drive neatly comes up as sda. However, on my
VAIO, the hard drive still shows up as sdb and the flash drive as sda. I
guess the VAIO is interpreting the flash drive differently, and I don't
really
Is there anybody out there? (Pink Floyd, The Wall)
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Okay... just tried the alternate installer, and the problem persists. I
believe it is easily reproduced - just create a USB installer using USB
startup disk creator; boot up the machine with the USB drive, and the
USB drive shows up as /dev/sda, with the main hard drive as /dev/sdb. I
think it is
okay... I think the issue might be more subtle. I tried installing lucid
again via usb, hoping to be able to select the correct drive in the
advanced options in the installation procedure... what I instead find is
that when in livecd mode, gparted reveals my usb drive as /dev/sda,
which I believe
I have so far installed karmic, along with grub2, on three computers,
and reinstalled on two, and have not had this problem there - just with
lucid. Maybe the nomination for karmic should be declined? Also, any
workarounds for this during the installation itself? I feel extreme
inertia in trying
Any ideas about this? I believe grub2 should exclude the installation
media from the menu or its installation - because the user would
normally not want that anyway. It should not be writing itself to the
installation media (With it having become more feasible to boot from a
USB key, I believe
I was plagued by this bug as well while installing Lucid from a Live USB
- after the install when I rebooted with the USB key removed, the
machine gave me an error `error: symbol grub_puts_ not found' and
dropped me into grub-rescue mode. Seeking to fix grub from the Live USB,
I rebooted with the
I upgraded to Lucid from Karmic and now I can't boot into Windows 7. I
get a blinking cursor.
I did a fresh install of Lucid, back to Karmic, and back to Lucid with
no luck.
I tried reinstalling Grub2. Then, I used my Windows 7 disk to get to a command
prompt to run:
BootRec.exe /FixBoot
From my post on ubuntuforums.org:
http://ubuntuforums.org/showthread.php?t=1466038
Quote:
Originally Posted by Lazy-buntu
When I upgraded to 10.04 it said something like install grub on every partition
if you're not sure where to install it. I did on every partition on sda, but
most failed.
Also affected: HP Proliant DL140, which has two Bays for SATA drives
connected to a LSI Logic Raid Controller.
10.04 64bit Server Beta1, Beta2 and Release Candidate all behave the same when
trying to install from USB stick.
Last binary I tried, downloaded a few hours ago:
I can confirm that installing from CD to an external USB drive/stick
still overwrites the MBR of the internal drive on Lucid Beta2.
Possibly related reports:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/45989
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/46520
--
** Tags added: lucid
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
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
I just spent a long frustrating day messing with this problem. Windows
Recovery Console finally rescued me, by re-writing my MBR. Ubuntu sure
didn't do much to help. This needs to be fixed right away. This is not
acceptable.
--
[karmic] grub re-writes boot sector on wrong drive on fresh
Grub2 also ignores request to not install boot loader.
I installed lucid 10.04 beta 1 to external USB (/sdb). Selected 'Advanced' and
deselected 'Install boot loader' (as I use grub2 with my karmic install to boot
into lucid). It prompted me - are you sure etc...
It then installed a boot loader
For the love of god, please fix this critical defect! There's been
ample discussion in this thread on why this feature is very, very bad.
Functionality that used to just work should not suddenly, arbitrarily,
and *irrationally* change. I've been putting Ubuntu on flash drives for
years.
When installing ubuntu I had a second hfs+ mac formatted drive installed
in my tower. Guess what? GRUB defaulted to this drive which I have not
found a way to recover. Aka massive data loss. GRUB should default to
the disk you are installing to or have a clear warning message directing
users to
I'm new to ubuntu 9.10. I have used windows XP for years. Recently, my
wife purchased a new HP laptop. It has windows 7 installed. I hate
windows 7, and got the bright Idea to download Ubuntu 9.10 64 bit
version to CD and install on a 32GB USB flash drive. The install went
okay. When I decided to
After many successful 32 bit Karmic installs from a live usb stick to usb
sticks and usb hard disks, I installed a 64bit Karmic from a CDROM (to a usb
stick) and clicking on the Advanced button, noticed the difference in the use
of (hd0) for the boot location instead of an actual device (e.g.
This got me too. Some how the initial installation (9.10 I think?) went
OK, perhaps because it was using grub1 but an upgrade to grub 2 post
installation was not successful in finding my Windows partition (which
was working well with grub1), and now I am having trouble getting that
drive to mount
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Incomplete
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hello grazanel, if you believe this information in this ticket to be
incomplete, could you please explain why?
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Confirmed
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You
** Summary changed:
- [karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu
install
+ [karmic] grub re-writes boot sector on wrong drive on fresh install
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Critical
--
[karmic] grub re-writes boot sector on wrong drive
29 matches
Mail list logo
