Secure erase compatible SSDs before every shoot. Block Erase is a function enabled only in SATA SSDs. It speaks to a Secure Erase and mentions a variety of memory array cell functions. Now when I power on the system it just says "No bootable device found". 2.5 HDDs that were previously used with our legacy products might still be compatible from a form. OK, there are likely weaknesses in my understanding and/or explanation but this paragraph from the HP paper linked below is interesting.
Help - Sandisk SSD not recognized after Secure Erase. And no solution out there, seems nobody else has a bios with this kind of limitations. To boot from the E2B USB drive, first configure the BIOS for Legacy booting from a USB drive. The bios seems to have a crazy limitation there's just no option to choose between uefi or legacy boot, no bootable devices are visible and I've tried everything, searched and tried different solutions, enable/disabled secure boot, set supervisor password, bios to factory reset but nothing. I then tried using diskpart to clean the usb and tried again still nothing, then I did same to the emmc 32gb drive (which worked for others with similar problems) which just made things worse because the drive was no longer visible in f12 boot options nor in the bios. I tried creating onother bootable, using rufus to convert usb from mbr to gpt in fat32 format all to no avail, the usb was no longer showing up in f12 boot options.
Sandisk secure erase legacy windows 10#
The installation using usb bootable windows 10 started working but would stop half way through saying "error, some installation files missing". Fixed bugs related to firmware update/Secure Erase or Sanitize using USB bootable drive if BIOS is set to legacy mode. Using third-party data recovery tools they were. I had similar issue reinstalling Windows 10 and had to format the partitions. Our in-house test lab have reported a 240GB SanDisk SSD can be wiped using BLOCK ERASE in around 10 seconds.