DC Reporting Low Disk, but it's not?

[tcs1]

Server 1 Win2k Server, all SP's applied. There is an additional DC (Server 2) on the network as well. About 6 months ago we encountered issues where Server 1 was locking up and not allowing file transfers to disk 1 (two partitions, "D" and "E", "D" is the one at issue), partition "D". We had other errata as well and went through MS tech support out of frustration who eventually had us rebuild DNS (although these are internal machines), which in conjunction with several other steps seemd to resolve the issue.

NOW, out of apparently nowhere the issue has resurfaced. There is over 2.6GB of free space on "D", but this morning it wouldn't allow a 170MB file to be written to disk. Had to reboot the server and run a checkdisk on all drives to get it back online.

ANYONE have ANY experience with this type of scenario?

Thanks.

 

[gbiello]

Just a hunch, but have you defragmented the drive at all?

 

[MitchCumstein]

It could be a paging file issue. If the file resides on "D:" and has a maximum size near your current amount of free space, I think Windows will stop you from copying large files to it.

Or maybe not...

 

[tcs1]

Yep. We've defragmented the drives. The exact configuration is 4 physical drives TOTAL in the machine, 0-3. Dirve 0 is system, 1 is mirror of system, 2 and 3 are partitioned to "D" and "E" and are mirrors of each other.

Now when we reboot we have to remove, physically disconnect, all but drive 0 to get the machine to boot, THEN reinsert drives 1-3 while operating, at which point they are recognized, otherwise the system hangs at re-boot.

There is over 2.5GB remaining on "D", an 18GB drive, so I do not believe it is a true disk space issue.

 

[gbiello]

Next shot-in-the-dark idea: How about updating the BIOS on the motherboard and the firmware on the SCSI/RAID card.

 

[GranSalseron]

Scandisk.