Tyler Erickson

Hi @yaarith, The current method is due to how we've interacted with different customers in the past and had binaries shared directly back to Seagate. This has been changing over...

Hi @yaarith, I have merged @Rungthida's code into develop. We had a miscommunication, but it is now on develop in both openSeaChest and openSeaChest_LogParser. Let us know if you have...

Hi @helpfirmy, Can you share the command line you are using? And which OS you are attempting the update in? Also, if you capture the verbose output to a file...

HI @TheOddball, Seagate drives do not allow switching between OEM and customer firmwares or visa-versa. It is possible that if the drive was SED locked, that was the reason you...

Thanks for the verbose output. This is very similar case to what I looked up on Seagate/ToolBin#22 with another product with IBM firmware. I checked with the firmware lead and...

Would you be willing to open a discussion, either here or on Seagate/ToolBin? Discussions can be useful for questions that may not directly relate to the software project and can...

Hi @yaarith, We have had some discussion about adding json output to our tools and what it should look like. I'll check our project schedule to see where we can...

Hi @atokje, If I understand this correctly, pass-through support on Seagate USB products with UAS support is blocked by the Linux kernel, so it is not possible to issue the...

Hi @jerrywoo96, The `--setSectorSize` option is only for SATA and SAS devices. For reformatting an NVMe device, you need to use the `--nvmFormat 4096` option. Also, Microsoft does not allow...

Hi @jerrywoo96, >what is the correct command to check the progress? That is the correct command, but it appears that is a bug in openSeaChest_NVMe. I just verified that it...