Raid 5 migration lvm error

[Bedy]

I have been running a 3 * 750 gig Raid 5 system for some time on firmware 1.0.10 without much trouble. I began to run short of space and so tried to add another 2 750 gig drives.
I think i made an error and the drives were automaticly set to add as spare (i since read this can cause issues). I then tried to migrate the 3 drive system into a 5 drive Raid 5 system, the interface let me do this without any complaints.
I noticed after a few minutes the web interface stopped responding but as all the drives seemed to be active i let it continue realising it would take many hours to complete. After 24 hours there was still no web interface and the drives were no longer being accessed. The LCD screen reported 30 odd percent complete on the migration and after a few more hours of no activity and no progress i decided to reboot the system as i assumed it had crashed.
The system powered up with a Raid N/A message and that is how it has stayed. The boot log shows 3 drives being mounted and 2 as spares, then complains the lvm is corrupt (or something of that nature).
I emailed Thecus about this a month ago and still havent heard back from them.
I really dont want to start again with the array as this was my backup and some data is not replacable.
If anyone can help me access what is left of my files i would be most grateful.

[ikonia]

depends what version of the kernel your running on that firmware as to if you can expand raid 5 arrays. Bellow version 2.6.20 (I think from memory) you can't dynamiclly change the size, if you've got a meta device under LVM control acting as the PE for your volumes, then changing the size of that will mess up the volume.

For that you'd need to remove the raid re-create the device, re-pe-create and then re-create the volumes.

[Bedy]

Ok i dont know how to find that info, i wasnt using the SSH module and was unsure whether to installing afterwards (but i suppose it gets stored on the flash disk?).
What does the PE stand for?
If there is a known problem with migration why is it not listed in the manual or disallowed by the web interface, it would have been nice to know eh.
Anyway, this is the log from the device incase that helps anymore:
N5200 : Healthy: The system N5200 is healthy now.
N5200 : N5200 boot
N5200 : Healthy: The system N5200 is healthy now.
N5200 : Can't mount data lvm
N5200 : mdadm: /dev/md0 has been started with 3 drives and 2 spares.
N5200 : [Disk sde] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79]
N5200 : [Disk sdd] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79]
N5200 : [Disk sdc] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79]
N5200 : [Disk sdb] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79]
N5200 : [Disk sda] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79]
N5200 : Can't mount data lvm
N5200 : Assemble RAID from [ /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 ]
N5200 : mdadm: /dev/md0 has been started with 3 drives and 2 spares.
N5200 : [Disk sde] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79;Sun Jun 3 14:04:31 2007]
N5200 : Assemble RAID from [ /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 ]
N5200 : [Disk sdd] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79;Sun Jun 3 14:04:31 2007]
N5200 : [Disk sdc] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79;Sun Jun 3 14:04:31 2007]
N5200 : [Disk sdb] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79;Sun Jun 3 14:04:31 2007]
N5200 : [Disk sda] UUID[raid5;c5236298:b9feb03c:a2f26537:87e08b79;Sun Jun 3 14:04:31 2007]

[Thecus - Yvon]

Dear Sir,

Would you please mail to support@theucs.com again, and apologize for missing your mail......

Yvon