Tag Info

New answers tagged

0

That's an HP ProLiant DL385 (G1) and was released in 2004 around the same time as the DL380 G4 (Intel variant). These were HP's first x86_64 servers, but still used some legacy technologies (like IDE for CDROM, parallel SCSI disks and PCI-X expansion). The full specifications for your server are here: DL385 Quickspecs. You can use any 80-pin SCSI SCA ...


0

In general, no. The 2 interfaces are completely different, and there's no way to "convert" one into the other, especially within the confines of a drive bay with backplane. I've done this before on an old Poweredge, many years ago. It basically involved shifting the backplane back off the chassis far enough away that I could route the SATA cables around it, ...


0

It's amazing how things get screwed up by RHEL, going completely against the philosophy of open source software (which it's is core, btw)... Hopefully somebody will come around and add the CCISS module so that I can use the "aging" hardware, or maybe I should use Windows instead of linux? (is the sarcasm obvious?)


3

Two things... You can add a warranty to an HP server whose factory warranty lapsed. It's not very expensive to add another year of support to the machine you have now. You can also initiate a per-incident support call/technician with HP and be liable for parts charges. Depends on how desperate you are... But here's a (lengthy) troubleshooting ...


5

HP had a pretty awful initial set of firmware releases for the ILO3 management interface. See the massive changelog documenting the evolution of the product. I was working for a firm that deployed a large number of ProLiant DL380 G7 servers and had to deal with the pain of managing the buggy feature set. In your case, you're trying to move from a very old ...


2

Yes and no... The server is capable of running the applications and Windows Server 2008/2012 from a CPU and RAM perspective. However, there is a fairly large limitation in the storage array controller for that particular server line. HP ProLiant servers are available in "e" (essential) and "p" (performance) variants. If you can afford the initial cost, the ...


2

Place your ILO, IPMI, DRAC and other management devices on their own management VLAN or network. Secure access to that network with VPN or prevent Internet connectivity. Only allow access from trusted networks. That's an acceptable way of mitigating the (still narrow) risk you outlined. You can also disable access to the ILO devices until an updated ...


5

Firmware is not the problem here. HP firmware rarely bricks a server; especially that model. Your issue here is the cocktail of drivers loaded on the system. I'd recommend using the HP Service Pack for ProLiant DVD (and the Smart Update Manager) to install system drivers, or just cherry-pick and download components directly from the support site for your ...


2

This may be a long shot, but ensure the "Plug and Play" service is started on the server. If it's not, from what I've read it could cause odd issues like you're experiencing. Otherwise, the firmware probably trashed the drivers on the server. You can attempt to uninstall/reinstall using the server DVD media (use the "Have Disk..." option) or do a repair ...


-6

Did you make a system restore point? Normally Windows updates automatically make restore points before updates. Check it by doing this: Go to control panel, Search "Create a Restore Point" Click whatever comes up A window should pop up and somewhere it should say "System Restore" in a button or link format. Click it. System Restore should pop up. Follow the ...


5

Interesting issue... So the HP RAID controller driver from around 2001 to ~2009 was the CCISS driver. There was a transition to the HPSA driver at some point, moving the Smart Array controller support back into the regular SCSI subsystem versus the dedicated block driver... HP servers from the G1 to G5 era used the CCISS driver. On newer operating systems ...


5

The answer here depends on the specific model of server being used. I was holding off until the OP could describe the actual server being used, as the SSD options vary. Read through the descriptions of HP's SSD portfolio for detailed information on the different classes of drive. For instance, with a G6 or G7 ProLiant, all SSD performance will be ...


3

The HP Solid State Drives (SSD) Quickspecs document likely has all the details you need. Besides raw speed and IOPS a large part in price difference between what HP calls Value Endurance, Mainstream Endurance and Enterprise Performance is how often the complete disk can be overwritten, because flash supports only a limited number of write cycles. I ...


3

I found the technical specs on insight for the HP drives: Specfications -> Performance -> 4KB Random Read 63000 IOPS 4KB Random Write 19200 IOPS Drive Transfer Rate 600 MBps (external) Internal Data Rate 480 MBps (read) / 185 MBps (write) I then looked up the Samsung Evo 840 specs, this case taken from [ebuyer], this case a 120GB ...


1

I can see the issue here - if you look on the compatibility tab of THIS link you'll see it's not a supported configuration. Presumably because it's 12800 memory rather than the 1066 or 1333 memory HP sell but it could be another factor - either way next time be more careful selecting products, if in doubt always buy from the vendor for this exact reason.


6

Hmm, that's Kingston RAM. Are you absolutely sure it is compatible? (I advocate using HP RAM in HP servers) What was the old RAM configuration? I'd suggest going back to the old configuration... To start, please remove power (and power cables) from the system for a few minutes. Plug them back in and try again. Also, is your ILO3 configured? You can use ...


0

You can configre RAID0 per available phisical disk. Let's say if you've got 8 disks, then you end up having something like that (CentOS 6): # hpacucli ctrl all show config | grep RAID logicaldrive 1 (558.9 GB, RAID 0, OK) logicaldrive 2 (558.9 GB, RAID 0, OK) logicaldrive 3 (558.9 GB, RAID 0, OK) logicaldrive 4 (558.9 GB, RAID 0, ...


2

It's possible to recover the data, provided no other actions have been taken on the array. You could do a few things like taking an image of the individual disks (via Clonezilla/dd/etc.) and keeping that as a fallback... The common approach is to try to either recreate the array with the same settings/RAID/level/strip size and boot via a recovery CD to ...


2

Risky upgrade... Remove power from the server. Unplug the cables. Let the machine sit for a few minutes. Plug the cables back in and power on. If this doesn't work, you'll want to reset NVRAM. Take a look at the HP ProLiant DL360p Gen8 Server Maintenance and Service Guide You have to clear the CPU errors... Try the sequence detailed here. If you have ...


0

This is likely a firmware issue with the server hardware. Many organizations and systems administrators don't take the time to update and maintain the firmware of their HP ProLiant servers. It requires a different mindset than a Dell or Supermicro system that's less tightly-integrated. You have an HP ProLiant DL160 G6 server, so that places the deployment ...


0

ProliantSupportPack is obsolete at least for Debian. HP drivers should be in stock kernel, utilities can be downloaded from "Management Component Pack". To use it, add this list to your /etc/apt/sources.list: deb http://downloads.linux.hp.com/SDR/downloads/ManagementComponentPack/debian/ wheezy/current non-free However on my G7 server with SmartArray ...


1

So here's what I'd do. The HP ProLiant DL180 G6 model you have is a 25-bay unit. There's a SAS expander embedded on the drive backplane and two SAS SFF-8087 cables routed to an HP Smart Array P410 PCIe controller. Part of that is why you see the odd port:bay presentation. I'd upgrade the backplane firmware and get your P410 controller to the last ...


1

Okay, this is sounds a bit off... so I'm going to make some assumptions about what you're trying to do. It seems like you're interested in obtaining the serial number of an HP ProLiant server programmatically. You ask about chassis information and the Array Diagnostics Utility (ADU). The Array Diagnostics Utility output is not where you want to look for ...


0

I would look at the dump files and see if there is an obvious way to identify a driver issue. http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888 http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx These steps sometimes give an obvious answer ...


1

Can you tell us what operating system you're wiring with? That's a big detail. I'll assume Red Hat or CentOS... An HP Gen8 server under a modern OS will be using the HPSA driver, not CCISS. So your drives will be /dev/sdX... e.g. /dev/sda, /dev/sdb, etc. (maybe this isn't a Gen8 server) Regardless, assuming RHEL or CentOS, you'll need the zerombr parameter ...


1

Solution: I am a numbskull and should have used the add_repo.sh script provided by HP. I was converting my deb line from an old format provided by their legacy SDR system and failed to notice some format changes. The correct format for the deb line is: deb http://downloads.linux.hp.com/SDR/repo/mcp/ubuntu/ precise/current non-free If you use the ...



Top 50 recent answers are included