OVM 3.3 on HP ProLiant DL 380 G7

Morning folks,
I'm considering using OVM 3.3 to virtualize multiple PCs which I currently use for RAC, Cloud Control, etc. into a single physical server. The server I'm considering is an HP ProLiant DL380 G7. According to Oracle's HCL, the DL380 G7 is good to go for OVM 3.3 and even OL 7. I have 3 questions:
1. The DL380 G7 contains a P410i RAID controller. I've seen elsewhere on the internet people reporting problems with earlier versions of OVM not seeing LUNs presented using this controller, even though that controller was in a different model ProLiant. Does anyone have direct experience of the DL380 G7 working fine with OVM 3.3 with the P410i controller?
2. For RAC, I still intend to use a separate PC running Openfiler for the shared storage. This works like a charm when I use bare metal Linux installs on my PC RAC nodes, but I've never used it when the RAC nodes have been virtualized using OVM. Does anyone know if this works? All Openfiler does is present iSCSI targets to Linux, so I can't see why a VM Linux node would not work when a bare metal Linux mode does.
3. Any other issues with the DL380 G7 I should be aware of?
Thanks in advance for any help, tricks or tips you can provide.
All the best!

A workaround found - remote install using LightsOut.

Similar Messages

Problem while installing solaris 10 on HP proliant DL 380 G5.

Hi,
facing problem while installing solaris 10 05/09 on HP proliant DL 380G5. The array controller is E200.
i have installed the raid controller driver CPQary3-2.1.0-solaris10-i386, it is going ahead but not detecting the whole hard disk space. My hard disk space is SAS 146GB. There are two 146GB hard disk present. It is showing only 978 MB & only one hard disk. So please help me out. my mail ID is [email protected]

I have a similar issue trying to load Solaris 10u4 on an IBM x236.
I had to put in a recognized SCSI card, attach an external array to the card, and install Solaris 10u4 on the array. Then I had to install the correct driver from OpenSolaris (an Adaptec one for IBM ServeRAID), and do a live upgrade onto the now-visible internal disks. Then I removed the array and cleaned up the traces from the live upgrade.
You may have to do something similar.
And last month the boot drive got corrupted when power was interrupted. "Oops. Wrong plugs..." This time the external array will stay connected.

Proliant dl 380 gen 3

Trying to find out how to know what the leds on status board,that are lit mean when server will not boot

Hi:
You may also want to post your question in the HP Business Support Forum -- DL Servers section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264
Paul

OVM Server 2.2.1 in a ProLiant BL680c G7 did not detect networks interfaces

Hello everybody
I just installed OVM Server in a HP ProLiant BL680c G7 and the installation finish. But the network interfaces was not detected. (The installation skip the network steps)
The Server have 24 network interfaces (FlexFabric Embedded Ethernet)
Any idea in order to recognize network interfaces??
greetings

Hi,
try using OVM 2.2.2 which was released a week ago. (edelivery.oracle.com/linux)
A lot of drivers were updated, maybe now your network cards are also detected.
Regards
Sebastian

Ovm virtual machine domain crashed

Hello
We are facing actually a problem. We have installed ovm 2.2.1 and installed 3 (A15, A16, A17) windows virtual machines on a HP Proliant DL380 G7 server.
A17 machine restart unexpectedly when the load is high on the network
Part of logs are:
/var/log/messages:
Sep 25 15:22:18 xxxxx avahi-daemon[7250]: Interface tap23.0.IPv6 no longer relevant for mDNS.
Sep 25 15:22:18 xxxxx avahi-daemon[7250]: Leaving mDNS multicast group on interface tap23.0.IPv6 with address fe80::c40f:d1ff:fe14:ce79.
Sep 25 15:22:18 xxxxx avahi-daemon[7250]: Withdrawing address record for fe80::c40f:d1ff:fe14:ce79 on tap23.0.
Sep 25 15:22:18 xxxxx kernel: xenbr1: port 2(tap23.0) entering disabled state
Sep 25 15:22:18 xxxxx kernel: device tap23.0 left promiscuous mode
Sep 25 15:22:18 xxxxx kernel: type=1700 audit(1348586538.915:90): dev=tap23.0 prom=0 old_prom=256 auid=4294967295 ses=4294967295
Sep 25 15:22:18 xxxxx kernel: xenbr1: port 2(tap23.0) entering disabled state
Sep 25 15:22:20 xxxxx kernel: xenbr1: port 3(vif23.0) entering disabled state
/var/log/xen/xend.log:
[2012-09-25 15:22:18 8235] WARNING (image:490) domain 10_xxxxx: device model failure: pid 11149: died due to signal 11; see /var/log/xen/qemu-dm-10_xxxxx.log
[2012-09-25 15:22:19 8235] WARNING (XendDomainInfo:1907) Domain has crashed: name=10_xxxxx id=23.
[2012-09-25 15:22:19 8235] DEBUG (XendDomainInfo:2757) XendDomainInfo.destroy: domid=23
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2230) Destroying device model
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2237) Releasing devices
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vif/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vbd/768
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vbd/832
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/832
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vbd/5696
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5696
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vbd/2048
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2048
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vbd/5632
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing vfb/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2250) Removing console/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:1144) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:117) XendDomainInfo.create_from_dict({'vcpus_params': {'cap': 0, 'weight': 256}, 'PV_args': '', 'features': '', 'cpus': [[], [], [], [], [], [], [], [], [], [], [], []], 'paused': 0, 'domid': 23, 'shutdown': 0, 'VCPUs_live': 12, 'PV_bootloader': '/usr/bin/pygrub', 'actions_after_crash': 'restart', 'vbd_refs': ['0b8eb7e0-91cb-1dd8-93ba-92b1a3ff26b3', 'cd42c91a-1f15-053e-78c4-d2ea9876e6d9', '16e4af8e-048d-7be9-5fc1-e14070ff3551', '4b836ae6-2352-73f0-94e8-b570764113b4', '9a5ce3cb-8a63-60ed-c8b1-ef00d666fe06'], 'PV_ramdisk': '', 'memory_dynamic_min': 8589934592L, 'name_label': '10_xxxxx', 'VCPUs_at_startup': 1, 'HVM_boot_params': {'order': 'c'}, 'platform': {'videoram': '4', 'hpet': '0', 'stdvga': '0', 'vnclisten': '0.0.0.0', 'loader': '/usr/lib/xen/boot/hvmloader', 'vncconsole': '1', 'serial': 'pty', 'vncunused': '1', 'xen_platform_pci': '1', 'monitor': '0', 'boot': 'c', 'rtc_timeoffset': -967, 'vncpasswd': 'XXXXXXXX', 'pci': [], 'pae': '1', 'vpt_align': '1', 'hap': '1', 'viridian': '0', 'acpi': '1', 'localtime': '0', 'timer_mode': '0', 'vnc': '1', 'nographic': '0', 'pci_msitranslate': '1', 'apic': '1', 'usb': '0', 'guest_os_type': 'default', 'device_model': '/usr/lib/xen/bin/qemu-dm', 'keymap': 'fr', 'pci_power_mgmt': '0', 'xauthority': '//.Xauthority', 'isa': '0'}, 'PV_kernel': '', 'console_refs': ['db501a0b-36a5-a080-dab2-d42bace0b21b', 'eba3a0c2-a3ff-00cf-4e40-7c6b433801a1'], 'online_vcpus': 12, 'blocked': 0, 'on_xend_stop': 'ignore', 'memory_static_min': 0, 'HVM_boot_policy': 'BIOS order', 'shutdown_reason': 3, 'VCPUs_max': 12, 'start_time': 1348534061.3324931, 'memory_static_max': 8589934592L, 'actions_after_shutdown': 'destroy', 'on_xend_start': 'ignore', 'crashed': 0, 'memory_dynamic_max': 8589934592L, 'actions_after_suspend': '', 'is_a_template': False, 'PV_bootloader_args': '-q', 'is_control_domain': False, 'uuid': 'c33d113b-46b3-91d3-0984-8c8b192e23c3', 'cpu_time': 22146.567213627, 'shadow_memory': 76, 'dying': 0, 'vcpu_avail': 4095, 'notes': {'SUSPEND_CANCEL': 1}, 'other_config': {}, 'auto_power_on': False, 'running': 0, 'actions_after_reboot': 'restart', 'vif_refs': ['ee5890ab-345b-479b-1504-f3a9405d4dbf'], 'target': 0, 'vtpm_refs': [], 's3_integrity': 1, 'devices': {'cd42c91a-1f15-053e-78c4-d2ea9876e6d9': ('vbd', {'uuid': 'cd42c91a-1f15-053e-78c4-d2ea9876e6d9', 'bootable': 0, 'devid': 832, 'driver': 'paravirtualised', 'dev': 'hdb', 'uname': 'file:/var/ovs/mount/58F85FD535AC460495D6CD8D56EF0E94/running_pool/10_xxxxx/JDEdwards.img', 'mode': 'w'}), 'eba3a0c2-a3ff-00cf-4e40-7c6b433801a1': ('console', {'location': '14', 'devid': 0, 'protocol': 'vt100', 'uuid': 'eba3a0c2-a3ff-00cf-4e40-7c6b433801a1', 'other_config': {}}), 'ee5890ab-345b-479b-1504-f3a9405d4dbf': ('vif', {'bridge': 'xenbr1', 'mac': '00:16:3E:03:AF:B3', 'devid': 0, 'type': 'ioemu', 'uuid': 'ee5890ab-345b-479b-1504-f3a9405d4dbf'}), '4b836ae6-2352-73f0-94e8-b570764113b4': ('vbd', {'uuid': '4b836ae6-2352-73f0-94e8-b570764113b4', 'bootable': 0, 'devid': 2048, 'driver': 'paravirtualised', 'dev': 'sda', 'uname': 'file:/var/ovs/mount/58F85FD535AC460495D6CD8D56EF0E94/running_pool/10_xxxxx/Backup.img', 'mode': 'w'}), 'db501a0b-36a5-a080-dab2-d42bace0b21b': ('vfb', {'vncunused': 1, 'other_config': {'vncunused': 1, 'vncpasswd': 'XXXXXXXX', 'vnclisten': '0.0.0.0', 'vnc': '1'}, 'vnc': '1', 'uuid': 'db501a0b-36a5-a080-dab2-d42bace0b21b', 'vnclisten': '0.0.0.0', 'vncpasswd': 'XXXXXXXX', 'location': '0.0.0.0:5901', 'devid': 0}), '0b8eb7e0-91cb-1dd8-93ba-92b1a3ff26b3': ('vbd', {'uuid': '0b8eb7e0-91cb-1dd8-93ba-92b1a3ff26b3', 'bootable': 1, 'devid': 768, 'driver': 'paravirtualised', 'dev': 'hda', 'uname': 'file:/var/ovs/mount/58F85FD535AC460495D6CD8D56EF0E94/running_pool/10_xxxxx/System.img', 'mode': 'w'}), '16e4af8e-048d-7be9-5fc1-e14070ff3551': ('vbd', {'uuid': '16e4af8e-048d-7be9-5fc1-e14070ff3551', 'bootable': 0, 'devid': 5696, 'driver': 'paravirtualised', 'dev': 'hdd', 'uname': 'file:/var/ovs/mount/58F85FD535AC460495D6CD8D56EF0E94/running_pool/10_xxxxx/MSSQL.img', 'mode': 'w'}), '9a5ce3cb-8a63-60ed-c8b1-ef00d666fe06': ('vbd', {'uuid': '9a5ce3cb-8a63-60ed-c8b1-ef00d666fe06', 'bootable': 0, 'devid': 5632, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': '', 'mode': 'r'})}, 'PV_superpages': 0})
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2327) XendDomainInfo.constructDomain
[2012-09-25 15:22:20 8235] DEBUG (balloon:181) Balloon: 3208900 KiB free; need 4096; done.
[2012-09-25 15:22:20 8235] DEBUG (XendDomain:452) Adding Domain: 24
[2012-09-25 15:22:20 8235] DEBUG (XendDomainInfo:2528) XendDomainInfo.initDomain: 24 256
Any idea ???

About the load it is just an observation
Other observation the virtual machine that reboots have is ram full.
It did not work before, it is like this since we installed the virtual machine
We did not change any hardware
The history of the problem:
1st day
We have oracle virtual server 2.2.1 running on a HP Proliant DL 380 G7
We have a (virtual machine) server under windows 2008 R2 (A17). We installed this machine in the last position
2nd day
We noticed we were not able to contact the different machine via the network
We checked the log and noticed an error NETDEV WATCHDOG: eth0: transmit timed and something else related to bnx2 driver
after some research under support of oracle we found something like this [ID 1312709.1] where the problem were supposed to be solved in oracle virtual server 2.2.2 or using an another kernel and when disabling option C-STATE in the BIOS C6 and C3.
were drivers related to NIC were updated. We installed this new kernel but the problem were now related to the windows server 2008 R2 machine.
Actually this machine reboot and the nic where the machine is cannot be contacted after the machine reboot
i mean if A17 on xenbr1(eth1) reboots ping on eth1 does not respond but still able to ping A15 and A16 on xenbr0(eth0)
and the nic is:
Lspci grep ethernet
Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
ethtool -i eth1
driver: bnx2
version: 2.0.8-rh
firmware-version: bc 5.2.3 NCSI 2.0.6
bus-info: 0000:33:00.1
end of the story
the problem sems to happen when users launch batch application which execute batch sql statement (midday or 5 pm). twice or once a day.
Any idea ?!!
thanks

ZFS on solaris10 panics HP Proliant server BAD TRAP page fault in kernel

When installing Solaris 9/10 on a HP Proliant DL 380 G5
the system resets when choosing ZFS as a root file system,
even after CPQary3 device driver has been installed.
The CPQary3 device driver is the latest version 2.3.0,is neccessary because of the presence of a HP Smart Array E200 Controller
and is installed sucessfully during the installation from DVD
When choosing UFS as a root file system, the OS installs fine.
But when zfs is used to configure a zps pool after the installation, the system resets again
Has anyone experienced the same problems ? knows how to solve this ?
Solaris installs fine when choosing UFS as a root file system.
After that, a second disk partition is created of type Other to hold a zfs pool with the following command:
zpool create datapool c0t0d0p2
After that the system PANICS: here is an extract from the /var/adm/messages files:
Mar 14 16:36:49 solarisintel ^Mpanic[cpu1]/thread=fffffe800069bc60:
Mar 14 16:36:49 solarisintel genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=fffffe800069b940 addr=238 occurred in
module "unix" due to a NULL pointer dereference
Mar 14 16:36:49 solarisintel unix: [ID 100000 kern.notice]
Mar 14 16:36:49 solarisintel unix: [ID 839527 kern.notice] sched:
Mar 14 16:36:49 solarisintel unix: [ID 753105 kern.notice] #pf Page fault
Mar 14 16:36:49 solarisintel unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x238
Mar 14 16:36:49 solarisintel unix: [ID 243837 kern.notice] pid=0, pc=0xfffffffffb8406fb, sp=0xfffffe800069ba38, eflags=0x10246
Mar 14 16:36:49 solarisintel unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6f0<xmme,fxsr,pge,mce,pae,pse>
Mar 14 16:36:49 solarisintel unix: [ID 354241 kern.notice] cr2: 238 cr3: 11ada000 cr8: c
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] rdi: 238 rsi: 4 rdx: fffffe800069bc60
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] rcx: 14 r8: 0 r9: 0
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] rax: 0 rbx: 238 rbp: fffffe800069ba60
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] r10: 0 r11: 1 r12: 100000
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] r13: 0 r14: 4 r15: ffffffffb3a61af0
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] fsb: 0 gsb: ffffffff9b2ac800 ds: 43
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] es: 43 fs: 0 gs: 1c3
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] trp: e err: 2 rip: fffffffffb8406fb
Mar 14 16:36:49 solarisintel unix: [ID 592667 kern.notice] cs: 28 rfl: 10246 rsp: fffffe800069ba38
Mar 14 16:36:49 solarisintel unix: [ID 266532 kern.notice] ss: 30
Mar 14 16:36:49 solarisintel unix: [ID 100000 kern.notice]
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069b850 unix:die+da ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069b930 unix:trap+5e6 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069b940 unix:cmntrap+140 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069ba60 unix:mutex_enter+b ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069ba70 zfs:zio_buf_alloc+1d ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069baa0 zfs:zio_vdev_io_start+120 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bad0 zfs:zio_execute+7b ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069baf0 zfs:zio_nowait+1a ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bb60 zfs:vdev_probe+f0 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bba0 zfs:vdev_open+2b1 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bbc0 zfs:vdev_open_child+21 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bc40 genunix:taskq_thread+295 ()
Mar 14 16:36:49 solarisintel genunix: [ID 655072 kern.notice] fffffe800069bc50 unix:thread_start+8 ()
Mar 14 16:36:49 solarisintel unix: [ID 100000 kern.notice]
Mar 14 16:36:49 solarisintel genunix: [ID 672855 kern.notice] syncing file systems...
Mar 14 16:36:49 solarisintel genunix: [ID 904073 kern.notice] done
Mar 14 16:36:50 solarisintel genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0t0d0s1, offset 108593152, content: kernel
Mar 14 16:36:54 solarisintel genunix: [ID 100000 kern.notice]
Mar 14 16:36:54 solarisintel genunix: [ID 665016 kern.notice] ^M100% done: 210699 pages dumped,
Mar 14 16:36:54 solarisintel genunix: [ID 851671 kern.notice] dump succeeded
Mar 14 16:38:21 solarisintel genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_142910-17 64-bit
I will try again now with solaris 10 5/09 (U7)
Chris.
Edited by: user5485639 on 14-Mar-2011 08:42

What do you mean after the driver is installed?
S10/U9 has the Compaq Array3 driver pre-installed. No more adding it to the jumpstart tree or "adding a driver" necessary.
I have setup several DL360 G3's and G4's which use the same controller.

BackupExec HP-Proliant-DL380G6-P410i

It seems to be an old problem, but I did not succeed in spite of all the
hints I found:
Starting the Symantec-BackupExec-Agent causes the system to do a
cold-reset (after one or 2 minutes).
Hardware:
HP-Proliant DL 380 G6
System ROM: P62 08/16/2010
SmartArray P410i Controller on System-Board: FirmwareVersion 3.50
OS:
NetWare6.5SP8
CompaqSupportPack 8.20
HPQCISS.HAM v 1.16b
Thanks for help
Oskar

Hello *,
thanks a lot!
The firmware, the proliant support packs (the required parts of them)
and the HPQCISS-driver has been up to date already.
The solution was the "HP Insight Management Storage Agents for NetWare
Version 8.21 (probably in combination of all updates before) ...
The Backup works with a excellent performance ~2.5GB/min
Thanks!
Oskar
Am 21.06.2011 21:47, schrieb wiegandb:
> Hello,
>
> in addition to what Anders Gustafsson said this may also help:
> "http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId =3884082&prodTypeId=15351&prodSeriesId=3884082&obj ectID=c02577266"
>
> saying that you need to update the driver HPQCISS.HAM v 1.16b (already
> done) and HP Insight Management Storage Agents for NetWare Version 8.21
> (or later) from
> "http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=1 5351&prodSeriesId=3884082&prodNameId=3884083&swEnv OID=1064&swLang=8&mode=2&taskId=135&swItem=MTX-291bf28cb02f4b028e6c83d193"
>
>
> Regards and good luck
>
> Burkhard Wiegand
>
> Netware Admin
> Debeka-Versicherungen
> D-56068 Koblenz

Windows Server 2012 - Disk IO & High Latency

We have a very strange issue on what appears to be all of our Windows 2012 servers.
We can build a basic server, HP Proliant DL 380 Gen 8 - RAID 0 (2x 300GB 15K SAS). Install Windows 2012, patch to latest levels, all HP firmware and drivers at latest levels on HP website.
Pretty much a vanilla Windows build, even without Anti Virus at this stage. (This same issue occurs with IBM HS22 blades as well with base build and all latest IBM firmware / drivers so does not appear to be single vendor issue).
Take a large file, for testing a 20GB VHD. If we copy this file from C:\Temp to C:\Temp we get about 1.4GB/s transfer speed (Not bad). However post copy all processes in Performance Monitor
Disk Latency increase to over 1500 ms. This happens every time we copy a large file.
The file systems is NTFS.
The array controllers cache settings are set 75% READ / 25% WRITE.
This problem is much worse when it occurs on our Windows 2012 Scale Out File
Cluster with Hyper-V hosts using the storage. In theory if a client (Hyper-V server) requests a large Read or Write activity you see a good throughput, but then followed by a large period of disk latency afterwards on all processes on the
file server. If multiple requests from clients occur simultaneously then this problem is severe enough to hang / crash the file server.
This also occurs when the servers are not using the "C:" drive and instead are using the CSV volumes on our IBM V7000 array. In this scenario the server has 4x 8Gb HBAs connected to
the 8x 8GB FC connections on the V7000. EasyTier is enabled SSD Disk Pool to 15K SAS Disk Pool. So in this scenario I know that the issue is not due to an underlying performance issue within the disk subsystem.
This does disk latency issue did not occur on Windows 2008 with the same hardware EG: HP Proliant DL 380 G7 with local or V7000 disk.
Therefore there appears to be a major difference / problem in the Windows 2012 disk IO stack.
Another thing to notice, if a process is running a large copy EG: the VHD copy above and a second or third copy is executed the data transfer of all process does not reach an equal level instead
one process reaches the highest transfer rate then slows down and the other process takes over. This kind of activity is again not what we used to see on 2008 or other operating systems.
Can anyone shed any light on this? Does anyone else see a similar IO profile?
We have a case with Microsoft support for weeks with no resolution.

Hi,
We do have multiple SoFS nodes in the cluster, all have have dual 10Gb NICs with RDMA ability (Mellanox Connect3) connected to Brocade VDX switches. RDMA works a treat between hosts using SMB Direct & SMB Mulitchannel. The SAN disks from SoFS are 8Gb
FC, the local disks are SAS.
The problem we have is locally not even remote. EG: The latency occurs on the SoFS when copying data from C: to C: or from CSV Vol1 to CSV Vol1.
It is very strange, not seen this issue before. It makes me think its a bug as it can be created on other Windows 2012 hosts with just local disk.

Unallocated disk space not showing up in disk management

I have an HP Proliant dl 380 running Windows 2008. My c:\drive was built on a 33 gig raid 1 partition. I am almost out of drive space. I have tried this method before on Windows server 2000 and it worked. However this time it did not. I took one
of the 33 gig drives out and put a 146 gig drive in it's place. I let the mirror rebuild itself. When it was done I put the other 146 gig drive in and let it rebuild. Now I still have the 33 gig partition but when I ran disk management
the unallocated space did not show up so I cannot extend the volume. I tried to rescan the drives and have device manager rescan as well but no go. I talked with hp and they had me update the firmware of the raid card and restart but still nothing.
Can anyone help?

Hi Eric,
Please refer the following HP article to expand your array , refer the TechNet article to expand your drive:
HP Proliant Servers - How to Expand an Array and Extend the Logical Drive
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/mostViewedDisplay/?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_efb5c0793523e51970c8fa22b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c03510253-1%257CdocLocale%253Den_US&javax.portlet.tpst=efb5c0793523e51970c8fa22b053ce01&sp4ts.oid=4231377&ac.admitted=1411638027623.876444892.199480143
TechNet article:
Extend System/Boot Volume on Windows Server 2008/ Windows Vista/Win7 Beta
http://blogs.technet.com/b/mghazai/archive/2009/02/24/extend-system-boot-volume-on-windows-server-2008-windows-vista-win7-beta.aspx
Extend a simple or spanned volume
http://technet.microsoft.com/en-us/library/cc776741.aspx
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

T5120 performance

Hi
I have a sparc T5120 8 cpu 4cores 8G RAM
I'm very disapointing about the server performance. 68 seconds to create a 1G file
I was wondering if someone could execute this command on a server similar to the T5120 model that we have, and send us the results. That would be of great help to us.
The command is going to create a 1 GB file filled with zeroes in my home folder. Look at the start and the end times once the command is run.
bash-3.00# date; dd if=/dev/zero of=myfile bs=1024 count=1000000; date
Thu Nov 4 12:54:10 EDT 2010
1000000+0 records in
1000000+0 records out
Thu Nov 4 12:55:18 EDT 2010
The system is patched and up to date. It is running ZFS and Solaris 10 OS. The OS is running on a RAID1 (2 drives).
Now, if I run the same command on a Virtual Machine that is using inferior storage (RAID 5 shared with 20 other VMs) I get better performance than on the physical system. It takes 30 seconds on this low end Virtual Machine server.
When we run the same command on an x86 server running Solaris 10 with ZFS (HP Proliant DL 380 G5, 2 drives RAID1), the test takes 8 seconds!
All systems are running Solaris 10 and ZFS, all patched and up to date.
Any suggestions will be appreciate!
Many thanks!
Norman

Hi
RAID 64k stripe size
ZFS zfs set recordsize=64k biblio/p6
dd bs=64k
bash-3.00# date;ptime dd if=/dev/zero of=/biblio/p6/ABC.txt bs=64k count=16000; date
Fri Nov 5 08:43:00 EDT 2010
16000+0 records in
16000+0 records out
real 2.606
user 0.091
sys 2.468
Fri Nov 5 08:43:03 EDT 2010
bash-3.00# ./iostat.tst
c1t0d0 123 MB/sec
c4t600A0B8000114260000070D94CB59A9Ad0 87 MB/sec
bash-3.00# iostat -XCn 1 15
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
3.0 1.6 286.3 31.5 0.0 0.1 0.0 14.4 0 1 c1
3.0 1.6 286.3 31.5 0.0 0.1 0.0 14.4 0 1 c1t0d0
11.8 30.6 1478.8 3502.7 0.0 0.5 0.0 12.5 0 8 c4
11.8 30.6 1478.8 3502.7 0.0 0.5 0.0 12.5 0 8 c4t600A0B8000114260000070D94CB59A9Ad0
11.8 30.6 1478.8 3502.7 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
12.0 0.0 1537.3 0.0 0.0 0.1 0.0 5.2 0 6 c4
12.0 0.0 1537.3 0.0 0.0 0.1 0.0 5.2 0 6 c4t600A0B8000114260000070D94CB59A9Ad0
12.0 0.0 1537.3 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
1356.0 6.0 85609.5 0.0 0.0 0.7 0.0 0.5 2 62 c1
1356.0 6.0 85609.5 0.0 0.0 0.7 0.0 0.5 2 62 c1t0d0
21.0 2.0 1810.4 0.0 0.0 0.1 0.0 3.0 0 7 c4
21.0 2.0 1810.4 0.0 0.0 0.1 0.0 3.0 0 7 c4t600A0B8000114260000070D94CB59A9Ad0
21.0 0.0 1810.4 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
1955.5 2.0 124896.4 0.0 0.0 0.9 0.0 0.4 3 86 c1
1955.5 2.0 124896.4 0.0 0.0 0.9 0.0 0.4 3 86 c1t0d0
22.0 0.0 2602.3 0.0 0.0 0.1 0.0 6.6 0 13 c4
22.0 0.0 2602.3 0.0 0.0 0.1 0.0 6.6 0 13 c4t600A0B8000114260000070D94CB59A9Ad0
22.0 0.0 2602.3 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
1946.7 2.0 124335.6 0.0 0.0 0.8 0.0 0.4 3 85 c1
1946.7 2.0 124335.6 0.0 0.0 0.8 0.0 0.4 3 85 c1t0d0
18.0 0.0 2302.5 0.0 0.0 0.1 0.0 5.4 0 9 c4
18.0 0.0 2302.5 0.0 0.0 0.1 0.0 5.4 0 9 c4t600A0B8000114260000070D94CB59A9Ad0
18.0 0.0 2302.5 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
914.1 0.0 58502.5 0.0 0.0 0.4 0.0 0.5 2 41 c1
914.1 0.0 58502.5 0.0 0.0 0.4 0.0 0.5 2 41 c1t0d0
16.0 769.1 959.2 96836.9 0.0 8.7 0.0 11.1 1 91 c4
16.0 769.1 959.2 96836.9 0.0 8.7 0.0 11.1 1 91 c4t600A0B8000114260000070D94CB59A9Ad0
16.0 767.1 959.2 96837.1 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
21.0 657.2 1684.6 83430.3 0.0 10.9 0.0 16.0 0 100 c4
21.0 657.2 1684.6 83430.3 0.0 10.9 0.0 16.0 0 100 c4t600A0B8000114260000070D94CB59A9Ad0
21.0 657.2 1684.6 83430.3 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
580.1 438.1 37513.6 55700.2 0.0 10.9 0.0 10.7 0 100 c4
580.1 438.1 37513.6 55700.2 0.0 10.9 0.0 10.7 0 100 c4t600A0B8000114260000070D94CB59A9Ad0
580.1 438.1 37513.6 55700.2 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
1411.1 231.0 90307.3 29380.1 0.0 10.9 0.0 6.6 1 100 c4
1411.1 231.0 90307.3 29380.1 0.0 10.9 0.0 6.6 1 100 c4t600A0B8000114260000070D94CB59A9Ad0
1411.1 231.0 90307.3 29380.1 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
1287.9 1085.9 82061.1 137549.3 0.0 10.7 0.0 4.5 1 100 c4
1287.9 1085.9 82061.1 137549.3 0.0 10.7 0.0 4.5 1 100 c4t600A0B8000114260000070D94CB59A9Ad0
1287.9 1083.9 82061.1 137549.3 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
1419.9 717.0 90980.1 90205.1 0.0 10.5 0.0 4.9 1 100 c4
1419.9 717.0 90980.1 90205.1 0.0 10.5 0.0 4.9 1 100 c4t600A0B8000114260000070D94CB59A9Ad0
1419.9 715.0 90980.1 90205.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 64.0 0.0 937.0 0.0 1.9 0.0 29.5 0 36 c1
0.0 64.0 0.0 937.0 0.0 1.9 0.0 29.5 0 36 c1t0d0
1320.0 897.0 85184.3 109671.9 0.0 8.7 0.0 3.9 1 97 c4
1320.0 897.0 85184.3 109671.9 0.0 8.7 0.0 3.9 1 97 c4t600A0B8000114260000070D94CB59A9Ad0
1320.0 895.0 85184.3 109671.9 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
147.0 939.1 9409.1 119387.4 0.0 9.9 0.0 9.1 1 100 c4
147.0 939.1 9409.1 119387.4 0.0 9.9 0.0 9.1 1 100 c4t600A0B8000114260000070D94CB59A9Ad0
147.0 939.1 9409.1 119387.4 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
2.0 914.0 256.0 116048.1 0.0 9.8 0.0 10.7 0 100 c4
2.0 914.0 256.0 116048.1 0.0 9.8 0.0 10.7 0 100 c4t600A0B8000114260000070D94CB59A9Ad0
2.0 914.0 256.0 116048.1 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
2.0 925.0 256.0 117514.6 0.0 9.8 0.0 10.6 0 100 c4
2.0 925.0 256.0 117514.6 0.0 9.8 0.0 10.6 0 100 c4t600A0B8000114260000070D94CB59A9Ad0
2.0 925.0 256.0 117514.6 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c4t600A0B8000114260000070D94CB59A9Ad0.fp2
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 ps10pfa:vold(pid519)

Some jobs fail BackupExec, Ultrium 215 drive, NW6.5 SP6

The OS is Netware 6.5 SP6.
The server is a HP Proliant DL-380 G4.
The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA, which I recently installed, in order to solve slow transfer speeds, and to solve CPQRAID errors which stalled the server during bootup (it was complaining to have a non-disk drive on the internal controller).
Backup Exec Administrative Console is version 9.10 revision 1158, I am assuming that this means that BE itself has this version number.
Since our data is now more than the tape capacity I have recently started running two jobs interleaved, to backup (around) half of the data at night. One which runs Monday, Wednesday and Friday and one which runs Tuesday and Thursday.
My problem is that while the Tue/Thu job completes succesfully every time, the Mon/Wed/Thu job fails every time.
The jobs have identical policies (except for the interleaved weekdays), but different file selections.
The job log of the Mon/Wed/Thu job fails with this error:
##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
##ERR##A hardware error has been detected during this operation. This
##ERR##media should not be used for any additional backup operations.
##ERR##Data written to this media prior to the error may still be
##ERR##restored.
##ERR##SCSI bus timeouts can be caused by a media drive that needs
##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
##ERR##termination, or a faulty device. If the drive has been working
##ERR##properly, clean the drive or replace the media and retry the
##ERR##operation.
##ERR##Vendor: HP
##ERR##Product: ULTRIUM 1-SCSI
##ERR##ID:
##ERR##Firmware: N27D
##ERR##Function: Write(5)
##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
##ERR##Sense Data:
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##NML##
##NML##
##NML##
##NML## Total directories: 2864
##NML## Total files: 23275
##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
##NML## Total time: 00:06:51
##NML## Throughput: 8,102,275 bytes/second (463.6 Megabytes/minute)
I am suspecting the new controller, or perhaps a broken drive?
I have run multiple cleaning jobs on the drive with new cleaning tapes. The cabling is secured in place.
I have looked for firmware updates, but even though theres a mentioning of a new firmware on hp's site (see http://h20000.www2.hp.com/bizsupport...odTypeId=12169), I can't find the firmware for netware HP LTT (the drive diagnosis / update tool).
I'm hoping someone can provide me some useful info towards solving this problem.
Regards,
Tor

My suggestion to you is to probably just give up on fixing this. I
have the same DL380, but a slightly newer drive(Ultrium 448). After
working with HP, Adaptec, & Symantec for over a year I gave up. I've
tried different cards (HP-LSI, Adaptec) , cables, and even swapped the
drive twice with HP but was never able to get it to work.
In the end I purchased a new server, moved the card and tape drive,
and cables all over to the new server and the hardware has been
working fine in the new box for the last year or so. Until I loaded l
SP8 the other day.
My guess is that the PCI-X slot used for these cards isn't happy with
the server hardware.
On Tue, 27 Jan 2009 11:16:02 GMT, torcfh
<[email protected]> wrote:
>
>The OS is Netware 6.5 SP6.
>
>The server is a HP Proliant DL-380 G4.
>
>The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
>
>The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA,
>which I recently installed, in order to solve slow transfer speeds, and
>to solve CPQRAID errors which stalled the server during bootup (it was
>complaining to have a non-disk drive on the internal controller).
>
>Backup Exec Administrative Console is version 9.10 revision 1158, I am
>assuming that this means that BE itself has this version number.
>
>Since our data is now more than the tape capacity I have recently
>started running two jobs interleaved, to backup (around) half of the
>data at night. One which runs Monday, Wednesday and Friday and one which
>runs Tuesday and Thursday.
>
>My problem is that while the Tue/Thu job completes succesfully every
>time, the Mon/Wed/Thu job fails every time.
>
>The jobs have identical policies (except for the interleaved weekdays),
>but different file selections.
>
>The job log of the Mon/Wed/Thu job fails with this error:
>
>##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
>
>##ERR##A hardware error has been detected during this operation. This
>
>##ERR##media should not be used for any additional backup operations.
>
>##ERR##Data written to this media prior to the error may still be
>
>##ERR##restored.
>
>##ERR##SCSI bus timeouts can be caused by a media drive that needs
>
>##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
>
>##ERR##termination, or a faulty device. If the drive has been working
>
>##ERR##properly, clean the drive or replace the media and retry the
>
>##ERR##operation.
>
>##ERR##Vendor: HP
>
>##ERR##Product: ULTRIUM 1-SCSI
>
>##ERR##ID:
>
>##ERR##Firmware: N27D
>
>##ERR##Function: Write(5)
>
>##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
>
>##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
>
>##ERR##Sense Data:
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##NML##
>
>##NML##
>
>##NML##
>
>##NML## Total directories: 2864
>
>##NML## Total files: 23275
>
>##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
>
>##NML## Total time: 00:06:51
>
>##NML## Throughput: 8,102,275 bytes/second (463.6
>Megabytes/minute)
>
>I am suspecting the new controller, or perhaps a broken drive?
>
>I have run multiple cleaning jobs on the drive with new cleaning tapes.
>The cabling is secured in place.
>
>I have looked for firmware updates, but even though theres a mentioning
>of a new firmware on hp's site (see http://tinyurl.com/d8tkku), I can't
>find the firmware for netware HP LTT (the drive diagnosis / update
>tool).
>
>I'm hoping someone can provide me some useful info towards solving this
>problem.
>
>Regards,
>Tor

Server recognizes only half of RAM

Greetings, we have 8 HP servers Proliant DL 380 G5 with Bios p56 2011.02.05 version (the latest one, as I understand). Now, all servers have 4 1-GB FBDIMMS, which work fine.
Recently we decided to upgrade and purchased memory KTH-XW667LP/8G (according to manufacturer, it is equivalent of 466440-B21 HP/COMPAQ and is fully compatible with this model). I installed two 8GB FBDIMMS in one of the servers, but he sees only half of memory. Instead of 16 Gb it recognizes only 8Gb.
Now, I tried several vaiants:
1. All 4 1-Gb FBDimms (the old one) are placed in banks 1A and 3A, 2C and 4C. The 8Gb FBDIMMS are placed in banks 5B and 7B (according to the guide, this should be fine). The server shows 12 Gb (in BIOS and in RHEL). I.e. it recognizes fully the old memory, but not the new one.
2. The old memory is completely removed for experimental purposes. The 8Gb FBDIMMS are placed in banks 1A and 3 A. The server shows 8 Gb only.
Now, I tried it on three servers with various 8GB FBDIMMS (we bought 10 packs) to make sure, that this is not caused by server damage or memory damage. Nothing helps, the result is the same. I guess, the problem is not in servers and not in memory. There are no BIOS updates that I can install (we have the most recent version). So, what could cause this problem? Maybe I need to switch something inside the server in order to recognize memory? Maybe this is a memory redundancy mechanizm, that can be turned off or what?
This question was solved.
View Solution.

Hi:
I don't have an answer for you, but I don't see that you posted your question on the HP Business Support Forum - Servers section.
I recommend you copy and paste your issue on a new post there.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264
Paul

Oracle licensing

Dear All
I am writing this query to take a dessition on the purchase of Oracle licenses for my company.
My company is planning to impliment Oracle E business ERP . The following are the detaild spec of my company's enviornment.
Server
HP Proliant DL 380 G5 server
core duo 2 GHz processor
4 GB RAM
C drive Mirrored
D drive RAID5
In my company almost 50 users are expected to be use the erp software
We are planning to install Oracle Database and Application in the same server.
Our ERP implementing company is saying that they are using Oracle 10g DB (Std Edn)and 10 g Application (Enterprise Edn)
They send me a proposal for the licensing (Named User Licensing)
Here I am confused with this licensing structure
Can sombody guid me which kind of license i want to purchase
Regards
sumanlal

Here I am confused with this licensing structure.
named user?You have two options:
1) Named users plus --> If you can determine the number of users (or an average)
2) Processor --> If you cannot determine the number of users
Is it the Oracle users which we are creating in Oracle?
(User name and password to log in to the ERP)Correct, total number of users defined in the system (not concurrent users).
I am afraid that if I created a user account under Oracle and the same person is leaving the company …. I cannot use that license anymore? Is it true?If you disable this user (account is not used anymore), then you can use the same license for another (new) user.
Can I use the same User ID to log in to the application from different desktops same time?
Is there any limitation on number of sessions that can open by a names user?You cannot just create one account and use it by different users; each user should have his/her own account.
If I am going for named user licensing How many user license I want to purchase
And I am looking for a lifetime license term Refer to the same document, under "How much software do we need to purchase now?" section.
Again, I would suggest you contact your Oracle Sales Representative for more details about the license.

Install AntiVirus in Server - impact on database ?

HI all,
my environment
hp proliant dl 380 g5
windows 2003 server sp2
oracle 10g (10.1.0.2)
i have been requested to install antivirus software in this server (Mcafee 8.7) , my question here is , what the impact in oracle of doing this? i undestand that the virus scans every time a user tries to access a file .. this wil slow down my database ... I'd like to you from you .. you experiencies , configurations etc.
Thanks for you attention.
Best Regards
Rui Madaleno

Hi all,
i found a document on this subject in metalink
Subject: How To Configure Anti-Virus On Windows Server Running Oracle Database
Doc ID: 782354.1 Type: HOWTO
Modified Date: 17-FEB-2009 Status: MODERATED
I've implemented the configs suggested in this document, also i've disable the "stop email worm from send mass email" for java.exe and oracle.exe (Enterprise Manager)
Best Regards
Rui Madaleno
Edited by: ruival on Mar 11, 2009 10:26 AM

Is there a way to associate what nlm's are used by hw device

I need to move an ultrium tape drive to another server, and the nlm's I found for it are not working. I am thinking I can copy the necessary nlm's from the old server to the new server, but I don't know how to do find that association. Both servers are running 6.5 sp6. Am I way off on this?

Here are the details. I would like to move the Ultrium 960 from an HP Proliant DL 360 to an HP Proliant DL 380. Both are running Netware 6.5 sp 6. Here is the startup.ncf file from the DL 360
LOAD ACPIDRV.PSM
####END PSM DRIVERS####
LOAD CPQSHD.CDM
LOAD IDE.CDM
LOAD NWTAPE.CDM
####END CDM DRIVERS####
LOAD IDEATA.HAM SLOT=10013
LOAD CPQRAID.HAM SLOT=10017
#LOAD LSIMPTNW.HAM SLOT=1
LOAD ADPU320.HAM SLOT=1
####END HAM DRIVERS####
Startup.NCF of the DL 380
LOAD ACPIDRV.PSM
####END PSM DRIVERS####
LOAD CPQSHD.CDM
LOAD IDECD.CDM
#LOAD NWTAPE.CDM
####END CDM DRIVERS####
LOAD IDEATA.HAM SLOT=10008
LOAD CPQRAID.HAM SLOT=10015
LOAD LSIMPTNW.HAM SLOT=201
LOAD LSIMPTNW.HAM SLOT=202
####END HAM DRIVERS####

OVM 3.3 on HP ProLiant DL 380 G7

Similar Messages

Maybe you are looking for