Hello everyone!
I've got an NT 4/SP6 server which has rebooted repeatedly during the last few days.
The server has three partitions (C, D and E) where C is formatted with the FAT filesystem and D and E are formatted with NTFS.
Partitions C and D resides on a RAID 1 made up of 2 IBM 18 GB drives on an IBM ServeRAID 4L.
Partition E resides on a single Fujitsu 73.6 GB drive on the same ServeRAID controller.
At this point there is a reliable way to make the server reboot.
It happens immediately when one specific (and possibly others as well) Windows 2000 Pro client accesses a file on the C: (FAT) drive. This has happened with all files tried so far, mostly just text- and log-files
It only happens when the files are accessed through the GUI. The server reboots instantly at this point, the effect being that of pushing the reset switch on the server.
When the files are copied, renamed, moved etc from a command line, there is no problem at all.
Accessing files on partitions D: and E: (both NTFS) is not a problem either.
Accessing the exact same files with an NT 4 Workstation client did not reboot the server.
At this point I tried another Windows 2000 Pro computer. This computer was successfully able to open files on the servers C partition without causing a reboot of the server.
Both Windows 2000 computers have Service Pack 3 installed.
The server has passed IBM's server diagnostics without showing any hint of trouble.
The RAM (2x128 MB ECC) has been replaced by 1x256 MB ECC without any improvement.
If anyone has experienced similar problems I would be really happy to know of any solution or at least some place to start looking.
Thanks in advance
/psson
Andreas Pettersson
I've got an NT 4/SP6 server which has rebooted repeatedly during the last few days.
The server has three partitions (C, D and E) where C is formatted with the FAT filesystem and D and E are formatted with NTFS.
Partitions C and D resides on a RAID 1 made up of 2 IBM 18 GB drives on an IBM ServeRAID 4L.
Partition E resides on a single Fujitsu 73.6 GB drive on the same ServeRAID controller.
At this point there is a reliable way to make the server reboot.
It happens immediately when one specific (and possibly others as well) Windows 2000 Pro client accesses a file on the C: (FAT) drive. This has happened with all files tried so far, mostly just text- and log-files
It only happens when the files are accessed through the GUI. The server reboots instantly at this point, the effect being that of pushing the reset switch on the server.
When the files are copied, renamed, moved etc from a command line, there is no problem at all.
Accessing files on partitions D: and E: (both NTFS) is not a problem either.
Accessing the exact same files with an NT 4 Workstation client did not reboot the server.
At this point I tried another Windows 2000 Pro computer. This computer was successfully able to open files on the servers C partition without causing a reboot of the server.
Both Windows 2000 computers have Service Pack 3 installed.
The server has passed IBM's server diagnostics without showing any hint of trouble.
The RAM (2x128 MB ECC) has been replaced by 1x256 MB ECC without any improvement.
If anyone has experienced similar problems I would be really happy to know of any solution or at least some place to start looking.
Thanks in advance
/psson
Andreas Pettersson