Good morning,

I shot a refurbished SE316M1R2 (8 HDD slots) with a Smart Array P410, running Debian jessie
with latest updates.
Now all slots are stuffed with disks but after testing with badblocks and writing /dev/zero disk by disk I saw the following errors in /var/log/syslog:

Dec 27 18:51:47 srv kernel: [538445.384663] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f9080Tag:0x00000000:000003e0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 18:51:47 srv kernel: [538445.384669] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 18:51:49 srv kernel: [538447.346236] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f9080Tag:0x00000000:000003e0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 18:51:49 srv kernel: [538447.346240] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 18:56:32 srv kernel: [538730.679531] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:56:32 srv kernel: [538730.679618] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:57:10 srv kernel: [538768.417086] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:57:10 srv kernel: [538768.417172] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:57:56 srv kernel: [538814.545090] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:57:56 srv kernel: [538814.545186] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:58:39 srv kernel: [538857.624544] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:58:39 srv kernel: [538857.624612] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:59:23 srv kernel: [538901.777368] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 18:59:23 srv kernel: [538901.777456] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:00:06 srv kernel: [538944.337646] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:00:06 srv kernel: [538944.337731] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:00:47 srv kernel: [538985.781224] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:00:47 srv kernel: [538985.781287] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:01:29 srv kernel: [539027.624373] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:01:29 srv kernel: [539027.624518] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:02:10 srv kernel: [539068.486771] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:02:10 srv kernel: [539068.486850] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:02:48 srv kernel: [539106.709280] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:02:48 srv kernel: [539106.709370] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:03:26 srv kernel: [539144.613964] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:03:26 srv kernel: [539144.614212] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:04:06 srv kernel: [539185.051880] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:04:06 srv kernel: [539185.051942] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:04:47 srv kernel: [539225.539093] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:04:47 srv kernel: [539225.539179] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:05:28 srv kernel: [539266.989874] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:05:28 srv kernel: [539266.989941] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:06:20 srv kernel: [539318.455943] hpsa 0000:06:00.0: scsi 4:0:0:5: resetting Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:06:20 srv kernel: [539318.456032] hpsa 0000:06:00.0: scsi 4:0:0:5: reset completed successfully Direct-Access     HP       LOGICAL VOLUME   RAID-0 SSDSmartPathCap- En- Exp=3
Dec 27 19:16:14 srv kernel: [539912.478868] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e24ba80Tag:0x00000000:000000f0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 19:16:14 srv kernel: [539912.478873] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 19:16:17 srv kernel: [539915.765388] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e24ba80Tag:0x00000000:000000f0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 19:16:17 srv kernel: [539915.765392] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 19:17:15 srv kernel: [539973.457800] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f8780Tag:0x00000000:000000f0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 19:17:15 srv kernel: [539973.457810] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 19:17:17 srv kernel: [539975.626265] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f8780Tag:0x00000000:000000f0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 19:17:17 srv kernel: [539975.626269] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:36:06 srv kernel: [544704.709570] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e248900Tag:0x00000000:00000120 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:36:06 srv kernel: [544704.709577] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:36:10 srv kernel: [544708.769058] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e248900Tag:0x00000000:00000120 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:36:10 srv kernel: [544708.769063] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:37:08 srv kernel: [544766.664563] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8809ee75b780Tag:0x00000000:00000100 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:37:08 srv kernel: [544766.664569] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:37:09 srv kernel: [544767.880729] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8809ee75b780Tag:0x00000000:00000100 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:37:09 srv kernel: [544767.880733] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:37:54 srv kernel: [544812.726962] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8805c7cc9080Tag:0x00000000:00000310 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:37:54 srv kernel: [544812.726968] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:37:58 srv kernel: [544816.672988] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8805c7cc9080Tag:0x00000000:00000310 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:37:58 srv kernel: [544816.672994] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:38:05 srv kernel: [544823.775287] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880206e78c00Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:38:05 srv kernel: [544823.775296] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:38:10 srv kernel: [544828.561327] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880206e78c00Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:38:10 srv kernel: [544828.561333] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:38:54 srv kernel: [544872.717609] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e249380Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:38:54 srv kernel: [544872.717618] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:38:58 srv kernel: [544877.256163] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880b8e249380Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:38:58 srv kernel: [544877.256167] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:39:54 srv kernel: [544932.696573] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f9c80Tag:0x00000000:000004a0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:39:54 srv kernel: [544932.696579] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:39:58 srv kernel: [544936.941115] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8806193f9c80Tag:0x00000000:000004a0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:39:58 srv kernel: [544936.941119] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:40:05 srv kernel: [544943.781126] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880206e79e00Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:40:05 srv kernel: [544943.781133] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:40:10 srv kernel: [544948.858441] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff880206e79e00Tag:0x00000000:000000d0 CDBLen: 6 CDB: 0x1201... SN: 0x0  SENT, FAILED
Dec 27 20:40:10 srv kernel: [544948.858447] hpsa 0000:06:00.0: scsi 4:3:0:0: FAILED to abort command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3
Dec 27 20:40:55 srv kernel: [544993.759610] hpsa 0000:06:00.0: scsi 4:3:0:0 Aborting command ffff8805f8d01800Tag:0x00000000:00000240 CDBLen: 6 CDB: 0x1201... SN: 0x0  BEING SENT
Dec 27 20:40:55 srv kernel: [544993.759615] hpsa 0000:06:00.0: scsi 4:3:0:0: Aborting command RAID              HP       P410             RAID-UNKNOWN SSDSmartPathCap- En- Exp=3

and so on. Some of the drives have repaired blocks on them but even if I write zeros to a drive without repaired errors I get those messages.

=> set target ctrl slot=2

   "controller slot=2"

=> show status

Smart Array P410 in Slot 2
   Controller Status: OK
   Cache Status: OK
   Battery/Capacitor Status: OK


=> pd all show status

   physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 72 GB): OK
   physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 72 GB): OK
   physicaldrive 1I:1:3 (port 1I:box 1:bay 3, 146.8 GB): OK
   physicaldrive 1I:1:4 (port 1I:box 1:bay 4, 146.8 GB): OK
   physicaldrive 2I:1:6 (port 2I:box 1:bay 6, 146.8 GB): OK
   physicaldrive 2I:1:8 (port 2I:box 1:bay 8, 146.8 GB): OK
   physicaldrive 2I:1:5 (port 2I:box 1:bay 5, 146.8 GB): OK
   physicaldrive 2I:1:7 (port 2I:box 1:bay 7, 146 GB): OK
=> show detail

Smart Array P410 in Slot 2
   Bus Interface: PCI
   Slot: 2
   Serial Number: PACCRID114409TH
   Cache Serial Number: PACCQID11231KM3
   RAID 6 (ADG) Status: Disabled
   Controller Status: OK
   Hardware Revision: C
   Firmware Version: 5.12
   Rebuild Priority: Medium
   Expand Priority: Medium
   Surface Scan Delay: 15 secs
   Surface Scan Mode: Idle
   Parallel Surface Scan Supported: No
   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: 0 secs
   Cache Board Present: True
   Cache Status: OK
   Cache Ratio: 25% Read / 75% Write
   Drive Write Cache: Disabled
   Total Cache Size: 256 MB
   Total Cache Memory Available: 144 MB
   No-Battery Write Cache: Disabled
   Cache Backup Power Source: Batteries
   Battery/Capacitor Count: 1
   Battery/Capacitor Status: OK
   SATA NCQ Supported: True
   Number of Ports: 2 Internal only
   Driver Name: hpsa
   Driver Version: 3.4.10
   Driver Supports HP SSD Smart Path: True
   PCI Address (Domain:Bus:Device.Function): 0000:06:00.0
   Host Serial Number: ***

Please find attached the ADU report and let me know if you are missing informations.

Cheers,
Christian

I bought some DL360 Gen6 servers to use as a sandbox for playing with Microsoft's Scale-Out File Server.  They don't have SAS HBA's with external connectors in them.  I'm considering a D2700 for the JBOD storage.  I'm a bit new at this, so I could stand a little advice from someone who knows more about it.

1. Can someone recommend a good HBA for these servers that I can get reasonably on the used market?  I don't need hardware RAID since SoFS uses JBOD.
2. Are there issues I need to be aware of connecting 2 of the DL360's to a single D2700?

Thanks in advance for the help.

Phil

Dear all,

My server (HP Proliant DL380 G9) have 02 array (Array A: 5x300GB and Array B: 3x3TB). I extended Array A ( + 2x300GB), and the Progress is hanging at 0.00%

Status message 785

- Background parity initialization is currently queued or in progress on Logical Drive 1.........

Active task:

- Logical Drive 1 is undergoing parity initialization. Progress: 0.00%

How could i finish this step ? Pls advice

Howdy,  at my company the previous IT guru quit and I ended up in charge of maintaining the servers.  I have relatively minor experience working with servers and need some assistance.

We have 3 HP ML350 servers running Windows Server 2012, and the 3rd one is setup to be a replica server for Hyper-V, and receives changes from the other 2 servers running various virtual machines.

This morning I noticed 3rd server started making an escalating fan speed noise.  When I first reboot it, it's very quiet, but after about 3 minutes the fans start to spin faster and faster, and they continue to escalate until they reach what sounds like max speed after about 15 minutes.  The machine is so loud at the moment that it can be heard around the entire office.

I've looked into the performance manager, and everything seems to be running really well.  CPU usage is tiny, memory usage is tiny, nothing seems out of the ordinary.

EDIT: I just went into BIOS and the fan speed will actually start to escalate while I'm in BIOS.  

I changed the Thermal Settings to "Reduced Acoustics" to see if it would fix the issue, but it doesn't seem to have made a difference.

UPDATE: so I shutdown the system, removed power for an hour, put it all back together and powered it back up, and the fan escalation has stopped.  I think I've lost half of my hair and a third of my hearing, but the system seems to be running normal again.

Hi

i have purchase a HP Proliant DL160 Gen9 with 2 HDD (450GB each). I need to create 4 partitions with these 2 HDD, each is 225GB. How can i archieve that?

Thank you.

Hello,

in SMH my NIC team has warning, when clicking on it I can see that status is degraded, however both NIC cards are green, linked have no errors etc., there were temporary problems with NICs for like 5 mins, but now they are back to normal. I have marked events in IML as "repaired" few hours passed, but the status of NIC TEAM is still "degraded".

HP Network Configuration Utility also shows this team in yellow status, however I can not see what is wrong with it (attachment).

Hi,

We have a DL380p Gen8 16 SFF disk modell server (original config, not updated). It has a 2nd smart array controller in one of the PCI slots, as required by the specifications.

The server is being repurposed, and we no longer need the disks in the additional 8SFF disk bay cage, but we do need 3 empty PCI slots (single CPU only, so can't use the 2nd riser).

Is it okay, to just remove the additional smart array controller, its cabling, and the disks from the "add-on" bay (repelacing with blanks) , and use the server like this? Is there any monitoring built into the add-on bay/backplane which would generate some allert conditions due to the lack of controller/cabling connectivity?

Thank you.

Hey Everyone,

So I am wondering if anyone has run into the same issue that I am having... also if they have found a fix? I have a HP DL380p Gen 8 Server, With P420i Raid Controller with 25 disks.

I am trying to setup and configure a Hyper-V USB Stick with HyperV Server 2016 core. I am looking to use to use storage spaces so I have set the 420i to hbamode so the OS can see the disks. ( Raid 0 and pass through do not work with out doing this it seems for this controller) However when I do this and boot the USB copy of HyperV I get the Inaccessible_boot_Device error on boot. Now I have added the Drivers for the P420i but this has also made no difference.

On a side note I also tried doing a direct install to a Hard disk and although the windows installer could see all the drives it would not install.. This is because the installer states none of the drives where bootable... So I am wondering if this is related to the above issue.

Now leaving the fact that I am playing with 2016 to the side for the moment and also keep in mind that I have of course had a poke about in the bios in relation to the above boot issue ( Fyi, Not really anything was found there to asssit )

Any one have any ideas ?

Cheers!

Hello there, season greetings to all.

I am an IT manager of a shipping company located in Greece and one of our vessels is on Galveston Fairway anchorage outside Houston Texas. It has a problem with its server, an HP Proliant ML 310 G8 which is on next business day on site support, and I am looking for an authorized warranty service center in Houston area to help me repair the server. 

The server is already in our local agent's office in Houston and waiting for support...

Can anyone help?

Hello. Yesterday one of my HP DL 380 Gen8 hung during backup process. There is no log records inside OS since the moment of hanging. Is there a way to see what's happened? There is Active Health Log in iLO, but i can't open it.

Hi all,

A new customer of us is running a Proliant DL180 gen9 server.
The server is a Non-Hot Plug version. Is it possible to make the server Hot Plug?

Kind Regards,
Jonas Van Belle

Running a DL380 G4 with an i6 controller. Been up and stable for months. Did a controlled stop, on restart the raid controller reported not configured. As of now it will not hold a configuration if power is removed. No on board battery as this option was not purchased. Any one have any idea what has happened? Id the controller bad? Looks like it is integrated to the motherboard. Motherboard battery is new.

Hello!

We have server DL380 G7 with P410i controller. Our goal is to create RAID 6 array using this controller. We really need it.

It turned out that SAAP 1.0 license is required for that. But all our suppliers told us that this postion (part number) is no longer available for request so we can not buy this license.

All i can find on HPe site is interesting statement in HP SSA download description. It says "HP Smart Array Advanced Pack 1.0 and 2.0 features are now part of the baseline features of HP SSA, with the appropriate firmware."

Our controller is on current firmware 6.64(b). But it seems that is still have licensing engine and requires SAAP 1.0 license. 

So what are HP plans for SAAP 1.0 license? Is it free? Is it going to be free? If yes - when? If nope - how we can buy it / what is replacement?

Thanks!

Greetings,

I recently ended up with 2 used DL380 G6's that seem pretty much identical.  Both have 8 x 146GB 10k RPM SAS drives with P410i RAID controllers.  Both have 48GB DDR3 RAM.  Both have dual socket Xeon E5540's.  I flashed all the latest firmware and removed the battery backup modules (the batteries were puffed).  I switched from RAID 5 to 1+0 on both machines and installed XenServer 6.5.  Everything I have looked at shows the machines to be configured the same.  The only difference I can spot is that one machine is getting acceptable drive performance off the array while the other is pathetic.

dd if=/dev/zero of=/tmp/output bs=256k count=1k; rm -f /tmp/output
Machine 1:
1024+0 records in
1024+0 records out
268435456 bytes (268 MB) copied, 0.824632 seconds, 326 MB/s

Machine 2:
1024+0 records in
1024+0 records out
268435456 bytes (268 MB) copied, 4.46843 seconds, 60.1 MB/s

Both are set to HP Static: High Performance Mode in the BIOS

Any idea why I'm getting such drastic performance differences between the 2 machines?

Hi,

I try to access info on the status of the hard drive of the server through SSH. 

The ilo version is iLO 4 Advanced 2.10.

I've access to the state of sensors, memory, cpu but not of the hard drive or array...

Here's a response of

</>hpiLO-> show /system1/

status=0

status_tag=COMMAND COMPLETED

Fri Nov 13 18:59:22 2015

/system1

  Targets

    firmware1

    bootconfig1

    log1

    led1

    network1

    oemhp_vsp1

    oemhp_power1

    cpu1

    memory1

    memory2

    slot1

    swid1

    swid2

    swid3

    swid4

    swid5

    swid6

    swid7

    swid8

    fan1

    sensor1

    sensor2

    sensor3

    sensor4

    sensor5

    sensor6

    sensor7

    sensor8

    sensor9

    sensor10

    sensor11

    sensor12

    sensor13

    powersupply1

  Properties

[...] cut for privacy reason.

Hello,

Does anyone know the max IOPS of P222 SA on a G8 box with SAS drives? I couldn't find the information in the HP manuals.

Thanks

Hello All,

I have three hard drives in my exchange server which failed together and when i ran HP Insight Diagnostics Version 8.5.0.3625A (x86_64) , it gives me error (64006 & 64001 ) as attached 

MY server is : 

• ProLiant DL380p Gen7 E

the OS is :

• Windows server 2008-R2 SP1/Ver: 6.1.7601

kindly find the diagnosis log attached

Please help me ASAP, this is an urgent issue.

Thanks in advance :)

Any thoughts for me? We are getting a replacement server, but wondering if there is a fix for this or if our data is at high risk for data loss.

Not sure if the xml was changed below in this post, because the forum mistaked it for invalid html.

On a server, we are seeing the following error in the event log:

Log Name: System
Source: Cissesrv
Date: 12/29/2015 11:43:02 PM
Event ID: 24606
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: 
Description:
Logical drive 1 of array controller P410i [Embedded] returned a fatal error during a read/write request from/to the volume.

Logical block address 263040, block count 8 and command 32 were taken from the failed logical I/O request.

Array controller P410i [Embedded] is also reporting that the last physical drive to report a fatal error condition (associated with this logical request), is located in bay 1 of box 1 connected to port 1I.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Cissesrv" />
<EventID Qualifiers="50229">24606</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-12-30T05:43:02.000000000Z" />
<EventRecordID>285781</EventRecordID>
<Channel>System</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>Cissesrv</Data>
<Data>P410i [Embedded]</Data>
<Data>1</Data>
<Data>263040</Data>
<Data>8</Data>
<Data>32</Data>
<Data>1</Data>
<Data>1</Data>
<Data>1I</Data>
</EventData>
</Event>

The server is an ProLiant ML350 G6 using the P410i embedded controller with a 512 MB array Accelerator. There are 6 drives in the array, plus a spare in the 7th slot. It's RAID 5.

I have updated all firmware on the recently replaced hard drives and original hard drives, as well as the firmware on the controller. 

I ran HP Array Config diagnostics, Smart Storage Administrator diagnostics, and Insight Manager online, and they all report healthy. 

Attached is the Array Config Diagnostics. 

Other events that may be related below, my comments are in red. 

Log Name: System
Source: Disk
Date: 12/29/2015 11:43:00 PM
Event ID: 7
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: 
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Disk" />
<EventID Qualifiers="49156">7</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-12-30T05:43:00.385677800Z" />
<EventRecordID>285779</EventRecordID>
<Channel>System</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk0\DR0</Data>
<Binary>030080000100000000000000070004C0000100009C0000C000000000000000000000070800000000F243D10200000000FFFFFFFF00000000580000840200040038200A2842072000001000003C00000000B0211280FAFFFFD0B24A0E80FAFFFF000000000000000030D8D31180FAFFFF0000000000000000800304000000000028000004038000000800000000000000700003000000000A00000000110000000000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 12/29/2015 9:23:21 PM
Event ID: 3
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: 
Description:
Filter Manager failed to attach to volume '\Device\Harddisk2\DR25'. This volume will be unavailable for filtering until a reboot. The final status was 0xc03a001c.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-FilterManager" Guid="{F3C5E28E-63F6-49C7-A204-E48A1BC4B09D}" />
<EventID>3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-12-30T03:23:21.128411700Z" />
<EventRecordID>285765</EventRecordID>
<Correlation />
<Execution ProcessID="8980" ThreadID="13568" /> Process ID 8980 is currently equal to VDS.exe in task manager
<Channel>System</Channel>
<Computer></Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FinalStatus">0xc03a001c</Data>
<Data Name="ExtraStringLength">22</Data>
<Data Name="ExtraString">\Device\Harddisk2\DR25</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 12/29/2015 8:29:59 PM
Event ID: 5
Task Category: None
Level: Error
Keywords:
User: DAHLBERG\administrator
Computer: 
Description:
{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\TEMP\BEV155A.tmp' was corrupted and it has been recovered. Some data might have been lost.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{A68CA8B7-004F-D7B6-A698-07E2DE0F1F5D}" />
<EventID>5</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-12-30T02:29:59.423284700Z" />
<EventRecordID>285744</EventRecordID>
<Correlation />
<Execution ProcessID="1104" ThreadID="4188" /> PID 1104 is equal to BEREMOTE.exe, the server is running Backup Exec 2012 for backups, and it backs up to external hard drives that are swapped daily. The backup has worked all week.
<Channel>System</Channel>
<Computer></Computer>
<Security UserID="S-1-5-21-1359813550-3578794935-3483755087-500" />
</System>
<EventData>
<Data Name="FinalStatus">0x8000002a</Data>
<Data Name="ExtraStringLength">31</Data>
<Data Name="ExtraString">\??\C:\Windows\TEMP\BEV155A.tmp</Data>
</EventData>
</Event>

Log Name: System
Source: Ntfs
Date: 12/29/2015 8:29:47 PM
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: 
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \\?\Volume{15991b20-3b9c-11e5-a68f-1cc1de72ca3a}.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">55</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-12-30T02:29:47.354594400Z" />
<EventRecordID>285743</EventRecordID>
<Channel>System</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\\?\Volume{15991b20-3b9c-11e5-a68f-1cc1de72ca3a}</Data>
<Binary>0D000C000200380002000000370004C000000000320000C00000000000000000000000000000000082091200FFFFFFFFFFFFFFFF</Binary>
</EventData>
</Event>

My apologies if this is not the correct channel/thread to post in.  This seems to be the only secion I can post in the forums.

I'm running a Debian variant Linux on a DL380 Gen5 server and all is working well. One quirk I noticed is that when plugging in a display into the front VGA port, the text is nice and sharp, using the monitor's proper resolution.

When I plug the monitor into the rear VGA port, it doesn't display port it doesn't use the same resolution. Everything still functions, but the text is bigger and sometimes goes off screen.

I'm not using any GUI interface; just the console. Any advise is appreciated, thanks in advance.

-Patrick