Tweet
We're running Disk test in BurnInTest V4 (1004) for 12 hours on systems just out of production and we get no errors.
When we're running the same test, same machine, not even rebooted, using BurnInTest V5 (1010) we get errors after a random amount of time. So far they are starting to show up after around 2-4 hours and continue to add up for as long as the test is running.
The latest test started at around 08:00 local time and the first errors started showing around 12:06.
The Event Log reports "Disk, /dev/nvme0n1p1: Test file could not be created...".
Since we had around 10 newly built production units we tested them all and they all passed the test using V4 but they failed the test using V5.
Since they are all brand new units I doubt it is a hardware error. Is anything changed in the way the tests are executed during the last couple of updates of V5? If I recall correctly we did not see these errors using build 1006 but on the other hand we did not test the exact identical systems so take that with a grain of salt.
When we're running the same test, same machine, not even rebooted, using BurnInTest V5 (1010) we get errors after a random amount of time. So far they are starting to show up after around 2-4 hours and continue to add up for as long as the test is running.
The latest test started at around 08:00 local time and the first errors started showing around 12:06.
The Event Log reports "Disk, /dev/nvme0n1p1: Test file could not be created...".
Since we had around 10 newly built production units we tested them all and they all passed the test using V4 but they failed the test using V5.
Since they are all brand new units I doubt it is a hardware error. Is anything changed in the way the tests are executed during the last couple of updates of V5? If I recall correctly we did not see these errors using build 1006 but on the other hand we did not test the exact identical systems so take that with a grain of salt.
Comment