Tyler Erickson

@NavCC, Thanks for the feedback and I'm glad you like the tools! We are doing our best to keep up with the Github issues as well as the ones we...

Thanks for the logs @NavCC! And no worries on the delay. Looking at those outputs, that test of changing the namespace value didn't resolve it either. This also tells us...

Hello, Sorry to hear about these issues affecting your drives. Would you please reach out to Seagate customer support and reference the Ticket Number 11187884 for further support? You will...

Thanks for the update. As with any software or operating systems, please make sure you are running the latest version. The SeaChest tools were recently updated and the latest version...

The best advice I can give for configuring any new product before integration into a system is to do it from a Live OS (LiveCD or LiveUSB) to reduce the...

Thanks for the update and glad that worked! I want to leave this issue open a little longer as we have been doing a review of the code and some...

This took a little while to wrap up, but the earlier commits I tagged this issue in should further help mitigate the issue in case something were to happen in...

Well that is really weird. Changing the sector size is not guaranteed to leave any data recoverable, which is why SeaChest requires you to confirm that this will erase data...

@cfelicio, thanks for the additional information. I haven't tested this on Win11 yet myself, so maybe that affected this. I wouldn't think the earlier release would have affected this, but...

Hi @jeremywaguet, We can look into having the CI compile statically for the Windows build. The closed source SeaChest is built and released as static builds if you would be...