The command that I used to create raid:

hpacucli ctrl sn=_SN_ADMON_ create type=ld drives=all raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192296
hpacucli ctrl sn=_SN_ADMON_ array A create type=ld raid=6 stripesize=128 size=1192292


The first time I ran this command I missed the final two lines, which cause some errors like this:

Disk /dev/cciss/c0d13: 1250.2 GB, 1250209521664 bytes
255 heads, 32 sectors/track, 299242 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Pay attention to its size. for my exp, *664 bytes isnt a valid value for this partition. when I use `fdisk -l`, I found that there are two more partitions missed, so I recreated the raid, after reboot, everything becomes ok now:

Disk /dev/cciss/c0d13: 1250.2 GB, 1250214018560 bytes
255 heads, 32 sectors/track, 299243 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes


so, It's highly sugguest that after you created raid, it's better to have a simple check by fdisk, and a reboot will be much helpful for your diag. you should fix the errors before you mkfs, otherwise, when you reboot your storage equipment, you may faced some wrong mapped partitions and some you data maybe mis-mapped!!