Z620 in UEFI boot mode does not recognize separate internal HD in drive bays 0,1 and 2

[MtothaJ]

---

@AnthonyK wrote:

---

@Brian1965 wrote:

Hi AnthonyK,

Would I be correct to assume that the SATA drives are visible in the BIOS but not under Computer Management?

Windows 10

Open Run with Windows+R hotkeys, type compmgmt.msc and tap OK

---

Hi Brian

You are right on the money.

Yes I can see the drives in the BIOS under legacy but I cannot see them under Computer Management / Disk Management.

I am not sure if this is related to older ME firmware or not.

Can you guide me ?

---

The ME features are largely irrelevant for the standard user, unless you have a whole network of these machines where you are remotely deploying updates, turning machines on and off etc. In any case it has nothing to do with recognizing disk drives - I would suggest disabling AMT in the bios.

[AnthonyK]

---

@Brian1965 wrote:

Hi Anthony,

Can you please confirm your boot block date?

Someone appears to have had a similar issue with a HP Z820. Please check out this post.

http://h30434.www3.hp.com/t5/Business-PCs-Workstations-and-Point-of-Sale-Systems/Cannot-update-HP-Z8...

---

Brian

My boot block date predates 2013 

[Brian1965]

Hi Anthony,

Looking at MtothaJ post above, do you actually need to use the ME features? I assume both 1TB drives are now visible and available in Wndows?

Unfortunately there is no way to update the boot block date, (except for replacing the motherboard or base unit to a more recent manufactured date). I understand this is effectively a board level revision update so there could also be physical differences between the pre and post 2013 block dates (as well as firmware).

If you're still having stability issues then I would be tempted to re-install all the hardware drivers in case anything has been corrupted. If you plan on giving it a go then please make sure the drivers are installed in the correct order, i.e. firmware, chipset then drivers. Remove any attached USB devices before you begin.

[AnthonyK]

---

@Brian1965 wrote:

Hi Anthony,

Good to see some progress. Initializing Disk 2 will make it visible in windows explorer.

Regarding the install issue, can you download either CCleaner or WiseRegistryCleaner and run a scan a couple of times to remove any bogus registry entries. Run the safe clean option, (not the advanced option). REBOOT afterwards.

Have you ran HP Support Assistant yet? Please try again now the new firmware is installed and detecting the SATA drives.

In the meantime I will do a bit of digging regarding the ME firmware issue.

All the best.

---

Hi Brian,

There is some progress in terms of that I do see both of the 1TB drives that I have here for backing up my date. However right after installing the Intel Rapid Storage Technology Enterprise

The troubles began.

Now only after I installed this Intel Rapid Storage Tech Driver I was able to view the "missing drives".

I will try to do uninstall this driver and see what happens and I will also try to disable AMT like was suggested.

[AnthonyK]

---

@MtothaJ wrote:

---

@AnthonyK wrote:

---

@Brian1965 wrote:

Hi AnthonyK,

Would I be correct to assume that the SATA drives are visible in the BIOS but not under Computer Management?

Windows 10

Open Run with Windows+R hotkeys, type compmgmt.msc and tap OK

---

Hi Brian

You are right on the money.

Yes I can see the drives in the BIOS under legacy but I cannot see them under Computer Management / Disk Management.

I am not sure if this is related to older ME firmware or not.

Can you guide me ?

---

The ME features are largely irrelevant for the standard user, unless you have a whole network of these machines where you are remotely deploying updates, turning machines on and off etc. In any case it has nothing to do with recognizing disk drives - I would suggest disabling AMT in the bios.

Dear MtothaJ

If these ME features are not relevant to me are we then talking about these Intel Rapid Storage Technology Enterprise ?

[MtothaJ]

---

@AnthonyK wrote:

---

@MtothaJ wrote:

---

@AnthonyK wrote:

---

@Brian1965 wrote:

Hi AnthonyK,

Would I be correct to assume that the SATA drives are visible in the BIOS but not under Computer Management?

Windows 10

Open Run with Windows+R hotkeys, type compmgmt.msc and tap OK

---

Hi Brian

You are right on the money.

Yes I can see the drives in the BIOS under legacy but I cannot see them under Computer Management / Disk Management.

I am not sure if this is related to older ME firmware or not.

Can you guide me ?

---

The ME features are largely irrelevant for the standard user, unless you have a whole network of these machines where you are remotely deploying updates, turning machines on and off etc. In any case it has nothing to do with recognizing disk drives - I would suggest disabling AMT in the bios.

Dear MtothaJ

If these ME features are not relevant to me are we then talking about these Intel Rapid Storage Technology Enterprise ?

---

These are two seperate matters:

- ME / AMT features can be disabled or enabled in the bios - the decesion is up to you. If you enable AMT, then there you should also install the Intel ME software drivers from HP (in the drivers - chipset section) else you will have various devices in Device Manager showing as unknown

- for the RST install the latest driver from HP. SInce you are using WIndows 10 more likely than not you will be asked whether you really want to install these drivers since they are older than those in WIn 10 (I had this happen on a Z420) - you should confirm this and install the HP drivers. Only after I installed the HP drivers I did not get any 'question marks' / unknown devices in Device Manager

Basically whatever scenario you choose you should be in a situation where you have no question marks / unknown devices in device manager. Disabling ME / AMT is useful since you have one less thing to deal with and in any case it is unlikely you will be using this.

[MtothaJ]

---

@Brian1965 wrote:

Unfortunately there is no way to update the boot block date, (except for replacing the motherboard or base unit to a more recent manufactured date). I understand this is effectively a board level revision update so there could also be physical differences between the pre and post 2013 block dates (as well as firmware).

---

Updating the boot block is only necessary if one wants to run the Xeon v2  CPU's, which also allow the use of 1866mhz memory. Bearing in mind that the price of these CPU's is constantly dropping and since the vast majority of Zx20 workstations are now out of warranty it is IMHO something which is worth contemplating at some point for those seeking to prolong the life of their machine by upgrading rather than stepping up to e.g. the Zx40 line. It will however not impact anything else.  

I am not familiar with the bios chip in the Z620 and Z820 but for the Z420 the updating can be done with a cheap $3-4 USB SPI programmer. The challenge is the fact that the chip is soldered to the board, so one can either use a chip clip (usually these work fine, but sometimes they don't and you are left with a partially flashed bios and a bricked PC) or - my preffered method - get the bios professionally desoldered (e.g. mobile phone / PC repair shops) and add in a socket for the bios chip (for the Z420 the SOK-SPI-16W socket is a good match).  

Its worth adding that the the latest bios editions contain some annoying check where with AMT enabled even if you have the 2013 boot block date but the older version 7.xxxxx ME firmware the system will fail to boot. For this reason if somebody wants to go down this road, my recommendation would be to use the stock bios image from the HP website (this contains both the newest boot block and the v.8.xxxxx ME) and just add your LAN mac address at offest  00001000 (fields 00 - 05).   

[AnthonyK]

Dear MtothaJ,

You, Brian1965 and others have helped me tremendously but it leaves me with a few
questions.

Q1. The issues I am currently still having with the rebooting / BSOD concerning the Intel ESRV_SVC_QUEENCREEK that is giving me a warning according to the Windows Event Logs as well as the Intel IAStorDataMgrSvc somehow causing my HP z620 to reboot after say a few hours or even 30 minutes or less depening on ... ?? I have no clue

I believe this to be related to the Intel Rapid Storage Technology program / driver that is currently running and causing me these headaches of rebooting when I do not want it or giving me BSOD and then reboot

Q2. This also leads me to the question of, Do really need the RST ? Is it essential to have fully functional z620 workstation able to use all drives attached ?

Q3. Are the rebooting issues only related to Windows 10 or do all previous Windows versions have the same issue with the ESRV_SVC_QUEENCREEK Energy Server Service and the Intel IAStorDataMgrSvc service ?

For full disclosure: I have disabled the AMT completely in the BIOS and have not attempted to update the firmware as Brian recommended before also because I cannot get it to work. I could be me but I am unable to upgrade the firmware and I question the need for it.

Sofar this has not been fun ride.

At any rate perhaps my System Report can tell you something that it cannot tell me 

ysteemrapport

Systeeminformatie
Naam van besturingssysteem: Microsoft Windows 10 Pro
Versie van besturingssysteem: 10.0.14393  9200
Systeemnaam: WS-ANTHONY
Systeemfabrikant: Hewlett-Packard
Systeemmodel: HP Z620 Workstation
Processor: GenuineIntel Intel64 Family 6 Model 45 Stepping 7 1,995 GHz
BIOS: Hewlett-Packard, J61 v03.91

Informatie over Intel® Rapid Storage Technologie voor Enterprise
Versie van gebruikersinterface: 4.3.0.1542
Taal: Nederlands (Nederland)
Intel-controller: SATA (AHCI)
Aantal SATA-poorten: 3
Intel-controller: SAS
Aantal phy's: 4
Versie van RAID Optie-ROM: 4.1.0.1026
Stuurprogrammaversie: 4.3.0.1198
NVMe driver version:  
ISDI-versie: 4.3.0.1542
RSTe spanning filter driver is absent

Informatie over opslagsysteem
RAID-configuratie

Hardware-informatie

Naam van controller: Intel(R) C600+/C220+ series chipset SATA RAID Controller
Type: SATA
Modus: RAID
Aantal volumes: 0
Aantal reserveschijven: 0
Aantal beschikbare schijven: 2
Opnieuw samenstellen na plaatsing bij een ingeschakelde computer:Uitgeschakeld
Fabrikant: 8086
Modelnummer: 2826
Productrevisie: 5
Direct aangesloten schijf: S1AXNSADB01147D
Direct aangesloten schijf: OCZ-379YF02VN2E113UQ

Naam van controller: Intel(R) C600 series chipset SAS RAID (SATA mode) Controller
Type: SAS
Modus: RAID
Aantal behuizingen: 0
Aantal volumes: 0
Aantal reserveschijven: 0
Aantal beschikbare schijven: 2
Leesbewaking: Uitgeschakeld
Opnieuw samenstellen na plaatsing bij een ingeschakelde computer:Uitgeschakeld
Fabrikant: 8086
Modelnummer: 1D6B
Productrevisie: 5
Direct aangesloten schijf: JPS930N11R5XPL
Direct aangesloten schijf: WD-WCC1U1110454

Schijf op Controller 0, Poort 0
Status: Normaal
Type: SATA SSD
Locatietype: Intern
Gebruik: Beschikbaar
Grootte: 477 GB
Systeemschijf: Ja 
Gegevenscache schijf: Ingeschakeld
Opdrachtwachtrijen: NCQ
Model: Samsung SSD 840 PRO Series              
Serienummer: S1AXNSADB01147D
Id van SCSI-apparaat: 0
Firmware: DXM06B0Q
Grootte van fysieke sectoren: 512 bytes
Grootte van logische sectoren: 512 bytes

Schijf op Controller 0, Poort 1
Status: Normaal
Type: SATA SSD
Locatietype: Intern
Gebruik: Beschikbaar
Grootte: 112 GB
Systeemschijf: Nee
Gegevenscache schijf: Ingeschakeld
Opdrachtwachtrijen: NCQ
Model: OCZ-AGILITY3                            
Serienummer: OCZ-379YF02VN2E113UQ
Id van SCSI-apparaat: 1
Firmware: 2.22    
Grootte van fysieke sectoren: 512 bytes
Grootte van logische sectoren: 512 bytes

Schijf op Controller 1, Phy 0
Status: Normaal
Type: SATA schijf
Locatietype: Intern
Gebruik: Beschikbaar
Grootte: 932 GB
Systeemschijf: Nee
Gegevenscache schijf: Ingeschakeld
Opdrachtwachtrijen: NCQ
Model: Hitachi HDS72101
Serienummer: JPS930N11R5XPL
Id van SCSI-apparaat: 0
Firmware: A3MA
Grootte van fysieke sectoren: 512 bytes
Grootte van logische sectoren: 512 bytes

Schijf op Controller 1, Phy 1
Status: Normaal
Type: SATA schijf
Locatietype: Intern
Gebruik: Beschikbaar
Grootte: 932 GB
Systeemschijf: Nee
Gegevenscache schijf: Ingeschakeld
Opdrachtwachtrijen: NCQ
Model: WDC WD10EFRX-68J
Serienummer: WD-WCC1U1110454
Id van SCSI-apparaat: 1
Firmware: 1A01
Grootte van fysieke sectoren: 4096 bytes
Grootte van logische sectoren: 512 bytes

Ongebruikte poort
Poort: 2
Controller SAS
Poortlocatie: Intern

Ongebruikte poort
Poort: 3
Controller SAS
Poortlocatie: Intern

-------------------------------------------------
System Report

System Information
OS name:  Microsoft Windows 10 Pro
OS version:  10.0.14393  9200
System name:  WS-ANTHONY
System manufacturer:  Hewlett-Packard
System model:  HP Z620 Workstation
Processor:  GenuineIntel Intel64 Family 6 Model 45 Stepping 7 1.995  GHz
BIOS:  Hewlett-Packard, J61 v03.91

Intel® Rapid Storage Technology enterprise Information
User interface version:  4.3.0.1542
Language:  English (United States)
Intel controller:  SATA (AHCI)
Number of SATA ports:  3
Intel controller:  SAS
Number of phys:  4
RAID option ROM version:  4.1.0.1026
Driver version:  4.3.0.1198
NVMe driver version:  
ISDI version:  4.3.0.1542
RSTe spanning filter driver is absent

Storage System Information
RAID Configuration

Hardware Information

Controller name:  Intel(R) C600+/C220+ series chipset SATA RAID Controller
Type:  SATA
Mode:  RAID
Number of volumes:  0
Number of spares:  0
Number of available disks:  2
Rebuild on Hot Insert:  Disabled
Manufacturer:  8086
Model number:  2826
Product revision:  5
Direct attached disk:  S1AXNSADB01147D
Direct attached disk:  OCZ-379YF02VN2E113UQ

Controller name:  Intel(R) C600 series chipset SAS RAID (SATA mode) Controller
Type:  SAS
Mode:  RAID
Number of enclosures:  0
Number of volumes:  0
Number of spares:  0
Number of available disks:  2
Read patrol:  Disabled
Rebuild on Hot Insert:  Disabled
Manufacturer:  8086
Model number:  1D6B
Product revision:  5
Direct attached disk:  JPS930N11R5XPL
Direct attached disk:  WD-WCC1U1110454

Disk on Controller 0, Port 0
Status:  Normal
Type:  SATA SSD
Location type:  Internal
Usage:  Available
Size:  477 GB
System disk:  Yes  
Disk data cache:  Enabled
Command queuing:  NCQ
Model:  Samsung SSD 840 PRO Series              
Serial number:  S1AXNSADB01147D
SCSI device ID:  0
Firmware:  DXM06B0Q
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

Disk on Controller 0, Port 1
Status:  Normal
Type:  SATA SSD
Location type:  Internal
Usage:  Available
Size:  112 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
Model:  OCZ-AGILITY3                            
Serial number:  OCZ-379YF02VN2E113UQ
SCSI device ID:  1
Firmware:  2.22    
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

Disk on Controller 1, Phy 0
Status:  Normal
Type:  SATA disk
Location type:  Internal
Usage:  Available
Size:  932 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
Model:  Hitachi HDS72101
Serial number:  JPS930N11R5XPL
SCSI device ID:  0
Firmware:  A3MA
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

Disk on Controller 1, Phy 1
Status:  Normal
Type:  SATA disk
Location type:  Internal
Usage:  Available
Size:  932 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
Model:  WDC WD10EFRX-68J
Serial number:  WD-WCC1U1110454
SCSI device ID:  1
Firmware:  1A01
Physical sector size:  4096 Bytes
Logical sector size:  512 Bytes

Empty port
Port:  2
Controller SAS
Port location:  Internal

Empty port
Port:  3
Controller SAS

[Brian1965]

Hi Anthony,

Been away for a few days so sorry for the late update but I found some additional info regarding the ME fimrware error that may help.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03424977-1.pdf

If you look at the document in the above link, (page 38 in the pdf, page 26 in the manual), you will see a reference to a jumper 36 which is labelled as ME/AMT flash override. Could it be a simple case of setting the jumper and running the ME firmware?

I remembered you have the earlier boot block date so the jumper may be in a different location on the motherboard.

Also, not sure if this helps but I've attached my BIOS settings FYI.

https://dl.dropboxusercontent.com/u/83715804/AdvisorConfig.doc

P.S. My HP Z620 is running Windows 7 Professional 64bit with a UEFI boot to a 256GB Samsung SM951 M.2. card located on PCIe slot 4 (via a ASUS Hyper M.2 X4 Mini PCIe card), a 480GB SSD in SATA0, 2TB 3.5" drive in SATA1 and 4TB 3.5" drive on SATA2. I also have a Syba SATA III card installed in slot 3 connected to a hot swappable ICY Dock 2.5"/3.5" drive bay.

[AnthonyK]

---

@Brian1965 wrote:

Hi Anthony,

Been away for a few days so sorry for the late update but I found some additional info regarding the ME fimrware error that may help.

http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03424977-1.pdf

If you look at the document in the above link, (page 38 in the pdf, page 26 in the manual), you will see a reference to a jumper 36 which is labelled as ME/AMT flash override. Could it be a simple case of setting the jumper and running the ME firmware?

I remembered you have the earlier boot block date so the jumper may be in a different location on the motherboard.

Also, not sure if this helps but I've attached my BIOS settings FYI.

https://dl.dropboxusercontent.com/u/83715804/AdvisorConfig.doc

P.S. My HP Z620 is running Windows 7 Professional 64bit with a UEFI boot to a 256GB Samsung SM951 M.2. card located on PCIe slot 4 (via a ASUS Hyper M.2 X4 Mini PCIe card), a 480GB SSD in SATA0, 2TB 3.5" drive in SATA1 and 4TB 3.5" drive on SATA2. I also have a Syba SATA III card installed in slot 3 connected to a hot swappable ICY Dock 2.5"/3.5" drive bay.

---

Hi Brian

Listen I am grateful for all the input I am getting here from you both.

I may look into this ME/AMT jumper later this week. 

As in regards to all the hick-ups, the rebooting constantly I uninstalled the 
Driver - Storage Intel Rapid Storage Technology Enterprise which caused most of the headaches these past days.

Now since I have done this I have to keep my fingers crossed, no unexpected reboots untill now.