Tag Info

New answers tagged

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

Reading your configuration, I see: 8 disks total... Disks 1,2,3,4 are in a RAID 1+0 array. Disks 5,6 are in a RAID 0 stripe. Disks 7,8 are in a RAID 0 stripe. I'm not going to ask why you have two RAID 0 arrays. Surprisingly, they're healthy! It looks like disk 2 was replaced. It's paired with disk 4. You could likely have READ errors on disk 4 that ...


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


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

The photo looks like your system is an HP ProLiant DL360 G6 or G7 1U rackmount server. I saw your note about defective HP disks. I work with a considerable number of HP servers and haven't seen this as a widespread problem. I do think that you could provide more information about the Smart Array RAID controller's status during the system's POST process. ...


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


10

Yes, they're completely hot-swappable. Think of them the same way as cables (note the link lights). Same for SFP+ direct-attach cables. It wouldn't make sense for them not to be hot-swappable. Heck, most network switches don't even have power switches :)


6

Generally yes they are, certainly I've never come across any that weren't - in particular I know for a fact that the top three on your list are, not used the bottom one so can't say with the same degree of confidence.


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


3

You'll want to look into implementing some of the SES commands. SES stands for SCSI Enclosure Services, and is the protocol used by external JBOD storage enclosures to report health and do things like illuminate disk LEDs. Nexenta has sesctl, but there are other third-party options like SmartMon-UX. Are you actually using real Solaris, or a ZFS-based ...


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


0

You will need a EEPROM programmer to reflash the BIOS chip with the correctly firmware to put this machine back in production. If it's on warranty, I would recommend you to call to HP and explain the whole situation and find a solution for this problem with the vendor. I do not recommend BIOS reflashing with a external programmer if you never done this. ...


0

We had the similar issue, and found out it is due to XFS log version change. Version 2 logs honor the stripe width set used with mkfs.xfs. If you do a lot of fsync, your raid card can not fake those logs writes anymore. You may test it by format the partition without any swidth setting(it does not make any difference with RAID 1+0). You can verify that with ...


2

You have a 3-disk RAID 5 disk array. One of the disks had failed or is failing. Another of the three disks may be failing. Do you know how long this drive has been in the failed state? (orange light means drive failure) What size disks are these? What model of server is this? My recommendation is to power the server off, remove the power cables and let ...


2

For your specific question, you can add disks without firmware updates. If the RAID controller thinks the disk firmware should ABSOLUTELY be upgraded, it will actually ask and give a 1770 - Disk Firmware Upgrade Recommended error at POST. I recommend running HP firmware updates often... either every 6 months on current hardware or at least yearly on older ...


4

Necessary - no, advisable - yes. It's because the updates are generally there to fix bugs, one bug that might be fixed might screw you over doing what you want to do - thus by upgrading you're reducing the risk of the work you're doing somewhat.


2

Does it matter which sensor #21 is? What would you actually do about it? Can you check your ambient temperature? What can you control about your environment to keep that within a reasonable range? Are you absolutely sure you don't have a failed fan? --edit-- It makes sense to ensure the firmware of ALL of your components is up-to-date. For you, that ...


1

There's no manual fan control. Trust your server and the engineering that went into the design of the product. This isn't a Supermicro server :) The option that HP recommends for workloads that may require additional cooling or system configurations with certain PCIe hardware installed is to select the "Optimal" or "Increased" cooling option in the BIOS. ...



Top 50 recent answers are included