Hot answers tagged hp
You can make this work with some effort. Normally, I'd be all like, "Use HP drives", but the fact that you're using a G7 ProLiant means that many of the firmware restrictions don't apply from either side. Gen8 ProLiant servers are a totally different story. So, in this case, it's just a formatting issue. The AX4 disks are formatted in 520-byte sectors, ...
is there something we are missing or is this hopeless? They're not supported, HP puts a specific firmware on their disks that provides a lot of additional diagnostic data over an off-the-shelf disk. This site is built for professional sysadmins, we like to build supportable solutions so I'd avoid trying to do what you're attempting.
Is there any reason you're not using HP disks in this server? I'm assuming you're using these Seagate SAS drives for capacity, since 7200 RPM 2.5" disks are usually a bad proposition and can cost more than 900GB 10k SAS... Either way, these servers/onboard controllers were not designed for 4k disks. If you're using a G7 system with a P410, just stick to the ...
Sometimes KVMs can be problematic on HP servers... Especially cheap KVM switches. Please check this post and follow the troubleshooting decision matrix: HP ProLiant DL360 G7 hangs at "Power and Thermal Calibration" screen
FBWC is the only option for modern HP controllers. BBWC is not offered anymore. There is very little practical use for the Zero-memory controller unless local disk performance isn't important to you. Otherwise, you will always want to have a cache available... this is necessary for some of the RAID controller options and being able to use SSDs.
It appears that your RAID controller have no cache. The main problem is that hardware RAID card tend to disable, by default, the disk's private DRAM cache. In short, this means that when, after some seconds (~30, to be precise) the dirty pagecache will be flushed to disk, a tons of random I/O request starts hammering your (slow) mechanical disk, killing ...
This is a situation where you should contact your vendor. If this is a new system, it makes sense to call whoever sold you the system or you have the option of contacting HP support. Feel free to check for loose components: fans, CPU heatsinks, etc. But in the end, it sounds like this machine is DOA.
It doesn't appear as though you have any write cache. Please confirm the generation and model of your server. If you don't have a Flash-backed write cache module (FBWC) on the controller that your disks are attached to, your VMware performance will suffer. The other issue here is LVM and some of the defaults that appeared in RHEL6 a few years ago. You'll ...
Unlikely to work, HP puts its own software onto the disks to keep people coming back to them for legit parts.
Yes there are definitely a few shortcomings when it comes to support for non-AD LDAP servers. If you leave out the "Directory User Context" fields out, then at least your users can login with their full DN, i.e. uid=joe,ou=people,dc=example,dc=com but obviously that's not a great solution. As far as looking at group memberships, not sure if OpenLDAP ...
What's going on here is that the tape in slot 21 is in some tape pool (probably something like "Default LTO"). That pool is marked as "Appendable", which means that Data Protector will write to that tape until it is full. Then it will move on to the next-best tape. The algorithm for choosing the "best" tape is: the tape with the fewest overwrites, and if ...
While this is similar to your other question, it would be very nice to understand the full context of what you're doing; e.g. why are you looking to query BIOS settings, and what does that have to do with the uptime of already-running systems? If you're looking at automating the BIOS configuration of multiple HP ProLiant servers, there are also tools for ...
Only top voted, non community-wiki answers of a minimum length are eligible