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

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

AndreC

Member
Oct 6, 2020
11
1
IMG_5098.jpg
Stuck on this
 
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!!
 
  • Like
Reactions: 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...
IMG_5099.jpg
IMG_5100.jpg
 
@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?

IMG_5101.jpg
 
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.
 
  • Like
Reactions: AndreC
Here are the logs.. The last one is interesting... it failed 0-75 but passed 100..
 

Attachments

  • RS006.TXT
    793 bytes · Views: 364
  • RS001.TXT
    753 bytes · Views: 363
  • RS002.TXT
    793 bytes · Views: 355
  • RS003.TXT
    793 bytes · Views: 361
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?
 
@Steve interesting development... I changed the BIOS from SATA to AHCI and tried again
 

Attachments

  • RS015.TXT
    1.5 KB · Views: 353
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.
 
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.
 

Attachments

  • RS012.TXT
    5.7 KB · Views: 366
  • RS010.TXT
    2.5 KB · Views: 370
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.
 
  • Like
Reactions: AndreC and DanR
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?
 
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.
 
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.