Stuck on '0' for a very long while...

[AndreC]

Stuck on this

 

[Steve]

Hey @AndreC... Hmmm. That's not supposed to happen and unless I've missed other reports, yours is the only case of this. I assume that the white bar at the top of the screen is not moving at all? It's just sitting there? And the "spinners" on the vertical sides of the banner =ARE= spinning? Could you power down, reboot and try again? We have seen a few instances of transient misbehavior that did not repeat. Thanks!!

 

[AndreC]

@Steve you are correct in your assumptions... I did just tried to fully power down the system and reboot and still same issue.
Note that I am booting DOS622 using F8 to bypass some config drivers like himem.sys and some others.

Can't wait for SpinRite 6.1 ... have few drives that need to be recovered as one of them should still have my old bitcoin .. yep I too did not took care of them years back when they only worth few pennies... Right now those all give a BSOD on SpinRite 6 which I hope to be resolved in 6.1 with new code...

 

[AndreC]

@Steve I just tried with a different drive via hot swap and that other drive works... I can see the white bar moving and results coming in..

Is there any diagnostics I can run on my other drive to see why it is not working?

 

[AndreC]

 

[PHolder]

Looks like maybe your disk is very unhealthy and unwilling to be speed tested? It would be nice if flaky hardware didn't cause software fits, but if, for example, the drive just never responds to commands when it gets into trouble, that is likely to cause even the best written software to go wayward.

 

[AndreC]

Here are the logs.. The last one is interesting... it failed 0-75 but passed 100..

 

[AndreC]

im running again on some of those drives I just tested but this time with extra switches to enable verbose and sanity info.
I'll attach results here for you to look at if you need/want/like/feel bored

Would initdisk do anything to those drives that are not recognize properly?

 

[AndreC]

@Steve interesting development... I changed the BIOS from SATA to AHCI and tried again

 

[DanR]

Would initdisk do anything to those drives that are not recognize properly?

Nope! InitDisk is for removable drives, e.g. USB sticks. It is not for fixed drives such as these.

I would expect InitDisk to "see" these driives as fixed and not process them.

 

[AndreC]

After switching to AHCI I managed to run most of my disks here on that same machine

Some of them caused big dumps which I have attached here.

 

[Barry Wallis]

Nope! InitDisk is for removable drives, e.g. USB sticks. It is not for fixed drives such as these.

I would expect InitDisk to "see" these driives as fixed and not process them.

In fact, InitDisk requires you to remove and reinsert the USB to prove that it is removable. @Steve doesn't want to be responsible for accidentally formatting a non-removable disk.

 

[bertwin]

After switching to AHCI I managed to run most of my disks here on that same machine

Some of them caused big dumps which I have attached here.

Your logs show SATA errors. Could that suggest a faulty cable or port?

 

[AndreC]

Your logs show SATA errors. Could that suggest a faulty cable or port?

I've used the same cable(s) for all my tests and those that failed I tried a second time by swapping the drive/cable to see if that repeat and to eliminate the cable variable.
I have another dozen drives that I will be testing today.
I'm compiling a spreadsheet with my results.
Those with errors I can post the TXT if anyone need to look at them for further investigations.

 

[AndreC]

ok, as @Steve suggested, I did fully power down the machine between swaps and some of those drives that were not getting recognized or giving errors managed to work on the first pass. A second pass without full power cycle mostly failed as a second run of the RS command failed.