SpinRite 6.1 Release 2 crashing

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

Drencor

Member
Mar 4, 2024
6
0
I am running Release 2 of SpinRite 6.1 on a Cisco C220M4 Server that I acquired to use here at home.
I have been using level 3 to refresh the drives, but keep crashing on one specific drive that might be having issues.
The drives in this server are SAS.

Screenshots of the crashes attached.
IMG_4264.jpg
IMG_4263.jpg
 
Last edited:
@Drencor: Since SpinRite v6.1 is well past release candidate now, so you should definitely be running the final SRv6.1 release (which is now at post-release release #2 with release #3 coming before long.)

And if this still happens under the release releases of SpinRite, I'd definitely love to see screenshots! Thanks!!
 
@Drencor: Since SpinRite v6.1 is well past release candidate now, so you should definitely be running the final SRv6.1 release (which is now at post-release release #2 with release #3 coming before long.)

And if this still happens under the release releases of SpinRite, I'd definitely love to see screenshots! Thanks!!
Ok let me see if I can download the current 6.1 then.
 
I was incorrect. It wasn't RC2. It is Release 2 that I had downloaded on the 12th.

I just re-downloaded it and am running it again on the same drive just to make sure though, but the screens match between the March 12th one and the one I just downloaded as far as the S/N and my name plus the Release 2 part.
 

Attachments

  • IMG_4287.jpg
    IMG_4287.jpg
    164 KB · Views: 63
Last edited:
Screenshots of the crashes attached.
The images on that post didn't come through. This forum is finicky about images. I think the size limit is around 500 kB.

the screens match between the March 12th one and the one I just downloaded
Right-click on them, go to Properties, then Details. The current "File version" is 6.1.8824.0.
1711415277431.png
 
@Drencor: Since SpinRite v6.1 is well past release candidate now, so you should definitely be running the final SRv6.1 release (which is now at post-release release #2 with release #3 coming before long.)

And if this still happens under the release releases of SpinRite, I'd definitely love to see screenshots! Thanks!!
Drencor_SpinRite_20240312.jpg
IMG_4293.jpg
 
Just to provide a little information as far as CPU on this system:

This system has:
2 x Intel Xeon E5-2650 V3
192GB RAM
 
192GB RAM
Wow... a nice bunch of RAM on that machine! The only thing I can think to suggest is to try re-creating the boot drive using another drive. I will be adding additional internal integrity checking to SpinRite with the next release update, but it's not there yet. At this point, yours is the only instance of Illegal Opcodes that we've seen in quite some time. Thanks!
 
Wow... a nice bunch of RAM on that machine! The only thing I can think to suggest is to try re-creating the boot drive using another drive. I will be adding additional internal integrity checking to SpinRite with the next release update, but it's not there yet. At this point, yours is the only instance of Illegal Opcodes that we've seen in quite some time. Thanks!
Yes that is a lot of RAM, but thankfully I didn't have to pay for it. Got to love when businesses dump off old hardware right when support for the product ends. :) Otherwise I know RAM reports as good as I ran MEMTEST86 on it. :D

I have SpinRite Release 2 on 3 different USB FlashDrives of different brands and sizes.

The last dump was the 64GB FlashDrive that I used. The first dump was from a 16GB and 32GB drives respectively.

I guess I could try booting off of the ISO image version via my IODD device and see if that makes any difference.

The only down side of the ISO is don't get the logs, but then again I guess when it crashes like it has been it hasn't been saving logs anyway. I will try the ISO after the scan on the current drive finishes. Which I am running Level 3.
 
Last edited:
If you've already seen this occur on two or three different boot drives (I didn't know) then I'm disinclined to think that's the trouble — assuming that the signature on your downloaded SpinRite is shown as good.

The three crashes you have shown all look “sane”. They all show the same operating segment (2D47) for the code, data and extra segments but the locations where SpinRite encountered itself attempting to execute illegal opcodes is all over the place, at: 00B0, 5E06, and 2EC1.

And this brings me back to that first line you wrote:
I am running Release 2 of SpinRite 6.1 on a Cisco C220M4 Server that I acquired to use here at home.

At this point, given that you are the sole user reporting any attempts of SpinRite to execute illegal opcodes, and this this is occurring on a “Cisco C220M4 Server” with SAS drives, the most reasonable conclusion would be that the system is not sufficiently PC Compatible to run SpinRite. I don't know why or how. It feels like something the machine is doing is altering some registers during some hardware interrupt or BIOS call that SpinRite doesn't expect to have altered.

But whatever is going on with that machine, SpinRite cannot run on it as is. And, the nature of the problem prevents me from diagnosing it remotely. There's just no way to know what's happening. So the conclusion needs to be that, close to a PC as that Cisco server may be, it's not sufficiently PC compatible in some (unknown) aspect of its behavior to run SpinRite... and I cannot fix it. Sorry! :(
 
Don’t ask me why, but the first thing I thought was to reduce the RAM and try it again. I can’t explain why I thought that 😂