Katherine 12m
Disk VSN: USN-0150/4000 | Data volume at beginning: 0.449 GB
VSN did not show up so I manually added it.
1700 UT - Experiment started OK (Tiege)
04:50 UT - Clock jump to 0.326 us (warren)
05:00 UT delay growing, dbbc reconfigure, scans affected 247-0449 to 247-0514 (w)
05:19 UT - 247-0519b next good scan (w)
05:45 UT - clock jump out to 0.32 us (w)
06:40 UT - delay out to 0.45 us (w)
06:45 UT - rebbot and reconfigure dbbc (w)
06:55 UT - back on schedule with scan 247-0655a (w)
08:07 UT - Drifting continues - so reconfigured dbbc (katie)
08:11 UT - Resume, scans missed 247 0847 - 247 0811b (katie)
09:10 UT - Drifting again - reconfiguring (katie)
09:13 UT - Resumed schedule (katie)
09:27 UT - Drifting again so rebooted this time. (katie)
09:43 UT - Resumed schedule (katie)
09:44 UT - FS crashed/then had to reconfigure dbbc again (katie)
10:24 UT - Schedule resumed. Scans missed 247 0909 - 247 1023 (katie)
Yarragadee 12m
Disk VSN: USN-0049/4000 | Data volume at beginning: 0.449 GB
VSN did not show up, have confirmed above drive via webcam. Was not sure if it is OK to manually add VSN post test-recording?