Server Gone to Fritz,

[fizunk]

here are the specs

Server: Asus AP1400R-T
Motherboard: TR-DLSR 1011.004 revision
Hardrives: (3) Cheetah 36ES Hard Drive ultra160 scsi
-Specs on hard drive
Capacity: 36.90GB Speed: 10,000 rpm, Seek Time: 5.4ms
manufacturer model: ST336706LC
SCSI Card: LSI Logic model #: 53C1010 (66 version)
The server is running windows 2000 server and has been fully updated with services packs

here is what is currently happening.
I boot up the server up, windows loads up fine, I can access the sales drive and the C drive, I cannot however access my engineering drive without it causing a memory dump of some sort, after about a gig or so of file transferring the server will start to beep and the drive seems to just turn non-responsive. I can work on getting a ss of the error but I cant sit here and think the drive is dead as I can reboot it everytime and it loads just dandy, its after a lil time has passed and the beep will start and it all just goes down hill.

*EDIT- I just wanted to point out that I have all 3 slots on the server filled each one representing a division C drive for windows/users, F Drive for Sales and E Drive for Engineer files.

 

[LiLithTecH]

What Event code is it giving?

 

[redbeard1]

Beeping sounds like a raid drive error. But you don't indicate that your running a raid card. Is it possible that your scsi setup has some sort of similar alarm warning?

 

[fizunk]

Event Log
3/3/2003 2:50:33 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk0\DR0 during a paging operation.
3/3/2003 2:47:43 PM Ftdisk Warning None 50 N/A BSISERVER03 {Lost Delayed-Write Data} The system was attempting to transfer file data from buffers to \Device\HarddiskVolume3. The write operation failed, and only some of the data may have been written to the file.
3/3/2003 2:47:35 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM EventLog Error None 6000 N/A BSISERVER03 The System log file is full.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
3/3/2003 2:37:58 PM Disk Warning None 51 N/A BSISERVER03 An error was detected on device \Device\Harddisk2\DR2 during a paging operation.


I am running a scsi raid card, but they (was set-up before I was hired) choose to not run a raid config as they felt the standard 10k rpm
would be okay, and it has been.

 

[LiLithTecH]

Event code 51 is not a Fatal code.

Seeing that you are getting the error on 2 drives,
have you checked the cabling to the carriers?

If you have a replacement cable, I would try that first.

Also, have you run a virus check lately? I have seen trojan's
do this, making changes to group policies.

 

[fizunk]

Yea I did replace the scsi cable, virus check well actually no I havent ran one and infact, its been some time since I checked that, will do that right now and will post what happens

 

[fizunk]

Well I checked on norton corporate and I did a scan atuomatically 6:00pm March 03, 2003, it came up clean and my problems had already been going on at that time The weirdest thing is I took it off the network this morning at 8:10, its being rebooted right now but had an uptime of 4 hours. Odd it seems like whenever it starts to pick up in traffic it goes to crap.

 

[redbeard1]

Something on one of the drives is faulty. That beeping is a warning from the scsi raid card that some sort of error has occured. It might be that the drives cache is bad. I'd say download seagates drive diagnostic program, and check the drives, especially the E: drive.

If the raid setup has it's own dedicated ram, you may need to install more, to handle the load. If it has ram, maybe there is an issue with it being bad.

 

[mechBgon]

Temperatures come to mind as another possible cause of beeps. Check your CPU and drive cooling too.