ReadSpeed Can't find drives

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

Jan 5, 2022
5
0
Hello all,

I'm running ReadSpeed on a ten year old HP ProLiant DL360 G7 server running ESXi. It's using a Broadcom iSCSI controller for a non-SSD terabyte drive. I'm getting the following error: "ReadSpeed didn't find any ATA or SATA hard drives with IDE or AHCI controllers." I have attached a screenshot.

I checked and confirmed that the SATA controller is enabled. Previously, I've had issues running SpinRite on this server. I'm wondering if there's one of the rare exceptions in the hardware that Steve has mentioned in the past.

This is my first post here, so I'm not certain of the process for getting additional debug/troubleshooting information to Steve. Is there an additional utility I could run or commands on the RS utility?
 

Attachments

  • ReadSpeed-2022-01-05-102049_001.jpeg
    ReadSpeed-2022-01-05-102049_001.jpeg
    438.3 KB · Views: 343
So Steve did respond, very quickly, but thought it was my equipment. I corrected the misunderstanding, and he may come here subsequently. In any case, here is what he said:

What do you see when running the DOS version of the PCI command?

The starting point for both ReadSpeed and SpinRite is the PCi
device Class, and to a lesser degree the ProgIf. If the machine
is declaring the controller as something unrecognizable then
neither ReadSpeed nor SpinRite will attempt to dig any deeper.

So I believe, on the ReadSpeed USB device you will find diagnostic commands, one of which is "pci". Exit ReadSpeed to the DOS prompt, and try running that command. You could redirect the output to a file by appending "> pci.txt" so the whole command will be "pci.exe > pci.txt" (minus quotes). Then post that pci.txt here in the forums. (Please use the format tool bar to mark the text as code. (It's under the three dots on the extreme right of the toolbar.)
 
As requested, here is the output from the PCI command:

Code:
+----------------------------------------------------------+
| PCI v1    Simple DOS-based PCI System Enumerator     GRC |
+----------------------------------------------------------+

+ Contemporary PCI subsystem detected.

Bus# Device Fnc Clas PgIf  Type  Vendor Device SubVen SubSys
---- ------ --- ---- ---- ------ ------ ------ ------ ------
  0    31    0  0601  00          8086   3A18    --     -- 
  0    30    0  0604  01          8086   244E    --     -- 
  0    29    0  0C03  00          8086   3A34   103C   330D
  0    29    1  0C03  00          8086   3A35   103C   330D
  0    29    2  0C03  00          8086   3A36   103C   330D
  0    29    3  0C03  00          8086   3A39   103C   330D
  0    29    7  0C03  20          8086   3A3A   103C   330D
  0    28    0  0604  00          8086   3A40    --     -- 
  0    28    4  0604  00          8086   3A48    --     -- 
  0    20    0  0800  00          8086   342E   003C   000B
  0    20    1  0800  00          8086   3422   003C   000B
  0    20    2  0800  00          8086   3423   003C   000B
  0    14    0  0600  00          8086   341C    --     -- 
  0    14    1  0600  00          8086   341D    --     -- 
  0    14    2  0600  00          8086   341E    --     -- 
  0    14    3  0600  00          8086   341F    --     -- 
  0    14    4  0600  00          8086   3439    --     -- 
  0    13    0  0600  00          8086   343A    --     -- 
  0    13    1  0600  00          8086   343B    --     -- 
  0    13    2  0600  00          8086   343C    --     -- 
  0    13    3  0600  00          8086   343D    --     -- 
  0    13    4  0600  00          8086   3418    --     -- 
  0    13    5  0600  00          8086   3419    --     -- 
  0    13    6  0600  00          8086   341A    --     -- 
  0    10    0  0604  00          8086   3411    --     -- 
  0     9    0  0604  00          8086   3410    --     -- 
  0     8    0  0604  00          8086   340F    --     -- 
  0     7    0  0604  00          8086   340E    --     -- 
  0     6    0  0604  00          8086   340D    --     -- 
  0     5    0  0604  00          8086   340C    --     -- 
  0     4    0  0604  00          8086   340B    --     -- 
  0     3    0  0604  00          8086   340A    --     -- 
  0     2    0  0604  00          8086   3409    --     -- 
  0     1    0  0604  00          8086   3408    --     -- 
  0     0    0  0600  00          8086   3406   103C   330B
  5     0    0  0104  00   RAID   103C   323A   103C   3245
  3     0    0  0200  00          14E4   1639   103C   7055
  3     0    1  0200  00          14E4   1639   103C   7055
  4     0    0  0200  00          14E4   1639   103C   7055
  4     0    1  0200  00          14E4   1639   103C   7055
  2     0    0  0880  00          103C   3306   103C   3309
  2     0    2  0880  00          103C   3307   103C   3309
  2     0    4  0C03  00          103C   3300   103C   3309
  1     3    0  0300  00          1002   515E   103C   31FB
 
Since Paul is not here at the moment, here is your reply from Steve:-


https://devicehunt.com/view/type/pci/vendor/103C/device/323A

As I suspected, it's a TRUE RAID controller, so it's not
accessible/usable as either AHCI, ATA or IDE. So SpinRite
will almost certainly never be able to work with it directly.

If it's connected to SATA drives, they could be moved to any
SATA controller for full SpinRite use. But I'll bet that SR v6.1
will run on it without trouble (though certainly not optimally).


+----------------------------------------------------------+
| PCI v1 Simple DOS-based PCI System Enumerator GRC |
+----------------------------------------------------------+

+ Contemporary PCI subsystem detected.

Bus# Device Fnc Clas PgIf Type Vendor Device SubVen SubSys
---- ------ --- ---- ---- ------ ------ ------ ------ ------
5 0 0 0104 00 RAID 103C 323A 103C 3245

--
________________________________________________________________
/Steve.
 
  • Like
Reactions: PHolder
Since Paul is not here at the moment, here is your reply from Steve:-


https://devicehunt.com/view/type/pci/vendor/103C/device/323A

As I suspected, it's a TRUE RAID controller, so it's not
accessible/usable as either AHCI, ATA or IDE. So SpinRite
will almost certainly never be able to work with it directly.

If it's connected to SATA drives, they could be moved to any
SATA controller for full SpinRite use. But I'll bet that SR v6.1
will run on it without trouble (though certainly not optimally).




--
________________________________________________________________
/Steve.
Thank you Alan for relaying Steve's reply. For what it's worth, my copy of SpinRite 6.0 does NOT run on it. I get a Division Overflow Error. I'm not sure if that's worth mentioning to Steve. I have attached a screenshot of the SpinRite error.
 

Attachments

  • SpinRiteError_1.jpg
    SpinRiteError_1.jpg
    351 KB · Views: 373
Thank you Alan for relaying Steve's reply. For what it's worth, my copy of SpinRite 6.0 does NOT run on it. I get a Division Overflow Error. I'm not sure if that's worth mentioning to Steve. I have attached a screenshot of the SpinRite error.
This is a known problem with SpinRite 6.0.

SpinRite 6.1 will not have this issue. No need to bother Steve with it.
 
  • Like
Reactions: GalacticDonkey