The tray has two servers. One of them can not be powered on. The power button/LED remains yellow while the other working one immediately turns green. The monitor shows no activity at all. The type is SL2x170ZG6. The disk is not a problem because it can be used on another machine. All power/data connections have been checked as OK. The UID LED is off. The machine has been working for ~3 years, but found recently not working. Any hints?

on the video here from hp it shows how to clip in the rack rails into the server easily. What it doesn't show is how to remove the rack rail from the rack.

at this point in the video http://www.youtube.com/watch?feature=player_detailpage&v=-4XUWsrOsKQ#t=22

you can see the levers which hold the rack in place.

If you have servers both on top and below, then there is no way to reach the those levers.

am i missing a trick here ?

Thanks

Have two simple questions:


1. My event log says:

Fan FAN2_OUTLET Lower Critical 940.4 RPM

Does this mean I should replace fan? Other 5 fans rpm are around 14988 RPM. I check to see if it needs clean up but it is all clean.


2. I noted on chassis there is a one empty fan slot. Can I plug 7th fan there? You may see attached picture, I checked google many same model boards are same.

 

 
 

My new client is recieving a 1787 POST error on his ML350. F1 will let the the server start but it is running slow.
It's a standard system so without having access to documentation or the original PO I am assuming that it has two Fujitsu 9.0Gb drives in a RAID configuration.
What are the odds that it is a bad SCSI cable causing this or is this a long shot?
Would I best be advised to have the client buy a new drive and from what I have read just reinstall the new drive and have it rebuild?
I am more of a system software tech so the RAID is not something that I have dealt with before.

Thanks,
Joe

P.S. This thread has been moevd from Storage > General to ProLiant Servers (ML,DL,SL). - Hp Forum Moderator

Hi, is there anything I should take in to consideration when upgrading my hosts?

Im running:

HP ProLiant DL360p Gen8

1CPU (E5-2640)

8x8GB+4x4GB DD3  HP memory (1333mhz)

OS: VMware ESXi, 5.1.0, 1312873

and are planning to upgrade this to:

2 CPU + all slots with 8GB memory (same kind as the other 8GBs allready in place)

That means removing the 4x4GB ones.

Plan is to move all the vms to a secondary host, put the host for upgrade in maintenance mode, switch it off - replace the 4GB with 8GB, fill up the rest of the slots with 8GB and putting in the secondary CPU - then booting it back up. Seems right?

****Edit/

VMware Community told me to remove vm's from host (transfer them to a different host) and then remove the host from the cluster after shutting it down before upgrading it. After upgrade just add it to the cluster again and start.

Still waiting for the CPUs to arrive, then I will do this procedure.

****Edit\

Hi,

Since the get go (December 2013) the PCI Slot 1 temperature for the P222 reporting has been off and states 80+ degreesC.  Is it is reporting in F and DL ILO not converting to C?

Anyway I thought no bother, until last night I got 3 alerts from ILO (Critical, Info, Repaired):

EVENT (04 Feb 21:20): Automatic Operating System Shutdown Initiated Due to Overheat Condition

EVENT (04 Feb 21:21): Automatic Operating System Shutdown Due to Overheat Aborted

EVENT (04 Feb 21:21): Automatic Operating System Shutdown Initiated Due to Overheat Condition

ilo, 1.32 Nov 05 2013 | ProLiant DL320e Gen8 v2, P80 09/01/2013

Controller in Slot 1

• Controller Status  OK Serial Number PDSXH0ARH5M1SF Model HP Smart Array P222 Controller Firmware Version 4.68 Cache Module Status  OKCache Module Serial Number PBKUA0BRH5N0YE Cache Module Memory

  524288 KB

   

   

   

Sensor Location X Y Status Reading Thresholds

01-Inlet Ambient  Ambient  11  1   OK  19C  Caution: 42C; Critical: 46C 

02-CPU 1  CPU  13  6   OK  40C  Caution: 70C; Critical: N/A 

03-P1 DIMM 1-4  Memory  11  6   OK  25C  Caution: 87C; Critical: N/A 

04-HD Max  System  5  3   OK  35C  Caution: 60C; Critical: N/A 

05-Chipset  System  11  10   OK  43C  Caution: 105C; Critical: N/A 

07-VR P1  System  14  3   OK  30C  Caution: 115C; Critical: 120C 

08-Supercap Max  System  7  14   OK  24C  Caution: 65C; Critical: N/A 

09-iLO Zone  System  14  14   OK  41C  Caution: 77C; Critical: 82C 

11-LOM Zone  System  11  15   OK  36C  Caution: 68C; Critical: 73C 

12-PCI 1 I/O Board 10 12  OK 84C Caution: 100C; Critical: N/A 

14-PCI 1 Zone  I/O Board  11  14   OK  36C  Caution: 69C; Critical: 74C 

15-PCI 2 Zone  I/O Board  12  14   OK  34C  Caution: 73C; Critical: 78C 

16-System Board  System  13  8   OK  25C  Caution: 68C; Critical: 73C 

17-Sys Exhaust  Chassis  14  15   OK  32C  Caution: 67C; Critical: 72C 

And in fahrenheit:

Sensor Location X Y Status Reading Thresholds

01-Inlet Ambient  Ambient  11  1   OK  64F  Caution: 108F; Critical: 115F 

02-CPU 1  CPU  13  6   OK  104F  Caution: 158F; Critical: N/A 

03-P1 DIMM 1-4  Memory  11  6   OK  77F  Caution: 189F; Critical: N/A 

04-HD Max  System  5  3   OK  95F  Caution: 140F; Critical: N/A 

05-Chipset  System  11  10   OK  109F  Caution: 221F; Critical: N/A 

07-VR P1  System  14  3   OK  86F  Caution: 239F; Critical: 248F 

08-Supercap Max  System  7  14   OK  75F  Caution: 149F; Critical: N/A 

09-iLO Zone  System  14  14   OK  106F  Caution: 171F; Critical: 180F 

11-LOM Zone  System  11  15   OK  97F  Caution: 154F; Critical: 163F 

12-PCI 1 I/O Board 10 12  OK 185F Caution: 212F; Critical: N/A 

14-PCI 1 Zone  I/O Board  11  14   OK  97F  Caution: 156F; Critical: 165F 

15-PCI 2 Zone  I/O Board  12  14   OK  93F  Caution: 163F; Critical: 172F 

16-System Board  System  13  8   OK  77F  Caution: 154F; Critical: 163F 

17-Sys Exhaust  Chassis  14  15   OK  90F  Caution: 153F; Critical: 162F 

Have checked with my fingers and it's not above 50c (generally one can't hold one's finger on something much hotter than 50C).  Is this a firmware issue with the P222?

Thanks,

Al

p.s. the formatting of the message was much nice before but HP forums won't let you copy and past their own HTML from ILO into this forum :-/

HP ML310 G5p server  - SAS drives not detected... please help.

Hello,

Ive recently bought an old HP ML310 G5p server from a friend, server wich fits my specs need at the moment...

I had 2 spare DELL Cheetah 15k SAS 600gb hdds lying around from an ebay sale...waiting to be used on such a server...so i tryed to fit them in...

The problem is that both of the hdd caddies light up at startup, flash some led lights and go off...but the hdds are not detected!

I tried enabling the Raid option in the BIOS but with no luck...when scanning for devices none are recognized.

I have looked some info up on adding a new hdd, and ive read about some need for an adapter for SAS hdds...

I can see the HP 451781-001 Proliant ML310 ML350 G5 Server SAS SATA Backplane Board installed inside and all cables are fitted...but still no detection..

Now my question is this: Do i need some other controller to be able to use SAS 15k 600gb on my server or both of the drives could have failed...thus a failed ebay purchase of them ?

Please help guys.

Evening!

Have installed RHEL 6.5 on a ProLiant DL360p Gen8. Have managed to get the system to do a gracefull shutdown on Windows by installing ProLiantMonitor (HP ProLiant Health Monitor Service) and sysdown (HP ProLiant System Shutdown Service)

But if we want this same behaviour on RHEL, what should be installed then? Cant seem to find an 'exact' counterpart for RHEL on Drivers

Regards

Richard

Someone tell me why it's so difficult to update a server using the new 6.2 HPSUM

The old Proliant Support Packs worked time after time. I've tried installing 6.2 on 3 machines and none of them will get up and work. I'm so frustrated. Updating a server used to take 30 mins. Now I've spent days just trying to complete the initial inventory. You're going backwards HP.

Theres very little useful documentation to follow with this software also. I have installed it on a non HP machine, just my local tower like I used to, and it will always fail the localhost inventory - yes b/c it's not an HP. I've also tried it on some DL360P G8, and a DL360p G6. None work.

So. I'm kind of lost where to begin - I can't even find the "Check the logs for errors" logfile that it's referring to so that I can begin to troubleshoot this. I did get the W2012R2 support pack installed - but that fails on my baseline of 2012R2 servers too.

The system has 4 x 2.5SATA drives. I have tried RAID10 and RAID1. Used a 500GB partition for the Windows install. Every time the install gets all the way to the end of the initial install after it completes copying the Windows files and it about to reboot when I get:

Windows could not prepare the computer to boot in the next phase of the installation. To install Windows, restart the installation.

This has happened 3 separate times all at the same place. What am I missing here? Is there some incompatability issue with Windows 2008 R2? The system has 2GB of RAM. I can't tell what kind of memory it is (ECC, non-ECC, etc.)

Thanks, Michael

I need to connect external disk for backup.

We have 2 internal 2,5 Hard Drive Bays (16 disk) with system and database information. 

Controller p410i with SAS expander.

1783 Slot 5 Drive Array Controller Failure

Command failure (cmd=11h, err=820h)

<><><>

Background

HP DL380 G5 with 8 internal SAS disks via P400 controller (which boots first and fine)

HP Smart Array 6400 series (6402) connected to MSA30 (14 U320 disks)

Running ESXI 5

When initializing the second controller (6402) after @ 5 mins I get the 1783 message.

Part numbers on the card are;-

273915-B21 (from the box)

Serial Number - TNHBLMPK6J (from the card)

SP - 309520-001 (on the card)

322391-001 (on the card)

Can anyone help please?

Thank you.

I'm wondering if someone can provided some assistance in installing Windows 7 x64 .

I have upgraded the PSU to a Corsair TX750M PSU.

When booting off the Windows 7 x64 DVD it gets past the loading windows files screen but gets stuck at the "Stating Windows Logo Screen"

I have tried it with different DVD's (tried x86 as well) and HD's and everytime it gets stuck at the "Stating Windows Logo Screen"

I have checked for a BIOS update (using the most current) and reviewed the BIOS and can't see anything that stands out

From viewing the forums I can see that it has been done, just wondering if someone point out what I'm missing.

I know it's old but it's the only Proliant M110 so far with a PCI-Express x16 slot

Thank you

I have a customer which is using an application on W2K8 R2 that relies on  the "friendly name" of the Broadcom NIC,

so the application  wants NC373i DP Multifunction Gigabit Server Adapter #1  and  #2.

On his server (DL380G5 with 2 NIC's integrated on it), both NIC's has the friendly name #48 and #49 instead of #1 and #2.

How can I change that back to the low values ?? 

I've tried that by uninstalling the NIC's in cp/system; (but #48 and #49 stays)

i've looked for hiddendevices via 'set devmgr_show_nonpresent_devices=1' and then Show hidden devices

(but there are no hidden NIC's)

i've tried within the registry (but after modify it (replace ownership); it was not saved)

So, is there anybody knows how to do that ???

Hello all,

we noticed alarm CpqDa6AccelStatusChange(Accelerator  Board  Status  Change) on ProLiant DL380 G5.

According to manual : "This trap  signifies that  the  agent  has detected  a change in the status of an array    accelerator cache  board.  The current status is represented by the variable  cpqDaAccelStatus. "

I'd like to ask you how to read variable  cpqDaAccelStatus from ProLiant DL380 G5.

Can somebody to help us ?

We can use HP Array Configuration Utility CLI or ILOM.

Server type:  Linux 2.6.18-238.1.1.el5 x86_64
Server model: ProLiant DL380 G5

   Thank you

        BR

                Milos

Hi guys

My apologies if my english is not so good, It's not my main language.

After many atempts I decided to try to ask you guys some help. I got this  ProLiant ML150 G6 that when I press the power button he tries to power on normaly (fans do the tipicall process of blowing a lot of air) after some seconds, the server just reeboots again. It just stays this way untill I shut it down. The leds are all green when I turn him on (the health led and power led, also the internal leds on the motherboard are green too).Initially I suspected it was the motherboard, since there was no sign of posting, so I took out the RAM to see if the board beeped from missing the RAM, so it did. Still searched for fisical signs of damage on the motherboard and there is no signs. I tought it was the cpu and I replaced it but still does the same reebooting. Tried to power on the computer  with only the basic components to see if the server would boot up, but I didnt. Tested the RAM's one by one and still no sign, checked all the leds but everything is green(even though the LED1 on the mother board is blinking, but in the manual I dont see any reference to that. The power supply led is also green. So after reading the model manual and trobleshot guide I'm out of ideas, so would anyone so kindly share some light on whats hapening?

Thanks for taking your time to read my problem.

HoraT

Hello !

I try to install proliant support pack agent on ProLiant DL380 G6  ,  SUSE Linux Enterprise Server 10 (x86_64)  , PATCHLEVEL = 3

This agent provides communication between client and server HP SIM .

After 5 minutes after i run ./hpsum /s  my server gone to reboot

Here /var/log/messages :

Jan 31 12:35:48 server_name auditLog[23918]: cpqacuxe-9 ====== HP Smart Update Manager Installation Log ======   Preparing...                ##################################################  cpqacuxe                    ##################################################    DOWNGRADE NOTE: To downgrade this application to any version prior to 9.10.x.x, the current RPM must be manually uninstalled using the "rpm -e" command before any prior versions can be installed.    LOCKING NOTE: The locking mechanism starting with versions 9.10.X.X, are not compatible with prior versions of the applications. Therefore, mixing older and newer versions of the various applications (ACU, HPACUCLI, HPACUSCRIPTING) is not recommended.    Component update finished successfully with return code: 0
Jan 31 12:35:50 server_name auditLog[23918]: fibreutils-3 ====== HP Smart Update Manager Installation Log ======   Preparing...                ##################################################  fibreutils                  ##################################################  Component update finished successfully with return code: 0
Jan 31 12:35:50 server_name kernel: ipmi_msghandler: module not supported by Novell, setting U taint flag.
Jan 31 12:35:50 server_name kernel: ipmi message handler version 36.0
Jan 31 12:35:51 server_name auditLog[23918]: hp-OpenIPMI-8 ====== HP Smart Update Manager Installation Log ======   Preparing...                ##################################################  hp-OpenIPMI                 ##################################################  Please read the Licence Agreement for this software at             /opt/hp/hp-OpenIPMI/COPYING                         and           /opt/hp/hp-OpenIPMI/hp-OpenIPMI.license    By not removing this package, you are accepting the terms  of the included licenses.    The man page, hp-OpenIPMI(4), describes how to enable and use  the hp-OpenIPMI device drivers.  Component update finished successfully with return code: 0
Jan 31 12:35:54 server_name automount[25762]: failed to mount /speal/share
Jan 31 12:36:00 server_name auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 auditLog[23918]: 6:00 1452275968ditLog[23918]: 6:00 14522759681452275984tLog[23918]: 6:00 14522759681452275984531000001012620501020g[23918]: 6:00 14522759681452275984531000001012620501020g
Jan 31 12:36:01 server_name sshd[19253]: debug1: Forked child 27355.
Jan 31 12:36:01 server_name sshd[27355]: debug1: rexec start in 6 out 6 newsock 6 pipe 8 sock 9
Jan 31 12:36:01 server_name sshd[27355]: debug1: inetd sockets after dupping: 3, 3
Jan 31 12:36:01 server_name sshd[27355]: Connection from 12.34.56.78 port 36769
Jan 31 12:36:01 server_name sshd[27355]: debug1: Client protocol version 2.0; client software version OpenSSH_4.2
Jan 31 12:36:01 server_name sshd[27355]: debug1: match: OpenSSH_4.2 pat OpenSSH*
Jan 31 12:36:01 server_name sshd[27355]: debug1: Enabling compatibility mode for protocol 2.0
Jan 31 12:36:01 server_name sshd[27355]: debug1: Local version string SSH-2.0-OpenSSH_4.2
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: initializing for "root"
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: setting PAM_RHOST to "server_name_another"
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: setting PAM_TTY to "ssh"
Jan 31 12:36:01 server_name sshd[27355]: Failed none for root from 12.34.56.78 port 36769 ssh2
Jan 31 12:36:01 server_name sshd[27355]: debug1: temporarily_use_uid: 0/0 (e=0/0)
Jan 31 12:36:01 server_name sshd[27355]: debug1: trying public key file /root/.ssh/authorized_keys
Jan 31 12:36:01 server_name sshd[27355]: debug1: matching key found: file /root/.ssh/authorized_keys, line 2
Jan 31 12:36:01 server_name sshd[27355]: Found matching RSA key: AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA
Jan 31 12:36:01 server_name sshd[27355]: debug1: restore_uid: 0/0
Jan 31 12:36:01 server_name sshd[27355]: debug1: temporarily_use_uid: 0/0 (e=0/0)
Jan 31 12:36:01 server_name sshd[27355]: debug1: trying public key file /root/.ssh/authorized_keys
Jan 31 12:36:01 server_name sshd[27355]: debug1: matching key found: file /root/.ssh/authorized_keys, line 2
Jan 31 12:36:01 server_name sshd[27355]: Found matching RSA key: AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA
Jan 31 12:36:01 server_name sshd[27355]: debug1: restore_uid: 0/0
Jan 31 12:36:01 server_name sshd[27355]: debug1: ssh_rsa_verify: signature correct
Jan 31 12:36:01 server_name sshd[27355]: debug1: do_pam_account: called
Jan 31 12:36:01 server_name sshd[27355]: Accepted publickey for root from 12.34.56.78 port 36769 ssh2
Jan 31 12:36:01 server_name sshd[27355]: debug1: monitor_child_preauth: root has been authenticated by privileged process
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: establishing credentials
Jan 31 12:36:01 server_name sshd[27355]: debug1: Entering interactive session for SSH2.
Jan 31 12:36:01 server_name sshd[27355]: debug1: server_init_dispatch_20
Jan 31 12:36:01 server_name sshd[27355]: debug1: server_input_channel_open: ctype session rchan 0 win 131072 max 32768
Jan 31 12:36:01 server_name sshd[27355]: debug1: input_session_request
Jan 31 12:36:01 server_name sshd[27355]: debug1: channel 0: new [server-session]
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_new: init
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_new: session 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_open: channel 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_open: session 0: link with channel 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: server_input_channel_open: confirm session
Jan 31 12:36:01 server_name sshd[27355]: debug1: server_input_channel_req: channel 0 request exec reply 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_by_channel: session 0 channel 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_input_channel_req: session 0 req exec
Jan 31 12:36:01 server_name sshd[27362]: debug1: PAM: reinitializing credentials
Jan 31 12:36:01 server_name sshd[27362]: debug1: permanently_set_uid: 0/0
Jan 31 12:36:01 server_name sshd[27355]: debug1: Received SIGCHLD.
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_by_pid: pid 27362
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_exit_message: session 0 channel 0 pid 27362
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_exit_message: release channel 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_by_channel: session 0 channel 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_close_by_channel: channel 0 child 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: session_close: session 0 pid 0
Jan 31 12:36:01 server_name sshd[27355]: debug1: channel 0: free: server-session, nchannels 1
Jan 31 12:36:01 server_name sshd[27355]: Connection closed by 12.34.56.78
Jan 31 12:36:01 server_name sshd[27355]: debug1: do_cleanup
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: cleanup
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: deleting credentials
Jan 31 12:36:01 server_name sshd[27355]: debug1: PAM: closing session
Jan 31 12:36:01 server_name sshd[27355]: Closing connection to 10.254.58.195
Jan 31 12:36:02 server_name kernel: ipmi_msghandler: module not supported by Novell, setting U taint flag.
Jan 31 12:36:02 server_name kernel: ipmi message handler version 36.0
Jan 31 12:36:02 server_name kernel: ipmi_msghandler: module not supported by Novell, setting U taint flag.
Jan 31 12:36:02 server_name kernel: ipmi message handler version 36.0
Jan 31 12:36:02 server_name kernel: ipmi_devintf: module not supported by Novell, setting U taint flag.
Jan 31 12:36:02 server_name kernel: ipmi device interface
Jan 31 12:36:02 server_name kernel: ipmi_si: module not supported by Novell, setting U taint flag.
Jan 31 12:36:02 server_name kernel: IPMI System Interface driver.
Jan 31 12:36:02 server_name kernel: ipmi_si: Searching for PCI Vendor 0x103c, Device 0x3302
Jan 31 12:36:02 server_name kernel: ipmi_si: Trying "kcs" at memory address 0xf1ef0000
Jan 31 12:36:02 server_name kernel: GSI 26 sharing vector 0xEA and IRQ 26
Jan 31 12:36:02 server_name kernel: ACPI: PCI Interrupt 0000:01:04.6[A] -> GSI 21 (level, low) -> IRQ 234
Jan 31 12:36:02 server_name kernel: ipmi_si: Found PCI BMC at BAR address 0xf1ef0000
Jan 31 12:36:02 server_name kernel: ipmi_si: Using PCI Plug and Play interrupt 234
Jan 31 12:36:04 server_name kernel:  IPMI kcs interface [0] initialized
Jan 31 12:36:05 server_name hpasmxld[27561]: hpDeferSPDThread: Starting thread to collect DIMM SPD Data.
Jan 31 12:36:05 server_name hpasmxld[27561]: WARNING: System Power Supply: General Failure (Power Supply 2)
Jan 31 12:36:05 server_name hpasmxld[27561]: WARNING: System Power Supplies Not Redundant
Jan 31 12:36:05 server_name hpasmxld[27561]: NOTICE: System Power Supply: General Failure (Power Supply 2) has been repaired
Jan 31 12:36:05 server_name hpasmxld[27561]: NOTICE: System Power Supplies Not Redundant has been repaired
Jan 31 12:36:05 server_name hpasmxld[27561]: WARNING: System Overheating (Temperature Sensor 1, Location Ambient, Temperature 42C)
Jan 31 12:36:05 server_name hpasmxld[27561]: A System Reboot has been requested by the management processor in 60 seconds.
Jan 31 12:36:05 server_name hpasmxld[27561]: A System Reboot has been initiated by the management processor.
Jan 31 12:36:05 server_name shutdown[27582]: shutting down for system reboot
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: disagrees about version of symbol ipmi_create_user
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: Unknown symbol ipmi_create_user
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: disagrees about version of symbol ipmi_destroy_user
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: Unknown symbol ipmi_destroy_user
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: disagrees about version of symbol ipmi_request_supply_msgs
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: Unknown symbol ipmi_request_supply_msgs
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: Unknown symbol ipmi_free_recv_msg
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: disagrees about version of symbol ipmi_get_version
Jan 31 12:36:05 server_name kernel: ipmi_watchdog: Unknown symbol ipmi_get_version
Jan 31 12:36:06 server_name hpasrd[27607]: Starting with poll 1 and timeout 600
Jan 31 12:36:06 server_name hpasrd[27607]: Setting the watchdog timer.
Jan 31 12:36:06 server_name hpasrd[27607]: Found iLO memory at 0xf1fe0000.
Jan 31 12:36:06 server_name hpasrd[27607]: Successfully mapped device.
Jan 31 12:36:07 server_name init: Switching to runlevel: 6
Jan 31 12:36:07 server_name hpasmxld[27561]: NOTICE: System Overheating (Temperature Sensor 1, Location Ambient, Temperature 42C) has been repaired
Jan 31 12:36:07 server_name hpasmxld[27561]: The system shutdown has been cancelled by the management processor.
Jan 31 12:36:07 server_name auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 auditLog[23918]: 6:07 audit12643774400g[23918]: 6:07 audit12643774400
Jan 31 12:36:08 server_name auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 auditLog[23918]: 6:08 aud%Log[23918]: 6:08 aud%
Jan 31 12:36:08 server_name kernel: bootsplash: status on console 0 changed to on
Jan 31 12:36:14 server_name automount[26362]: failed to mount /speal/share
Jan 31 12:36:15 server_name xinetd[19912]: Exiting...
Jan 31 12:36:24 server_name hpasrd[27607]: Stopping the timer.
Jan 31 12:36:26 server_name hpasmxld[27561]: Process has been instructed to stop from the user interface. Stopping hpasmxld process. . .
Jan 31 12:36:33 server_name syslog-ng[27876]: Error connecting to remote host AF_INET(19.144.4.105:514), reattempting in 60 seconds
Jan 31 12:36:34 server_name sshd[19253]: Received signal 15; terminating.
Jan 31 12:36:35 server_name multipathd: mpathh: stop event checker thread
Jan 31 12:36:35 server_name multipathd: mpathg: stop event checker thread
Jan 31 12:36:35 server_name multipathd: --------shut down-------
Jan 31 12:36:36 server_name [CMA]: Received signal to stop CMA
Jan 31 12:36:36 server_name [CMA]: Shutting down cma
Jan 31 12:36:38 server_name shadow[28193]: new group added - group=hpsmh, gid=7011999, by=0
Jan 31 12:36:38 server_name useradd[28194]: new account added - account=hpsmh, uid=7018275, gid=7011999, home=/opt/hp/hpsmh, shell=/sbin/nologin, by=0
Jan 31 12:36:38 server_name useradd[28194]: running USERADD_CMD command - script=/usr/sbin/useradd.local, account=hpsmh, uid=7018275, gid=7011999, home=/opt/hp/hpsmh, by=0
Jan 31 12:36:44 server_name automount[27766]: failed to mount /speal/share
Jan 31 12:36:47 server_name auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 auditLog[23918]: 6:47 aud%Log[23918]: 6:47 aud%
Jan 31 12:36:57 server_name kernel: Kernel logging (proc) stopped.
Jan 31 12:36:57 server_name kernel: Kernel log daemon terminating.
Jan 31 12:36:58 server_name syslog-ng[27876]: syslog-ng version 1.6.8 going down
Jan 31 15:07:22 server_name syslog-ng[4618]: syslog-ng version 1.6.8 starting

Hello.

We have 6 new DL380p G8 servers each with 2 on-board 10gigE ports and 1 iLO (the only RJ45).

Today we decided to enable iLO Shared Network port on 1 of the servers and ever since we haven't been able to access that iLO again.

Apparently we must have made a mistake while configuring the Shared port but since the Shared port is enabled it means that the dedicated port is disabled. This way we can't connect neither through the dedicated port nor through the shared port.

Just to spice things up a bit we don't have a KVM on the datacenter...

Is there anyway we can factory default that iLO so that we can regain connection?

Thanks in advance

Hi,

I was trying to expand my HP ProLiant server by adding additional hard disk. I was having 300 GB x 3 + 600 GB x3 hdd in different Raid 5. Now i wanted to remove the 600 GB x 3 and add 1.2 TB x 5 hdd and make the same Raid as before, so i will have 4.8 TB as storage. I did remove the 600 GB x 3 and added 1.2 TB x 5, but when i run HP Array configuration utility i cant find there create array to create new array. Can somebody help me on this.

Thanks and regards,

Shameer Mohammed

Currently we have an HP Proliant ML335 server with four 146GB SAS drives in a hardware RAID5 setup.  The array is divided into 2 logical drives which are drive "C:" and drive "D:".  See attached diagram.

 The array controller is a "HP Smart Array E200i".   All of the array controller GUI based utilities are installed.  The OS is Windows SBS2008.  

We are running out of space on the "C:" drive and need to increase our storage space.  We are trying to determine the best way to do this.    We intend to double our total drive space.

One way, according to the HP Smart Array E200i manual would be to add new drives and run the "Expand" and "Extend" utility in the "Array Configuration Utility " (ACU).  However, the manual states that the expansion works at the speed of about 1GB per 15 minutes.  For our server which has about 430GB total capacity, this would take about 4.5 days!

Another way would be to use our Windows SBS2008 full backup and do a "bare metal" recovery to new drives.   To me this seems like the best solution, however, my concern is that the recovered image would be looking for different hard drives and this would create a problem.  Also, would the HP array configuration utility automatically readjust for different hardware?

Any suggestions from anyone who has experience with doing this would be greatly appreciated.