====== aua034 ======

**Hobart 26m**

Disk VSN: HOB+0131/32000/1024

1900UT Experiment started OK (mas)

Data Volume at Beginning: 2.821 GB

  * 00:06:30 Windstowed (JMc)
  * Windstowed 0000-0031. First valid data is scan no0055 (JMc)
  * 00:46:50 Windstowed again (JMc)
  * Windstowed 0046-0350. First valid data is scan no0096 (JMc)
  * 0354 - Windstowed again... (JMc)
  * Windstowed 0354-0437. First valid data no0104 (JMc)
  * 0548 - Windstowed. First valid data no0120 (JMc)

**Katherine**

Disk VSN: HOB+0043/36000/1024 and HOB+0025

Data Volume at Beginning: 3.205 GB

  * 1900UT Experiment started OK (mas)
  * 21:13:06 Schedule halted to remove r4 module for shipping. Late start for scan No0046 (JMc)

**Yarragadee**

Disk VSN: NAIC-004/2000/1024

Data Volume at Beginning: 3.077 GB

1900UT Experiment started OK (mas)

  * 00:00:39 - Module full, phoned Yarragadee to swap in a fresh module. Scheduled resumed on  HOB+1009 at 00:04:59 (JMc)
  * 05:16   Mark5B crashed. (Warren)
  * 05:40   Called conrtrol room to restart Mark5B (Warren)
  * 05:48 synced Mark5B (Warren)
  * 06:39  Mark5B responding but producing connection errors. Rebooted and resynched. First good scan no0131 (Ross)
  * 15:53UT mk5 has konked out again, first restart has not helped, trying a second restart now, First scan affected no0220 (Tiege) 
  * 16:27UT Second restart caused the mk5 to not want to rise from the dead, called Yg and they manually power cycled. This didnt fix it, so IP power cycled one more time. This time everything appears to be running OK. First good scan should be No0230 (Tiege)
  * 17:03UT It was not running OK, called Jamie, seems to be running okay now as of scan No0236. Jamie believes it is something to do with there being 2 modules in the Yg mk5. (Tiege)
  * 17:40UT Errors + alarms are back again and drives are stuck, going to leave it until morning for a fix as once its up again there will be only 45 mins left of experiment (assuming it works first try...) (Tiege)