Renice LS1046-ARM storage server motherboard




Processor: 4 cores ARM COTEX A72, up to 1.8Ghz
Memory: DDR4 16GB
Storage: 8x SAS or SATA Solid State Drives
OS: LINUX
PCIe interface: 1 channel X4 PCIE3.0
Internet: 4-channel Gigabit network interface, 2-channel 10 Gigabit network interface, 1x BMC 10M/100M management network port
SF8087: 2-channel SF 8087 interface, configurable into 3 X1 PCIe or 1 X4 PCIe interface
Power Supply: Provide 1 power input interface, 1 power output interface, 1 power management interface
Fan interface: 5 channels (4 lines, PWM, SENCE, 12V, GND)
USB interface: 2x USB3.0 host interfaces, 1x USB3.0 device interface
Serial port: 1x RS232 universal serial port, 1x RS232 debugging serial port
Size: 243.84mm x 243.84mm
Operating voltage: the motherboard uses +5V and +12V, 3.3V power supply
Typical power consumption: <30W

To learn more, please email sales@renice-tech.com.

Comments

Post a Comment

Popular posts from this blog

Renice r-Backup® Power Failure Protection of SSD

Image
rBackup (Rapid Backup) refers to a technique of how to flush data stored in DDR into NAND Flash within a very short period. It is developed by Renice to solve the problem that regular power failure protecting mechanism (based on super capacitor or tantalum capacitor) does not work when capacitor ages with power less than initial design as time goes by. Background Mainstream SSD deploy SDRAM or DDR to improve the R/W speed. That follows the issue of data loss or mapping table loss when sudden power failure occurs. To guarantee the data integrity, usually SSD makers design a power failure protecting mechanism based on Super-Capacitor or Tantalum Capacitor, which will work as backup power for SSD in power failure circumstance. This design seems to be perfect to balance the performance and reliability. However there is a potential hazard behind it in real application. Both Super-Capacitor and Tantalum Capacitor keep aging as charge & discharge times increase. Common warranty pe...
Read more

About SSD AES-encryption

Self-encrypting drives use an encryption engine built into the SSD’s controller to encrypt every file stored on the drive. The purpose of AES Encryption is to convert standard input data known as plaintext to an unintelligible output known as cipher text. So if AES encryption on SSD used for data randomization function only, it only provides some data protection in the sense that if the controller is damaged, a 3rd party would not be able to read the data on the flash. In normal usage, however, there would be no data protection as any party that is in possession of the drive can read the data. Methods of using AES on SSD to Secure Data Hardware-based Encryption Self-encrypting drives include dedicated AES encryption engines that do not require software to run on the host. The randomized AES encryption keys are generated at product initialization using the controller’s true random number generator and encrypted in the SSD. This could also be implemented by a Trusted Platform Modu...
Read more

How to extend SSD life expectancy by 3 folds? Renice Non-Balance Wear Leveling Algorithm

Image
The first portion of this article introduces the background of wear leveling and some commonly used algorithm while the second portion covers a kind of wear leveling that can prolong life by three folds: Non-balance Algorithm. Experts may skip directly to the later portion. In order to prolong the life cycle of NAND flash by avoiding some blocks being frequently erased and becoming bad blocks rapidly while the existence of other less erased blocks will cause an unbalance Program/Erase situation that shorten the overall SSD product life as a drawback. There are various algorithm towards wear leveling and garbage collection raised by NAND flash practitioner as strategy to avoid these potential problems. Background of Wear Leveling Algorithm The wear leveling algorithm is based on the basic characteristics of flash memory: 1. Do not support local update (outplace-update that is data in original location cannot be overwrite or change directly, this data will need to be relocated t...
Read more