Renice: the Physical Destruction of SSD



SSD Physical Destruction video:





(https://www.youtube.com/watch?v=IAJvNfo2MpY)

It’s not the worst burning in the video, other components are also burned and you could see the fire if press destruction button repeatedly. Here are several questions that you might want to know after watching the video.

Q1, Is the Nand flash totally destroyed?
 Yes.



Q2, It seems the burning takes long time, can it be faster?
      Yes. Burning time is controlled by singlechip, so the time not only can be set freely but also ensure complete destroy. Our test result shows that 10s can destroy all Nand flash (only for approved flash model).

Q3, How long does the burning take?
      Press the button for more than 5 seconds to trigger the physical data destruction function and start burning the NAND flashes, each Nand flash burning will take 5 seconds.

Q4, Only through the button to trigger Physical Destruction function?
       No.
  Physical Destruction can be triggered by button, also can be triggered under other conditions, e.g. Binding the SSD with host, when used in unauthorized host, the SSD will auto-start data destruction function. Also, restricting the SSD only used in certain distance, once taken away from the region, the SSD will auto-start data destruction program.
   In a word, Physical Destruction can be developed with many requirements according to different applications.

Q5, Physical Destruction is acted through high-pressure breakdown upon to Nand flash, isn’t it, and what any other technological difficulties?
It’s easy to destroy, but destruction is a double-edged sword, it can completely destroy the SSD when needed, however, more often than not, there is destruction when there is no need for destruction, which leads to even worse result.
So, how to prevent the false trigger is the real technical difficulty, it’s common to see the false trigger happening from some Physical Destruction SSD solution providers, for example:
(I) The SSD is immediately burned down when power on, even connect with authorized host.
(II) When affected by electromagnetic interference, SSD accidentally executes destruction function even during normal usage.
 (III) If the button has been in the wrong pressing state when booting computer, the SSD will get burned.


Q6, Is there any requirements for the host if configure SSD with Physical Destruction?
  Of course there is.
   a) It needs the Pin definition of host storage interface is exactly the same as the SSD interface’s Pin definition.
   b) When in storage array, the array backboard must allow enough current to pass through, otherwise, it will burn the backboard firstly.

Q7, What kind of interface SSD can support Physical Destruction function?
      Theoretically, all kinds of interface SSDs can support.

Q8, Does Physical Destruction need to modify the Firmware?
       No, only logical Destruction needs to.


To customize your Physical Destruction solution, please feel free to contact Renice team, we are your reliable SSD partner. 


Contact information:

May Lau

Renice Technology Co., Limited
Add: Rm1101, Unit2, Block B, Kexing Science Park, No.15 Keyuan Rd,
Central Zone, NanShan High-Tech Park, 518057, ShenZhen, China
Tell: +86 0755 83258725
Fax: +86 0755 83257295
Email: may@renice-tech.com
Website: www.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