Is SpinRite not working or is SSD too far gone?

[Noswal]

Hi, I've been never been sure about using SR on a SSD and trying it last night seem to confirm worries

Showing pics attached, I started it about 11pm and went to bed with it saying it will take over an hour, this morning I wake up to find its somewhat stuck and several days to finish.
So per thread title is SpinRite not working correctly or is SSD too far gone? ssd is about 3 years old. In that its day to day use (has only Game files) there isnt any determent when playing/using it.

 

[ColbyBouma]

Would you be willing to share your log files? They are in the SRLOGS folder of your SpinRite boot drive. I recommend putting them in a ZIP file before uploading them here.

 

[PHolder]

As Colby suggested, there is probably useful information in your log files.

Since a SpinRite level 2 pass is mostly just a read pass (unless read problems are encountered and then data recovery would be attempted) this implies there is something with this drive that it is running really slowly while attempting to read the data. I see a bunch of command timeouts... that makes me wonder about your cabling. Perhaps as the drive warms up, there is a marginal connection or something. Try re-seating the cables.

It's also possible that there is some weird interaction with SpinRite and your drive's firmware. You could try launching SpinRite from the command line with the FORCEBIOS command parameter, this will slow SpinRite down a lot, but will make it use smaller buffers that could potentially be upsetting your drive in some way.

 

[Noswal]

Hi, thanks for answers. Here is log.

 

[ColbyBouma]

Here is log.

Thanks!

The big thing I wanted to check is "vendor-device", which is your disk controller. You have the same one as me, 8086-A102, so that's definitely not the problem.

The only other thing that stands out to me is that you're running Release 1. I don't remember if Steve changed anything related to this, but it's probably worth trying Release 4.

https://www.grc.com/upgrade.htm

I agree with Paul about trying FORCEBIOS. Hikvision is an uncommon SSD brand. It's possible their firmware doesn't play nice with SpinRite's default 32,768 sector transfers.

Command Line · Wiki · GRC Community / SpinRite 6.1 Wiki · GitLab

GitLab.com

gitlab.com

 

[Noswal]

Thanks, have redownloaded SR for rel 4. Its Friday morning now and work to do, so will only run it over night, tonight

 

[SeanBZA]

Hikvision is a rebadge, they generally are used in DVR applications, where the drive does not really do much error correction, and I think it will not really be fast either. Got Hikvision thumb drives, they are cheap, and for the intended application I have them, reading off DVR video, they are glacially slow, basically well suited to the low power processor in a DVR, which can just about handle the video streams in real time, and where USB is sort of allocated any spare cycles in the processor, so saving a file takes time. As a SSD they are optimised for writing, and for linear access, as that is the intended life, writing to block after block and then redoing it again, so the drive will happily lose an erase block and not care, and error correction failing just results in a bit of noise in a frame or three. Perfect for DVR use, and that is what they are aimed at.

 

[Noswal]

Hi, well I let SR rel 4 run, but same slow and incomplete after about 8 hours. I then tried the Forcebios command and it just froze per pic. So Im giving up on this drive with spinrite although it works fine on my other two hard disks.

 

[DanR]

I let SR rel 4 run, but same slow and incomplete after about 8 hours. I then tried the Forcebios command and it just froze per pic. So Im giving up on this drive with spinrite

Sadly there are limits to what SpinRite can do. This drive may be beyond those limits.

One thing you might try is: spinrite xfer X

Where X is any integer between 1 and 32,768. I note your latest log shows 32768 which this drive is absolutely refusing to accept. ForceBIOS uses 127. That did not work either.

So . . . I would say try something like xfer 16 or xfer 8 or xfer 4 (for example) to make SR as gentle as possible. Just for curiosity. Or not.

 

[ColbyBouma]

I note your latest log shows 32768

Something I forget is that Level 1 and 2 actually use a transfer size of 1,024. That field in the log shows the largest transfer size SpinRite thinks this drive can handle across all Levels.

https://grc.com/groups/spinrite.dev:55554

https://grc.com/groups/spinrite.dev:47760