XRAID will not mount (journal corruption)

Question

Hi guys, I have seen in the unanswered archived article below someone with exactly my problems, really looking for a solution to repair the journal within OS X, any ideas or developments on this?
http://discussions.apple.com/thread.jspa?threadID=374802
[QUOTED HERE FOR CONVENIANCE]
Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
[/QUOTE]

Answer 1

I was using RAID mirroring two SCSI drives under 10.3 Server (not an XRAID) and found that one of the two drives was slow to spin up. The System considered the array "degraded" and made the single "good" drive available. Nothing that made any sense to me could get the "slow" drive repaired or re-incorporated into the pair. I could not split the pair for repair, and even after it was spun up and ready, Disk utility refused to repair it or its acceptable partner.
What I eventually did, with some coaching from the forums and re-reading of Mac Help, was to delete the errant drive from the set. Then I could erase it as a single drive, and add it back into the set as a "new" replacement drive. The system accepted it as a replacement, and brought it up-to-date with its partner automatically.
I have got to say that I find this approach completely counter-intuitive. It gives me the creeps to delete the "safety-net" drive, even if I know it is mucked up.
But perhaps a similar approach would work in your situation.