On Friday, March 14th the “warning” indicator on Merlin2 was flashing, and the third drive was also flashing yellow. As we were in the middle of the data move from Merlin to Merlin2, we decided to push onward and deal with the problem later.

Today, the OS went BSOD. The server was shut down, then powered back up. The server came back up without any data loss and automatically started rebuilding the array onto the previously failed disk.
Continue reading →

Jim found the source of the trouble – a wireless access point in Trimble 004. The device has been taken off the network until it can be examined.

The trouble continues in Trimble Hall. A malfunction occurred with the same symptoms. We have isolated the problem to the switch in Trimble 007. We disconnected the TH network piece by piece while monitoring connectivity with ping. When the 007 switch was disconnected, connectivity returned. Upon reconnecting the 007 switch, the network maintained connectivity. We will have to wait until the next failure to isolate the trouble to a specific port on that switch.

The Trimble Hall problem continues with a similar malfunction this afternoon. Jim dropped the Trimble Hall uplink to 10 Mbps, which cleared the problem.
Continue reading →

The network in Trimble Hall malfunctioned again, causing campuswide network slowdowns. It appears that rebooting any switch in Trimble will clear the problem. This time, the switch in Trimble 007 was rebooted.

A switch in Trimble Hall 107 malfunctioned and caused a traffic flood into the rest of the network. Trimble Hall was disconnected from the network for approximately 1 hour while the issue was resolved. A reboot of the switch solved the problem.
Continue reading →

Webboard hung. To correct the problem, the machine was rebooted.

We have been struggling with a faulty disk array on tahoma. Compaq service was on site, and replaced a faulty connector cable. The disk array is functioning normally.

The Webboard server was rebooted to re-enable access.