Description of Problem:
In using fdisk to set up partitions, I found that disk druid had problems
with finding partitions afterword.
I was trying out the fdisk option because the Beta3 grub had problems with
the autopartition'd layout. So I removed all the partitions and set them up
like they would be in the 'old days'...
/dev/hdb1 -> /boot
/dev/hdb2 -> extended partition
/dev/hdb5 -> /
/dev/hdb6 -> /home
/dev/hdb7 -> /usr/local
/dev/hdb8 -> <swap>
The first problem was what I would call a UI mis-information... I would
select a partition created but could not edit it until I selected
'reformat' the partition. The text area where I would normally enter / or
whatever did not seem to be grayed out and it took a bit of fiddling to
figure out what needed to be done so I could put a partition there.
I also ran into this problem on an install where I had already put the beta
on the system and just wanted to re-install.
The second problem was a bit more severe, but similar. I tried to go onto
the next stage, but the installer could not find a SWAP partition. It was
clearly marked, but it took a bit of fiddling with the UI of telling it to
reformat the swap partition as a swap partition to get it to work.
Still trying to figure out why auto-partition and GRUB didnt work (/boot
was under 1024 this time).
This defect is considered SHOULD-FIX for Fairfax.
For the next release we plan on changing the UI to better indicate this. The
problem you hit is the 'Type' column is overloaded at the momemnt. If there is a
valid filesystem on the partition, we display its type. If there is no
filesystem, we display the partition type code on the partition.
I will see if there is something I will do that won't break translations or
screenshots for the current release.
Very similar to bug 51637.
requires changes to parted scheduled for 1.5 development cycle. When
verify-probed-fs-with-open is done we'll be in good shape.
We made some changes in RC1 that I beleive address these issues.