NVME DST test fail on new computer

[Curtc]

I have a less than a week old HP Envy 13, bought HP refurbished, running Linux Mint 18.3 / Cinnamon.  The last several days Chrome has been highly unstable, crashing left and right on Google apps gmail, calendar, etc. and other places as well that never had issues before.

I thought perhaps there was a RAM issue with this machine, so booted into the HP Diagnostics.  Memory tests didn't indicate any issue, but the HD test claims to fail, excerpts from test logs are below.  HP Support immediately said "Bad hard drive send it in for replacement".  I'm not necessarily buying that.  the NVMe has 52 power cycles and 126 power on hours according to its smart log.  Aside from the above weirdness with Chrome, I haven't had any other issues.  To me, it looks like the self test routines are bugged for this late 2017 model notebook with a nvme ssd.  But I'd love to hear opinions before I lose a ton of my time shipping this back to HP for unclear results, and have to spend many hours setting it up from scratch again.

2018-03-07 19:36:55 [L]> Loaded NVMe PciIo: Location(Seg:0,Bus:4,Dev:0,Func:0), BAR(0x00000000A4000000).
2018-03-07 19:36:55 [L]> NVMe Controller Version: 1.2
2018-03-07 19:36:55 NVMe device connected at NamespaceID 0x1
2018-03-07 19:36:55 Device Node NVMe(0x1,00-00-00-00-00-00-00-00).

2018-03-07 19:36:55 HDD 0 Model : INTEL SSDPEKKF512G7H
2018-03-07 19:36:55 HDD 0 Firmware: HP01

2018-03-09 03:33:52 Hard Drive Quick Test Selected
2018-03-09 03:33:52 No USB Hard drive detected.
2018-03-09 03:33:52 Estimated Total Time Required = 123s
2018-03-09 03:33:52 SMART Check Started
2018-03-09 03:33:52 SMART Check Completed - Result 1
2018-03-09 03:33:52 Short DST Started
2018-03-09 03:33:52 NVMeSendSelfTest(): DST Test not in Progress
2018-03-09 03:33:52 NVMePassThruStartDST(): Sending SELF-DST Success
2018-03-09 03:33:52 NVMeCheckSelfTestDone(): DST Result Not Found.
2018-03-09 03:33:52 NVMeCheckSelfTestDone(): Status = Device Error
2018-03-09 03:33:52 NVMeSendSelfTest(): DST Test not in Progress
2018-03-09 03:33:52 NVMePassThruStartDST(): Sending SELF-DST Success
2018-03-09 03:33:52 Short DST Completed - Result 3
2018-03-09 03:33:52 Error Code=0x303
2018-03-09 03:33:52 Short DST Completed - Result 3
2018-03-09 03:33:52 Device path: PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-00-00)
2018-03-09 03:33:52 0 0 23 0
2018-03-09 03:33:59 Hard Drive Quick Test Completed

[CherylG]

@Curtc

I am not very familiar with Linux-other than playing with a LiveCD here and there- but I'm sure there are Disk Imaging tools for it just like Windows. Make a backup Image saved on usb hdd or large flash drive and send it in for a new ssd. Restore the Image and you are setup just like it is now.

[Curtc]

I'm well aware of disk imaging, thanks.

[CherylG]

Sorry-I was assuming otherwise due to the statement :

 But I'd love to hear opinions before I lose a ton of my time shipping this back to HP for unclear results, and have to spend many hours setting it up from scratch again.

[Curtc]

I found my Chrome crash issue, zero-copy rasterizer was turned on in chrome://flags  

Turning that off put Chrome back to rock solid condition

[Curtc]

I found that there is an Intel SDD Toolkit for the NVMe drive, booted Windows and did the comprehensive test.  Passed.

Also found that HP has a Windows based test suite, installed that, and the disk test also Passed.  Took all updates including the UEFI test updates, BIOS, etc.  Then retested the F2 menu diagnostics again, still immediately fail with a DST 0x303.

I think this is all fairly conclusive evidence that the F2 menu built in disk tests are bugged and report a false positive.

[CherylG]

I have seen F2 act flaky and give erroneous reports- but usually just the opposite where it passes a failing hdd. Happy you are now more confident in the tests you have run. My thoughts were something had to cause that laptop to be sent back and then refurbished and sold. With only a 3 month warranty on refurbs I would keep close check on it.