And still happening in the current Lucid daily, reopening.

** Description changed:

  Binary package hint: ubiquity
  Version: 1.99.28
  LiveCD daily: 06-Oct-2009 08:18
  
  When installing through ubiquity the Volume Boot Record(s?) of extended
  partition(s?)  are wiped.
  
  I've taken a hit from this problem since on my main machine I have grub
  installed to the VBR of an extended partition. Then when installing
  karmic directly to a usb stick (specifically installing grub to the mbr
- of the usb) I then wiped the grub from my extended partition on the main
- hard disk.
+ of the usb) I then wiped the grub vbr from my extended partition on the
+ main hard disk.
  
  I have furthermore done some testing in a virtualbox with two virt
  harddrives, confirming that ubiquity (but not the grub2 tools) will mess
  up the extended partition(s?) whenever performing an install:
  
  Some notes on the testing:
  
  Installed jaunty inside extended partition on sda5 (swap to sda6), grub vbr 
installed to sda1 via ubiquity.
  grub setup to mbr using livecd.
  sudo grub
  root (hd0,4)
  setup (hd0)
  
  Install karmic to sdb1 (specifying no using swap on sda6), specifying
  bootloader to /dev/sdb, noting that last screen says partition table of
  both sda and sdb will be changed (!?)
  
  using sudo dd if=/dev/sda1 bs=512 count=1 | xxd
  I notice that what formerly was a grub VBR is now only a few odd bits that I 
guess is only for describing the extended partition
  
  I reinstalled grub-legacy to sda1 using jaunty:
  sudo grub
  root (hd0,4)
  setup (hd0,0)
  
  Ran commands:
  sudo grub-setup '(hd1)'
  grub-install /dev/sdb
  from karmic with no change to vbr of sda6
  
  boot livecd start ubiquity:
  Again installing to sdb1 but now leaving bootloader to install to default 
(hd0)
  Again the vbr of sda1 is wiped.

** Changed in: partman-basicmethods (Ubuntu)
       Status: Fix Released => Confirmed

-- 
ubiquity overwrites VBR of extended partition
https://bugs.launchpad.net/bugs/445067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to