FYI SpinRite's Development Roadmap

[PHolder]

I guess I'll be waiting.

Well the trick is that the ONE specific page https://dev.grc.com/users/sign_up is protected with old style HTTP Auth protection. It needs a specific hard coded userID and password, which Steve has requested stay only listed on the Newsgroup. (If you don't provide it, you will receive an error: 401 Authorization Required
nginx )

So the ideal solution is to join the newsgroup, which is not always a trivial experience, but you can start that at https://www.grc.com/discussions.htm

 

[Ron_Arad]

Following your description in Ep 912 of 6.1 crashing on certain disks, I ran 6.0 today on a 2013 HGST 1TB drive from 2013 and spinrite crashed while doing a level 2 scan (at 80% along the 2nd partition which is 850G in size),
see attached. The drive was connected via a USB3 station (Blueendless HD05), hope this is informative and useful.

 

[Dagannoth]

Following your description in Ep 912 of 6.1 crashing on certain disks, I ran 6.0 today on a 2013 HGST 1TB drive from 2013 and spinrite crashed while doing a level 2 scan (at 80% along the 2nd partition which is 850G in size),
see attached. The drive was connected via a USB3 station (Blueendless HD05), hope this is informative and useful.

Steve has already fixed the 6.0 crashes in 6.1. How does 6.1 Alpha 21 handle that drive? You'll have to connect it to a SATA port since Alpha 20 limits BIOS drives (USB, SAS, NVMe, RAID, etc) to 137 GB due to the discovery of a severe memory corruption issue in multiple BIOSes.

 

[PHolder]

hope this is informative and useful.

In general Steve has explicitly said he is NOT receiving SpinRite feedback for development versions here in these forums. The only place he wants to receive such feedback is on his newsgroup which has information and links for a specific GIT wrapper for opening report tickets. If you are interested in being involved at that level, start by going here: https://www.grc.com/discussions.htm (Read the instructions carefully.... and Steve's newsgroup server is currently having an issue with secured connections, so you'd need to configure your reader to not use them.)