RSS
 
 

Archive for the ‘CentOS’ Category

HP Servers with Non HP Disk Drives, Where is Temperature Sensor #29 on DL380?

05 Nov

I have a home built system consisting of several HP Proliant DL380 Gen7 & Gen8 servers.
Now normally when sitting idle these are solid servers with fairly low power consumption and in many cases Whisper quiet when under no load.

That was until a recent upgrade of a failed disk drive.
Actually the server went from one seagate drive to almost exactly the SAME model of Seagate drive with a slight difference in the part number.

From a ST2000LM007 to ST2000LM015, both are: 2.5″ SATA 6Gb/s 5400RPM, 128Mb ram.
This simple change has left the internal fans running at 90% of full speed and continual warnings of the drives over heating.

Temperature Sensor #29
It is believed that this is a “pseudo sensor”, take a bunch of system temperatures pass them though a formula or table matrix and arrive at some sort of “system Health” number.
Why think this?, because it is possible to “fool” this sensor in reporting different temperatures that are not related to anything temperature like in particular

There has also been a very interesting support note released by HP recently covering most of the HP production and EOL systems.
Notice/ ProLiant Gen7 Gen8 and Gen9 Servers – Fan Speed May Be Higher Than Expected If No Hard Drive Is Present In the System

I think what we are looking at is not actually a system problem ,but rather a iLO X problem, or more likely a design “feature” to lock down the hardware.
Why would anyone run a server without disk drives?, simple…. cloud implementation… throw in a few optical connectors to an optical switch and a fiber based NAS
and you have very cheap computing systems that can be easily configured from a central location ,no local disk drives needed.

Problem is, that this increase in fan speed “by design” as HP likes to put it , is potentially breaking the law of some countries related to Environmental impact of electronic equipment.
Those extra ramped up fans are adding 90-100W to the power consumption , which equates to over 2KWh a day. which adds up to several hundred KWh per year of power that is being “deliberately wasted” for no reason what so ever(parts NOT fitted in the server, as an option to SAVE power resources.).

 

coreos-cloudinit not found. Could not validate config.

02 Jul

When Installing coreos, this is a common problem depending on the ‘live CD’ used:


./coreos_install.sh -d /dev/sdb -C stable -c ~/cloud-config.yaml
./coreos_install.sh: coreos-cloudinit not found. Could not validate config. Continuing...\

All manner of ‘solutions’ appear on the internet, actually it is simply stating that ‘coreos-cloudinit’
is missing.

The reason being that the so called install scripts are actually not fully integrated.

Simply following the instructions at :
http://www.formatccolon.com/installing-coreos/

will ONLY work IF you use a liveCD that contains ‘coreos-cloudinit’

Get in the prerequisites first:

So:
1. Build your cloud-config.yaml BUT validate it first at:

https://coreos.com/validate/

Then ensure that you perform the following BEFORE attempting the installation

your working directory:
wget https://github.com/coreos/coreos-cloudinit/archive/master.zip
unzip master.zip
cd coreos-cloudinit-master/
./build
cd bin
#ensure you put the binary on a path where it can be found
cp coreos-cloudinit /usr/bin/coreos-cloudinit

Then cd back to your original working directory where you have:
coreos-install.sh (or whatever you called it)


./coreos-install.sh -d /dev/sdb -C stable -c ~/cloud-config.yaml
Checking availability of "local-file"
Fetching user-data from datasource of type "local-file"
Downloading the signature for http://stable.release.core-os.net/amd64-usr/current/coreos_production_image.bin.bz2...
2015-07-02 20:12:43 URL:http://stable.release.core-os.net/amd64-usr/current/coreos_production_image.bin.bz2.sig [543/543] -> "/tmp/coreos-install.GLOoJSUz0c/coreos_production_image.bin.bz2.sig" [1]
Downloading, writing and verifying coreos_production_image.bin.bz2...
2015-07-02 20:14:03 URL:http://stable.release.core-os.net/amd64-usr/current/coreos_production_image.bin.bz2 [196978663/196978663] -> "-" [1]
gpg: Signature made Thu Jun 18 17:08:09 2015 HKT using RSA key ID xxxxxxxxx
gpg: key xxxxxxxxx marked as ultimately trusted
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Good signature from "CoreOS Buildbot (Offical Builds) "
Installing cloud-config...
Success! CoreOS stable current is installed on /dev/sdb

And that gets you to the next stage.

 

CentOS 6 installing the Graphical interface (GUI)

06 Aug

When doing work for customers I work mainly on VM installations. This allows me to try things out and then rollback the OS should anything not work out.(Just HOW cool is it to be able to take snapshots & rollbacks of a complete os!!)
Normally this is fine for 99.99% of all the work I do, It also allows me the ability to offer the customer complete security, because once the VM is securely erased, absolutely all the customer job information is removed from the machine.
Read the rest of this entry »