Drive Eraser 6.11 and Configuration Tool 2.11 - Release notes

Highlighted features:

• ALBUS-4829, ALBUST-553 - Limit the maximum amount of simultaneous erasures (a.k.a. "Batch Erasure").
  • In a nushell, 100 drives can be erased in e.g. 2 batches of 50 drives, 5 batches of 20 drives or any other combination.
  • The operator should simply select the drives to erase, set the maximum amount of simultaneous erasures and run the erasure, the rest will be handled automatically.
• ALBUS-6600 - Faster NIST Purge on large HDDs.
  • The "NIST 800-88 Purge" standard has been optimized on HDDs and the erasure duration can be divided by 6 on some drives.
• ALBUS-6641, ALBUST-558 - Configurable threshold on drive speed to fail the erasure.
  • BDE can be configured to fail the erasure if the erasure speed is slow and below a set threshold.
• ALBUS-6628 - Per-drive custom field values can be filled in through a job specification.
  • This achieves sending e.g. an Asset ID per drive from the Asset Management System to BDE and keeping the report information complete.
• ALBUS-6491, ALBUST-539 - Enable the Two-Way Communication on BDE HW Images.
  • The 2WC is now possible on BDE_HW images that are meant to be permanently installed on an erasure station.
• ALBUS-6385 - Support for TCG Cryptographic Erasure on SCSI/SAS drives.
  • The Trusted Computing Group is an organization that develops open standards for trusted computing platforms.
  • BDE's "NIST 800-88 Purge" erasure standard supports both the TCG Opal Crypto Erase and the TCG Enterprise Crypto Erase commands on SCSI/SAS drives.
• ALBUS-6642 - Blink all drives with one button.
  • All connected drives can be located (blinking their LED) with one button in the BDE UI to achieve an easy physical identification.
• ALBUS-6678, ALBUST-572 - Spin down idling HDDs.
  • Any HDDs that is idling (not being erased, already erased, queued, etc.) can be spun down (they stop rotating) after 5 minutes of inactivity.

Improvements and bug fixes:

• ALBUS-6792 - In some occasions, the remapped sectors were not being detected properly and the remapped sectors count was missing from the BDE UI.
• ALBUS-6714 - The booting parameters that have been used to boot BDE are now reported.
• ALBUS-6026, ALBUS-6244 - Pressing the "Refresh Drive List" button duplicated the list of currently detected drives in some environments.
• ALBUS-6211 - The erasure got stuck at some point on some SSDs such as WD Green SSD M2 or SanDisk SSD Plus.
• ALBUS-6761 - The estimation of the erasure duration has been improved on erasures executing the TCG Crypto Erase command.
• ALBUS-6684 - The wireless adapter "Intel(R) Dual Band Wireless AC 8260" failed often with the error "unknown network error".
• ALBUS-6632 - Sanitize (purge) commands failed on drives connected to HP Smart Array RAID controller P410 and P420.
• ALBUS-6517 - Some erasure settings were not stored between appliance boot-ups.
• ALBUS-6254, ALBUS-6613 - Inputting data in custom fields (remote control) was not possible in some cases.
• ALBUS-6519 - The connection with the embedded BMC was not established automatically after HW appliance was booted.
• ALBUS-6644, ALBUS-6793, ALBUS-6746 - In some server environments, the mouse was not visible in the UI.
• ALBUS-5889 - The maximum or nominal processor speeds were sometimes detected as being 0Hz.
• ALBUS-6774 - Some exceptions related to verifications and thresholds were repeated in some corner cases.
• ALBUS-6627, ALBUS-6553 - Erasure or verification were failing on drives connected to LSI controllers.
• ALBUS-6512 - The printer settings were visible even if the BDE_HW installation had an external BMC.
• ALBUS-6468 - BDE_HW could not be installed on logical drives.
• ALBUS-6313 -The auto-backup messages in the UI have been rephrased.
• ALBUS-6547, ALBUS-6548 - Drives disconnected during the erasure or verification were failing without any clear reason or could crash the software.
• ALBUS-6750 - Adding detection for a new hybrid drive.
• ALBUS-6711 - The battery "socket" icon was not shown on Apple MacBooks.