Abstract: In a storage system including a plurality of storage nodes and a plurality of storage devices that provide storage areas to the storage nodes, a cluster control unit that has detected occurrence of a failure in another storage node requests an external control device to execute a detach process of detaching a storage device allocated to a failure storage node from the failure storage node and an attach process of allocating the storage device to an alternative storage node. Then, the alternative cluster control unit restores, based on a log stored in a storage device allocated to a storage node in which a most recent failure has occurred among the storage nodes belonging to the same redundancy group as a failure storage control unit of the failure storage node, storage content of a memory of the alternative storage node.

Abstract: A method may include: receiving a plurality of log-text examples from network devices and labels indicating if the log-text example is anomalous or not anomalous; identifying, from the log-text examples and labels, rules for weak annotation, and validation labels for a validation dataset and test labels for a test dataset; organizing log-text examples in the validation dataset into a plurality of time windows; concatenating log-text examples in each time window; providing the concatenated log-text examples and the rules for weak annotation to a weak annotation framework, to a LLM training dataset; training a LLM with the LLM training dataset; collecting runtime log-texts from the network devices for a period of time; concatenating the runtime log-texts for the period of time; and prompting the LLM for analysis with the concatenated log-texts, wherein the LLM outputs a response of anomaly or no anomaly and a confidence in the response.

Abstract: Upon failure of a host and, in response to a lack of hots having available processing units, a host is selected and one or more processing units of the selected host are allocated as shared CPUs for use by one or more components of the failed host. The selected host may be selected according to requirements, such as affinity, anti-affinity, and latency. The shared CPUs may have been previously allocated as a dedicated CPU. The shared CPUs may be bound to the one or more components. The one or more components may include a container.

Abstract: Architectures and techniques are described that can leverage a container storage interface (CSI) driver to initiate volume health tests for a storage system in accordance with certain embodiments of this disclosure. The CSI driver can conform to a CSI specification or standard and can be used to expose the storage system to a container orchestration system. The volume health tests can be tailored to reduce or mitigate the impact of testing based on a status or state of the volumes. For instance, enforcement can be provided to ensure that only shorter, low-impact testing is performed on volumes having a published state, whereas longer, more intensive testing can be performed on volumes that are not in the published state.

Abstract: In some examples, a system detects disabling of a driver of a storage control feature included in a main processor of the system, where the storage control feature to manage access of a storage device. In response to detecting the disabling of the driver of the storage control feature included in the main processor, the system initiates a remediation action to prevent a fault in the system.

Abstract: A method for reporting a hot-swap error, a processor architecture, a device, and a storage medium are provided by an embodiment of the present application. The method is applied to an advanced reduced instruction-set computer (RISC) machine (ARM) platform, the ARM platform includes a baseboard management controller (BMC), an operating system (OS), and a basic input output system (BIOS). Data transmission between the BMC and the OS is performed based on a data interface service configured via the BIOS. During operation of the ARM platform, in response to a system control processor (SCP) in the BIOS detecting a PCIe CE type reporting error information corresponding to any interface, the SCP transmits the PCIe CE type reporting error information to the BMC and the OS.

Abstract: Methods, systems, and devices for reset techniques for protocol layers of a memory system are described. A communications link may be established between a host system and the memory system. In some examples, the communications link may be based on one or more first parameters associated with a first protocol layer and one or more second parameters associated with a second protocol layer. The system may support communication (e.g., from the host system to the memory system) of an indication to reset the communications link, and the host system, the memory system, or both may reset the one or more first parameters based on communicating the indication to reset the communications link. The host system and memory system may attempt to reestablish the communications link based on resetting the one or more first parameters and maintaining the one or more second parameters.

Abstract: A system can maintain a data storage system, wherein the data storage system comprises persistent memory and chunk storage, wherein the persistent memory is more performant than the chunk storage, wherein the chunk storage stores data in chunks of a fixed-size, and wherein respective chunks of the chunks correspond to respective parity values. The system can, based on receiving a request associated with a storage account to write data to the data storage system, write the data to the persistent memory concurrently with writing the data to the chunk storage. The system can, after completing writing the data to the persistent memory and before completing writing the data to the chunk storage, send an indication, to the storage client, that the data has been successfully stored in the data storage system.

Abstract: Systems and methods for in-system, self-recovery (ISSR) in a system-on-a-chip (SoC) are disclosed for detecting and recovering from a bit corruption event that has caused an SoC subsystem to crash. If a bit flip event is detected through observation of a subsystem crash, ISSR steps are taken in an attempt to correct the issue. If the ISSR steps are successful, then the system is not halted and mission mode operations continue. If the ISSR steps are unsuccessful, then the system is halted and an return material authorization (RMA) can then be issued for return of the failed part to the OEM. Crash events and self-recovery attempts preferably are logged by the ISSR system and provided to the OEM.

Abstract: Embodiments of the present disclosure disclose a method and a system for managing geo-redundant cloud servers. The method includes: receiving, by a set of first geo-redundant operators associated with a set of first databases hosted on a set of first servers of a first data system, state information of corresponding first server of the set of first servers, health information of a set of second servers of a second data system, from a corresponding first manager of a set of first managers associated with the set of first servers. The method includes synchronizing, by the set of first geo-redundant operators, stateful data from each first database of the set of first databases to a corresponding second database of a set of second databases associated with the set of second servers based on the state information, the health information and one or more synchronization parameters.

Abstract: The present disclosure provides a method for processing storage medium failure, an apparatus, and a solid state disk thereof. The method includes: acquiring a failed storage medium; detecting a state of the failed storage medium in real time, where the state at least includes an idle state, an open state, and a closed state; and processing the failed storage medium in real time according to the state of the failed storage medium.

Abstract: A method for handling faults in an integrated circuit system includes receiving fault interface signals from safety-critical logic and generating a fault request indicating a fault and a domain identifier based on the fault interface signals. The fault interface signals include a fault signal and a fault domain identifier signal. In an embodiment of the method, the fault interface signals include synchronous signals received from the safety-critical logic using a synchronous interface and the synchronous signals include a fault clock signal. In an embodiment of the method, generating the fault request includes asserting the fault request in response to the fault signal having a first asserted signal level and maintaining assertion of the fault request until a fault acknowledgement is received from a fault collection and control circuit.

Abstract: An integrated circuit includes a compute circuit and a trace data mover circuit coupled to the compute circuit. The trace data mover circuit is configured to convey trace data generated by the compute circuit to a destination circuit. The trace data mover circuit includes a controller circuit configured to receive a stream of trace data from the compute circuit and generate instructions for writing the trace data. The trace data mover circuit includes a writer circuit configured to write the trace data to the destination circuit responsive to the instructions generated by the controller circuit.

Abstract: A technique is directed to managing a server cluster that includes multiple servers. The technique involves receiving, from a server in the server cluster, set of heartbeat signals through a power transmission circuit constructed and arranged to deliver power to the server cluster. The technique further involves detecting an interruption in receiving the set of heartbeat signals. The technique further involves, in response to detecting the interruption in receiving the set of heartbeat signals, performing a remedial activity to coordinate input/output (I/O) operations among the multiple servers in the server cluster.

Abstract: Systems and methods for re-aligning data replication configuration of a cross-site storage solution after a failover are provided. According to one embodiment, after a failover, the new primary distributed storage system orchestrates flipping of the data replication configuration of a peered consistency group (CG) to reestablish zero RPO and zero RTO protections for the peered CG. The primary causes the secondary distributed storage system to perform an atomic database operation on its remote configuration database to (i) delete an existing source configuration that identifies the secondary as a source of data replication; and (ii) persist a new destination configuration identifying the secondary as a destination of data replication.

Abstract: An apparatus comprises a processing device configured to obtain monitoring data for devices comprising a plurality of features, determining two or more rankings of the features using two or more filter-based feature selection algorithms, and selecting a subset of the features based at least in part on the two or more rankings. The processing device is also configured to generate a failure prediction for a given one of the devices using at least one classifier that takes as input the selected subset of features, and applying a conformal prediction framework to the generated failure prediction to obtain a confidence measure indicating a quality of the generated failure prediction and a credibility measure indicating a quality of the monitoring data. The processing device is further configured to initiate one or more remedial actions based at least in part on the generated failure prediction, the confidence measure, and the credibility measure.

Abstract: The present invention provides a control method of a server, wherein the control method includes the steps of: periodically controlling a first register and a second register of a first node to have a first value and a second value, respectively; periodically controlling a third register and a fourth register of a second node to have a third value and a fourth value, respectively; controlling the first register and the fourth register to synchronize with each other, wherein the first value is different from the fourth value; controlling the second register and the third register to synchronize with each other, wherein the second value is different from the third value; and periodically checking if the third register has the third value and the fourth register has the fourth value to determine if the first node fails to work.

Abstract: The disclosure relates to an MCU failure detection device and method. According to the disclosure, a device for detecting a failure in a microcontroller unit (MCU) comprises a receiver receiving first watchdog output information for determining a failure from an electronic control device, a determination unit determining whether the electronic control device has a failure based on the first watchdog output information, and upon determining that the electronic control device has the failure, transmitting a first reset signal to the electronic control device.

Abstract: One example method includes performing, as part a planned failover procedure, operations that include connecting a replica OS disk to a replica VM, powering up the replica VM, booting an OS of the replica VM, disconnecting a source VM from a network, and connecting replica data disks to the replica VM. IOs issued by an application at the source VM continue to be processed by the source VM while the replica OS disk is connected, the replica VM is powered up, and the OS of the replica VM is booted.

Abstract: A strongly consistent distributed data storage system comprises an enhanced metadata service that is capable of fully recovering all metadata that goes missing when a metadata-carrying disk, disks, and/or partition fail. An illustrative recovery service runs automatically or on demand to bring the metadata node back into full service. Advantages of the recovery service include guaranteed full recovery of all missing metadata, including metadata still residing in commit logs, without impacting strong consistency guarantees of the metadata. The recovery service is network-traffic efficient. In preferred embodiments, the recovery service avoids metadata service downtime at the metadata node, thereby reducing the impact of metadata disk failure on the availability of the system. The disclosed metadata recovery techniques are said to be “self-healing” as they do not need manual intervention and instead automatically detect failures and automatically recover from the failures in a non-disruptive manner.