A request to program a set of host data items to management units (MUs) of a fault tolerant stripe associated with a memory sub-system is received. A set of memory access operations to be executed at the MUs of the fault tolerant stripe in accordance with the received request is determined. The set of memory access operations include one or more read operations to read data from the MUs of the fault tolerant stripe. The set of memory access operations also include one or more write operations to write the set of host data items and redundancy metadata associated with the set of host data items to MUs of the fault tolerant stripe. A first series of commands corresponding to the one or more read operations of the set of memory access operations is executed. The redundancy metadata associated with the set of host data items is generated based on the data read from the MUs of the fault tolerant stripe during execution of the first series of commands and the set of host data items. A second series of commands corresponding to the one or more write operations of the set of memory access operations is executed.

Reliability of data reports can be determined by a device that receives a number of reports from different sources. One method includes: receiving data reports from devices. The data reports are associated with an occurrence of an event. The method also includes determining reliability data representing reliability of the data reports. The reliability can be determined based on one or more different defined characteristics such as the location at which a data report was generated relative to the location of the event, whether the data report was the most recently-received data report and/or the number of data reports reporting that an event is ongoing relative to the number of data reports reporting that the event is no longer ongoing. The method can also include determining whether a data report includes information indicative of a false positive report or a false negative report.

Reliability of data reports can be determined by a device that receives a number of reports from different sources. One method includes: receiving data reports from devices. The data reports are associated with an occurrence of an event. The method also includes determining reliability data representing reliability of the data reports. The reliability can be determined based on one or more different defined characteristics such as the location at which a data report was generated relative to the location of the event, whether the data report was the most recently-received data report and/or the number of data reports reporting that an event is ongoing relative to the number of data reports reporting that the event is no longer ongoing. The method can also include determining whether a data report includes information indicative of a false positive report or a false negative report.

A retimer includes a first port to couple to a die over a first interconnect, where the first interconnect includes a defined set of lanes and utilizes a first communication technology, and the die is located on a first package with the retimer. The retimer further includes a second port to couple to another retimer over a second interconnect, where the second interconnect utilizes a different second communication technology, and the second retimer is located on a different, second package to facilitate a longer reach communication channel.

A retimer includes a first port to couple to a die over a first interconnect, where the first interconnect includes a defined set of lanes and utilizes a first communication technology, and the die is located on a first package with the retimer. The retimer further includes a second port to couple to another retimer over a second interconnect, where the second interconnect utilizes a different second communication technology, and the second retimer is located on a different, second package to facilitate a longer reach communication channel.

An apparatus, such as a memory (e.g., a NAND memory), can have a controller, a volatile counter coupled to the controller, and a non-volatile memory array coupled to the controller. The controller can be configured to write information, other than a count of the counter, in the array each time the count of the counter has been incremented by a particular number of increments. Counts can be monotonic, non-volatile, and power-loss tolerant.

An apparatus, such as a memory (e.g., a NAND memory), can have a controller, a volatile counter coupled to the controller, and a non-volatile memory array coupled to the controller. The controller can be configured to write information, other than a count of the counter, in the array each time the count of the counter has been incremented by a particular number of increments. Counts can be monotonic, non-volatile, and power-loss tolerant.

Provided herein are a memory system and method of operating the memory system, which have improved reliability. A method of operating a controller for controlling a semiconductor memory device including a plurality of memory blocks, the method comprising generating a program command and a program address for performing a program operation on at least one page included in an open block, among the plurality of memory blocks, reading data from the at least one page corresponding to the program address and transmitting the program command and the program address to the semiconductor memory device when the number of fail bits included in data read from the at least one page is equal to or less than a first reference value.

Example implementations relate to data center configuration. For example, a server system is configured in a data center by a configuration system including an input processor that receives a data file having multiple record types including a range record type. An error checking processor verifies that the data file has correct syntax and that each of the multiple record types is a valid record type with required attributes. If no error is detected, a record processor converts each of the record types in the data file into a set of ReST API and an output processor sends the set of ReST API requests to a data center configuration manager.

Example implementations relate to data center configuration. For example, a server system is configured in a data center by a configuration system including an input processor that receives a data file having multiple record types including a range record type. An error checking processor verifies that the data file has correct syntax and that each of the multiple record types is a valid record type with required attributes. If no error is detected, a record processor converts each of the record types in the data file into a set of ReST API and an output processor sends the set of ReST API requests to a data center configuration manager.