Guest Noctaire Posted December 21, 2007 Posted December 21, 2007 I'm seeing the below entry in my system log: ************************************************ Event Type: Warning Event Source: nfrd960 Event Category: None Event ID: 129 Date: 12/20/2007 Time: 4:14:27 PM User: N/A Computer: XXXXXXXXXX Description: The description for Event ID ( 129 ) in Source ( nfrd960 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort0. ************************************************ This appears to be a timeout issue of some sort but I'm finding limited examples on it out there. Anyone have any links or an explanation? Thnx!
Guest Edwin vMierlo [MVP] Posted December 21, 2007 Posted December 21, 2007 Re: Event ID 129 in Source nfrd960.... "Noctaire" <noctaire@yahoo.com> wrote in message news:e7e15V3QIHA.5184@TK2MSFTNGP05.phx.gbl... > I'm seeing the below entry in my system log: > > ************************************************ > Event Type: Warning > Event Source: nfrd960 > Event Category: None > Event ID: 129 > Date: 12/20/2007 > Time: 4:14:27 PM > User: N/A > Computer: XXXXXXXXXX > Description: > The description for Event ID ( 129 ) in Source ( nfrd960 ) cannot be > found. The local computer may not have the necessary registry > information or message DLL files to display messages from a remote > computer. You may be able to use the /AUXSOURCE= flag to retrieve this > description; see Help and Support for details. The following information > is part of the event: \Device\RaidPort0. > ************************************************ > > This appears to be a timeout issue of some sort but I'm finding limited > examples on it out there. Anyone have any links or an explanation? > > Thnx! There is indeed limited information on this. Basically it is a timeout occurring in storport.sys driver, but reported to the HBA or SCSI-adapter driver, in your case nfrd960.sys. First of all, ensure you are running the latest nfrd960.sys from IBM Second, you really need to ensure you are running the latest storport.sys from Microsoft. at the moment that would be KB-943545. But you must check what version your SCSI-adapter vendor supports for the nfrd960.sys driver And open a case with your (storage) vendor, IBM in your case. Rgds, Edwin. and if you really want to dig in : The 129 event is actually listing the device and the error code as well, here is how you decode this : (please open a support call with your vendor, at this point you will need expert help on inner-workings of drivers) the Data structure of an event id 129 in this case has a similar layout as an event id 51, and you can use http://support.microsoft.com/?id=244780 to look at the various values Example: Data: 0000: 0f 00 18 00 01 00 66 00 ......f. 0008: 00 00 00 00 81 00 04 80 ....�..? 0010: 04 00 00 00 00 00 00 00 ........ 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 2e 00 81 00 04 80 ....�..? 0038: 00 00 00 00 00 00 00 00 ........ the first byte starting at 0000: is 0x0F, this translatest in an IOCTL (device control io, you can also see a write (0x04) or a read (0x03) here, depending what the driver was doing at the time of the timeout) then byte 5 6 7 8 on "line" 0008: is 81 00 04 80, this is the error code in little endian encoding So that would mean the real value is (from right to left) 0x80040081 This error would mean IO_WARNING_RESET (this is also repeated at the last 4 bytes of line 0030:) Then byte 3 on line 0030: is 2E, this would be the LUN number, which you can relate back to actual disk it has a problem with LUN 2E would translate into LUN 46. Sometimes an Error is recorded in the first 4 bytes on line 0010: again in little endian coding So tht would mean in this example the real value is (from right to left) 0x00000004 (0x4) Which in this example would be ERROR_SLOT_NOT_PRESENT Decoding this might help your support people to pinpoint to the real issue, Please note, all the above is an example, and your values might differ from what I have detailed here.
Recommended Posts