The problem is that parted treats local files (as used by vmbuilder)
differently from "actual" disk files, and changes the sector size
accordingly (without an option to change it). As a result, the partition
start locations are too small for grub2 to install. I had originally
reproduced this by using vmbuilder to install Ubuntu, and then
attempting to update to grub2, which would fail, since there wasn't
enough room.
My previously attached hack/work-around for vmbuilder was to skip a
sector when building the first partition.
** Changed in: parted (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/556167
Title:
vmbuilder uses parted to create disk images, which leads to broken
sector counts (cannot use grub2 on disk images created by
vmbuilder/parted)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/556167/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
