CentOS 5 :: Regular Procedure After Power Failiure And Fsck Forced?

I had a server with CentOS 5.5 and Asterisk fail today most likely due to the power failure. I guess the stupid electrician turned the power ON and OFF multiple times while changing the burned out fuse without unplugging the PBX. It was set in CMOS to power back on when there is power outage so my two HDDs which were set in RAID-1 now shot.

Trying to start the system and it goes through some check and fixes and then tells me to do Ctrl+D or enter password and run fsck. I have tried both methods and I don't think they yeild anything.

Ctrl+D reboots and same store again with the system fixing and asking me to Ctrl+D again. Putting the password and doing "fsck -y" gives many errors and it fixes it and then it just keeps looping. I am afraid this is making it worst than better. So, after few loops I did few more restarts and just give up. Took out the HDDs and installed new ones and install CentOS+Asterisk so business runs as usual on Monday.

However, I am kind f*ked if I don't get the files out of these HDDs. This is my first time using fsck and also encountering this type of a problem. What is the normal procedure when fixing inodes misplaced in a case like this? and what should I do to at least be able to grab my files?

I have already connected one of the drives to Windows and used Disk Internals (which maps Linux drives) but I see only folders with no contents except for /tmp/ which has contents. While the HDDs were in the system I could actually browse files and they were fine. I am really keen to get the drives fixed but I am also afraid that bad usage of fsck might replace lots of files and burn it all.