Event 15 on W2K and NT

  • Thread starter Thread starter news.lightship.net
  • Start date Start date
N

news.lightship.net

I have a few different Asus A7V type mother boards. The A7V, A7V133,
A7V266, A7V8X, and also the A7N8X Deluxe. On many of them I am having a
serious problem with data corruption and blocks on the hard drive going bad.
I usually start seeing this message in the Event Log in W2K and Windows NT
4.

Event ID: 15
Source: Disk
Type: Error
User: N/A
Category: None
Description: The device, \Device\Harddisk1\DR1, is not ready for access yet.

It starts at boot and give about 15-25 messages over the course of about a
minute, then occasionally throughout the day it will do it for a few
minutes.

Luckily, I am mirroring the drives (Using NT and 2K's mirroring) and keeping
solid backups so I can usually just shutdown and replace one of the drives
and go forward, but every couple of months one drive is going to the
crapper.
 
Hi,

This is far from normal - drives should not be going for a dive after a few
months like this.

I would start by looking at the RAID 1 controller you are using, the
firmware version and the drivers for it.

- Tim
 
Wazza said:
What brand of hard drives are you using?
Click to expand...

Wazza, if you reply to the person to which you are responding, then you will
have fewer problems such as in the numlock thread. Responding to somebody
who did not pose the question to which you reply is bound to cause
confusion.

Ben
 
Seagate, IBM, Wester Digital. All have done the same. I just don't get it.
The ones being used as file servers die the fastest because they are getting
the most use, but it is still way to short of a life span.

I try to keep the PC hardware as similar as possible so all the computers
have an A7V type board, whether it is the 133,266, or 8X board. This way if
I have to swap the mobo out for some reason it is not a killer.

All the computers are using:

3Com Etherlink 3c905 100Mb cards
ATI Rage 128 AGP (Xpert 2000) video

Parts that make no difference for drivers are slightly different like the CD
drives, Cases, and Hard Drives. The difference between the servers and the
work stations are the processor speed and the memory amount.
 
RAID drivers.....
Bios versions....

Are you mixing make and model of disc drives?
Are yiou using the latest RAID Drivers?

Sounds like you are mixing drives on controllers.

- Tim
 
Exact same drives ALL the time and always purchased the same day. They are
even the same lot.

I usually keep up on the bios so it could be a variety of the revs over the
years, however I don't recall ANY of the revs for the bios ever mentioning
"This rev fixes hard drive corruption" so that should not be the problem. I
also don't recall any of the drivers mentioning that they fixed hard drive
corruption either.

Do you recall a specific RAID driver or BIOS version on the A7V, A7V133,
A7V266, or A7V8X that mentioned that there were problems with drive
corruption?
 
Do you get any other errors reported in the event log?
Any other symptoms / observations?
Do you have any common components between the systems?
Are you using the option to power down disc drives during idle time?
Are the drives in exchangeable containers?
Could there be power / power cable faults - causing the drives to power down
and up again. This happens and normally windows just cruises through with a
bit of a stall.

If not, then I would raise a support call with MS. Since you are using soft
raid (I have for years and never had trouble with it on 2 crappy old SCSI
discs - crappy power cable occured in this raid 0 config and there was no
corruption) and you indicate that it is not motherboard, bios, firmware /
driver (na since it is s/w raid). Is there any common factor?

BTW: Recently there was a case where a bios update had to match a driver
update for a raid controller otherwise a disc corrution would occur. It was
with a gigabyte board. Agreed: bios is thankfully reliable.

- Tim
 
It is not just the computers that I am using the NT raid on. It is also the
desktops that just have the one hard drive as well.

As far as the power management, I usually set the bios to not power down the
hard drives and on the servers I always turn the power management settings
to never power down the drives, never power down the monitor, and never go
to idle. I also try to do this on the workstations as well.

The only two parts that are common on all the systems are the ATI Xpert 2000
AGP video card that uses the Rage 128 chipset and the 3Com 3C90X 10/100 NIC
that is one of the most common NICs in the world. I can't see either of
these being the problem especially since I have not had any issues with
either of these items in years. Come to think of it, I did have a server
that had NetGear NIC and a 3D Labs video card and it still happend to that
as well so I don't think that is the cards.
 
Back
Top