Dears i ma facing a problem wich is i am not able to that my HP Proliant dl580 g7  server  support windows server2016 or no .?

¿Me podrán decir qué tipos de discos puedo colocarle a un servidor ProLiant Server DL180 G6?

Lo tengo con discos originales, de casi 300Gb, y necesito ampliar la capacidad de almacenamiento. Quisiera reemplazar los discos por unidades de, al menos, 4TB, y no se que tipos de discos son compatibles. 

Muchas gracias!

Требуется помощь - сервер hp proliant DL 180 G6, операционная система windows server 2008 SR, сильно шумят вентиляторы охлаждения - в bios 7000 оборотов в минуту, регулировка через bios неактивна. Как уменьшить скорость вращения?? Что - то типа silent режима можно поставить??

Hi

We have an old hp server which I am trying to install windows 2008 32bit on (just got some old tape drives and tapes that we need to restore some data from).

The problem is that windows is not recognising any drivers I found for that raid controller (.Smart Array 642 )

I have done some googling and people suggesting updating firmware but I cannot find any firmware or drivers, actualy HP website not finding the serial number at all ( 8324KJ4Z1031 )

Any suggestions?

Thanks

hello'

i seen alot of upgrading but i was wondering if i could down grade

ml350p e5-2620v2 single proc

i have to e5-2667 processors extra heat sink and fan

i read about going from v1 to v2 but not the backwards

is this possible

than you

Quick question regarding SSA Scripting in WinPE.

I work in a lab environment where I have a certain model of an unconfigured server coming in with different hard drive configurations... Up to as many as 20 configurations per model... DL380, 580, BL460 Gen9. 

I have created script files for SSA scripting to create a standard configuration... 2 disks in a RAID1 and the rest in a RAID5. 

I want to create a universal SSA scripting file that'll look for two smaller sized hard drives on the controller and put those in a RAID1 (independent of box:bay:port), and the rest of the HDD's put in a generic RAID5.

Sometimes the servers come in with different physical drive installations but the sizes are similar.. My script that i have no points to a box:bay and doesn't always put the 2 smallest HDD's in the RAID1. 

Hello.

Firstly, I'm a french guy and my english is very bad, sorry if I made mistakes.

I would like to convert a LogicalDrive in a D2600 from RAID level 6 to RAID level 5.

My first question : Is it possible ?

My server is a "HP Proliant DL380 Gen9" with a RAID Card P441 and an additional storage HP2600.

The Operating system is VMware vSphere 6 Essentials,  installed with the custom ISO HPE.

All the storage on the D2600 is dedicated for one volume presented to one VM (Windows server 2012 R2).

We have got a pb on this storage for a few days. All free space are used by temporary vm disk and the

VM is unavailable.

I want increase the free space available on the D2600 storage converting from RAID level 6 to RAID level 5, if it's possible.

[root@ESX-Video:~]  /opt/hp/hpssacli/bin/hpssacli controller slot=3 show detail

Smart Array P441 in Slot 3

   Bus Interface: PCI

   Slot: 3

   Serial Number: PDNMH0ARH9M05N

   Cache Serial Number: PEYFP0BRH9L3R7

   RAID 6 (ADG) Status: Enabled

   Controller Status: OK

   Hardware Revision: B

   Firmware Version: 4.02

   Rebuild Priority: High

   Expand Priority: Medium

   Surface Scan Delay: 3 secs

   Surface Scan Mode: Idle

   Parallel Surface Scan Supported: Yes

   Current Parallel Surface Scan Count: 1

   Max Parallel Surface Scan Count: 16

   Queue Depth: Automatic

   Monitor and Performance Delay: 60  min

   Elevator Sort: Enabled

   Degraded Performance Optimization: Disabled

   Inconsistency Repair Policy: Disabled

   Wait for Cache Room: Disabled

   Surface Analysis Inconsistency Notification: Disabled

   Post Prompt Timeout: 15 secs

   Cache Board Present: True

   Cache Status: OK

   Cache Ratio: 10% Read / 90% Write

   Drive Write Cache: Disabled

   Total Cache Size: 4.0 GB

   Total Cache Memory Available: 3.8 GB

   No-Battery Write Cache: Disabled

   SSD Caching RAID5 WriteBack Enabled: True

   SSD Caching Version: 2

   Cache Backup Power Source: Batteries

   Battery/Capacitor Count: 1

   Battery/Capacitor Status: OK

   SATA NCQ Supported: True

   Spare Activation Mode: Activate on physical drive failure (default)

   Controller Temperature (C): 66

   Cache Module Temperature (C): 43

   Number of Ports: 2 External only

   Encryption: Disabled

   Express Local Encryption: False

   Driver Name: HP HPSA

   Driver Version: 6.0.0

   PCI Address (Domain:Bus:Device.Function): 0000:08:00.0

   Negotiated PCIe Data Rate: PCIe 3.0 x8 (7880 MB/s)

   Controller Mode: RAID

   Controller Mode Reboot: Not Required

   Latency Scheduler Setting: Disabled

   Current Power Mode: MaxPerformance

   Host Serial Number: CZJ53309DM

   Sanitize Erase Supported: True

   Primary Boot Volume: None

   Secondary Boot Volume: None

[root@ESX-Video:~]  /opt/hp/hpssacli/bin/hpssacli controller slot=3 ld all show detail

Smart Array P441 in Slot 3

   array A

      Logical Drive: 1

         Size: 54.6 TB

         Fault Tolerance: 6

         Heads: 255

         Sectors Per Track: 32

         Cylinders: 65535

         Strip Size: 256 KB

         Full Stripe Size: 2560 KB

         Status: OK

         MultiDomain Status: OK

         Caching:  Enabled

         Parity Initialization Status: Initialization Completed

         Unique Identifier: 600508B1001C774B946337A89DC8C106

         Logical Drive Label: 02447D2CPDNMH0ARH8Z0AUC32C

         Drive Type: Data

         LD Acceleration Method: Controller Cache

[root@ESX-Video:~]  /opt/hp/hpssacli/bin/hpssacli controller slot=3 pd all show

Smart Array P441 in Slot 3

   array A

      physicaldrive 1E:1:1 (port 1E:box 1:bay 1, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:2 (port 1E:box 1:bay 2, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:3 (port 1E:box 1:bay 3, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:4 (port 1E:box 1:bay 4, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:5 (port 1E:box 1:bay 5, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:6 (port 1E:box 1:bay 6, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:7 (port 1E:box 1:bay 7, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:8 (port 1E:box 1:bay 8, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:9 (port 1E:box 1:bay 9, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:10 (port 1E:box 1:bay 10, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:11 (port 1E:box 1:bay 11, SAS, 6001.1 GB, OK)

      physicaldrive 1E:1:12 (port 1E:box 1:bay 12, SAS, 6001.1 GB, OK)

  Can i convert the logicaldrive 1 in slot 3 on the smart array P441 from RAID level 6 to the RAID level 5 with all the system ONLINE?

Thanks

Hello  Everyone,

I have a BTO 812643-001   ML110 Gen9 with 4  LFF  NON-HOTPLUG HDDs.   I need more than 4 HDDs and I want to add a DRIVE CAGE  784584-B21   for LFF   HOTPLUG HardDrives.
Do I need an extra cable to conect the new Cage?
Will the controller B140i support more than 4 drives in different cages? ,  (Mix non-htplg  and htplg)

Thank you!    

Hi everyone！

I have 4x4TB driver on P212 but it unsupport. I try update the firmware using SPP, but always error.

What should I do?

Hi guys,

A couple weeks ago i got a server from somebody who wanted to throw it away.
It is an hp proliant ml130.
So first if all, when I got the server it was in a bad condition, it was very, very, very dusty, around half a centimeter of dust on the base of the server and 3MM carpet on the place where the fan sucked the air in, so after using some canned air, we could take it inside.

But when i installed windows ten to see if everything was working, i noticed that the cpu fan mad a lot off noise, turned oid the bearings were broken.

I had an 80mm fan lying around so i tried to use that one, then i noticed that it was thicker than the original fan, so i remove the plastic and put the fan it without the little holder with the yellow arrow, the tension of the cooler kept it tight.

but the new fan had onther connector so i sanded od the little notches so it would fit, and it did it even turned on.

But it said there was a cpu fan failure.

Ans then it plays an ear raping beep and turns of.

Can i discable this? because it auto shuts off.

kind regards, 

Vincent

Having problems installing Server 2012 r2 Foundation from DVD after the server was used to test server 2016 TP5 Ess.

Have cleared the SSD drive used for the OS and re-set the disks on the B120i.

The problem is that when I try to install the foundation product from the Server 2012 R2 Foundation DVD (ROK) the Storage server software is installed (NOTE - I'm a home User with a little understanding the server product) based on using Windows Home server v1, v2, then the Business server release. 

Had a 2012 release when i got the ml310e but lost the key and have been using Server 2016 tp5 essensals but thought it was about time to replace the os. was looking a the 2016 version but at £500+ too much so I got the £200 Foundation version. but can not get it to insatll the full foundation / essentials software or is it thet the foundation version does not have the essentals package on it?  

I have just purchased a couple of Dl380 G6 to setup a home lab and I was looking to update the Bios firmware, but when I go to download the latest update it says I need to sign in and have entitlement is required, which I am guessing you need a service agreement for. 

Is there anywhere I can download the latest Bios firmware for the Proliant dl380 G6 without having the entitlement requirement?

regards

Stewart

Hi,

What type of graphics card can I put in so that I can display output to HDMI for the KVM Console Switch?

Hi ,

Today we got an NMI error in one of our server and as a result the server goes rebooted . So i wanted to know that what cause this NMI error . is it any kind of hardware failure ? 

What is the resolution for this NMI error ?

 ProLiant DL380p Gen8

Thanks in Advance

Добрый день. Сплавили нам старичка ML570 G3, с небольшой особенностью - при загрузке bios выдает ошибка типа "ERROR! Adapter Malfunctioning!" (первая картинка).

Надпись появляется еще два раза, после чего (минут 15) сервер "проглатывает" ошибку и грузится дальше. При попытке установить ESX 3.5 5U установка зависала на этапе загрузки драйвера "mptscsi_2xx". После перепрошивки BIOS'a ошибка временно исчеза  и я умудрился установить на этот сервер ESX 3.5 5U. Но после переноса в серверную (естес-но с отключением от сети питания) сервер опять начал выдавать эту же ошибку при этом перепрошивка BIOS не помогает.

Если его перегрузить, то ошибка не выскакивает и сервер начинает искать устройства типа "Searching for device at HBA 0, ID 0, LUN 0". Так он может искать устройства почти час и только потом грузится (последняя картинка), но ESX всё равно не грузится. 
Также если если оставить его минут 15 (с питанием), то он обратно начинает выдавать ошибку типа  "ERROR! Adapter Malfunctioning!", если меньше ошибка типа  "Searching for device at HBA 0, ID 0, LUN 0".

Надеюсь на помощь по данному вопросу. Заранее спасибо)

Hi

Have installed Windows 2012 R2 on a bl460c G6. Have ran Windows Update and latest SPP. Then PSP came at the end and tried update the NICs drivers it crashed with a BSOD. So just left that out, but after WU the drivers seems to be updated.

Next tried to configure teaming on the nc532i NICs, but as soon i click ok it crash with a BSOD.

Tried to set another vlan id in the properties for the card and again BSOD. After a reboot tried to use another driver and get BSOD, remove NIC from device manager and BSOD, changed IRQ in BIOS, but still the same. WTH?!

Have ran this server for years with 2008 R2, but not used teaming and trunk/vlan tagging and had no problems. Use passthrough on the c7000 with OA fw ok, passthrough FW is 2.8.3. The only difference is that i have replaced 4x 4GB ram with 6x 16GB Kingston chips. Will try putting back the old ram, but i think its unlikely this could be the cause, or?

Anyone experienced this? Need advice.

PLz Help me  I am getting a constantly occurring BSOD  "BAD_POOL_HEADER " on a Windows 2012R2 server

I upgrade all drivers from  

Service Pack for ProLiant (SPP) Version 2016.10.0 and one day was OK

this is my dmp file

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\\122116-44718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 9200.17581.amd64fre.win8_gdr.151112-0600
Machine Name:
Kernel base = 0xfffff800`98801000 PsLoadedModuleList = 0xfffff800`98acdae0
Debug session time: Wed Dec 21 11:16:06.128 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:42.887
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffff8a004de7000, 13b0, 40000000500}

*** WARNING: Unable to verify timestamp for MxG2hDO64.sys
*** ERROR: Module load completed but symbols could not be loaded for MxG2hDO64.sys
Probably caused by : MxG2hDO64.sys ( MxG2hDO64+51676 )

Followup:     MachineOwner
---------

1: kd> 
1: kd> 
1: kd> 
1: kd> 
1: kd> 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffff8a004de7000, The pool pointer being freed.
Arg3: 00000000000013b0, The number of bytes allocated for the pool block.
Arg4: 0000040000000500, The corrupted value found following the pool block.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  6.2.9200.17581 (win8_gdr.151112-0600)

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  ProLiant DL380e Gen8

SYSTEM_SKU:  669253-B21      

BIOS_VENDOR:  HP

BIOS_VERSION:  P73

BIOS_DATE:  08/02/2014

DUMP_TYPE:  2

BUGCHECK_P1: 21

BUGCHECK_P2: fffff8a004de7000

BUGCHECK_P3: 13b0

BUGCHECK_P4: 40000000500

BUGCHECK_STR:  0x19_21

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80098b59170
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80098b59370
GetUlongPtrFromAddress: unable to read from fffff80098b59488
GetPointerFromAddress: unable to read from fffff80098b59078
 fffff8a004de7000 Paged pool

CPU_COUNT: 4

CPU_MHZ: 704

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2d

CPU_STEPPING: 7

CPU_MICROCODE: 6,2d,7,0 (F,M,S,R)  SIG: 710'00000000 (cache) 710'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  TDT-KAROL

ANALYSIS_SESSION_TIME:  12-21-2016 12:43:11.0938

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80098a738a4 to fffff8009885b240

STACK_TEXT:  
fffff880`0f63cbf8 fffff800`98a738a4 : 00000000`00000019 00000000`00000021 fffff8a0`04de7000 00000000`000013b0 : nt!KeBugCheckEx
fffff880`0f63cc00 fffff880`0c251676 : fffff8a0`04de7000 fffff8a0`04de7000 00000000`00000001 00000000`58544d44 : nt!ExDeferredFreePool+0xc9c
fffff880`0f63cce0 fffff8a0`04de7000 : fffff8a0`04de7000 00000000`00000001 00000000`58544d44 00000000`00000001 : MxG2hDO64+0x51676
fffff880`0f63cce8 fffff8a0`04de7000 : 00000000`00000001 00000000`58544d44 00000000`00000001 fffff880`0c23b8a9 : 0xfffff8a0`04de7000
fffff880`0f63ccf0 00000000`00000001 : 00000000`58544d44 00000000`00000001 fffff880`0c23b8a9 fffff8a0`feed8801 : 0xfffff8a0`04de7000
fffff880`0f63ccf8 00000000`58544d44 : 00000000`00000001 fffff880`0c23b8a9 fffff8a0`feed8801 00000000`00000000 : 0x1
fffff880`0f63cd00 00000000`00000001 : fffff880`0c23b8a9 fffff8a0`feed8801 00000000`00000000 00000000`00000000 : 0x58544d44
fffff880`0f63cd08 fffff880`0c23b8a9 : fffff8a0`feed8801 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0f63cd10 fffff8a0`feed8801 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MxG2hDO64+0x3b8a9
fffff880`0f63cd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0c23ddff : 0xfffff8a0`feed8801


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  d93e7e508606190ce593763d0543e5735e964a33

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1174279a56edc2ba24456bf43235758fb265eb00

THREAD_SHA1_HASH_MOD:  4232a9146b1c73ed2b8af3fca159239e0edb31a6

FOLLOWUP_IP: 
MxG2hDO64+51676
fffff880`0c251676 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  MxG2hDO64+51676

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MxG2hDO64

IMAGE_NAME:  MxG2hDO64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fedf361

BUCKET_ID_FUNC_OFFSET:  51676

FAILURE_BUCKET_ID:  0x19_21_MxG2hDO64!unknown_function

BUCKET_ID:  0x19_21_MxG2hDO64!unknown_function

PRIMARY_PROBLEM_CLASS:  0x19_21_MxG2hDO64!unknown_function

TARGET_TIME:  2016-12-21T10:16:06.000Z

OSBUILD:  9200

OSSERVICEPACK:  17581

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  2

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8

OSEDITION:  Windows 8 LanManNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-12 21:06:25

BUILDDATESTAMP_STR:  151112-0600

BUILDLAB_STR:  win8_gdr

BUILDOSVER_STR:  6.2.9200.17581

ANALYSIS_SESSION_ELAPSED_TIME: 50f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x19_21_mxg2hdo64!unknown_function

FAILURE_ID_HASH:  {cb0b6dab-9351-2c20-ff5c-fc21bcade3d9}

Followup:     MachineOwner

i 

Hi,

Does anyone know whether the "HP Insight Diagnostics Online Edition Survey Utility" is compatible with RHL 6.4 ?

Good Morning

Would anyone please be able to advise which specific MIBs are required to monitor a ProLiant DL380 Gen9?

Our company uses an EM product called BES to receive SNMP traps, but currently the formatting isn't correct for the Event Text.  I need to ensure we have the correct MIBs for that server installed as the first point of call.

I have found the MIB Kit here - http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04272529

Any help or advise is much appreciated.

Thanks

Steve

(p.s. Merry Christmas!)

Hello.

Please could anybody advice, how many disk failures can a 12 drive raid 1+0 tollerate.

Logical Drive: 1
Size: 1.6 TB
Fault Tolerance: RAID 1+0
Heads: 255
Sectors Per Track: 32
Cylinders: 65535
Strip Size: 256 KB
Full Stripe Size: 1536 KB
Status: Interim Recovery Mode
Array Accelerator: Enabled
Unique Identifier: 600508B1001CA1D048CD513F48AFA793
Disk Name: /dev/cciss/c1d0
Mount Points: None
OS Status: LOCKED
Logical Drive Label: A07020545001438021307A284AD5
Mirror Group 0:
physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 300 GB, OK)
physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 300 GB, OK)
physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 300 GB, OK)
physicaldrive 1I:1:4 (port 1I:box 1:bay 4, SAS, 300 GB, OK)
physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 300 GB, Predictive Failure)
physicaldrive 1I:1:6 (port 1I:box 1:bay 6, SAS, 300 GB, OK)
Mirror Group 1:
physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 300 GB, Failed)
physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 300 GB, OK)
physicaldrive 1I:1:9 (port 1I:box 1:bay 9, SAS, 300 GB, OK)
physicaldrive 1I:1:10 (port 1I:box 1:bay 10, SAS, 300 GB, OK)
physicaldrive 1I:1:11 (port 1I:box 1:bay 11, SAS, 300 GB, OK)
physicaldrive 1I:1:12 (port 1I:box 1:bay 12, SAS, 300 GB, OK)