Abstract: In some examples, a system for determining whether an operating system fault has occurred includes data storage and a processing system. The data storage may store image data indicative of a computing system display output. The processing system may access the stored image data. The processing system may determine that the computing system display output corresponds to a fault display output associated with a fault state of an operating system, which determination may include the processing system determining an extent of similarity between the accessed image data and a reference image associated with the fault display output. The processing system may generate a fault indication responsive to determining that the computing system display output corresponds to the fault display output.

Abstract: In some examples, a system for determining whether an operating system fault has occurred includes data storage and a processing system. The data storage may store image data indicative of a computing system display output. The processing system may access the stored image data. The processing system may determine that the computing system display output corresponds to a fault display output associated with a fault state of an operating system, which determination may include the processing system determining an extent of similarity between the accessed image data and a reference image associated with the fault display output. The processing system may generate a fault indication responsive to determining that the computing system display output corresponds to the fault display output.

Abstract: An example method may include receiving a plurality of control variable signals indicative of at least an operating state of health of a processor of a device and an operating state of an operating system component of the device, the operating state of health of the processor being one of a good state, a degraded state or a critical state, the operating state of the operating system component being one of under control of an operating system driver, under control of a pre-boot component, or a critically failed state; determining an overall state of the device based on the received plurality of control variable signals, the overall state being one of an up state, a degraded state, a scheduled down state and an unscheduled down state; and tracking an amount of time spent in at least the up state, the scheduled down state and the unscheduled down state.

Abstract: Systems, methods, and computer-readable and executable instructions are provided for providing network attached storage (NAS) devices 232 to management sub-systems 214. Methods for providing a NAS device 232 to a management sub-system 214 can include implementing a network file system (NFS) 220 within the management sub-system 214, 102. Providing a NAS device 232 to a management sub-system 214 also can include communicatively coupling the NFS 220 and the NAS device 232, 104. Furthermore, providing a NAS device 232 to a management sub-system 214 can include providing the management sub-system 214 access to the NAS device 232 via the implemented NFS 220, 106.

Abstract: Systems, methods, and computer-readable and executable instructions are provided for booting a server using a remote read-only memory image. Booting a server using a remote read-only memory (ROM) image can include accessing a remote ROM image from a second server for the first server, wherein the first server does not have a complete ROM image 102, and storing the image in a subsystem memory 104. Booting a server using a remote ROM image can include booting the first server from the remote ROM image in the subsystem memory 106.