NetRaid Log file

[Rob_171]

I found this file and started reading through it. I noticed ever since I did a quick initialization of a logical drive it started putting this message down every 3 days:

Log Started.
- Fri Mar 19 14:02:26 2004
NOTIFY:Check Condition on Ch 1 ID 12 with the following sense key - Fri Mar 19 14:02:26 2004
70 00 02 00 00 00 00
0a 00 00 00 00 04 01
NOTIFY:Check Condition on Ch 1 ID 12 with the following sense key - Fri Mar 19 14:02:26 2004
70 00 02 00 00 00 00
0a 00 00 00 00 04 01

I'm not sure exactly what it means. Also, if anyone knows where I can find out the results of a check consistency that'd be great. Event Viewer in NT4 told me the check consistency progress (what % done) but since I did a quick initialization on the logical drive I want to see if I can find a result, such as "inconsistencies cured".

Thanks.

[amhakassa]

Hi Rob,

This link will give u a cure

http://isupport2.hp.com/Solution.asp?id=IS8952

I recommend to update the FW on the raid conroller to the latest and the FW on the hard drive too

Let me know if the problem solved

Regards
Amha Kassa

[Rob_171]

Your link isn't working

[kris rombauts · Accepted solution]

Rob,

the SCSI sense key that you found in the Netraid log file means this :

02 : not ready
Indicates that the logical unit addressed cannot be accessed.

04 01 :LOGICAL UNIT is in progress of becoming ready

This is reported by disk ID=12 on channel 1.


Pls check your NT4 Operating System Eventlogs to see if their are no disk related errors or SCSI timeouts present, if not then i would not worry to much since these events could be from a power up/reboot situation where this disk did not became Ready in due time and the Netraid controler detected this.

Their was also a problem with the contents of the raid.log file in a way that each time you open the Netraid Asisstant utility, the sense keys will be copied again in the raid.log file every time but their date and timestamp are not from the real date/time of the issue and get the current date/time when you started the utility. This is what i see in your case since the 'Log Started' message (the date/time you opened the Netraid Assistant utility) and the sense key date/time is exact the same.
To be sure this is the case, reopen Netraid Assistant again and have a look at these date/time stamps, if they are again all equal then this means those SCSI events are old and not new ones, so don't worry then.

Their is a way to clear them but for this issue i don't want you to go through these steps as it isn't worth taking the risc to do that procedure really.

If new SCSI sense keys do occur, they will be added and you'll see them in the raid.log file.

It's importent that you install the Netraid monitor software at the Operating System level, this way you will see SCSI sense keys appear in the Windows eventlog at the time they really take place.

see here :

http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?locale=en_US&pnameOID=15688&taskId=135&prodTypeId=329290&prodSeriesId=62471〈=en&cc=us&swEnvOID=24


HTH

Kris

[Rob_171]

Thanks for the reply. Mainly a curious question, but if it's no big deal I won't worry about it. The drives are online and all three activity lights are active when data is written to it. Just being extra careful before I throw data on the drive.

One last thing though, as I mentioned Event Viewer displayed a check consistency on all three logical drives, but I want to know if the results of that are stored anywhere. I did a quick initialization of one this particular logical drive and I want to see if inconsistencies were cured or if I should manually do a check consistency again.

Thanks.

[kris rombauts]

Rob,

no their is no detail available of what the consistency check eventually corrected. Bottom line here is that the consistency check runs a full check on the logical drives and it cures any inconsistencies, if it can't then it will abort the check and then you have to worry more and try to find the bad disk(s).

So if you see a 'completed' messages then the array is healthy.

Just keep an eye in the near future on your eventlog and eventual raid.log. The raid.log only gets updated after you start the Netraid Assistant, don't look off-line via explorer i.e. to the contents of raid.log because it is a static file and receives no updates as long as Netraid Assistant in't used.

regards, Kris

[Rob_171]

The only messages received in the Event Log due with start and progress. There were three logical drives getting consistency check.

One message for each drive that it is starting, and then various messages saying something along the lines of:

"Adapter 0 Logical Drive 2 Consistency Check 68% completed"

I never got one for any of the logical drives say it finished.

[kris rombauts]

Rob,

the number of entries you will see depends on how long the consistency check takes. So for a large array where the CC takes hours, you'll see multiple entries i.e. 7%, 20 % 40% ... etc. The entry is added at a fixed interval (default 15 minutes), so for small arrays you might only see few entries.
The interval can be configured on the commandline with the megactrl command i.e.

megactrl -LogProg500

for a reporting update every 500-seconds
(see megactrl /? and in the readme file for more details)


I think you might be using an old version of the software because the message below shows you how it looks like in the Application EventLog using this version :

RAID Monitor Service Ver 5.07(40-ld) Nov 07,2002 started



Event Type: Information
Event Source: NetRAID.Log
Event Category: None
Event ID: 6107
Date: 3/14/2004
Time: 6:37:24 PM
User: N/A
Computer: xxxxx
Description:
Adapter 0 LogDrv 4: Check Consistency is COMPLETED.


regards, Kris