At 06:28 local time Tuesday 22 May, h2fw0 crashed and restarted itself. Unfortunately the ini and par files had changed since the last DAQ restart and therefore h2fw0's frames contained bad data. The whole H2 DAQ was restarted at 8am to resync the whole system. A solution to the out-of-sync-configuration is being installed. The cause of the original crash is still under investigation.