Katherine 12m

Disk VSN: OSOD-067/2000 | Data volume at beginning: 0.192 GB

• 1830UT - Experiment started OK (Tiege)
• 2005UT - Two clock jumps at Ke one after the other. Going to monitor and see if it stabilises now. (as with this previous experiment). (Tiege)
• 1534UT - MK5 crash / DIMino Crash (JS)
• 1612UT - MK5 reset. (JS)
  • Lost scans 264-1531 through 264-1610
• 1612UT - FS locked up during `midob` resetting FS (JS)
  • yg FS was temporarily stalled & unresponsive to commands at the same time but resumed without dying …. hmmmmm
• 1626UT FS reset, resuming experiment at scan 264-1632 (JS)
  • Lost scans 264-1531 through 264-1628
• 1626UT “ALARM: scan_check reports Mark5 data format problem” this is likely due to a syncerr_eq_3 across the previous partial recording (264-1628) monitoring for further issues before escalating (JS)
• 1638UT receive another “m5 -104 mk5cn” error, halted and restarted MK5 (JS)
  • affected scan 264-1641b
• 1647UT MK5 reset hasn't solve the issues, still plagued by “m5 -104 mk5cn” error whenever a scan ends, despite DIMino running and responding (JS)
• 1710UT after calling Jamie, the conclusion is that there are bad HDD in the current module causing read/write lag that the field system doesn't like. The data should be recording ok, but the errors will persist (JS)

Yarragadee 12m

Disk VSN: BKG-0048/2000 | Data volume at beginning: 0.288 GB

• 1830UT - Experiment started OK (Tiege)