1833866 Members
2717 Online
110063 Solutions
New Discussion

mraidnt errors

 
Karri Zellmer
Occasional Contributor

mraidnt errors

I have an HP Netserver LH II, running NT 4.0 service pack 4. I have a 40 gig internal drive which I can no longer see. It was my F drive. I can see drives C & D, which are on a separate disk. In my event log I am receiving the following messages:
Event ID: 4
Source: mraidnt
Driver detect an internal error in its data structures for. (It does not specify what for . . .)

Event ID: 7026
Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: mraidnt

I tried to do a ctrl + m upon boot, but this utility no longer works (I have used it in the past with success). The screen I am getting with Ctrl+m is:
BIOS v.A.03.00 June 10, 1997
Firmware initializing . . .
Host adapter at base port FC10H is not responding. No netraid adapter controller available.

I booted with the boot floppy to run diagnostics, and it says it is scanning the hardware configuration, but it hangs up there.

Can you offer any suggestions to help me?

Thank you for your time,

Karri
2 REPLIES 2
Greg Carlson
Honored Contributor

Re: mraidnt errors

Karri,

I'm assuming that your C,D drives are off the embedded controller. Have you tried moving your netraid to another slot to see if you can access ctrl-M in another slot? Make sure that you do not use slot 8 in the LHII as it shares IRQ with the embedded SCSI. Also try having nothing cabled to the netraid and see if you can access the netraid with nothing attached. If there is no change with any of these steps and you can't flash the fw of the netraid you have a dead netraid.
Lets Roll!
Marino Meloni_1
Honored Contributor

Re: mraidnt errors

hi
if you are a message firmware initializing, the problem could be one of the hdd in the raid who are broken, check the light of the hdd , you should see two leds, one is power, the second is activity, at boot time the controller send an enquire to each hdd , you should see a rapid flash on the activity led, if you have a hdd broken the activity led would stay on for lot of time (until scsi time out).
try to remove this hdd out of the raid.
bye
marino