Mac Pro Slow Shutting down Disk Ut says needs repair

Question

Hi hope someone can help,
My mac pro has been taking a long time to shut down recently and this morning when i booted up all i had was a black screen with my mouse pointer (really weird).
I used Disk Utility to "verify disk" and it said that repairs were necessary. Here's the log:
Aug 24 08:31:55: Disk Utility started.
Verifying volume “Aygies Raid”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file PACESupport.plist
(It should be 0 instead of 1)
cking multi-linked files.",0)
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
@ needs to be repaired.",1)
Aygies Raid
Error: The underlying task reported failure on exit
Disk Utility stopped verifying “Aygies Raid” because the following error was encountered:
The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
I have a clone of my drive on an external drive so i booted from that i tried to repair permissions on mac pros drives but it said repairs weren't needed, Log:
Verifying volume “Aygies Raid”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume Aygies Raid appears to be OK.
Mounting Disk
1 HFS volume checked
Volume passed verification
But then i booted from the mac pro again and it said that it needs repair! I used disk warriour and this is its log:
DiskWarrior scanned the disk named "Aygies Raid" checking all files and folders for damage and potential
compatibility problems.
Permissions:
Started verify/repair permissions on disk disk2 Aygies Raid
Determining correct file permissions.
The privileges have been verified or repaired on the selected volume
Verify/repair finished permissions on disk disk2 Aygies Raid
Disk: "Aygies Raid"
The Property List data was checked in 17,785 files.
The Resource Data was checked in 9,721 files.
The maximum Folder Depth on this disk is 17. This does not exceed the maximum recommended depth.
The System Symbolic Link Files were checked and no problems were found.
Location: "Desktop"
File: ".a23t.obdev.LSD.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character
at line 1
Old-style plist parser error:
Unexpected character '0x4' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.SysternatemsCorporation.StudioExcellence.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.EtworataCorporation.Zonesys.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.AppersEurope.Sickle.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.Roverbetter.Eclecticism.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.Hostcyte.Craziness.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
Explanations:
Folder Depth: This number indicates how many folders are nested inside each other. If a disk contains only three
folders and Folder A is inside Folder B and Folder B is inside Folder C, then this disk has a maximum folder depth of
three. Folders nested too deeply can cause software compatibility problems.
Property List: This is a standard file format for storing data and is often used to store preferences. The names of
these files normally end with a .plist file extension. Corrupt property list files can cause system instability.
Resource Data: This is an older file format for storing data and was often used to store preferences. The names of
these files normally end with a .rsrc file extension. Corrupt resource data files can cause system instability.
System Symbolic Link Files: These are files used by the operating system that are similar to aliases. If these files are
damaged it may prevent startup or cause system instability.
Time: 24/8/07 08:44:56
DiskWarrior Version: 4.0
Went back to Disk utility and now it says that my hard drive doesn't need repair! whats going on! can anyone help?!
Thank you

Answer 1

Two things off the top:
128MB are GUID partitions that are not user volumes.
There is also a 200MB EFI partition as well.
Drive Genius needs to get their program updated.
You need to work from an "emergency" boot drive to repair your boot drive, RAID or no. I hope you are and not from CD or DVDs.
Forget about Permissions. They are very minor. They only have to do with ownership and security and based on what is in
/Library/Receipts
Trying to verify? all you want to do is repair and rebuild.
If you ran DU and DW and did repair and rebuild and WROTE NEW DIRECTORY and the problem remains, erase and restore, or...
+I am useless with RAID and have no idea...+
Don't use it except to test, learn, experiment with. But not for system drive.
Above I asked, "are these a matched pair of drives" ie, same make, (looks like same size), vendor, model? they should be. Less chance of trouble if nothing else.
ON the boot volume, do a Get Info when you click on the drive, look for "Ignore Ownership on this Volume" and make sure it is NOT CHECKED. It can't be to repair permissions and be bootable.
The underlying cause of disk errors may be marginal or bad RAM. Test those FBDIMMs. Run Apple Hardware Test and Memtest (even Microsoft uses Memtest for Vista).
Drives rarely break. Systems do. Directory and btree catalogue and volume information blocks do.