On 27/11/12 12:26, Jeremy Visser wrote:
I just upgraded it to Ubuntu 12.04 using the GUI dist-upgrade tool, and
it overwrote the unique TrueCrypt MBR, rendering the Windows 7
installation useless.
And just so Google doesn't forever remember me as the idiot who upgraded
without backups, this
I'm running a laptop dual-booting Windows 7 with TrueCrypt (thus
TrueCrypt MBR) and Ubuntu 10.04.
I just upgraded it to Ubuntu 12.04 using the GUI dist-upgrade tool, and
it overwrote the unique TrueCrypt MBR, rendering the Windows 7
installation useless. I don't have the recovery disc, so all my
As the previous comment indicated, grub checks to make sure the drives
are the same that were selected before, and if not, prompts again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495423
Title:
On 19/11/2012 02:07, Phillip Susi wrote:
As the previous comment indicated, grub checks to make sure the drives
are the same that were selected before, and if not, prompts again.
I was thinking more along the lines of linking to Debian changelog
entries and specifying the actual package
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495423
Title:
update to grub-pc writes MBR without checks, prompt or backup
To
Not intending to troll, but...
On 18/11/2012 15:30, Phillip Susi wrote:
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Fix Released
[citation needed]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded grub on a VM which I had snapshotted - apparently, this
changes the disk ID.
This was on Precise Server. I was prompted for which drive to reinstall
grub to, which is pretty much the desired result - grub is not
installing itself to a disk it hasn't seen before.
Can I infer this has
Collin, couldn't debconf store the md5sum of the MBR ( after zeroing out
the partition table ), and on upgrade, verify that it still matches, or
prompt for confirmation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
During the installer grub can be installed onto a partition instead of
MBR, however during updates it ignores this installation option and
overwrites the MBR? There should be a GRUB_DEVICE setting saved
somewhere and checked by the grub update script otherwise having the
option in the installer
** Tags added: grub2 mbr trucrypt update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495423
Title:
update to grub-pc writes MBR without checks, prompt or backup
To manage notifications about
Is there a way to get this prioritized? Come on guys... wiping out MBR
without asking...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495423
Title:
update to grub-pc writes MBR without checks,
I can confirm this bug (looks more like plain stupidity than a bug) and
it affected me badly.
Never ever update of anything should touch MBR or 'autoidiotically' change
vital system areas
unless explicitly told to do so by admin.
Would it be easier to detect other bootloaders?
No. No one can
kubuntu 11.04 beta2
1. installed windows
2. installed kubuntu 11.04 and encrypted
3. encrypted windows using pgp
everything was fine until grub2 update kicked in and overwrote mbr, so
now I cannot see windows encrypted partition anymore in grub2, this is
easy to fix, but the problem that pgp also
Would it be easier to detect other bootloaders?
I would guess that most common suspects do not change frequently ; AFAIK
Windows never updates the MBR automatically after installation.
There may be some characteristics of the various encrypted partition
bootloaders that can also be readily
Same issue affected my, already filled a duplicate bug as I did not see
this one. Details are:
Hard drive has the following partitions-
SDA1 FAT 16 Dell recover partition
SDA 2 NTFS windows recovery partition
SDA3 window (truecrypt encrypted system drive)
SDA4 Extended
SDA5 EXT4 Ubuntu 10.04
Colin,
There's no reliable way to tell whether GRUB is installed in an MBR or not-
This seems unlikely. I am sure a best Guess could be made, at which point a
confirmation question could be asked.
About asking for confirmation each time- Yes I can see this may cause
problems
Abut creating a
On Fri, Feb 04, 2011 at 12:36:31PM -, Ronan Mooney wrote:
There's no reliable way to tell whether GRUB is installed in an MBR or
not-
This seems unlikely. I am sure a best Guess could be made, at which
point a confirmation question could be asked.
Unlikely or not, it's my assessment that
Thanks Colin, That does make perfect sense.
So it seems like the only, and easiest solution is for the grub update
script to create a copy of the MBR before it is overwritten, and for
instructions regarding moving the grub install to remind people to run
sudo dpkg-reconfigure grub-pc
--
You
Hello,
This very same issue affected me January 1st 2011.
My setup is:
- a laptop with HDA encrypted using SafeBoot (require a SafeBoot MBR to work)
- Ubuntu 10.04 LTS 64-bit version on an external USB disk (this becomes
HDB/SDB)
Selecting using BIOS boot menu whether to boot using
Almost the same sequence of events as in the bug description happended
to me on the evening of 15th December 2009.
In my case it was a USB flash memory containing Ubuntu 9.10 Karmic and
not a HDD, but I assume that has no significance.
The bug has had a critical impact for me since it was
And I right in saying that the device that grub boots is identified by
UUID and the device that it installs grub to is identified by a path in
/dev ?
--
update to grub-pc writes MBR without checks, prompt or backup
https://bugs.launchpad.net/bugs/495423
You received this bug notification
Am Montag, den 14.12.2009, 22:16 + schrieb Adrian Wilkins:
And I right in saying that the device that grub boots is identified by
UUID and the device that it installs grub to is identified by a path
in
/dev ?
The GRUB device which gets used during boot is only searched with UUID
if you
22 matches
Mail list logo
