Comment 27 for bug 573477

I know that this bug doesnt exist with 10.04.1 with an array constructed in 10.04.1 using mdadm.

I gave up on this bug as it wasnt a show stopper (server was rarely rebooted), but have made some observations during the new build that might shed some light on this. I used the palimpest disk utility to construct my array and Im 99% sure I did previously too, though this time I noticed some quirks, like the utility being unable to expand an array built by mdadm or the disk utility (saying the device wasnt big enough to add, but it is identical to the other drives.), mdadm unable to assesmble a array made by the disk utility while the disk utility was able to and on boot the disk utility has the array as started but degraded (stopping/starting the array fixes this). The array would work store data and mount without issue if constructed and stopped/started using the disk utility.

This got me thinking that maybe this was somehow related to the issues I was having previously. Anyone else assemble their arrays with the disk utility? Just putting it out there....