Closed Identifies 1 of 2 hard 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.)

ChuckM

New member
Jan 17, 2021
3
1
Hi Steve,

I'm not sure if this is similar to issue:
Pending fix - No drives found | GRC Public Forums

I have a Dell XPS 8930 PC with two hard disks:
1) 2 TB M.2 SSD (Toshiba KXG50PNV2T04), this is the normal OS boot
2) 8 TB spinning HD (WD Ultrastar)

ReadSpeed only runs for #2.

Normal run:

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
  1  8.0TB HGST HUS728T8TALE6L4          250.9   225.6   213.2   165.8   109.1

                  Benchmarked: Sunday, 2021-01-17 at 12:41

With /ident and /verbose options:

Code:
  AHCI '.' and IDE '-' drive reset & diagnostic latencies in milliseconds:

  61.624

  Associating BIOS drive [80-80]:

  [ 80 ]
  [ 80 ]

   No BIOS association for AHCI controller:  0:23:0  on port: 1              

  BIOS drive count: 1

  BIOS Inter Bus Location Dev Port Intr
  ---- ----- --- -------- --- ---- ----
   80   USB  PCI  0:20:0  14                                                  

  BIOS Location Type Clas Pg Vend Devi Prt Intr Cmmd Ctrl Mast Driv Link Size
  ---- -------- ---- ---- -- ---- ---- --- ---- ---- ---- ---- ---- ---- -----
    1   0:23:0  RAID 0104 00 8086 2822  1   11  < AHCI Cntrl >  6.0  6.0 8.0TB

                  Benchmarked: Sunday, 2021-01-17 at 14:01


And finally, the output of pci:

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   A2C9   1028   0859
  0    31    2  0580  00          8086   A2A1   1028   0859
  0    31    3  0403  00          8086   A2F0   1028   0859
  0    31    4  0C05  00          8086   A2A3   1028   0859
  0    30    0  1180  00          8086   A2A7   1028   0859
  0    28    0  0604  00          8086   A291    --     --
  0    28    2  0604  00          8086   A292    --     --
  0    28    3  0604  00          8086   A293    --     --
  0    28    4  0604  00          8086   A294   002F    --
  0    23    0  0104  00   RAID   8086   2822   1028   0859
  0    22    0  0780  00          8086   A2BA   1028   0859
  0    20    0  0C03  30          8086   A2AF   1028   0859
  0     8    0  0880  00          8086   1911   1028   0859
  0     2    0  0380  00          8086   3E98   1028   0859
  0     1    0  0604  00          8086   1901    --     --
  0     0    0  0600  00          8086   3E30   1028   0859
  1     0    0  0300  00          10DE   1E84   1028   C723
  1     0    1  0403  00          10DE   10F8   1028   C723
  1     0    2  0C03  30          10DE   1AD8   1028   C723
  1     0    3  0C80  00          10DE   1AD9   1028   C723
  4     0    0  0200  00          1969   E0A1   1028   0859
  3     0    0  0280  00          168C   0042   1028   1810
  2     0    0  0C03  30          1B21   1242   1028   0859

Any idea why the SSD is not identified?

Thanks!
 
My understanding is that SpinRite 6.1 will support NVMe SSDs up to 2.2 TB, although with limited performance. Will there be an update to the ReadSpeed utility as a POC of this capability?

Thanks!
 
It will only support NVMe drives through the BIOS. ReadSpeed is testing Steve's new direct drivers which bypass the BIOS and talk directly to AHCI and IDE drives. NVMe and USB drives under 2.2TB will only work at the slower speeds through the BIOS.
 
My understanding is that SpinRite 6.1 will support NVMe SSDs up to 2.2 TB, although with limited performance. Will there be an update to the ReadSpeed utility as a POC of this capability?

Thanks!
Hey @ChuckM, sorry for the confusion. As Alan said, the ReadSpeed benchmark was created only to validate the operation of our new IDE/ATA/SATA/AHCI drivers. So it is not meant to show what SpinRite will see. As you noted, SpinRite WILL run on all of our drives, just not super-speedy on the NVMe drive. SRv7.x will fix that!
 
  • Like
Reactions: Barry Wallis