I can confirm this issue as well, on a Dell PowerEdge R210 with two 500GB drives.
Device Model: WDC WD5002ABYS-18B1B0
Serial Number: WD-WCASYC640636
Firmware Version: 02.03B04
User Capacity: 500,107,862,016 bytes
Device Model: WDC WD5002ABYS-18B1B0
Serial Number: WD-WCASYC631505
Firmware Version: 02.03B04
User Capacity: 500,107,862,016 bytes
The boot problem was the same (dumped to initramfs prompt on reboot after install). I found the same cylinder 60802 anomaly with the partition tables when I used the installer's partitioner to create them.
My partitions consisted of a 484GB main partition (marked bootable) and a 16GB swap partition on each disk, all set to type FD (Linux RAID autodetect) and added to /dev/md0 and /dev/md1 respectively. md0 was then formatted ext4 and mounted to /, and md1 was set to swap.
To workaround the issue, I created my partitions with fdisk instead (alt-switched to another tty during partitioning step) and then created my RAID sets in the installer's partitioner. As a result I could still create partitions that filled the whole drive. This worked and the system now boots properly.
I can confirm this issue as well, on a Dell PowerEdge R210 with two 500GB drives.
Device Model: WDC WD5002ABYS-18B1B0
Serial Number: WD-WCASYC640636
Firmware Version: 02.03B04
User Capacity: 500,107,862,016 bytes
Device Model: WDC WD5002ABYS-18B1B0
Serial Number: WD-WCASYC631505
Firmware Version: 02.03B04
User Capacity: 500,107,862,016 bytes
The boot problem was the same (dumped to initramfs prompt on reboot after install). I found the same cylinder 60802 anomaly with the partition tables when I used the installer's partitioner to create them.
My partitions consisted of a 484GB main partition (marked bootable) and a 16GB swap partition on each disk, all set to type FD (Linux RAID autodetect) and added to /dev/md0 and /dev/md1 respectively. md0 was then formatted ext4 and mounted to /, and md1 was set to swap.
To workaround the issue, I created my partitions with fdisk instead (alt-switched to another tty during partitioning step) and then created my RAID sets in the installer's partitioner. As a result I could still create partitions that filled the whole drive. This worked and the system now boots properly.
My partition table looks like this:
root@belair- auto2:/ # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b35fa
Device Boot Start End Blocks Id System
/dev/sda1 * 1 58843 472654848 fd Linux raid autodetect
/dev/sda2 58843 60801 15728160+ fd Linux raid autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c1204
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 58843 472654848 fd Linux raid autodetect
/dev/sdb2 58843 60801 15728160+ fd Linux raid autodetect
(kweichel...md devices snipped)