On Nov 22, 2007, at 10:48 PM, SoftRAID support wrote:
Have you contacted SoftRAID as this would appear to be an issue
with
their kext.
He was in touch, and I had suggested deleting the kextcache and
mkext
cache files also. I don't think that worked, but Mike has not
been in
touch in a couple days.
I don't think this is a specific problem with our kext, but I have
passed this on to Tim Standing to investigate.
thanks dhan
Quite frankly I think he has a corrupt kext, probably from file
corruption -- most probably caused by his unclean shutdown. The
other possibility is he has silent file corruption, which of
course would be much worse.
But I'm fairly certain, from the indicators, that it's not a
kernel cache issue.
-dhan
I am the original poster, and I have to agree with Dan here. It
really felt to me as if this was a SoftRaid problem. I was forced
to restore from my backup and was down for about a day.
I didn't say it was a problem with SoftRAID, but that the problem is
caused by (probably a bad) kext that happens to be from SoftRAID. I
suspect there's not a problem in SoftRAID itself but with the copy of
the kext on your system.
-dhan
------------------------------------------------------------------------
Dan Shoop
Computer Scientist
iWiring / U.S. Technical Services
