[blue68f100]

Indication of a fan that may be going out....
Qhwmon: CPU Fan3b is slow (5400), try to kick start it.

Eithernet port not configured correctly.....
bonding: bond0: link status definitely up for interface eth0. kernel 10-Mar 4:30:08 PM
tg3: eth0: Flow control is on for TX and on for RX. kernel 10-Mar 4:30:08 PM
tg3: eth0: Link is up at 1000 Mbps, full duplex. kernel 10-Mar 4:30:08 PM
bonding: bond0: making interface eth1 the new active one. kernel 10-Mar 4:30:08 PM
bonding: bond0: link status definitely up for interface eth1. kernel 10-Mar 4:30:08 PM
tg3: eth1: Flow control is on for TX and on for RX. kernel 10-Mar 4:30:08 PM
tg3: eth1: Link is up at 1000 Mbps, full duplex. kernel 10-Mar 4:30:08 PM
W
bonding: bond0: Error: found a client with no channel in the client's hash
table kernel 10-Mar 4:30:08 PM
W
bonding: bond0: Error: found a client with no channel in the client's hash
table kernel 10-Mar 4:30:08 PM
bonding: bond0: now running without any active interface ! kernel 10-Mar 4:30:08 PM
device eth1 left promiscuous mode kernel 10-Mar 4:30:08 PM
bonding: bond0: link status definitely down for interface eth1, disabling it kernel 10-Mar 4:30:08 PM
tg3: eth1: Link is down. kernel 10-Mar 4:30:08 PM
device eth1 entered promiscuous mode kernel 10-Mar 4:30:08 PM
bonding: bond0: making interface eth1 the new active one. kernel 10-Mar 4:30:08 PM
bonding: bond0: link status definitely down for interface eth0, disabling it kernel 10-Mar 4:30:08 PM
tg3: eth0: Link is down. kernel 10-Mar 4:30:08 PM
bonding: bond0: link status definitely up for interface eth1. kernel 10-Mar 4:30:08 PM
tg3: eth1: Flow control is on for TX and on for RX. kernel 10-Mar 4:30:07 PM
tg3: eth1: Link is up at 1000 Mbps, full duplex. kernel 10-Mar 4:30:07 PM
bonding: bond0: making interface eth0 the new active one. kernel 10-Mar 4:30:07 PM
bonding: bond0: link status definitely up for interface eth0. kernel 10-Mar 4:30:07 PM
tg3: eth0: Flow control is on for TX and on for RX. kernel 10-Mar 4:30:07 PM
tg3: eth0: Link is up at 1000 Mbps, full duplex. kernel 10-Mar 4:30:07 PM
bonding: bond0: enslaving eth1 as an active interface with a down link. kernel 10-Mar 4:30:07 PM
bonding: bond0: enslaving eth0 as an active interface with a down link. kernel 10-Mar 4:30:07 PM
bonding: MII link monitoring set to 100 ms kernel 10-Mar 4:30:07 PM
I
bonding: In ALB mode you might experience client disconnections upon
reconnection of a link if the bonding module updelay parameter (0 msec)
is incompatible with the forwarding delay time of the switch kernel 10-Mar 4:30:07 PM
Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

Only real error that may indicate whats happening is this one...
I SnapExtension Framework shutdown failed snap_extension 10-Mar 4:26:39 PM
I snap_extension 10-Mar 4:26:39 PM
I Shutting down SnapExFramework: snap_extension 10-Mar 4:26:39 PM

The last one is probably were the problem arises from... This should beable to be stopped/disabled from the snap extensions...

Go to disaster recovery and terminate the scheduling.... should stop the process... delete previous files from server. If space has been filled and needs to overwrite may contribute to your original problem.

Now if the error is being generated due to ethernet connection problem , correct that.

The only other thing I can suggest is revolk the recovery console (touch /nopivot from debug) and reinstall or upgrade the OS... I know a clean install will work but you will loose everything on the server.

If you have Support with Overland, may ring their bell. There is a newer GOS out 5.1.. The reports are that areas of problem (ram management has been re-written and the OS now runs faster than previous model.

Are you have a Snap 10, 30 or 50 connected, saw indications that you may..

I've run out of ideas. I do believe the problems lies with the scheduling or does not have space to write the file, but it say it's looking for the file. Use the built in help to locate where the files are saved to and transfer off of server or delete them all may fix the problem.