[Parted-maintainers] Bug#384653: bug with d-i parted and Sun disk labels

[Josip Rodin]

Hi,

I think I reproduced this the other day on my Fire v240.

Initially, the partitioner in d-i recognized all drives properly (which was
pretty cool to see!). But then, when I created a new disk label in order to
remove the old partitions (from Solaris), and went on to create a new one,
it only saw some 13 GB out of 36 total. This didn't bother me at the time
because I only wanted a 5 GB partition, but still, it was strange.

And later, after the system was installed, I went to create partitions on
another two 72 GB disks in the system, but only got 13 GB.

Then I went into fdisk, created a new Sun disk label, used the
custom+autodetect option, and pressed enter on almost all the options
(I only changed the RPM setting, but I don't see how that should have
affected the partition table), and now it seems fine, all ~72 GB are there.

One thing that struck me in fdisk was that I kept seeing the number of
8922 cylinders, both in the good and the bad result.

So now I checked the 36 GB disks again, and here it is:

% sudo fdisk -l /dev/sd{a,b} 

Disk /dev/sda (Sun disk label): 27 heads, 107 sectors, 4425 cylinders
Units = cylinders of 2889 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0      3380   4882410   83  Linux native
/dev/sda3             0      4427   6394801+   5  Whole disk

Disk /dev/sdb (Sun disk label): 27 heads, 107 sectors, 4425 cylinders
Units = cylinders of 2889 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sdb3             0     24618  35559877+   5  Whole disk

The disks are physically the same, but the special 3rd partition seems to
be broken on the first (the one where I created that 5GB partition).

Should I send over the first 512 bytes of both of those disks?

-- 
     2. That which causes joy or happiness.