Date: Fri, 29 Mar 2024 10:05:32 +0000 (UTC) Message-ID: <378660635.8492.1711706732572@support.blancco.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8491_1397114699.1711706732572" ------=_Part_8491_1397114699.1711706732572 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There have been some issues w= ith some Smart Array/CCISS RAID controllers where the erasure verification keeps failing (for examp= le: SmartArrayP800). The erasure process itself is completed normally,= but the erasure result verification part fails.
The problem is related to one of= the controller=E2=80=99s settings called the surface scan delay. This sett= ing is the time interval before surface scan analysis activates (possi= ble values from 1-30 sec.). This time does not begin counting until th= ere are no commands being sent to the controller. Surface scan analysi= s is a background process that scans hard drives for bad sectors in fault t= olerant logical drives. In RAID 5 or RAID ADG configurations, surface = scan also verifies the consistency of parity data. Whenever the e= rasure part is completed, the surface scan is activated during the verifica= tion part and the controller starts writing some meta/RAID data on the= drives. This naturally provokes the verification failure and subseque= ntly the whole erasure process failure. Unfortunately, the surface sca= n cannot be disabled nor delayed more than 30 seconds.
If you happen to have a HP Smart Arra= y RAID controller that presents this problem, before booting Blancco, remov= e manually all of the RAID logical array configurations.Boot Blancco 5 and = follow the normal erasure procedure. Some HBAs will create (a) logical arra= y(s) automatically during boot if they find unassigned physical disks which= don't belong to any RAID array. That automatic creation has to be manually= skipped by pressing ESC (this key press might vary, see hardware=E2=80=99s= documentation for more info) to prevent the problem from happening again.<= /span>