[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#278116: Seems to be a bug with libparted



I booted from Warty live CD (debian sid based distro) and the kernel (2.6) was able to detect
all partitions properly. I was able to mount all my partitions in -rw without
any problems.

Here is the partition table given by fdisk:

Disk /dev/hda: 10.2 GB, 10262568960 bytes
255 heads, 63 sectors/track, 1247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1         266     2136613+   b  W95 FAT32
/dev/hda2             269        1247     7863817+   f  W95 Ext'd (LBA)
/dev/hda3             267         268       16065    6  FAT16
/dev/hda5             269         892     5012248+   b  W95 FAT32
/dev/hda6             893        1247     2851506    b  W95 FAT32

Partition table entries are not in disk order

And this is the correct partition table

With parted however, I got this:

Disk geometry for /dev/hda: 0.000-9787.148 megabytes
Disk label type: loop
Minor    Start       End     Filesystem  Flags
1          0.000   9787.148  fat16

Which is incorrect.

Thus one can conclude that the problem with partman lies in libparted.
 
Also, when I used parted and selected /dev/hda1 (or any partitions for
that matter), I get this:

Disk geometry for /dev/hda1: 0.000-2086.536 megabytes
Disk label type: loop
Minor    Start       End     Filesystem  Flags
1          0.000   2086.536  fat32

If you refer to the partition table produced by fdisk (ie. the correct one), you
would know that /dev/hda1 is indeed a 2GB fat32 partition, so parted is having
no troubles detecting the size and type of the partition. Yet, it *did not* show
the boot flag on the partition.

Reply to: