All ProLiant Servers (ML,DL,SL) posts

Hi folks,

I've been digging a bit more trying to pinpoint the problem. I uninstalled the HP ProLiant Agentless Management Service, and the errors stopped filling up the log. It also seemed that this service flooded the PowerShell log with informational messages (~40000 per day), which now is down to the occasional logging of "normal" PowerShell events.

But the question remains, whether there are issues with the controller or motherboard interface, or buggy software. Running diagnostics on the controller gives nothing, everything in good order.

Checking on the temperatures, sensor 25 reports a temperature of 75 °C. IMHO it seems a bit high, but still well within limits.

Any comments very welcome.

Best regards,

Pete

Sorry - too eary in the day to think ...

It's a ProLiant DL80 Gen9 server with a Dynamic Smart Array B140i RAID Controller

It's running Windows Server 2012 R2

I had been using the HPE Systems Management and that was giving me the details on the disk controller. I've now installed HPE SSA and run a diagnostics report which is at https://www.dropbox.com/s/ig8ikj35ne7dcq6/ADUReport.zip?dl=0. I'm working my way through this but not seeing anything with my untrained eye that helps.

Thanks

Motherboard from server HP ProLiant SE1220 (p/n of mb: 591747-001). Screen -https://goo.gl/9UJ5Fd

Search has no result!

Please, give me a full description about this motherboard. Want to know all possible information.
Amount, and version of all ports: Ethernet, USB, PCI, SATA... Possible configuration of RAM, version of BIOS, and other...

Can't find this info on HP official site

Hello - We recently subscribed to the Datto Siris Backup 'Soulution'. The product works well except that after level 3 support, their BMR (Bare Metal Restore) is not comatable with HP Smart Array. Level 3 support suggested turning off the Smart array but I do not think that is possible as we are using the SAS drives.

1) Is there a way to run a SAS drive without the Smart Array?

2) Has anyone used the Datto Siris Product?

Many Thanks - Rich

Hi was hoping I can get some help - newbie to servers/networking. Have a proliant DL380 G7, have a SSD for OS and had 7 SATA HDDs that I was trying to set up for RAID5 but wanted one as a spare. Used both ORCA and HP SmartStart, but doesn't give me the option of setting up spare drive (the option is listed but won't let me select it). I am otherwise able to set up the logical drive as a RAID 5 and seems to be recognized ok but want to have a spare drive in case of failure. Also, anyone know why when trying to create logical drive for SSD, it forces RAID 0? Seems to create logical drive ok, but I thought RAID 0 was meant to have 2 drives. Should I be creating RAID 0 logical drive for SSD? Thanks for the help

Perfect, it works!

It's the iLO4 Core driver (iLO34MgmtCtrlPkg - hpqilo3core.sys)

Thanks for helping me!

Thanks - it has been rebooted several times.

F2 shows messages that the disk array needs to be rebuilt and is queued for rebuilding

F1 continues to boot

I've looked in the Smart Disk Array controller from boot up and couldn't see any options there to trigger the rebuild. Everything indicates it is queued for rebuilding and it should just happen. But it's been a few weeks and still nothing!

In the B140i User guide please read chapter

Recovering from compromised fault tolerance

Hi,

Anyone from HP that can answer why you develop drivers for VMware (as vSphere 6.5) but not newer drivers for Windows?

Latest driver release was for Windows Server 2012 but thankfully worked also under Windows Server 2012R2.

Br,

Ase

Hello,
DL 160 G9 is not detecting network adeptor 530 sfp ...network adeptor is not booting,
please guide me ,

Installing this fixed the issue for me

http://h20564.www2.hpe.com/hpsc/swd/public/detail?swItemId=MTX_c93c5f85ea0d471baddb6eadfeThanks

Proliant DL360 Gen 9

Windows 2012 R2

Thanks for the help

Mak

Since your Server has about 4TB Logical Volume to rebuild from "good" disk (D006) to the replaced one (D007):

[2017-07-19 09:03:50] Array B Unit U01: RAID 1
[2017-07-19 09:03:50]   U01 from 2 drives: D006D007[R]
[2017-07-19 09:03:50]   stripsize=512 (256 KiB) volstate=NEEDS_REBUILD datadrives=1 paritygroups=1 cache=disabled accel=disabled/disabled
[2017-07-19 09:03:50]   offset=0x0 logical_blocks=0x1D1BFBEB0 (3725 GiB)
[2017-07-19 09:03:50]   uf=0x0 srf=0x1 dt=3 pdm=0 psf=4 bd=0x0 naz=0x0 nwz=0x0 bsf=512 muf=0x0

where D006 and D007 disks are, respectively:

[2017-07-19 09:03:50] D006 p0|0x1 [01]P2I:02:03,HDD  ATA     ,ST4000NM0033-9ZM,SN06    ,S1Z2GDX1            ,NCQ,07K,SCFW=11,SCTYPE=1
[2017-07-19 09:03:50] D007 p0|0x1 [01]P2I:02:04,HDD  ATA     ,ST4000NM0033-9ZM,SN06    ,S1Z2KC9C            ,NCQ,07K,SCFW=11,SCTYPE=1

supposing the only one remaining disk (D006) of that particular RAID 1 is good enough (has no unrecoverable errors) then the rebuilt process - in the very best case - would be very long (leaving the RAID 1 Volume U01 "degraded" and so unprotected against another drive failure)...probably it would take up to 2 weeks (considering an average of 20 minutes per Gigabyte)...if it starts.

It's not starting...AFAIK.

Regarding the ADU logged Error, the HPE ProLiant Gen9 Troubleshooting Guide (Volume II: Error Messages) reports:

Logical drive state: The logical drive is queued for rebuilding

Symptom

Logical drive state: The logical drive is queued for rebuilding.

Cause

A logical drive is queued for rebuilding.

Action

No action is required. Normal operations can occur; however, performance will be less than optimal during the rebuilding process.

Maybe I'm wrong in reading ADU logs...but it seems that the drive you used as replacement (D007) ran for at least 1400 hours (Power On hours) - so it's not "new" - compared to about 8300 hours of the drive your RAID 1 is rebuilding from (D006)...don't know if this is positive or not regarding rebuilding speed (Server I/O Load it is for sure...since Online rebuilding happens when OS is running...you should consider this point)...another thing to say reading your logs (Slot0b.txt) is that D006 and D007 about 1 Year ago (August 2016) were differents units (see theirs respective Serial Numbers), same models:

[2016-06-28 09:05:06] D006 p0|0x1 [01]P2I:02:03,HDD  ATA     ,ST4000NM0033-9ZM,0001    ,Z1Z0TMBP            ,NCQ,07K,SCFW=11,SCTYPE=1
[2016-06-28 09:05:06] D007 p0|0x1 [01]P2I:02:04,HDD  ATA     ,ST4000NM0033-9ZM,0001    ,Z1Z18VW3            ,NCQ,07K,SCFW=11,SCTYPE=1

this means that something (bad sectors? failure(s) due to overtemperature?) already happened in the past to those two drives (initial D006 failure - U01 remained in degraded state for days/weeks since D006 was replaced with a new Disk, then rebuild started finally on September, 9th 2016 [*] and then, June 22nd 2017 very bad day for you old D007 disk this time, your Server started to have another issue on your old D007 - the one with S/N Z1Z18VW3 - replaced the day after).

On June, 23rd D007 was replaced with the one your Server has actually (S/N S1Z2KC9C) but its rebuild process never started (or, eventually if started as expected, never actually ended...which is a thing I personally doubt).

Also Surface Analysis processes seem to have, generally speaking, issues - Surface Analysis not completed - on all your RAID 1 / RAID 5 Volumes (at least for U00, U01 and U02 as per ADU Logs)

At this point, what's about:

Checking your Server's status regarding Firmware version (especially the SystemROM for your Server which embed Firmware for Dynamic Smart Array B140i) and B140i Software Drivers version (especially the Storage driver) for your Microsoft Windows Server 2012 R2 operating system?
Checking if disks you use are good enough (failure rate is strange or they are very heavily used or not best suited to be used into a Server) considering they look like non genuine HPE SATA drives (their Firmware looks the Seagate Constellation ES.3 original one, not the typical HPE - HPxx(x) - customized one found on genuine branded HPE drives for HPE ProLiant Gen9).
Checking Server's operational temperature (the higher it is the worst it is for rotational disks).

So questions, in the end, are:

Why rebuild process of U01 is not starting?
Is the D006 drive really good? (it hasn't unrecoverable errors that may stop rebuild process to start)

Note that Rebuild Priority for the HPE Dynamic Smart Array B140i is set to Rapid High.

[*] September, 9th rebuild of D006 from D007 happened:

[2016-09-09 10:29:19] Array B Unit U01: RAID 1
[2016-09-09 10:29:19]   U01 from 2 drives:  D006[R] D007
[2016-09-09 10:29:19]   stripsize=512 (256 KiB) volstate=NEEDS_REBUILD datadrives=1 paritygroups=1 cache=enabled accel=disabled/disabled
[2016-09-09 10:29:19]   offset=0x0 logical_blocks=0x1D1BFBEB0 (3725 GiB)
[2016-09-09 10:29:19]   uf=0x0 srf=0x1 dt=3 pdm=0 psf=4 bd=0x0 naz=0x0 nwz=0x0 bsf=512 muf=0x0
[2016-09-09 10:29:19] Array B Unit U01: RAID 1
[2016-09-09 10:29:19]   U01 from 2 drives:  D006[R] D007
[2016-09-09 10:29:19]   stripsize=512 (256 KiB) volstate=REBUILDING datadrives=1 paritygroups=1 cache=enabled accel=disabled/disabled
[2016-09-09 10:29:19]   offset=0x0 logical_blocks=0x1D1BFBEB0 (3725 GiB)
[2016-09-09 10:29:19]   uf=0x0 srf=0x1 dt=3 pdm=0 psf=4 bd=0x0 naz=0x0 nwz=0x0 bsf=512 muf=0x0
[2016-09-09 10:29:19] Starting rebuild U01 D006 ibc=2048
[2016-09-09 10:39:19] Rebuild progress U01 D006: 0x1C66B16B0 blocks remaining, 2.5% complete (will START OVER if reset)
[2016-09-09 10:49:20] Rebuild progress U01 D006: 0x1BB09D6B0 blocks remaining, 4.9% complete (will START OVER if reset)
[2016-09-09 10:59:21] Rebuild progress U01 D006: 0x1AFA4F6B0 blocks remaining, 7.4% complete (will START OVER if reset)
[2016-09-09 11:09:22] Rebuild progress U01 D006: 0x1A458F6B0 blocks remaining, 9.8% complete (will START OVER if reset)
[2016-09-09 11:19:22] Rebuild progress U01 D006: 0x19923B6B0 blocks remaining, 12.2% complete (will START OVER if reset)
[2016-09-09 11:29:24] Rebuild progress U01 D006: 0x18DE92EB0 blocks remaining, 14.6% complete (will START OVER if reset)
[2016-09-09 11:39:25] Rebuild progress U01 D006: 0x182BC76B0 blocks remaining, 17.0% complete (will START OVER if reset)
[2016-09-09 11:49:26] Rebuild progress U01 D006: 0x177B946B0 blocks remaining, 19.4% complete (will START OVER if reset)
[2016-09-09 11:59:26] Rebuild progress U01 D006: 0x16CAFBEB0 blocks remaining, 21.7% complete (will START OVER if reset)
[2016-09-09 12:09:27] Rebuild progress U01 D006: 0x161D216B0 blocks remaining, 24.1% complete (will START OVER if reset)
[2016-09-09 12:19:27] Rebuild progress U01 D006: 0x156FFE6B0 blocks remaining, 26.4% complete (will START OVER if reset)
[2016-09-09 12:29:28] Rebuild progress U01 D006: 0x14C3756B0 blocks remaining, 28.7% complete (will START OVER if reset)
[2016-09-09 12:39:29] Rebuild progress U01 D006: 0x141A45EB0 blocks remaining, 31.0% complete (will START OVER if reset)
[2016-09-09 12:49:31] Rebuild progress U01 D006: 0x1370DEEB0 blocks remaining, 33.3% complete (will START OVER if reset)
[2016-09-09 12:59:32] Rebuild progress U01 D006: 0x12C7536B0 blocks remaining, 35.5% complete (will START OVER if reset)
[2016-09-09 13:09:33] Rebuild progress U01 D006: 0x12219E6B0 blocks remaining, 37.8% complete (will START OVER if reset)
[2016-09-09 13:19:35] Rebuild progress U01 D006: 0x117BE16B0 blocks remaining, 40.0% complete (will START OVER if reset)
[2016-09-09 13:29:36] Rebuild progress U01 D006: 0x10D8BF6B0 blocks remaining, 42.2% complete (will START OVER if reset)
[2016-09-09 13:39:37] Rebuild progress U01 D006: 0x103661EB0 blocks remaining, 44.4% complete (will START OVER if reset)
[2016-09-09 13:49:38] Rebuild progress U01 D006: 0xF9719EB0 blocks remaining, 46.5% complete (will START OVER if reset)
[2016-09-09 13:59:38] Rebuild progress U01 D006: 0xEF8736B0 blocks remaining, 48.6% complete (will START OVER if reset)
[2016-09-09 14:09:40] Rebuild progress U01 D006: 0xE5B566B0 blocks remaining, 50.7% complete (will START OVER if reset)
[2016-09-09 14:19:40] Rebuild progress U01 D006: 0xDBFF36B0 blocks remaining, 52.8% complete (will START OVER if reset)
[2016-09-09 14:29:41] Rebuild progress U01 D006: 0xD27086B0 blocks remaining, 54.9% complete (will START OVER if reset)
[2016-09-09 14:39:42] Rebuild progress U01 D006: 0xC8FC9EB0 blocks remaining, 56.9% complete (will START OVER if reset)
[2016-09-09 14:49:43] Rebuild progress U01 D006: 0xBFAC26B0 blocks remaining, 58.9% complete (will START OVER if reset)
[2016-09-09 14:59:44] Rebuild progress U01 D006: 0xB679E6B0 blocks remaining, 60.9% complete (will START OVER if reset)
[2016-09-09 15:09:45] Rebuild progress U01 D006: 0xAD4C16B0 blocks remaining, 62.8% complete (will START OVER if reset)
[2016-09-09 15:19:46] Rebuild progress U01 D006: 0xA4710EB0 blocks remaining, 64.7% complete (will START OVER if reset)
[2016-09-09 15:29:47] Rebuild progress U01 D006: 0x9B94AEB0 blocks remaining, 66.6% complete (will START OVER if reset)
[2016-09-09 15:39:49] Rebuild progress U01 D006: 0x92E556B0 blocks remaining, 68.5% complete (will START OVER if reset)
[2016-09-09 15:49:49] Rebuild progress U01 D006: 0x8A701EB0 blocks remaining, 70.3% complete (will START OVER if reset)
[2016-09-09 15:59:50] Rebuild progress U01 D006: 0x81FA46B0 blocks remaining, 72.1% complete (will START OVER if reset)
[2016-09-09 16:09:51] Rebuild progress U01 D006: 0x799F96B0 blocks remaining, 73.9% complete (will START OVER if reset)
[2016-09-09 16:19:51] Rebuild progress U01 D006: 0x715E6EB0 blocks remaining, 75.7% complete (will START OVER if reset)
[2016-09-09 16:29:52] Rebuild progress U01 D006: 0x6942DEB0 blocks remaining, 77.4% complete (will START OVER if reset)
[2016-09-09 16:39:53] Rebuild progress U01 D006: 0x615F76B0 blocks remaining, 79.1% complete (will START OVER if reset)
[2016-09-09 16:49:54] Rebuild progress U01 D006: 0x59AB66B0 blocks remaining, 80.8% complete (will START OVER if reset)
[2016-09-09 16:59:54] Rebuild progress U01 D006: 0x51F5FEB0 blocks remaining, 82.5% complete (will START OVER if reset)
[2016-09-09 17:09:55] Rebuild progress U01 D006: 0x4A93F6B0 blocks remaining, 84.0% complete (will START OVER if reset)
[2016-09-09 17:19:56] Rebuild progress U01 D006: 0x43347EB0 blocks remaining, 85.6% complete (will START OVER if reset)
[2016-09-09 17:29:57] Rebuild progress U01 D006: 0x3C1F06B0 blocks remaining, 87.1% complete (will START OVER if reset)
[2016-09-09 17:39:57] Rebuild progress U01 D006: 0x3524CEB0 blocks remaining, 88.6% complete (will START OVER if reset)
[2016-09-09 17:49:59] Rebuild progress U01 D006: 0x2E298EB0 blocks remaining, 90.1% complete (will START OVER if reset)
[2016-09-09 18:00:00] Rebuild progress U01 D006: 0x27628EB0 blocks remaining, 91.6% complete (will START OVER if reset)
[2016-09-09 18:10:01] Rebuild progress U01 D006: 0x20C1F6B0 blocks remaining, 93.0% complete (will START OVER if reset)
[2016-09-09 18:20:02] Rebuild progress U01 D006: 0x1A3986B0 blocks remaining, 94.4% complete (will START OVER if reset)
[2016-09-09 18:30:04] Rebuild progress U01 D006: 0x1400E6B0 blocks remaining, 95.8% complete (will START OVER if reset)
[2016-09-09 18:40:06] Rebuild progress U01 D006: 0xDCABEB0 blocks remaining, 97.1% complete (will START OVER if reset)
[2016-09-09 18:50:08] Rebuild progress U01 D006: 0x7BFEEB0 blocks remaining, 98.4% complete (will START OVER if reset)
[2016-09-09 19:00:10] Rebuild progress U01 D006: 0x1E076B0 blocks remaining, 99.6% complete (will START OVER if reset)
[2016-09-09 19:03:25] Ending rebuild U01 D006 status=0x0
[2016-09-09 22:02:13] Logical drive U01 has completed a surface analysis pass.

Thank you! Navigating to that URL fixed it for me!

Hi,

Just found out why it was not working. I had to remove Names: in the Filter Area.

In resume: If you want to add a specific server for specific user, only the Server name of the Ilo should work.

Then after, we can add Warning and Critical error message.

Hello,
please guide me
Thanks,

The faulty drive:

684057-001, 397377-010, Spare: 454273-001
It´s a Hitachi HUA722010CLA330, FW: A3MA

According to the firmware number its not "special".
So I could replace it with the same Modell from HGST?

Or are these somehow different "locked"?
In General: Is it highly recommendable that both drives
are exactly the same, or is this for an "simple" raid 1 array not really a thing?

Thank you,
greetings

Martin

Hi.

Try to boot from HP SmartStart CD/USB key and use HP Array Configuration Utility. You should be able to use hot spare option from here.

br,

Are you referring to HPE Ethernet 10Gb 2-port 560SFP+ Adapter (665249-B21)?

What System ROM version is your HPE ProLiant DL160 Gen9 server currently running on?

What Operating System your HPE ProLiant DL160 Gen9 server is running?

Yse,
SPP 2016.10.1

Thanks - that seems to have solved it.

I followed the F2 option at boot up and several layers down behind the information message was an obscure option which when selected set off the rebuild. We're now at 1.78% so hopefully finished by next week.

For anyone coming across this ... all the "you don't need to do anything it just does it itself" posts out there didn't work for me. It did need manually initiating via the F2 option that comes up once it loads the smart array at boot up (well before Windows).

Re: Windows 2016 Smart Array P440 controller and failed IOCTL errors in StorDiag event log

Re: Smart Array Ready for Recovery - but recovery not starting

Where can i find all description of this motherboard ?

Datto Siris Backup

Need help with spare drive HP Proliant DL380 G7 with p410i 512mb cache controller

Re: Windows Server 2016 HP Proliant DL380 G9 - Driver Issue

Re: Smart Array Ready for Recovery - but recovery not starting

Re: Smart Array Ready for Recovery - but recovery not starting

Re: DL120G7 + P410 - Windows 2016 Support

Network adeptor 530 sfp

Re: HP System Management Homepage Blank

Re: Smart Array Ready for Recovery - but recovery not starting

Re: iLO4 remote console from Linux machine with Firefox doesn't start

Re: Alert Email Notification for specific Server

DL 160 G9 dose not detect 560 sfp+

Re: ML330 G6, bad drive, replace with off the shelf drive possible?

Re: Need help with spare drive HP Proliant DL380 G7 with p410i 512mb cache controller

Re: DL 160 G9 dose not detect 560 sfp+

Re: DL 160 G9 dose not detect 560 sfp+

Re: Smart Array Ready for Recovery - but recovery not starting