Comment 22 for bug 282756

I'm thinking this has something to do with the "cciss" driver being used.

Linux is detecting the drive fine. But as Steve mentions, in the syslog you can see where you see:

Mar 4 20:58:53 ubuntu ubiquity: tune2fs: Bad magic number in super-block while trying to open /dev/cciss/c0d0^M
Mar 4 20:58:53 ubuntu ubiquity: Couldn't find valid filesystem superblock.
Mar 4 20:58:53 ubuntu partman: Error running 'tune2fs -l /dev/cciss/c0d0'
Mar 4 20:58:53 ubuntu ubiquity: tune2fs
Mar 4 20:58:53 ubuntu ubiquity: :
Mar 4 20:58:53 ubuntu ubiquity: Bad magic number in super-block
Mar 4 20:58:53 ubuntu ubiquity:
Mar 4 20:58:53 ubuntu ubiquity: while trying to open /dev/cciss/c0d0
Mar 4 20:58:53 ubuntu ubiquity: ^M
Mar 4 20:58:53 ubuntu ubiquity: Couldn't find valid filesystem superblock.
Mar 4 20:58:54 ubuntu partman: Error running 'tune2fs -l /dev/cciss/c0d0'
Mar 4 20:58:54 ubuntu ubiquity[5609]: debconffilter_done: Partman (current: Partman)
Mar 4 20:58:54 ubuntu ubiquity[5609]: dbfilter_handle_status: ('Partman', 141)

@Bryan
    Do you have other machines that use the "cciss" driver for the disk controller? Can you attempt to try an install with the latested dated build on one of those?