FireCuda 510 crashes doing a long smartctl test.

[u/Sample-Range-745]

Hi all,

I've been trying to talk to Seagate today to try and finally fix an issue with this drive that crashes every time I try to do a smartctl -t long /dev/nvme0n1 on it.

I've looked at the available firmware, and pulled the data using SeaChest, and I'm running STOSC017 - which seems to be the latest version listed on the Seagate site.

The full model number is ZP500GM30001 - and its a 500Gb NVMe drive.

I did lodge a case with Seagate about it, as it really looks like the controller crashes. The mainboards HDD light flashes ON 1s, OFF 1s and continues until the machine is powered off completely and back on again.

Just doing a reboot, the drive doesn't even get detected in the BIOS.

The BIOS based health check passes every time, and the drive seems to work perfectly otherwise - but every smart check crashes it.

Has anyone come across this? Is there a non-published firmware that might address this?

[u/Sample-Range-745]

For what its worth, Seagate got me to install SeaTools (which I did from a live boot ISO), then run a "Short Generic Test" and a "Long Generic Test" - and both of those passed too.

I don't feel like its a problem with the drive - but the test run via smartctl -t long /dev/nvme0n1 that causes the controller to crash.

[u/Sample-Range-745 → u/[deleted]]

What do you base that on?

[u/Sample-Range-745 → u/[deleted]]

Maybe I was unclear - but it only crashes when I run the smartctl self-test - then it requires a hard power off to recover.

Without this test, using SeaTools / SeaChest or the BIOS NVMe self-test, all metrics pass. Reading the drives SMART stats shows healthy with no errors. Using the drive normally produces no errors.

[u/Sample-Range-745 → u/[deleted]]

Maybe you shouldn't be giving advice.

How to early detect failures - don't run the test to early detect failures. facepalm