[Bug 379348] Re: Installing next to Windows places Linux beyond 137GB and makes system unbootable (grub error 18).

[Phillip Susi]

This should no longer be an issue since grub2 handles booting beyond 137
GB.


** Changed in: ubiquity (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/379348

Title:
  Installing next to Windows places Linux beyond 137GB and makes system
  unbootable (grub error 18).

Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  I tried to install Ubuntu 9.04 (Jaunty) on my laptop, a Dell Precision
  M20.

  I was using a new 250GB drive, with Windows XP already installed.

  The installer detected the Windows install and offered to set up
  alongside Windows and even import the user settings - very nice touch
  there.

  Everything looked good until rebooting. Then, grub error 18. Not only
  can I not boot Linux, my previous Windows install is now also
  inaccessible. Indeed, as far as any non-expert knows, it is completely
  destroyed.

  This is *not* acceptable. The installer *must not ever* do this. The
  stories that circulate, after it happens to someone trying Linux out
  for the first time, do irreparable damage to the reputation of Ubuntu
  and of Linux in general. Bugs like this stop bug #1 from ever being
  fixed. They will not get reported, because the user now has no
  bootable system. Sure, they can run the live CD they just tried to
  install off. Are they likely to, now that it has just apparently nuked
  their machine?

  Now, I know and you know what the issue is. The kernel and grub data
  has been put beyond 137GB. If I go back and reinstall the whole thing,
  putting a /boot partition at the start of the disk, it'll work. I
  looked around: this bug gets reported all over the place, and always
  this workaround has been suggested in response and the matter then
  considered closed.

  If Ubuntu needs a /boot partition at the start of the disk then the
  installer should make one itself. If it can't do that because existing
  partitions are in the way, then it should explain the problem and must
  stop the installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/379348/+subscriptions