Closed An experimental test release (SRPR-EX1)

  • 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.)

Steve

(as in GRC)
Staff member
Feb 1, 2019
905
1,252
69
Southern CA, USA
www.grc.com
SpinRite has still been stumbling when it encounters drives that are in very bad condition. In every case, their owners already know that the drive in question is no longer useful — other than to test SpinRite. So we all want SpinRite to do the best thing possible, even with seriously troubled drives.

I spent the day carefully watching the error return codes from Western Digital and Seagate drives. What I learned has been incorporated into an experimental test release of SpinRite: “SRPR-EX1.EXE”. I haven't published it yet as a pre-release because it's really only of any use or interest to anyone who has a drive that's been stumping SpinRite — meaning it believes that the drive has gone offline or into Device Fault status when it apparently hasn't.

So, if you're interested, you can obtain this experimental release the usual way, by going to GRC's /prerelease.htm page, entering your SpinRite serial number, and obtaining single-use links. HOWEVER, rather than clicking on the link for the DOS "SRPR-EXE" you must COPY the link, paste it into your browser's URL field, then edit the filename to: SRPR-EX1.EXE which will deliver this test release to you.

If it does anything different, good or bad, I'm all ears! Thanks!!
 
  • Like
Reactions: markav2
I ran it on the same 3TB drive and it stopped at the same spot. No keyboard or mouse input locked up. This drive doesn't have any problems.
 

Attachments

  • 3tbSC-EXT.jpg
    3tbSC-EXT.jpg
    150.3 KB · Views: 72
I ran it on the same 3TB drive and it stopped at the same spot. No keyboard or mouse input locked up. This drive doesn't have any problems.
We're now at pre-release 5.05 and, so far, everyone has been reporting that places where previous releases got into trouble, SpinRite is now successfully plowing through. So... Could you give the current release (5.05) a spin?? Thanks!!
 
We're now at pre-release 5.05 and, so far, everyone has been reporting that places where previous releases got into trouble, SpinRite is now successfully plowing through. So... Could you give the current release (5.05) a spin?? Thanks!!
Ran 5.05 on a 120GB drive with errors. It didn't finish, stop about 70% trying to repair a bad sector. Keyboard quite taking responses and it's locked up. Now I'm running 5.05 on the good 3TB drive again to see if stops again on level 4.
 
Ran 5.05 on a 120GB drive with errors. It didn't finish, stop about 70% trying to repair a bad sector. Keyboard quite taking responses and it's locked up. Now I'm running 5.05 on the good 3TB drive again to see if stops again on level 4.
Ran 5.05 on 3TB level 2 and finished with no error. Ran it again at level 4, didn't finish and quite taking response and locked up sooner then older version.
 

Attachments

  • 3tbSC-505.jpg
    3tbSC-505.jpg
    190.5 KB · Views: 61
Hmmmmmm.... Did the little graphic “spinner” in the upper right corner stop spinning? ... or did it continue with its animation? And how are these drives connected to the machine? Are they connected via USB? Or parallel IDE or serial SATA cable?

Thanks!!
 
Hmmmmmm.... Did the little graphic “spinner” in the upper right corner stop spinning? ... or did it continue with its animation? And how are these drives connected to the machine? Are they connected via USB? Or parallel IDE or serial SATA cable?

Thanks!!
Yes it stop spinning. Using a old Asus, intel P4 with 2gb of ram. The 60gb and 120gb are connected directly with IDE. Both have problems. The 3tb is connected directly with SATA cable. No problems with hard drive, it will finish on level 2 but will NOT on level 4. I haven't tried my 10tb since the first time I got 6.1,
 
@sweeney746: The graphical “spinner” is driven by the lowest-level hard interrupt system. It's the most "reliable" indicator of "life" in the system. I asked about USB connectivity since USB uses the BIOS and some USB BIOSes deliberately disable hardware interrupts during drive error recovery... so we sometimes see the “spinner” pause its spinning then resume.

But you're seeing this total freeze up on two different non-BIOS drive technologies, parallel IDE and SATA. That means that SpinRite's own native drivers are being used and that SpinRite is never handing over control to the BIOS. And SpinRite never disables hardware interrupts.

Is there any way you could try doing what's causing the hang on that machine — on any other machine?

I dislike pointing fingers elsewhere, since that's not the way to find every problem. But so far, we don't have any other reports of any sort of hang like this, despite many people also running SpinRite over their very troubled drives. So the wildcard is that old Asus Pentium 4 machine.

If you can get a different machine to hang, then it's likely not the machine — it's SpinRite. But if SpinRite running on a different machine on the same drives doing the same thing never hangs, then I think that narrows the trouble down to that P4 machine.

Thanks!!!
 
@sweeney746: The graphical “spinner” is driven by the lowest-level hard interrupt system. It's the most "reliable" indicator of "life" in the system. I asked about USB connectivity since USB uses the BIOS and some USB BIOSes deliberately disable hardware interrupts during drive error recovery... so we sometimes see the “spinner” pause its spinning then resume.

But you're seeing this total freeze up on two different non-BIOS drive technologies, parallel IDE and SATA. That means that SpinRite's own native drivers are being used and that SpinRite is never handing over control to the BIOS. And SpinRite never disables hardware interrupts.

Is there any way you could try doing what's causing the hang on that machine — on any other machine?

I dislike pointing fingers elsewhere, since that's not the way to find every problem. But so far, we don't have any other reports of any sort of hang like this, despite many people also running SpinRite over their very troubled drives. So the wildcard is that old Asus Pentium 4 machine.

If you can get a different machine to hang, then it's likely not the machine — it's SpinRite. But if SpinRite running on a different machine on the same drives doing the same thing never hangs, then I think that narrows the trouble down to that P4 machine.

Thanks!!!
Just ran the IDE 120gb on an old ASUS AMD. A different computer didn't help. It errored at the same spot. I'm run the IDE 60gb now. I will run the 3TB an ASUS PK5 with 8gb of ram in a couple of days. It's in the process of recovering the 10TB files after it failed.
 

Attachments

  • 120GB-505.jpg
    120GB-505.jpg
    208 KB · Views: 60
  • 120GB-505error.jpg
    120GB-505error.jpg
    225.3 KB · Views: 62
@sweeney746: I'm worried that we may be talking about different events and behavior. When you say:
Just ran the IDE 120gb on an old ASUS AMD. A different computer didn't help. It errored at the same spot.
THAT is exactly what I would expect when you ran the same drive on a different computer. THAT red dialog showing that the drive has done offline is a problem that we would expect to “follow the drive” no matter where you run in.

The “try it on a different computer” issue I was referring to was the “total freeze” of SpinRite that you previously described. Did THAT happen at any point or time on this other machine?? Thanks!!
 
  • Like
Reactions: Rouslan