Repair superblock? RAID5 volume crash

Question

I have a fiber channel raid connected to my G5 Mac. Yesterday video and audio suddenly started dropping out on the volume. Audio was static and video would have all sorts of blocks and corruption.
This is the second time this has happened in the past few months. I am looking for advice on which component might be failing. It is RAID5 and the subsystem is reporting no disk errors. My thoughts are that the raids controller or maybe even the computers fiber channel card may be on its way out? The disk has since totally dropped off and can no longer be mounted.
I tried out a demo of data rescue to restore a few files and everything it returns is totally corrupt.
I will try out DiskWarrior next for rebuilding I suppose.
Any suggestions or advice would be appreciated.
Here's a bit of output from terminal:
edittheta$ /sbin/fsck_hfs -fdr /dev/rdisk3s2
** /dev/rdisk3s2
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
Journal replay returned error = 6
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
hfsUNswapBTNode: invalid node height (1)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
Missing thread record (id = 32965)
Invalid extent entry (4, 832)
Incorrect block count for file A017C013_0805Q7001.R3D
(It should be 2097152 instead of 256)
Incorrect number of thread records
(4, 176)
CheckCatalogBTree: fileCount = 19939, fileThread = 19956
** Checking multi-linked files.
** Checking Catalog hierarchy.
Missing thread record (id = 38125)
Invalid volume file count
(It should be 19934 instead of 19939)
** Checking Extended Attributes file.
Overlapped extent allocation (file 3 Extents Overflow BTree)
extentType=0x0, startBlock=0x2da35, blockCount=0x1400, attrName=(null)
** Checking volume bitmap.
Volume Bit Map needs minor repair
** Checking volume information.
Invalid volume free block count
(It should be 573459245 instead of 1830097600)
invalid VHB nextCatalogID
invalid VHB attributesFile.clumpSize
Volume Header needs minor repair
(2, 0)
Verify Status: VIStat = 0xa800, ABTStat = 0x0000 EBTStat = 0x0000
CBTStat = 0x0800 CatStat = 0x00004230
** Repairing volume.
DoMinorRepair: Repair for type=-510 failed (err=32).
** The volume Colossus could not be repaired.
volume type is pure HFS+
primary MDB is at block 0 0x00
alternate MDB is at block 0 0x00
primary VHB is at block 2 0x02
alternate VHB is at block 14642907054 0x368c907ae
sector size = 512 0x200
VolumeObject flags = 0x07
total sectors for volume = 14642907056 0x368c907b0
total sectors for embedded volume = 0 0x00

Answer 1

Just to follow up... ended up using DiskWarrior to attempt to rebuild the disk. DiskWarrior was able to rebuild the directory structure and get the drive to mount. It errored at the very end with some sort of error code though.
I can copy all the files off now though most appear to have all sorts of digital gunk on images, videos, ect... very strange. Solution for now is to backup and reformat... will update if discover what caused this odd file corruption. Sad that 4TB of data is rendered basically useless with absolutely no sign of failure prior.