v0.7 - Inconsistent results

[JLBrocx]

Hey mate - Overall great update with v0.7 - UI is much improved and it seems the previous issue I had is resolved.

However I did notice that I got some inconsistent results with one of my devices. It's quite possible something odd with this drive as it doesnt seem to happen to other ones but as it's consistently reproducible, thought i'd raise it.

If i format it with Windows, then it "fails" the test. If I run the test again then it will succeed.

Video below showing me reproducing it.

https://github.com/user-attachments/assets/b06cb0df-ffdc-41b5-87be-c097a6f9df45

[c0xc]

Thanks, I'm glad you find the new UI better than the old one.

What happens if you run a full test (select, then next instead of quick start)? It should tell us a bit more.

Also, there are two things you could try. After formatting, when you select it and click next, it should list that one newly formatted filesystem at the bottom. You could try to A) unmount it explicitly right before starting the test or B) remove the filesystem to really make sure nothing is trying to access it at the wrong time. For option A, select the storage, hit next, there should be an unmount button at the bottom if it's been detected. Try that first (I'm curious, even though unmounting isn't really a concept on Windows it'll just temporarily "disconnect" it). For option B, select the storage but don't just yet hit next, open the menu above the list on the right, go to the format tool, first option there is to clear the partition table, do that.

[JLBrocx]

Thanks for your reply. I was still to replicate it this morning even with a full test (see attached below) however it seems after clearing the partition table it's resolved it for this drive. Cheers

https://github.com/user-attachments/assets/8991835c-d6b4-4c36-9fd2-d53c3855845b

[c0xc]

Thanks for the feedback, I'm glad it works for you now, after clearing the partition table.

I'm still thinking it might be some OS lock The result text I'm showing in this case is unfortunately too generic (I did add a couple of error types but when it happens at this early stage, they're not shown here). What you could do if you were really curious (other than wait for a new minor release) is start the program with a certain environment variable set which will enable logging. But it looks like this is Windows, it's probably not worth the trouble.

I'll leave this open for now. There's some other minor thing I'll have to add too, so chances are there's going to be another minor release in the near future.