topic mraid35x error???????????? in Netservers

mraid35x error????????????

myauto_1 — Sat, 07 May 2005 23:24:45 GMT

Event Type: Error
Event Source: mraid35x
Event Category: None
Event ID: 9
Date: 2005-4-26
Time: 10:09:45
User: N/A
Computer: FINANCE1
Description:
The device, \Device\Scsi\mraid35x1, did not respond within the timeout period.
Data:
0000: 00 00 10 00 01 00 6a 00 ......j.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 01 01 00 50 00 00 00 00 ...P....
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 07 00 00 00 ........

Re: mraid35x error????????????

myauto_1 — Sat, 07 May 2005 23:28:18 GMT

Our server is LH6000

Re: mraid35x error????????????

Marco Hogeveen_1 — Mon, 09 May 2005 02:30:24 GMT

Hi,

The mraid35x driver is the driver of your netraid controller. It had a timeout. Please check the netraid log to see if there are any errors in there. (file is called raid.log).

Marco

Re: mraid35x error????????????

myauto_1 — Mon, 09 May 2005 02:40:21 GMT

Checked c:\NetRAID\CLIENT\Raid.log
Here is the following,but it seems noting to do with that error message

Log Started.
- Thu Jul 29 20:32:31 1999
Log Started.
- Mon Sep 27 07:33:24 1999
Log Started.
- Wed Sep 13 15:09:20 2000
Log Started.
- Wed Sep 13 15:09:26 2000
Log Started.
- Fri Nov 03 21:43:48 2000
Log Started.
- Tue Oct 19 14:23:39 2004
NOTIFY:Check Condition on Ch 1 ID 0 with the following sense key - Tue Oct 19 14:23:39 2004
f0 00 04 00 a6 d0 3e
28 00 00 00 00 15 01
Log Started.
- Tue Oct 19 15:31:44 2004
NOTIFY:Check Condition on Ch 1 ID 0 with the following sense key - Tue Oct 19 15:31:44 2004
f0 00 04 00 a6 d0 3e
28 00 00 00 00 15 01

Re: mraid35x error????????????

Marco Hogeveen_1 — Tue, 10 May 2005 01:52:43 GMT

Hmmm, nope the dates don't match.

What driver version are you using? (system32\drivers\mraid35x.sys properties)

Re: mraid35x error????????????

myauto_1 — Tue, 10 May 2005 02:07:22 GMT

file version:5.0.2174.1
product version:5.28

Re: mraid35x error????????????

Bryan_83 — Thu, 19 May 2005 11:42:30 GMT

Looking at the sense key data, it looks like there was a mechanical error on the specified HDD. In your sense key data, the second Byte (04) indicates that a Hardware error has occured. Byte 12 and 13 (15) and (01) indicate that the hardware failure was a mechanical positioning error.

So it sounds like the drive it was referencing is going bad.

Bryan