After about 30 mins of disk activity h1boot completed its reboot. Here is the current status of the systems:

DAQ

DAQ Frame Data Was Lost. Here are the frame gaps on the two frame writers

So no data from 08:30 to 10:45PDT. We should investigate if we cannot make the DAQ more independent of h1boot. During run time the DAQ logs to the target area, and I assume that is why the frame writer stop times are after h1boot's demise and at different times.

At 11:18 I performed a clean restart of the DAQ since the framewriters and broadcaster had restarted themselves. All came back ok except:

h1lsc model is showing a DAQ error in its STATEWORD. No error from h1dc0 on this node.

h1broadcaster0 shows the same swap memory problems, I rebooted this unit to clear the error. We will add more memory soon to fix this.

Front Ends

All the front ends EPICS updates became unfrozen, no restarts were needed. The DAQ restart cleared the h1iopoaf0 0x2000 status (model change last week) but an h1lsc DAQ error is showing (see above)

Workstations

Good news on the workstations, they all became unfrozen and appear to be operational. Some wall mount TV servers seem to be not operational, we can fix these tomorrow.

Remote Monitoring

The Vacuum and other MEDM screens are being updated on the cds  web page.

Remote access using 2FA now working.

SysAdmin

Looking at dmesg and logs on h1boot I cannot determine if a full FSCK was ran. We should still schedule this for Tuesday.

I have switched the RSYNC backup of h1boot by cdsfs1 on again.

IFO

I'll leave the verification of IFO operations to the commissioning crew to check.