Nevermind, after looking at the cfdisk code it seems that it needs a
major rewrite to handle out of order partitions.
** Changed in: util-linux (Ubuntu)
Status: In Progress => Triaged
** Changed in: util-linux (Ubuntu)
Assignee: Phillip Susi (psusi) => (unassigned)
--
You received
Triaged > Confirmed. I'm actually working on removing the offending
code though, so marking as in progress.
** Changed in: util-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: util-linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: util-linux (Ubuntu)
Ass
Phillip Susi writes ("[Bug 107023] Re: cfdisk complains about auto-resize
generated setup"):
> This is easy to reproduce by simply creating two logical partitions out
> of order. This is an error in cfdisk not parted.
>
> ** Changed in: parted (Ubuntu)
>Stat
This is easy to reproduce by simply creating two logical partitions out
of order. This is an error in cfdisk not parted.
** Changed in: parted (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
So (c)fdisk complains that the partitions are not in order? I'd say
that's their bug; there's nothing wrong with them not being in natural
order.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/107023
In my case using gparted to resize a partition within the extended
partition caused the problem.
dpkg -p gparted | grep Version
Version: 0.4.5-2
I suggest:
fixed it up with booting from a live-cd and using a usb-key.
sfdisk -d /dev/hda>hda.out
where hda.out is in on my usb key.
then
sfdisk /de
Still present in hardy/jaunty -- I recently installed Hardy on my box,
which contained an existing Jaunty installation. (Bug #333584
#https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/333584 stopped
me installing Intrepid, so I had to install Hardy). After I had done,
the partition table co
Contains detailed (albeit inconclusive) diagnosis by a developer. Do not
close.
** Changed in: parted (Ubuntu)
Status: Invalid => Triaged
** Changed in: util-linux (Ubuntu)
Status: Invalid => Triaged
--
cfdisk complains about auto-resize generated setup
https://bugs.launchpad.net/
Feisty is not supported anymore.
** Changed in: parted (Ubuntu)
Status: New => Invalid
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
cfdisk complains about auto-resize generated setup
https://bugs.launchpad.net/bugs/107023
You received this bug notification because
** Tags added: iso-testing
--
cfdisk complains about auto-resize generated setup
https://bugs.launchpad.net/bugs/107023
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
This is the sanity check in cfdisk that's being tripped:
for (i = 0; i < num_parts && p_info[i].last_sector < first; i++);
if (i < num_parts && p_info[i].id != FREE_SPACE) {
if (last < p_info[i].first_sector)
*errmsg = _("logical partitions not in disk order");
Partitions not being in disk order seems like an intrinsic property of
resizing a big partition near the start and adding multiple partitions
in the middle, unless you think it's a good idea to renumber existing
partitions. I'm therefore not concerned about the fdisk error.
I'm not sure what the c
** Attachment added: "typescript"
http://librarian.launchpad.net/7336737/typescript
--
cfdisk complains about auto-resize generated setup
https://bugs.launchpad.net/bugs/107023
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
13 matches
Mail list logo
