2.2 TB Boot Test
This test checks the consistency of the reported disk size in a preBoot and a Windows environment.
The drive size reported in the preBoot environment should exactly match the drive size reported in Windows. Because the preBoot device driver is different from the Windows device driver, the test must check for consistency of the reported drive capacity in order to ensure that disk accesses do not encounter problems caused by a variance in the reported sizes.
Test details
Associated requirements |
Device.Storage.Controller.BootDeviceGreaterThan.BasicFunction |
Platforms |
Windows 7 (x64) Windows 7 (x86) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2 |
Expected run time |
~10 minutes |
Categories |
Certification Functional |
Type |
Automated |
Running the test
Before you run the test, complete the test setup as described in the test requirements for the type of storage controller that you are testing: Storage Adapter or Controller Testing Overview.
Before starting the test, you must first ensure that the boot drive is attached to the test adapter and on a machine that supports Secure Boot where Secure Boot is disabled. In Windows, the test configures the boot configuration to boot into a preOS environment during the next reboot to run the test cases. The computer reboots to the preBoot environment to allow the preBoot test cases to run. When the test cases are finished, the computer reboots back to the Windows environment to collect the logs and determine the test results.
Troubleshooting
For troubleshooting information, see Troubleshooting Device.Storage Testing.
Mismatch in preOS and Windows last block error
The test ensures that these two values are the same. If they are different, there may be an error. Before the test restarts the machine to run the preBoot test cases, it allocates space in a file for the results from the preBoot test cases. This file is initially empty, but is filled by the preBoot test cases. If they do not run however, the file will remain empty and when it is compared against the size from windows it will report this error. The root cause is that the preBoot tests did not actually run because some component prevented them from executing. BitLocker has been observed to cause issues with running preBoot content and should be disabled before running the test.
Could not disable the integrity check. 0xc0430002 or Could not add the preos tool to the bootsequence. 0xc0430002
This indicates that some component is preventing the preBoot application from being entered into the boot sequence. It is usually caused by having Secure Boot enabled. Disable Secure Boot and run the test again.
More information
Command usage
| Command | Description |
|---|---|
TwoTBBootTest.exe /device “[DiskDeviceObjLink]” |
Configures the preBoot environment. DiskDeviceObjLink example: \\.\PhysicalDrive0 |
TwoTBBootTest.exe /createlogs |
Generate the log files. |
Note
For command-line help for this test binary, type /?.
Command syntax
| Command option | Description |
|---|---|
TwoTBBootTest.exe |
The command line options for the test are listed below. |
/nc |
Do not clean up the folders and BCD objects created by the tool. This switch can be used for debugging purposes. |
/createLogs |
The tool needs to be run with this switch after the preOS tool has been run to create wtt log files. |
/device |
The boot device containing the boot drive to be run against. |
File list
| File | Location |
|---|---|
TwoTBBootTest.exe |
<testbinroot>NTTest\BaseTest\boot\TwoTBBootTest\ |
TwoTBBootTest.wim |
<testbinroot>NTTest\BaseTest\boot\TwoTBBootTest\ |
TwoTBBootTestPreOS.efi |
<testbinroot>NTTest\BaseTest\boot\TwoTBBootTest\ |
TwoTBBootTestPreOS.exe |
<testbinroot>NTTest\BaseTest\boot\TwoTBBootTest\ |