I've got a 'virgin' machine from Nocster running CentOS 5, including a SATA drive (shows up as "SCSI").
It looks like it'll be a straight-forward install [url], but I wondered if anyone has had this exact combination before and if there are any problems I should expect? Given that it's a dedicated machine I don't have physical access to, I'm slightly paranoid about screwing up.
I installed 2 SATA raptors drives on my server. I formatted/partitioned one of the drives through WHM. After rebooting both drives disappeared. They are still detected within the BIOS but not in CentOS. It is possible that I installed a wrong driver or made a bad configuration change.
CentOS 4.6 64bit cPanel/WHM Motherboard: [url]OS is running on a 250GB IDE drive 2 SATA WD Raptors (That I am trying to get to work)
we've been testing CentOS 5.3 on Intel DG35EC board (G35+ICH8+82566 Gb NIC), and found that the write speed out of 7200rpm SATA-II drive, connected to on-board ICH8 controller, is consistently under 10MB/sec which is quite horrible!
the same set of hardware can get 100MB+/sec transfer rate with Debian 5.0 and FreeBSD 7.1, just not the CentOS5.3! it doesn't matter whether AHCI mode is selected in BIOS or not, and of course BIOS has been updated with latest version.
I'm testing out the old version of CentOS which is CentOS 2.1 on Virtual PC and I'm running into some problems. After installation of CentOS, it asks me to reboot the system so then I reboot it. Then it prompts me for the login and password.
I type in "root" and my password. Then I'm stuck inside this command prompt that says:
Now, how exactly do I get into CentOS graphical user interface, or is this it?
I'm trying to install imagemagick on centos using yum... I did the yum update, then tried 'yum install ImageMagick', but that didn't work - "Nothing to do". I also tried the i386 RPM, which also did not work, I'm missing a bunch of dependencies, has anyone installed this on CentOS know of a specific rpm or another way to install? Ideally, without installing through source.
I followed a combination of this tutorial:[URL]and this tutorial [URL] (I had to use a combination since following each individually brought up errors along the way).
Anyhow, installing OpenVPN was a breeze but I think I am getting hung up on the configuration part. Basically after generating all of the certificate files and stuff, when i try to "service openvpn start" i just get the message "FAILED".
Where do I look to see what the reason for the failed start could be?
I decided to go with Cent OS after reading about it in the forums here, but I've had nothing but problems trying to install it. I first tried to do a net install but the installation took nearly an entire day because it would keep popping up messages about corrupt files when downloading the package files. Eventually it just gave up or rebooted because I came in in the morning to find it at a message saying "No OS installed". I then burned all 7 installation disks and tried that way, still got a few of the corrupt file messages (but far fewer than the previous time) and made it through the installation only to still have it say "no os installed" again after the reboot. I thought maybe it had something to do with the fact that I was not installing a boot loader (there is no other OS installed anyways) but when I tried to reinstall a third time, this time with the boot loader, it now says that the CD drive (USB) is already mounted on tty2 and I can't even start the installation? WTH!
The server is a Dell PowerEdge R300 with two Intel Core 2 Duo 64-bit processors. I'm using the x86_64 ISOs from the Centos.org mirrors.
how to install CentOS by not using the installer. This guide should be great when installing over networks, don't have a graphical console available (for installing over serial), when you're not content with the installer's job, installing CentOS from another distro, or plainly want to learn more about how CentOS works.
Requirements: * Have a host OS that has the "rpm" package manager available. Some distributions have it in their repositories (even if the package manager for the distro itself is not rpm), and knoppix (a linux live/rescue CD) has it aboard too. You can use the first CentOS ISO CD too (use linux rescue at boot), and it has all the necessairy packages aboard * Access to the CentOS base repository. It's on the first CentOS ISO CD * Use your BRAIN. This guide is ment to be interpreted, not copy/pasted
Code: # First, setup your disks to your liking. You can use whatever you want here, # RAID, LVM, etc... Remember your disk configuration because you'll need it # to configure grub, menu.lst and fstab. Using RAID, LVM, or others will require # more configuration than this guide covers. To keep it simple I'm using a # single disk. An example:
$ fdisk /dev/sda $ mount /dev/sda3 /target $ mkdir /target/boot $ mount /dev/sda1 /target/boot
# Depending on the host OS you're using, you may need to initialize the rpm db # on the host OS $ rpm --initdb
# Use the following command to install the packages. I'll be addressing this # command as $rpm.
$ rpm --root /target -i
# Use your shell's tab completion to complete the package filenames. I # deliberatly left out the versions so these instructions apply to a wide range # of versions
# Let's install some basics $rpm setup basesystem filesystem
# Install bash first, this is needed for post-install scripts $rpm bash glibc glibc-common termcap libgcc tzdata mktemp libtermcap
# Install some dependencies (this is mainly to keep the next command smaller) $rpm grep pcre libstdc++ info ncurses zlib gawk sed ethtool
# If this command gives an error, you can safely ignore this because it's not # of importance. What is important is that grub-install copied the right files # to /boot/grub that we need for booting. $ /sbin/grub-install /dev/sda
# Manually install grub if the previous step failed. - means type it in the grub # shell $ grub $- root (hd0,0) $- setup (hd0)
# Optional packages # You may want to install passwd so you can set passwords ;-) $rpm passwd libuser openldap cyrus-sasl-lib
# These are used to set the keyboard language (loadkeys) $rpm kbd usermode
# ** Right now you should have a bootable system! Here are some tips to help you # through your 1st boot ***
# Most of the system configuration happens in /etc/sysconfig. See
for full documentation.
Some quick post-install tips: * Configure your keyboard in /etc/sysconfig/keyboard using the KEYTABLE variable
* Configure networking Take a look at /etc/sysconfig/network-scripts. See ifcfg-lo for an example.
# This recreates the RPM database. If the host OS you used has a different # version of db, rpm will complain with # rpmdb: unable to lock mutex: Invalid argument $ rpmdb --rebuilddb
Code: [root@server ~]# sh ./hypervm-install-master.sh --virtualization-type=openvz Here is the output it's returning to me (From log file)
Code: Installing packages which lxlighttpd zip unzip lxphp lxzend curl mysql mysql-server mysqlclient10... Setting up Install Process Setting up repositories Reading repository metadata in from local files Excluding Packages in global exclude list Finished Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package lxphp.i386 0:5.2.1-90 set to be updated ---> Package lxzend.i386 0:3.3-lxa set to be updated ---> Package lxlighttpd.i386 0:1.4.13-1 set to be updated --> Running transaction check --> Processing Dependency: libmysqlclient.so.14(libmysqlclient_14) for package: lxphp --> Processing Dependency: libmysqlclient.so.14 for package: lxphp --> Finished Dependency Resolution Up2date Gave Error... Trying Again...
Just to make things clear, i am not new at setting up VPS nodes, i have set up all of my servers with the HyperVM/OpenVZ setup and they work perfectly, but im having a problem with a new server.
Just received my new server, installed HyperVM-Slave, rebooted but the OpenVZ kernel was not installed for some reason, so i manually installed the OpenVZ Kernel using the RPM as yum seemed to install the wrong kernel.
I then installed the kernel using RPM and got this error at the end of installation:
grubby: unable to open /dev/hda: No such file or directory grubby: unable to open /boot/boot.b: No such file or directory grubby fatal error: unable to find a suitable template
I have never encountered this error with any of my other servers before...
Also after installation everything seems to be correct. /etc/grub.conf has the new OpenVZ kernel displayed, and default is set to 0, so upon startup it should be booting the correct kernel, but the thing is, when i reboot the machine the default kernel is loaded even though the grub.conf is configured to load the OpenVZ Kernel.
Im thinking that this may be due to the error i got when installing the kernel.
I'm currently in the process of ordering a new server and would like to throw another $50-$70 at the default SATA II 7k 250 GB to increase performance. The server will host a site similar to WHT (php, mysql, and some forum traffic ).
There are three options I can get for the price:
1. Add another SATA II 7k 250 GB and set up RAID 1 2. Add a 73GB 15k RPM SA-SCSI and put mySQL on it. No RAID. 3. Toss out the SATA II 7k and take two SATA 10k 150 GB instead. Put mySQL on one of them. No RAID.
Please keep in mind that the question is budget-related (I know I can get more if I spend an extra $200 but that's not what I want ). Which of the above will make me happiest?
I currently have a Dell Poweredge 2650 from a few years back, it is running...
2x Xeon 2.4ghz 512K 3GB DDR266 RAM 1x73GB SCSI
Back in the day this system cost $2000, now it's not worth close to that.
So my plans were to dump this bad boy as an SQL server, seeing it has the SCSI backplane and 3GB of RAM, and SQL usually doesn't need as much CPU as a web server.
Now my question, would it be better to use this server or would it be better to build a cheap Core 2 Duo with a RAID0 array with a few SATA drives?
Before you start going off on RAID0, it doesn't matter to me because I am using clustering/failover so data will not be lost and no downtime will be received if the array fails.
Basically what I want to know, is it worth it to keep this server and build upon it or would it be better to sell this server and look into spending an extra few hundred to build a new system with SATA RAID.
I'm going by price/performance rather than reliability as I am using failover to let you know once again .
To work on an HP ProLiant DL360/380. All I know is they are SCSI U320 drive bays, or that is the type of drive they take. Can anyone provide any insight on what may work? We are trying to get a more cost effective way to get more storage into a server. The largest SCSI drive I can find is 300GB for $200. You can get 2TB drives for that much these days.
is it really worth the money nowadays to put in SCSI or SAS instead of SATAII (single disk, non-raid here), IF reliability is the only concern (i.e. NOT i/o performance) during the usual 3 year life time of a server?
Actually, I was pretty amazed by the sata reliability, in the past 3 years the only hdd failure was two sata on a mismatched mobo, which didn't support SATAII (a lot of read/write error, eventually died). Although we have 0% scsi and sas failure.