| 2010-04-23 21:26:50 |
vadim |
bug |
|
|
added bug |
| 2010-04-24 07:25:25 |
vadim |
attachment added |
|
Diagrammatic representation of changes http://launchpadlibrarian.net/45151517/diagram.png |
|
| 2010-04-25 11:31:43 |
vadim |
description |
Binary package hint: ubiquity
Disk is partitioned as follows using Microsoft DiskPart version 6.1.7600
Primary1
Primary2
Primary3
Logical1
Logical2
Logical3
Logical4
DiskPart creates MBR and EBR tables padded with hidden sectors and uses 2048 sectors in total (in contrast to the traditional 63)
http://www.multibooters.co.uk/partitions.html
Ubuntu install:
During install 'specify partitions manually' is chosen.
Partition Logical2 is changed: Ext4, format the partition, mount point /
No other changes are made.
At some point during installation the following changes are made to the partition tables:
The EBR table preceding Logical1 is moved forward 2046 sectors toward the end of the hidden sectors created by DiskPart.
The MBR is updated accordingly to reflect the new offset of the table and the reduced extended partition size (2046 sectors smaller).
The EBR tables for Logical1 (now moved) Logical2 and Logical3 are changed to reflect the new offsets (reduced by 2046 sectors) of their proceeding respective extended partitions caused by moving the first EBR.
Why does this happen? Ubuntu was not instructed to make changes to my partition tables. It was instructions only to format a partition (it did not even have to change the partition ID).
More to the point why the hell does this happen at all? There should be no reason to move the EBR table around like that!
How can I stop this happening in the future? |
Binary package hint: ubiquity
Disk is partitioned as follows using Microsoft DiskPart version 6.1.7600
Primary1
Primary2
Primary3
Logical1
Logical2
Logical3
Logical4
DiskPart creates MBR and EBR tables padded with hidden sectors and uses 2048 sectors in total (in contrast to the traditional 63)
http://www.multibooters.co.uk/partitions.html
Ubuntu install:
During install 'specify partitions manually' is chosen.
Partition Logical2 is changed: Ext4, format the partition, mount point /
No other changes are made.
At some point during installation the following changes are made to the partition tables:
The EBR table preceding Logical1 is moved forward 2046 sectors toward the end of the hidden sectors created by DiskPart.
The MBR is updated accordingly to reflect the new offset of the table and the reduced extended partition size (2046 sectors smaller).
The EBR tables for Logical1 (now moved) Logical2 and Logical3 are changed to reflect the new offsets (reduced by 2046 sectors) of their proceeding respective extended partitions caused by moving the first EBR.
Behaviour does not occur if Logical2 contains and existing Ext4 filesystem. If Logical2 is filled with zeros then the EBR is moved.
Why does this happen? Ubuntu was not instructed to make changes to my partition tables. It was instructions only to format a partition (it did not even have to change the partition ID).
More to the point why the hell does this happen at all? There should be no reason to move the EBR table around like that! |
|
| 2010-04-25 11:41:59 |
vadim |
description |
Binary package hint: ubiquity
Disk is partitioned as follows using Microsoft DiskPart version 6.1.7600
Primary1
Primary2
Primary3
Logical1
Logical2
Logical3
Logical4
DiskPart creates MBR and EBR tables padded with hidden sectors and uses 2048 sectors in total (in contrast to the traditional 63)
http://www.multibooters.co.uk/partitions.html
Ubuntu install:
During install 'specify partitions manually' is chosen.
Partition Logical2 is changed: Ext4, format the partition, mount point /
No other changes are made.
At some point during installation the following changes are made to the partition tables:
The EBR table preceding Logical1 is moved forward 2046 sectors toward the end of the hidden sectors created by DiskPart.
The MBR is updated accordingly to reflect the new offset of the table and the reduced extended partition size (2046 sectors smaller).
The EBR tables for Logical1 (now moved) Logical2 and Logical3 are changed to reflect the new offsets (reduced by 2046 sectors) of their proceeding respective extended partitions caused by moving the first EBR.
Behaviour does not occur if Logical2 contains and existing Ext4 filesystem. If Logical2 is filled with zeros then the EBR is moved.
Why does this happen? Ubuntu was not instructed to make changes to my partition tables. It was instructions only to format a partition (it did not even have to change the partition ID).
More to the point why the hell does this happen at all? There should be no reason to move the EBR table around like that! |
Binary package hint: ubiquity
Disk is partitioned as follows using Microsoft DiskPart version 6.1.7600
Primary1
Primary2
Primary3
Logical1
Logical2
Logical3
Logical4
DiskPart creates MBR and EBR tables padded with hidden sectors and uses 2048 sectors in total (in contrast to the traditional 63)
http://www.multibooters.co.uk/partitions.html
Ubuntu install:
During install 'specify partitions manually' is chosen.
Partition Logical2 is changed: Ext4, format the partition, mount point /
No other changes are made.
At some point during installation the following changes are made to the partition tables:
The EBR table preceding Logical1 is moved forward 2046 sectors toward the end of the hidden sectors created by DiskPart.
The MBR is updated accordingly to reflect the new offset of the table and the reduced extended partition size (2046 sectors smaller).
The EBR tables for Logical1 (now moved) Logical2 and Logical3 are changed to reflect the new offsets (reduced by 2046 sectors) of their proceeding respective extended partitions caused by moving the first EBR.
Behaviour does not occur if Logical2 contains and existing Ext4 filesystem. If Logical2 is filled with zeros then the EBR is moved.
Why does this happen? Ubuntu was not instructed to make changes to my partition tables. It was instructions only to format a partition (it did not even have to change the partition ID).
More to the point why the hell does this happen at all? There should be no reason to move the EBR table around like that!
Probably related to this:
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/342485 |
|
| 2010-04-25 16:17:15 |
vadim |
ubiquity (Ubuntu): status |
New |
Confirmed |
|
| 2010-04-25 17:16:56 |
vadim |
bug task added |
|
debian-installer (Ubuntu) |
|
| 2010-04-25 17:31:30 |
vadim |
summary |
extended boot record tables MOVED and modified when no partition changes are requested |
if an extended partition contains unallocated space before the first logical partition, the start of the extended partition is moved to start of first logical partition [first EBR is MOVED and affected MBR and EBR tables updated when no such partition changes are requested] (present in both GUI and text installers) |
|
| 2010-04-26 17:04:30 |
vadim |
bug task added |
|
partman-base (Ubuntu) |
|
| 2010-10-13 15:05:08 |
Marcos Felipe Mello |
removed subscriber Marcos Felipe Mello |
|
|
|
| 2014-12-19 06:24:11 |
Robert Blair |
bug |
|
|
added subscriber Robert Blair |
| 2020-03-05 12:05:12 |
Marcus Tomlinson |
ubiquity (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2020-05-06 12:15:50 |
Marcus Tomlinson |
ubiquity (Ubuntu): status |
Incomplete |
Invalid |
|
