Reporting Spinrite Error

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

ShootThePicture

New member
Jan 12, 2023
2
1
Long time Spinrite user, first time poster.

I went to use Spinrite 6.0 on an Samsung 500 GB SSD today, and I ended up receiving an error. It said to report it, so I'm trying to do so.

When I went to run level 2 on the drive, I was told that it was "MBR followed by EFI". It then said, "This partition exceeds the size of this drive as defined by the system's BIOS or BIOS extension." It told me I should "NOT PROCEED". However, I went to the GRC forums at https://forums.grc.com/threads/spinrite-mbr-warning-message-and-question.138/ where the person was having the same issue as me and received a response from Steve himself saying it was safe to proceed. I did so.

It ran for awhile, but then gave me a "Division Overflow Error". The "critical" error occurred at B04E. I can't reproduce the exact values in the registers.

The drive still seems to be working fine. I'm copying files off of it right now. However, since I have another drive that receives the same message about "MBR followed by EFI" before it can run, and it is having real problems, I thought I should report this.
IMG_5434.jpeg
IMG_5443.jpeg
 
  • Like
Reactions: Cozmo
This seems to be a drive with an MBR partition and a GPT partition. SR 6.0 cannot handle GPT partitions. SR 6.1 will handle GPT just fine.
It's from an old Windows 10 machine. Oh, well. This drive should be okay. I don't think Spinrite damaged it. The other one is definitely damaged--NOT by Spinrite--because two computers boot up telling me that the SMART system is saying the drive is going to fail soon.

Thanks for your help!
 
". . . I went to use Spinrite 6.0 on an Samsung 500 GB SSD today, and I ended up receiving an error. It said to report it, so I'm trying to do so. When I went to run level 2 on the drive, I was told that it was "MBR followed by EFI". It then said, "This partition exceeds the size of this drive as defined by the system's BIOS or BIOS extension." It told me I should "NOT PROCEED". However, I went to the GRC forums at https://forums.grc.com/threads/spinrite-mbr-warning-message-and-question.138/ where the person was having the same issue as me and received a response from Steve himself saying it was safe to proceed. I did so. It ran for awhile, but then gave me a "Division Overflow Error". The "critical" error occurred at B04E. I can't reproduce the exact values in the registers. The drive still seems to be working fine. I'm copying files off of it right now. However, since I have another drive that receives the same message about "MBR followed by EFI" before it can run, and it is having real problems, I thought I should report this . . ."

The fact that you got B04E error in SpinRite 6 on a smaller than 549 GB drive belies the analysis that went into the MDFYSR60 patch, however . . .

Run MDFYSR60 first anyway, and use the FORCE command line option.

Then let us know if that empowers SpinRite 6 in any way.

Thanks.

.
 
The fact that you got B04E error in SpinRite 6 on a smaller than 549 GB drive belies the analysis that went into the MDFYSR60 patch, however . . .
Really? Do you think proceeding on a partition that SpinRite 6.0 sees as greater than the drive size might have something to do with it?
 
". . . Really? Do you think proceeding on a partition that SpinRite 6.0 sees as greater than the drive size might have something to do with it? . . ."

@Steve Gibson can comment on what the FORCE command line does in SpinRite 6.

If it treats the drive as raw, presumably accepting BIOS-discovered physical geometry, or instead if the FORCE command line causes SpinRite to accept bogus geometry, or maybe even something else, @Steve will suggest what FORCE does.

Is there any way to discern the 'illegal' geometry that SpinRite suggests might be recorded on the drive?

Is it maybe really a corrupt partition sector, not a GPT partition?

Burned out or corrupt firmware?

Is there a way to know?

Perhaps manually viewing, sector by sector, with HxD? https://mh-nexus.de/en/hxd/

If the drive itself is broken, misreporting for whatever reason, what will a custom MDFYSR60 provide?

And if a custom MDFYSR60 provides full function to both SpinRite and the drive, why not publish for everyone and anyone?

Instead of, well, whatever is the reason not to allow others similarly situated to take advantage of whatever is learned here?

Whaddayathink?

Thanks.

.