Support for USB HDD Drives (which have no SATA connection)

  • DNS Benchmark v2 Release 5 with Consultant License
    Guest:
    If you own any earlier release of our DNS Benchmark you may immediately download its release #5 replacement. Running an earlier release will detect the new release and help you upgrade.

    Although this release is cosmetic, appearance matters and affects ease of use. The biggest change, as seen in the image above, is that the DNS Benchmark now has a traditional Windows application menu to more fully expose its many features. This release is also "Consultant License Aware" and GRC will now issue a Consultant version when owners have previously purchased four "Personal Use" licenses. If you have previously purchased four DNSB licenses, or if you wish to upgrade your "Personal Use" license to Consultant, GRC's purchase process will direct you through that process.
    /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.)

B

BP9906

Member
Nov 25, 2020
16
1
I recently bought SpinRite 6.1 for a few scenarios and drives I've accumulated over the years knowing that at some point I'd be able to recover the data.
Recently had a WD MyPassport Drive from 2018 start acting weird. Used it on MacOS for Timemachine to do backups every 3-6 months since then. Now it wont complete a backup. Ran Spin Rite 6.1 on my SpinRite machine, got the 137GB warning and nothing found.

I would connect the MyPassport to SATA but by asking AI tools (Gemini and Claude and ChatGPT) they all say the board on the MyPassport has no SATA at all. As a result I'm stuck. I'll have to hold onto this drive and not power it up and just wait for SpinRite 7 to support USB drives at 2TB-ish or higher.
 
BP9906 said:
Ran Spin Rite 6.1 on my SpinRite machine, got the 137GB warning and nothing found.
Click to expand...
That, unfortunately, is a limitation of the BIOS on that specific machine.

If you have a another machine available you should try that. A different machine with a different BIOS may not have that limitation.
 
DanR said:
That, unfortunately, is a limitation of the BIOS on that specific machine.

If you have an another machine available you should try that. A different machine with a different BIOS may not have that limitation.
Click to expand...
It’s an HP EliteDesk 800 G2.
Suggestions? Is it trial and error?
 
BP9906 said:
It’s an HP EliteDesk 800 G2.
Click to expand...
Ahh . . . That is a 2015 vintage PC. Now I think I know what the problem is..

A series of mysterious crashes in SR 6.1 development led to the discovery of a coding error in certain AMI BIOS. When accessing a USB drive beyond the first 137 GB of its capacity, this BIOS code error would manifest itself by randomly (And most improperly!) writing to ram. When SR code in RAM was overwritten SR would crash. A more serious implication is if this errant BIOS writing to RAM altered a buffer used by SR for temporary data storage, then data corruption would result. Hence an absolute 137 GB limit was enforced for all USB drives.

It was subsequently learned that most PC's copy the BIOS firmware code to RAM and execute it from RAM. In these instances, SR can now detect the code error in RAM, patch it on the fly (each time SR runs) in RAM (if present) and lift the 137 GB limitation.

There are only a few systems however, that only execute the BIOS firmware from ROM. Your old HP appears to be one of them. SR cannot patch the BIOS code in these systems. Thus, SpinRite will rigidly apply the 137 GB limitation in these systems.

If you have access to a newer system there is a very, very good chance that it will not be subject to the 137 GB limitation.
 
"... asking AI tools (Gemini and Claude and ChatGPT) they all say ​
the board on the MyPassport has no SATA at all ..."​

Probably accurate for WD.

But I'd shuck the drive and check anyway.

Solder on a SATA connector:

https://share.google/aimode/LCtYGzAvDXkfYN1RT

- - - - -

"... Ran Spin Rite 6.1 on my SpinRite machine, got the 137GB ​
warning and nothing found ..."​

Try other computers until the 137 GB USB BIOS threshold is not
presented.
 
Last edited:
DanR said:
Ahh . . . That is a 2015 vintage PC. Now I think I know what the problem is..

A series of mysterious crashes in SR 6.1 development led to the discovery of a coding error in certain AMI BIOS. When accessing a USB drive beyond the first 137 GB of its capacity, this BIOS code error would manifest itself by randomly (And most improperly!) writing to ram. When SR code in RAM was overwritten SR would crash. A more serious implication is if this errant BIOS writing to RAM altered a buffer used by SR for temporary data storage, then data corruption would result. Hence an absolute 137 GB limit was enforced for all USB drives.

It was subsequently learned that most PC's copy the BIOS firmware code to RAM and execute it from RAM. In these instances, SR can now detect the code error in RAM, patch it on the fly (each time SR runs) in RAM (if present) and lift the 137 GB limitation.

There are only a few systems however, that only execute the BIOS firmware from ROM. Your old HP appears to be one of them. SR cannot patch the BIOS code in these systems. Thus, SpinRite will rigidly apply the 137 GB limitation in these systems.

If you have access to a newer system there is a very, very good chance that it will not be subject to the 137 GB limitation.
Click to expand...
Thanks for the detail. No I don’t have any old machines. Looking for suggestions on a mini PC. I know about the older zima boards. Looking to keep it under $100 for just SR.
 
BP9906 said:
Thanks for the detail. No I don’t have any old machines. Looking for suggestions on a mini PC. I know about the older zima boards. Looking to keep it under $100 for just SR.
Click to expand...
Unfortunately I do not have any suggestions. AI demands for RAM and storage drives has driven the price of used PCs (and new PCs) up.
 
I came across another thread about running it in a VM. I run Proxmox with pfsense and so I could try a usb connection to a VM.
 
Unofficial, for our SpinRite DOS/FreeDOS diskette:

USBCHK.COM for SpinRite 6.1 (and compatible with 6.0) - Detects
and bypasses a 137 GB limit and memory corruption bug in some
American Megatrends (AMI) USB BIOSes. USBCHK asserts that this
BIOS (any vendor) can access USB drives and unknown BIOS drives
over 137 GB by changing their interface description to SCSI.

Quick setup (all files must be in the current directory):

Run USBCHK.

Run DRVCHK nn where nn is the BIOS number (80, 81 ...) of a
drive connected to a USB port.

Run HSHCHK mm where mm is the BIOS number of the same
drive connected to a non-USB port.

If all steps pass, add USBCHK or USBCHK > NUL to AUTOEXEC.BAT.

Or then run manually:
USBCHK
SPINRITE ... with any command line options

Run each utility with /? to confirm its command-line options.
 

Attachments

  • USB2SCSI.zip
    7.2 KB · Views: 90
BP9906 said:
I came across another thread about running it in a VM. I run Proxmox with pfsense and so I could try a usb connection to a VM.
Click to expand...
USB access works well under VirtualBox and QEMU; haven’t tried any other virtualization solutions.
 
peterblaise said:
Unofficial, for our SpinRite DOS/FreeDOS diskette:

USBCHK.COM for SpinRite 6.1 (and compatible with 6.0) - Detects
and bypasses a 137 GB limit and memory corruption bug in some
American Megatrends (AMI) USB BIOSes. USBCHK asserts that this
BIOS (any vendor) can access USB drives and unknown BIOS drives
over 137 GB by changing their interface description to SCSI.

Quick setup (all files must be in the current directory):

Run USBCHK.

Run DRVCHK nn where nn is the BIOS number (80, 81 ...) of a
drive connected to a USB port.

Run HSHCHK mm where mm is the BIOS number of the same
drive connected to a non-USB port.

If all steps pass, add USBCHK or USBCHK > NUL to AUTOEXEC.BAT.

Or then run manually:
USBCHK
SPINRITE ... with any command line options

Run each utility with /? to confirm its command-line options.
Click to expand...

Fails I guess.
 
When USBCHK and HSHCHK fail, that is a good confirmation that the
BIOS is not handling more than 137 GB well through USB. We tried.
 
  • Like
Reactions: BP9906
You must log in or register to reply here.

Similar threads

jlariviere
NAS support?
Replies
3
Views
1K
SpinRite 7.0
jlariviere
jlariviere
L
A Wish For the Future (to Steve)
Replies
0
Views
466
SpinRite 7.0
lyonadmiral1981
L
Simon Zerafa
  • Contains 1 staff post(s)
Automatic Power Cycling for SATA Drives?
Replies
4
Views
2K
SpinRite 7.0
Simon Zerafa
Simon Zerafa
ShadowMeow
  • Contains 4 staff post(s)
USB Floppy Drive Support
Replies
22
Views
8K
SpinRite 7.0
Fuzzball
Fuzzball
I
New features - Thoughts and wishes for the future
Replies
2
Views
905
SpinRite 7.0
peterblaise
peterblaise
Top Bottom
Back