SpinRite 6.1 RC won't run on disk - HP Omen 17-cb0xxx

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

Omen5188

New member
Nov 10, 2023
4
1
Hi Steve,

I have an HP Omen 17-cb0xxx Laptop with a 500 NVMe SSD as the boot drive and a 1TB spinner for a data disk. I just downloaded the RC 3 today and it was unable to access my SSD, but had no problem with the spinning media. Is this because of the AHCI issue mentioned in the DriveEnum output?

Here's the output from each of the utilities:

PCI.EXE:
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   A30D   103C   8603
  0    31    3  0401  00          8086   A348   103C   8603
  0    31    4  0C05  00          8086   A323   103C   8603
  0    31    5  0C80  00          8086   A324   103C   8603
  0    29    0  0604  00          8086   A330    --     -- 
  0    29    5  0604  00          8086   A335    --     -- 
  0    29    6  0604  00          8086   A336    --     -- 
  0    27    0  0604  00          8086   A340    --     -- 
  0    23    0  0104  00   RAID   8086   282A   103C   8603
  0    22    0  0780  00          8086   A360   103C   8603
  0    21    0  0C80  00          8086   A368   103C   8603
  0    21    1  0C80  00          8086   A369   103C   8603
  0    20    0  0C03  30          8086   A36D   103C   8603
  0    20    2  0500  00          8086   A36F   8086   7270
  0    20    3  0280  00          8086   A370   8086   0034
  0    18    0  1180  00          8086   A379   103C   8603
  0     8    0  0880  00          8086   1911   103C   8603
  0     1    0  0604  00          8086   1901    --     -- 
  0     0    0  0600  00          8086   3E20   103C   8603
  1     0    0  0300  00          10DE   1ED0   103C   8603
  1     0    1  0403  00          10DE   10F8   103C   8603
  1     0    2  0C03  30          10DE   1AD8   103C   8603
  1     0    3  0C80  00          10DE   1AD9   103C   8603
  2     0    0  0604  00          8086   15E7    --     -- 
  3     2    0  0604  00          8086   15E7    --     -- 
  3     1    0  0604  00          8086   15E7    --     -- 
  3     0    0  0604  00          8086   15E7    --     -- 
  4     0    0  0880  00          8086   15E8   103C   8603
 58     0    0  0C03  30          8086   15E9   103C   8603
 61     0    0  0805  01          17A0   9750   103C   8603
 60     0    0  0200  00          10EC   8168   103C   8603
 59     0    0  0108  02  Other   1179   011A   1179   0001

DrivEnum.exe:
Code:
+----------------------------------------------------------------+
| DrivEnum, v1.1          Enumeration of system's ATA/IDE drives |
+----------------------------------------------------------------+

Location Clas PgIf Vend Devi Pin Irq# P:Cmd  Ctrl S:Cmd  Ctrl Mast
-------- ---- ---- ---- ---- --- ---- ----------- ----------- ----
 0:23:0  0104  00  8086 282A  1   11   >8000>E000   5050 5040 5020             
59: 0:0  0108  02  1179 011A  1   11   >0004 0000   0000 0000 0000             

BIOS drive count: 2

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

Command Control : Master : Slave
------- ------- : ------ : ------ -----Legacy controllers------
 01F0    03F6        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF               
 0170    0376        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF               
 01E8    03EE        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF               
 0168    036E        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF               
                                  -----PCI/ATA controllers-----
 5050    5042        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF               
  SpinTest was unable to locate any ATA-compatible hard drives.

  This is to be expected for systems with their controllers in
  AHCI mode, since our work so far has been exclusively for ATA
  IDE-mode controllers. We have seen that many AHCI controllers
  also provide ATA/IDE-mode operation, even while in AHCI mode,
  but this system is apparently not one of those. The NEXT round
  of development will work to support pure-AHCI-mode systems.

SpinRite.exe DIAGS:

Code:
  ############################################################################
  # SpinRite Detailed Technical Log generated at 11:40 pm on Nov 10th, 2023. #
  ############################################################################
                               release candidate 3         

Command line: diags


         SpinRite User-Requested Debugging Log           
          2023-11-10 at 23:40, release candidate 3                           


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Vendor: 8086 Device: 282A Bus: 00 Dev: 17 Func: 00 Class: 0104 ProgIf: 00
---------------------------------------------------------------------------
   HBAR (Host Base Address Register): DA21D000
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  bar-0: FFFFFFFF - legacy base address register 0
  bar-1: FFFFFFFF -   "       "       "       "  1
  bar-2: FFFFFFFF -   "       "       "       "  2
  bar-3: FFFFFFFF -   "       "       "       "  3
  bar-4: FFFFFFFF -   "       "       "       "  4
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    cap: E534FF40 - host capabilities
    ghc: 80000000 - global host control
     is: 00000000 - interrupt status
     pi: 00000001 - ports implemented
     vs: 00010301 - version
ccc ctl: 00000000 - command completion ccoalescing control
ccc prt: 00000000 - command completion coalsecing ports
enc loc: 01600002 - enclosure management location
enc ctl: 07010000 - enclosure management control
   cap2: 0000003C - enclosure management control
   bohc: 00000000 - BIOS/OS handoff control and status

=[ Port: 0 ]=

    clb: 0009E800 - command list base address, 1K-byte aligned
   clbu: 00000000 - command list base address upper 32 bits
     fb: 0009EC00 - FIS base address, 256-byte aligned
    fbu: 00000000 - FIS base address upper 32 bits
     is: 00000000 - interrupt status
     ie: 00000000 - interrupt enable
    cmd: 00000006 - command and status
   rsv0: 00000000 - reserved
    tfd: 00000150 - task file data
    sig: 00000101 - signature
   ssts: 00000133 - SATA status (SCR0 SStatus)
   sctl: 00000700 - SATA control (SCR2 SControl)
   serr: 00000000 - SATA error (SCR1 SError)
   sact: 00000000 - SATA active (SCR3 SActive)
     ci: 00000000 - command issue
   sntf: 00000000 - SATA notification (SCR4 SNotification)
    fbs: 00000000 - FIS-based switch control
  dvslp: 00000000 - Device Sleep

         (SATA drive's LBA support is confirmed.)

 Extended Bios 80 Params: 0006004A 00000EBD 000000FF 0000003F 039D2000 00000000
 Bus:PCI Interface:USB    73754220 4943503A 746E4920 61667265 553A6563 20204253
                          20200020 69766544 50206563 6D617261 72657465 62615420

 BIOS ItemFlags: 0x00000000
 
Hi Steve,

I have an HP Omen 17-cb0xxx Laptop with a 500 NVMe SSD as the boot drive and a 1TB spinner for a data disk. I just downloaded the RC 3 today and it was unable to access my SSD, but had no problem with the spinning media. Is this because of the AHCI issue mentioned in the DriveEnum output?

Here's the output from each of the utilities:

PCI.EXE:
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   A30D   103C   8603
  0    31    3  0401  00          8086   A348   103C   8603
  0    31    4  0C05  00          8086   A323   103C   8603
  0    31    5  0C80  00          8086   A324   103C   8603
  0    29    0  0604  00          8086   A330    --     --
  0    29    5  0604  00          8086   A335    --     --
  0    29    6  0604  00          8086   A336    --     --
  0    27    0  0604  00          8086   A340    --     --
  0    23    0  0104  00   RAID   8086   282A   103C   8603
  0    22    0  0780  00          8086   A360   103C   8603
  0    21    0  0C80  00          8086   A368   103C   8603
  0    21    1  0C80  00          8086   A369   103C   8603
  0    20    0  0C03  30          8086   A36D   103C   8603
  0    20    2  0500  00          8086   A36F   8086   7270
  0    20    3  0280  00          8086   A370   8086   0034
  0    18    0  1180  00          8086   A379   103C   8603
  0     8    0  0880  00          8086   1911   103C   8603
  0     1    0  0604  00          8086   1901    --     --
  0     0    0  0600  00          8086   3E20   103C   8603
  1     0    0  0300  00          10DE   1ED0   103C   8603
  1     0    1  0403  00          10DE   10F8   103C   8603
  1     0    2  0C03  30          10DE   1AD8   103C   8603
  1     0    3  0C80  00          10DE   1AD9   103C   8603
  2     0    0  0604  00          8086   15E7    --     --
  3     2    0  0604  00          8086   15E7    --     --
  3     1    0  0604  00          8086   15E7    --     --
  3     0    0  0604  00          8086   15E7    --     --
  4     0    0  0880  00          8086   15E8   103C   8603
 58     0    0  0C03  30          8086   15E9   103C   8603
 61     0    0  0805  01          17A0   9750   103C   8603
 60     0    0  0200  00          10EC   8168   103C   8603
 59     0    0  0108  02  Other   1179   011A   1179   0001

DrivEnum.exe:
Code:
+----------------------------------------------------------------+
| DrivEnum, v1.1          Enumeration of system's ATA/IDE drives |
+----------------------------------------------------------------+

Location Clas PgIf Vend Devi Pin Irq# P:Cmd  Ctrl S:Cmd  Ctrl Mast
-------- ---- ---- ---- ---- --- ---- ----------- ----------- ----
 0:23:0  0104  00  8086 282A  1   11   >8000>E000   5050 5040 5020            
59: 0:0  0108  02  1179 011A  1   11   >0004 0000   0000 0000 0000            

BIOS drive count: 2

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

Command Control : Master : Slave
------- ------- : ------ : ------ -----Legacy controllers------
 01F0    03F6        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF              
 0170    0376        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF              
 01E8    03EE        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF              
 0168    036E        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF              
                                  -----PCI/ATA controllers-----
 5050    5042        .        .   FFFFFFFFFFFFFF FFFFFFFFFFFFFF              
  SpinTest was unable to locate any ATA-compatible hard drives.

  This is to be expected for systems with their controllers in
  AHCI mode, since our work so far has been exclusively for ATA
  IDE-mode controllers. We have seen that many AHCI controllers
  also provide ATA/IDE-mode operation, even while in AHCI mode,
  but this system is apparently not one of those. The NEXT round
  of development will work to support pure-AHCI-mode systems.

SpinRite.exe DIAGS:

Code:
  ############################################################################
  # SpinRite Detailed Technical Log generated at 11:40 pm on Nov 10th, 2023. #
  ############################################################################
                               release candidate 3        

Command line: diags


         SpinRite User-Requested Debugging Log          
          2023-11-10 at 23:40, release candidate 3                          


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Vendor: 8086 Device: 282A Bus: 00 Dev: 17 Func: 00 Class: 0104 ProgIf: 00
---------------------------------------------------------------------------
   HBAR (Host Base Address Register): DA21D000
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  bar-0: FFFFFFFF - legacy base address register 0
  bar-1: FFFFFFFF -   "       "       "       "  1
  bar-2: FFFFFFFF -   "       "       "       "  2
  bar-3: FFFFFFFF -   "       "       "       "  3
  bar-4: FFFFFFFF -   "       "       "       "  4
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    cap: E534FF40 - host capabilities
    ghc: 80000000 - global host control
     is: 00000000 - interrupt status
     pi: 00000001 - ports implemented
     vs: 00010301 - version
ccc ctl: 00000000 - command completion ccoalescing control
ccc prt: 00000000 - command completion coalsecing ports
enc loc: 01600002 - enclosure management location
enc ctl: 07010000 - enclosure management control
   cap2: 0000003C - enclosure management control
   bohc: 00000000 - BIOS/OS handoff control and status

=[ Port: 0 ]=

    clb: 0009E800 - command list base address, 1K-byte aligned
   clbu: 00000000 - command list base address upper 32 bits
     fb: 0009EC00 - FIS base address, 256-byte aligned
    fbu: 00000000 - FIS base address upper 32 bits
     is: 00000000 - interrupt status
     ie: 00000000 - interrupt enable
    cmd: 00000006 - command and status
   rsv0: 00000000 - reserved
    tfd: 00000150 - task file data
    sig: 00000101 - signature
   ssts: 00000133 - SATA status (SCR0 SStatus)
   sctl: 00000700 - SATA control (SCR2 SControl)
   serr: 00000000 - SATA error (SCR1 SError)
   sact: 00000000 - SATA active (SCR3 SActive)
     ci: 00000000 - command issue
   sntf: 00000000 - SATA notification (SCR4 SNotification)
    fbs: 00000000 - FIS-based switch control
  dvslp: 00000000 - Device Sleep

         (SATA drive's LBA support is confirmed.)

 Extended Bios 80 Params: 0006004A 00000EBD 000000FF 0000003F 039D2000 00000000
 Bus:PCI Interface:USB    73754220 4943503A 746E4920 61667265 553A6563 20204253
                          20200020 69766544 50206563 6D617261 72657465 62615420

 BIOS ItemFlags: 0x00000000

I may have posted too soon - is it the NVMe? I just read that support for that won't be until 7.2.
 
  • Haha
Reactions: Darcon
It's likely that your NVME is running in a mode that is only visible to the UEFI firmware.

For 6.1 NVME storage will work but only if it's visible to the BIOS/CSM. What motherboard do you have?
 
It's likely that your NVME is running in a mode that is only visible to the UEFI firmware.

For 6.1 NVME storage will work but only if it's visible to the BIOS/CSM. What motherboard do you have?
Given it is a laptop, all I have to go on is what is reported by msinfo32:

HP 8603 v45.48

My bios lets me switch to legacy mode so I can boot to dos and run spinrite, but there are actually very few options listed and I don't see any that are obvious to let me change NVMe settings.
 
I have an HP Omen 17-cb0xxx Laptop with a 500 NVMe SSD as the boot drive and a 1TB spinner for a data disk. I just downloaded the RC 3 today and it was unable to access my SSD, but had no problem with the spinning media.
Until we get to SpinRite 7 — which I am headed to with all possible speed — SpinRite 6.1 is only able to operate on the two drive categories for which it does not have its own native hardware drivers — USB and NVMe — if the system's BIOS does support those drives and thus make them available to SpinRite. Since USB has been around for many years, BIOS support for USB is pervasive. But since NVMe is comparatively recent, it's likely that old-school BIOS support will be missing from a more recent system's firmware.
 
". . . I have an HP Omen 17-cb0xxx Laptop with a 500 NVMe SSD as the boot drive and a 1TB spinner for a data disk. I just downloaded the RC 3 today and it was unable to access my SSD, but had no problem with the spinning media . . ."

Move the NVMe to a USB adapter and run @Paul F's terrific USBCHK suite of programs * to make SpinRite see it as a full size SCSI drive, then run SpinRite 6.1.

If the HDD boots Windows, try ValiDrive on the NVMe in a USB adapter and tell us how that works, too.

Let us know what you find.

* The 137 GB USB Issue https://dev.grc.com/Steve/miscellany/-/issues/5
USBCHK.COM, DRVCHK.COM, HSHCHK.COM, and MAKE-HCW.COM (HSHCHK-W.EXE) can be found here:
https://drive.google.com/drive/folders/1zYqxaOEn5ATRnjmUW3sEKRs9v2k9mutY
 
Last edited:
Move the NVMe to a USB adapter and run @Paul F's terrific USBCHK suite of programs * to make SpinRite see it as a full size SCSI drive, then run SpinRite 6.1.

If the HDD boots Windows, try ValiDrive on the NVMe in a USB adapter and tell us how that works, too.

Let us know what you find.

* The 137 GB USB Issue https://dev.grc.com/Steve/miscellany/-/issues/5
USBCHK.COM, DRVCHK.COM, HSHCHK.COM, and MAKE-HCW.COM (HSHCHK-W.EXE) can be found here:
https://drive.google.com/drive/folders/1zYqxaOEn5ATRnjmUW3sEKRs9v2k9mutY?usp=share_link

.
In this case I will continue to wait for 7.2 (please no more side projects Steve! :)) to scan that drive. The drive isn't having any issues and I just wanted to see if 6.1 could see it. Hopefully it doesn't have any issues before 7.2 comes.
 
NVMe is happening immediately, in SR7.0. Along with USB, it's on the short list for support.

As for side projects, I cannot make any promises about that. ValiDrive, with 60,000+ total downloads and currently 1,200 per day, has clearly been a huge hit. And "Never10" and "InControl" have been very important. What I believe I can promise is no more “SQRL scale” sidelines. That was a very expensive lesson that's been well learned! (y)
 
  • Like
Reactions: Omen5188
This is exactly why I argued solid USB support would have been very beneficial until SR7 materializes.
And no one argued that you were wrong, Joep. But it wasn't the optimal path. Solid USB support (and NVMe support) are both waiting for us over in RTOS-32... So why take an unknown length of time to bring solid USB support to DOS, only to then scrap it when we move to SR7? That's what would make no sense.