Spinrite 6.1 Release 4 hangs on defective SD Card sector but operates differently if restarted before hang

[excel]

I am running 6.1 version 4 on a 256GB SD card attached via a USB adapter. Valid drive reports three areas with red, indicating no storage. It reports the drive size as 63.9GB.

1) I run Spinrite from 0 or 23%. Spinrite reports a bad area starting ~23.2% in. At this point I cannot stop spinrite via the menu - it is non-responsive. It will continue for days with little progress. The only recourse is to reboot. Note: Spinrite responds to the escape key and stop, but never stops or exits.

2) I reboot the PC and run Spinrite at 23%. Before it stops at the bad sector, I exit Spinrite to the menu or to dos. I restart Spinrite at 23%. Spinrite reports one bad "dot" and then continues through the rest of the drive without any issues.

3) I have reformatted the drive and filled it with data several times. On the first try, Spinrite reported a series of "B" blocks starting at 23%. Unfortunately, I do not have a snapshot of that run. However, on recent runs, it never gets past the first bad "B" block on a clean reboot.

I filled the drive with data just to see if the files were really bad. Checksums confirmed that many copied files had the wrong checksum.

I have replicated this process several times and it is repeatable except for the initial 3). I do not trust either result since Validrive reports three "no storage" areas, but Spinrite either 1) never completes or 2) only reports one bad area. I have also run Spinrite on several different computers and verified memory for a while. Same results.

Suggestions?

 

[DanR]

1) ValiDrive has confirmed this drive to be fake.

2) Both ValiDrive and SpinRite have found serious issues in the 64GB NAND chip at the front of the drive

3) This is a fake drive made with a defective 64GB NAND chip masquerading as 256 GB. It is way beyond SpinRite's ability to fix it.

This drive is worthless junk! Please throw it away.

Please get yourself a good legitimate drive.

 

[excel]

DanR, apologies for the confusion. The issue is not the drive - I understand that is it not valid.

The issue I am concerned about the different behavior of Spinrite when it is run from a clean boot vs. being restarted after boot.

 

[PHolder]

different behavior of Spinrite

You're expecting repeatable behaviour from a broken drive? How do we know that the problem you're experiencing is not being caused by whatever defective firmware is loaded in the drive? IMHO, It doesn't seem worth any further time investigating.

 

[DanR]

The issue I am concerned about the different behavior of Spinrite when it is run from a clean boot vs. being restarted after boot.

Ahhh . . . Ok. Got it. I still believe the problem is the defective and fake drive and not SpinRite.

I'm thinking that perhaps SR is encountering a problem just before 23% that stops it dead in its tracks. But starting at 23.0000 % is just past the problem spot?

Maybe start a run at 22.0000 % and see what happens? It may or may not show anything useful depending on what the hacked firmware may be doing.