Q: XSAN VOLUME WILL NOT START

I am hoping that someone can help with the following problem. Our xsan volume was running fine until we had an unexpected power outage on Friday night. When the power came back on our volume would not restart. running cvfsck gives the following information...

mdcmaster:~ admin$ sudo cvfsck
Password:
Xsan File Systems on host mdcmaster.itvplc.ads:

1) XSAN1

Choose a file system by number (1-1) or zero (0) to exit -> 1


Created directory /tmp/cvfsck2110a for temporary files.
Creating MetadataAndJournal allocation check file.
Creating Data allocation check file.

** NOTE ** Read Only Check.
File system journal will not be recovered.
The results may be inconsistent and mis-leading.


Super Block information.
FS Created On : Thu Jan 1 01:00:00 1970
Inode Version : '0.0'
File System Status : Clean
Allocated Inodes : 0
Free Inodes : 0
FL Blocks : 0
Next Inode Chunk : 0x0
Metadump Seqno : 0
Restore Journal Seqno : 0

Fatal: Super Block - Inode Version of 0x0 is wrong! Should be { 0x203,0x204,0x205 }
Stripe Group MetadataAndJournal ( 0) 0x746f60 blocks.
Stripe Group Data ( 1) 0x82fe5a0 blocks.

Building Inode Index Database 13312 (???%).
Error: buildinodes: Corrupted IEL block/0x8ad Repairing.
Building Inode Index Database 22528 (???%).
Error: buildinodes: Corrupted IEL block/0xa08 Repairing.

Error: buildinodes: Corrupted inode 0x282180 (Bad Marker(s)).

Error: buildinodes: Corrupted inode 0x282181 (Bad Marker(s)).

Error: buildinodes: Corrupted inode 0x282182 (Bad Marker(s)).

Error: buildinodes: Corrupted inode 0x282183 (Bad Marker(s)).
Building Inode Index Database 70656 (???%).
Error: buildinodes: Corrupted IEL block/0x10ad Repairing.
Building Inode Index Database 81920 (100%).
Super Block - Number of Inodes of 0x0 is wrong! Should be 0x14000.
Super Block - Next Inode Chunk of 0x0 is wrong! Should be 0x11a0.

Verifying Free List Extents.
Super Block - Free List Size of 0x0 is wrong! Should be 0xe.

Scanning inodes Segmentation fault
mdcmaster:~ admin$

If anyone could help with what may be the cause of this it would be greatly appreciated.

Thanks in advance,

Richard