Hp proliant 380

Hey! I'm having problems with my DL380 G4 server.
After updating the bios and the firmware, and installing a second CPU the computer screen shows nothing but black when i start the server. If i remove the second CPU i get a picture. Why is this? Any ideas?

Hi:
I recommend you also 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

Similar Messages

HP Proliant 380 G4 / SmartArray 6 / HP driver / No Floppy disk.

Hello!
And here I am with a "nice" problem:
I want to run Solaris on a HP Proliant 380 G4 series with SmartArray 6. HP kindly provide drivers for Solaris 10 on their homepage. Those drivers need to be extracted to a floppy disk. Now here is where the trouble starts: I do not have a floppy disk drive for ther server nor is it easy to just plug one in. I've tried a USB floppy disk drive which at least got me as far as the first part of the installation. It then fails when it tries to actually install the driver onto the system as it does not know anything about USB drives.
I somehow need to inject the driver to the system without having a floppy drive. I'm not sure if you can do this on installation or by somehow copying the files onto the installation ISO or using jumpstart.
Any clues or hints how this might work would be very much appreciated. I'm sitting here with my head spinning.
Thank you very much,
Georg

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>rogerisland wrote on Fri, 03 June 2005 11:25</b></td></tr><tr><td class="quote">
>That is, you can boot Solaris from the install CD (or DVD) together >with
>HP's driver from the ITU floppy in the USB floppy drive, and copy >Solaris to
>the raid array. And after that, the Solaris installer tries to mount the >ITU floppy
>(to copy the raid array driver from the floppy to the raid array), but >fails
>because no PS/2 floppy device /dev/diskette is present?
Basically, yes (and I want to install Solaris 10 on x86)
</td></tr></table>
OK, Solaris 10 should have less issues with USB floppy support than
older Solaris 9 or Solaris 8 releases.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
I have to use the console installation (without the GUI) because the interactive one hangs at the end of the disk.
</td></tr></table>
Yep, that's a known bug in the Solaris 10 x86 GUI installer. It didn't
exist in Solaris 9 x86 and older.
When the GUI installer is in use, the final step of installing the extra
driver from the ITU floppy prompts for something on /dev/console,
but with the S10 installer GUI running there's no way to type
/dev/console input.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
Another problem is that the installer tries to copy the driver to the array before disc 1 is finished (after it installed all the files though) where no reboot is attempted.
I'd like to try your suggestion though.
Is it possible to fire up a shell if I use option 3 on the installer (console install in GUI) or interactive shell (option 1) (if it wouldnt hang..but maybe it hangs BECAUSE it tries to access the disk) ?
</td></tr></table>
If the GUI installer is running, right click on the desktop and open a
"Terminal" window, to get a shell.
If you run the "ptree" command when the installation has stopped after
copying the packages from CD1 to the HDD, you should notice the
following processes:
<div class="pre"><pre> 2678 /usr/sbin/install.d/pfinstall -f /swap2 -s /dev/dsk/n 9335 sh -c /sbin/sh /tmp/diskette_rc.d/icdinst9.sh 9336 /sbin/sh /tmp/diskette_rc.d/icdinst9.sh 9345 sh /tmp/diskette_rc.d/inst9.sh 9348 sh /tmp/diskette_rc.d/inst9.sh</pre></div>
The last one ("inst9.sh", PID 9348 in my case), is blocked in a read()
system call waiting for data from /dev/console (this can be verified with
"pstack $pid" and "pfiles $pid").
You can use "kill -9 $pid" to stop that inst9.sh process which hangs the
installer.
Before you kill inst9.sh, manually mount the ITU floppy from the USB
floppy drive and install the raid drivers manually.
Btw.: I'm not 100% sure, but the installation from CD1 is probably
complete anyway and the only thing missing is the raid array driver from
HP's ITU floppy. In this case it should be sufficient to boot into single user
mode from the S10 x86 installation CD/DVD (but don't forget to add HP's
raid array drivers from the USB floppy). At the "select type of installation"
prompt (options 1 .. 4) use "b -s" to boot into CD single user mode.
On the single user shell, mount both the the raid array and the UFS floppy
and use the "install.sh" script on the ITU floppy to install the missing
raid array driver to the raid array.

Windows server 2012 R2 Slow RDP

Hi
I have server 2012 R2 Datacenter installed on HP Proliant 380 G8. All drivers and firmwares are updated and confirmed by HP. The machine is quite powerful with hundreds of gigs of RAM.
When I RDP into the machine, The screen hangs on "welcome" screen for a good 10 seconds. Same hardware with server 2012 Datacenter is much faster. It is also fast with 2008 R2.
I deployed 4 servers so far and all have the same issue.
Has any one experienced this slowness before?
I appreciate any help.
Thanks

Hi Atif,
Thank you for your posting in Windows Server Forum.
First of all please try to provide TP’s answer. In addition, what’s the version of client OS and RDC? If you are using Windows 7 then use RDP 8.1 for better performance. Apart from this, try to DisableTaskOffload in the IP-parameters. For more information,
kindly go through beneath article.
Performance Tuning Windows 2012: Network Subsystem–Part 1
Also try to configure below setting, might helpful for your case.
On the server:
Computer Config > Windows Settings > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Select RDP transport protocol = Use only TCP
On the client:
Computer Config > Windows Settings > Admin Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client > Turn off UDP on Client = Enabled
Hope it helps!
Thanks,
Dharmesh

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.

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.

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

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

Proliant DL380 G5 - Dual nic drops gateway after windows update.

On yesterday Microsoft windows update updated my DL 380 G5 sever. Part of the update was a nic driver. Needless to say the server didn’t like the update. After the update, the dual nic card will not keep the gateway. I've rolled back the driver but still no luck. Any ideas on how to fix this? My first thought was roll back the driver. Second thought download the drivers from the manufacture but I cannot determine which nic it is. How can I go about finding the exact nic type and name?

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#.Ujohb18o7Gg

Solaris 10 x86 installation problem on ProLiant DL380..

I'm trying to put Sol10 b72 on a dual-proc ProLiant DL380 here, with the Compaq 5i array controller.
I have the Solaris 9 drivers from HP; they seem to work just fine for the installation.
The problem comes at the end of the first disc.
Sidebar:
For one thing (and this drove me NUTS until I got lucky and caught it during a reboot), at the end of the install, on the console, it asks for the driver diskettes..again.
The problem is, it doesn't say this ANYWHERE else, only on the console..and if you're doing the installation in the X desktop, you just never know it. It doesn't write this to the xconsole window. I tried installing a good 5-6 times before, instead of hitting the power button out of frustration after the install just hung again, I actually opened up a terminal and typed 'reboot'..and caught the "Please insert the diskette and press Enter" as it killed X. If anyone at Sun is reading this..you may want to fix this, before someone gets very frustrated that their installations never seem to finish...
End Sidebar.
So...I'm doing the console text install (otherwise you'll never see the message to insert the driver diskettes for the Broadcom NIC and the Compaq array), and sure enough, at the end of the install, it asks for the diskette. I pop in the diskette it's specifically asking for (the Compaq array diskette in this instance), and hit enter. It chugs for a second and then says it can't find the driver on the diskette.
Which is incorrect, because if it haden't found it on the diskette during the device configuration assistant phase during bootup, it wouldn't have even been able to install Solaris.
So..what's up? Anyone have any ideas why Solaris finds it one time but can't find it later? Is this a bug or problem in the installation script?
Thanks,
Greg

problem 1 is that it's looking for ../../s0.. Which I
managed to
fake out by creating the dir in the same mount
point.
Problem 2 is that it can't find .tmp_proto, which I
must
concur with. I can't find that on any of the b72 cd
images.
So, the setup_install_server fails.This seems to be the problem when you try to setup an install
server on a Solaris SPARC system for Solaris x86 clients, using
the Solaris 9 or Solaris 10/Express CD media.
There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
and it's supposed to be mounted on the "s0" mount point,
otherwise setup_install_server won't work. On a Solaris x86 box,
vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
mount point for the platform independant ISO9660 part of the CD
media, /cdrom/cdrom0/s0 is the UFS root filesystem.
Problem is that Solaris SPARC:
- does not understand Solaris x86 disk labels
- does not allow mounting x86 UFS filesystems
(and vice versa).
AFAIK, Solaris 9 DVD media does not have this problem. I
guess the same will be true when Solaris 10 DVD media is
available in a few months. On the DVD media there's enough
free space to include an extra copy of the files in the ISO9660
filesystem.

Problem booting Solaris 10 on ProLiant server after installation.

Hi all!
I have a brand new HP ProLiant DL360 G5 server. It contains 6 internal
hard drives. RAID 5 is configured on these drives using built-in HP
Smart Array P400i controller. I've just installed Solaris 10 8/07 on this
server. Solaris requires a driver for P400i controller. I'm using Driver
Update CD created from HP provided ISO image. Solaris 10 is
officially supported OS for DL360 G5 server.
Installation proceeds as expected:
1) At the begining of Solaris installation, Driver Update is used to
load HP driver for raid controller. During installation, disk is
recognized as c1d0t0 (the only disk in system); one partition is
created on this disk.
2) Disk is devided to 6 slices:
c1d0t0s0 - swap, 4GB
c1d0t0s1 - /, cca 32GB
c1d0t0s[3,4,5,6] - /zones/[a,b,c,d] - each cca 160GB
3) At the end of installation, CPQary3 driver is installed to target
system without any errors reported. No errors are reported during
installation at all.
After reboot, GRUB is started. It shows boot menu containing two
options:
- Solaris 'normal' boot
- failsafe boot
PROBLEM: Selecting 'normal' boot leads to immediate system restart.
According to documentation, this case occurs when PCQary3
driver is not installed.
I'm able to boot using 'failsafe' option in grub. After entering single
user, I load PCQary3 driver to runtime using 'install-du' command.
I'm also able to find instaled Solaris using 'install-recovery' and mount
its root volume to /a directory. Necessary driver IS installed inside
/a/kernel/drv/ directory. Options 'bootpath' in /a/boot/solaris/bootenv.rc
file is set up correctly pointing to device associated with /dev/dsk/c1d0t0s1
device. Also GRUB is able to recognize UFS filesystem for boot partition.
I've already tried (without success):
1) Use RAID 1+0 instead of RAID5
2) Create only 3,5GB partition instead of 700GB large one.
3) Place / on c1d0t0s0 instead of c1d0t0s1.
4) Re-create boot archive using 'bootadm update-archive -R /a'
So, everything seems to be installed correctly, but system cannot boot.
Do you have any ideas how to fix this problem?
Jozef

Sounds like an issue I just had with a brand new X4150, installation and failsafe worked fine, but normal booting led to immediate reboot of the server. This was due to an incompatibility of solaris and intel's newest generation xeon chips.
You can still boot 'normal' solaris in 32-bit mode:
hit 'e' at the grub menu, 'e' again to edit the 'normal' boot entry and add 'kernel/unix' after multiboot. This should boot up solaris in 32-bit mode. From there, download and install the latest patch set (125370-06 and 127112-05 are fixing this issue). After that you should be fine.
Bjoern

Installation Problem: Solaris 8 on a HP ProLiant DL360G3

When i try to install Solaris 8 02/02 on a ProLiant DL360G3 (3GHz, 2GB RAM, 18GB-SCSI) with a Broadcom NetExtreme Gigabit-NIC 5703 , the following error message appears when Solaris is trying to boot for the first time from cd:
Boot panic: traptyp e, error 0 at 1357d9
cr0: 80000011, cr2: 8, cr3: 17d000
eax: 0, ebx: 17ff78, ecx: 24e8d8, edx: ffffffff
esi: 0, edi: 800, ebp: 1fc78, esp: 1fc60
cs: 10, eip: 1357d9, ds: 63700008, es: 70640008
Entering boot debugger:
[1357d9]
Maybe a driver problem?? I have tried all drivers i found (from HP or Broadcom�s Website), but it doesn�t solve the problem.

Hold down the STOP key and also press the A key to get the Sparc 20 to come to the ok prompt. At the ok prompt type boot cdrom
press enter and away you go. Solaris will 'at a later time' ask you if you want to format the drive.
One Note: Sometimes the Sparc can be a pain to get to the ok prompt. Watch your keyboard lights ie: Num lock, Caps lock etc. right after they get tested and flash, press stop and A. Sometimes you have to hold down the stop and press the A key by itself. Hope this helps.
Carl

Install Solaris10 on HP ProLiant ML370 G6, "No Disk" error

Hello,
I want to install Solaris10 on HP ProLiant ML370 G6 servers which are on the Hardware Compatible List( HCL). However, I always encounter "No disk" issue and installation fails. The disks are HP SAS disks.
I searched online and knew that CPQAry3 driver must to be installed first. I did but the "No disk" error still happens later.
I am wondering what else I should do?
Tom

Hi Tom,
You have to apply the ROMPaq Firmware Upgrade before.
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=emea_africa&prodNameId=3884311&prodTypeId=15351&prodSeriesId=3884310&swLang=13&taskId=135&swEnvOID=2023
Marco

HP Proliante 320 g8 and Windows 7 64 bit

I know that HP Proliante 320 g8 and HP Proliante 320 g8 v2 do not supported Windows 7, but our company already has bought these computers and license Windows 7. I can install Windows 7, but I do not have drivers. More precisely Windows wants drivers only on chipset and usb. Is it possible find this? May be i can install drivers for others Proliants?
p.s. sorry for my english

Hi:
You may also want to copy and paste your question to the HP Business Support Forum--Proliant Servers section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264#.Ul7yrdco7Gg

Nstalling Windows Home Server 2011 on a ProLiant ML350e Gen 8 Server (Nothing appearing in Operating System Selection During Install)

We just purchased Windows Home Server software that required a new server to be purchased. We went with the ProLiant350e Gen8 Server. IUpon starting up the new ProLiant server I booted from CD-Rom and got to the Windows Install program. I clicked "Install
A New Server" However, as soon as this page loads it gives me an error that says "Load Driver" "A required CD/DVD Drive Device Driver is Missing. If you have a floppy disk, CD, DVD, or USB flash drive, please insert it now." It gives
me the option to browse or click okay. Browse only brings up the (x:) Boot drive and VID. It doesn't find the driver in VID Than if I click okay it gives me a message that says "No Device Drivers were found. Make sure that the Installation media contains
the correct drivers and then click ok" I have tried to use smart provisioning but this fails as it cannot recognise the media from the DVD drive.
Thanks in advance,

You should use HP smart start DVD to install the Windows Home Server. If you are booting directly from the Windows DVD it would some times not detect the drivers because of the hardware compatibility issue. You should contact the the vendor and seek help
from him.
http://www.arabitpro.com

Hp proliant 380

Similar Messages

Maybe you are looking for