i want to change my server to a intel d510mo withoutchanging the installation.The old nstallation runs on a centos 5.4 asus amd board witha sata raid, sata-sil adapter in no raid modus.and that is the problem.i boot the centos on the intel board, and only the sata-sil module is loaded, so noata drive is found.How can i change this? udev? i disabled the scsi-hostadapter in modprobe.conf, but no
View 1 RepliesI make upgrade from CentOS 5.4 to CentOS 5.5. Architecture is historical i386. On first boot my system was freezed by disabled earlier but not removed manualy writed xdm service. I disable it. But not found network. I see hardware address of card fe:ff:ff:ff:ff:ff. This address is not normal. But how to restore eeprom of this network adapter?
I don't think its trouble of new CentOS. I think this is random incident.Configuration of computer is Intel D510MO motherboard with integrated atom processor and realtek 8111dl nic. I know some trics about fix mac address in centos, but how to fix this address in bios?
The situation: computer based on Asus P6T motherboard. Two RAIDS:
- 'boot', on motherboard built-in RAID controller (CentOS 5.5 installed on this RAID)
- 'data' on 3dware RAID card
At one moment a CPU fan fails and the system halts. After the fan is replaced, BIOS informs it's reset and all the inner controller data are forgotten. After I switch it to 'RAID' mode, it remembers it was a mirror raid (RAID 1) installed, but the file system on it is completely trashed.
The 'data' RAID run by external controller isn't affected by the system failure. Three questions:
- is it worth trying to install OS on the rebuilt 'boot' RAID once again? Looks like if BIOS settings are lost for some reason, there's chance of completely losing RAID data
- has someone encountered similar problem with built-in RAID nd was it possible to recover data?
- will the software RAID be worth creating instead of using hardware RAID to replace the 'boot' drive?
I've installed from the CD the Centos version 5.5. When I try to connect to Internet I can't because I received some errors. I've the Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller also a wireless slot (I've the wireless card DWL-G650+) When I turn on the pc and I go to "Ethernet Device", I see set: peth0 (Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) ETHERNET CONTROLLER) and also set "Bind to MAC address": fe:ff:ff:ff:ff:ff I've set manually the IP address (I'm under router). Status is "Active" but can't go on the Net. When I change to "eth0 (Intel EtherExpress/100 driver)...sometimes become "Active" an other times said that the MAC address is different or to check the cable because can't find the IP. What can I do?
View 5 Replies View RelatedI have an intel DP35DP motherboard - ICH9 southbridge - set to AHCI mode. Working fine under 5.2. Yesterday I updated to centos 5.3, and got kernel 2.6.18-128.1.16 and now it can't boot. It hangs trying to read sata1 with DRDY errors and exceptions.So then I installed 5.3 from a DVD onto a new drive, and got kernel 2.6.18-128. This worked, most of the time, but occasionally gave me this error. I then updated my BIOS, and the error went away.Then I updated this new working drive to the latest kernel (yum update again) and got kernel 2.6.18-128.1.16, and now it wont boot again, with the same message.
ata1: failed to read log page 10h (errno=-5)
ata1.00 exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: cmd 60/08:00:61:4b:38/00:00:3a:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1.00: revalidation failed (errno=-2)
ata1.00: revalidation failed (errno=-2)
[Code]....
I've a Centos 5.1 server on S5000vsa Intel board with 6 bay HD in raid 1 mode (2 HD), and working fine until I've decide to make a yum update. Today the Centos is 5.4 but seems necesssary to upgrade the megasr driver for the raid function (i.e. , is not possible to contact the raid firmware trought Web Console 2). I've download the last megasr driver from Intel and I follow the instruction to upgrade the driver with s.o. installed, but when I start the server and choose via grub the new img boot file, the display show :
megasr.ko invalid module format -1 and stop. The linux version is the same in the machine (uname -a) and from the driver (2.6.18-164.9.1.el5). Another question : in Intel instruction spoken about megasr.o , but on img file I found a megasr.ko . I think instructions referre to old linux 2.4
I installed centos 5.1 in my system, it installed perfectly, but when I am trying to install centos 5.2 then it is not let me install.
My system has 220 SATA HardDisk Intel Core 2 Duo 4 GB RAM Intel Desktop Board DG41TY when I try to install centos 5.2, it show me menu bar After hit enter key to install centos 5.2, it show me loading usb drive and then showing some strange font. System is hang after this Can you please tell how I install centos 5.2
I have installed ddclient for use with dyndns.org.
I can manually run it from the prompt with /etc/rc.d/init.d/ddclient start
and can verify that it works by checking that my IP has succesfully been changed at dyndns.
When I reboot though, during the startup, I get the following:
Starting ddclient: /bin/bash: ddclient: command not found [FAILED]
I am very new to Linux, so I am not sure what or where I should be looking to solve the problem. It seems to me that it must be looking in the wrong spot for ddclient, but I don't know what to check or change to point it at the right place.
ntpd startup fails during boot.Does startup just fine manually from command line once it's booted though. Any suggestions what I might adjust?
View 2 Replies View RelatedI'm running a fresh install on an intel i7 system on an asus p6t deluxe v2 motherboard with the onboard NIC (Marvell Technology pci-e). I know the NIC is working as when I boot into the onboard OS that Asus provides (Asus Express Gate SSD)I have a working net connection.Booting up CentOS hangs at determining IP information for eth0 and eventually fails with the following error:PING xxx.170.30.1 from xxx.170.31.231 eth0: 56(84) bytes of data---xxx.170.30.1 ping statistics ---4 packets transmitted, o received, +3 errors, 100% packet loss, time 2999ms, pipe 3 failed.
RTNETLINK answers: file exists.
RTNETLINK answers: file exists.
RTNETLINK answers: file exists.
[code]....
I'm trying to install a dual booting machine with OpenSUSE v11.1 32bit and CentOS v5.2 64bit. I installed OpenSUSE first and allowed it to install and configure grub in the MBR and after that I wanted to proceed with CentOS v5.2. The installation went fine with two notable exceptions:- when I had to configure grub installation parameters, CentOS offered me only 2 solutions: either install it on the MBR of the first hard disk or not installing it at all. Other distributions are more flexible allowing you to install it in the boot sector of the root partition for example. Because I didn't want to ruin the existent grub onfiguration, I reluctantly accepted not to install it for CentOS assuming that I could manually configure the entry later in grub's menu.lst file.
- when I was presented with the options for software components installation, I've clicked on virtualization category/function because I intend to use the machine as a VMware host. There was no guidance on screen at that point and I blindly assumed that by choosing the virtualization function I would get necessary tools and drivers that will help me further on. It seems that this was a wrong move as you can see it below.
After completing the installation, I tried to search for a template or guiding on how the menu entry in menu.lst should look like but the grub directory was empty, not surprisingly because I've told CentOS earlier not to install it. Using the files in the /boot directory from the CentOS installation I tried to improvise a menu entry but it's not working. The boot stops with famous Error 13: Invalid or unsupported executable format. Using the file command to check what kind of files I'm trying to load as kernels I'm getting :
marte:~ # file /mnt/vmlinuz-2.6.18-92.el5xen
/mnt/vmlinuz-2.6.18-92.el5xen: gzip compressed data, from Unix, last modified: Tue Jun 10 19:20:51 2008, max compression
[code]....
I am trying to install Centos 5.6 on a motherboard with a built in Marvel 88SE61xx drive controller.NO drive arrays are configured using the Marvel BIOS configuration utility.During the install CENTOS displays loading MARVEL_PATA driver and it waits and waits and waits.Looking on one of the system message screens I get the following types of messages:qc timeoutfailed to identifyI/O errorLink is slow to respondSRST failed errno=16ata4: reset failed - giving upAny ideas as to how to get CENTOS to recognize the drives connected to the motherboard Marvell controller on a NON-RAID configuration?
View 1 Replies View RelatedI got a crash on intel machine running intel cpu (CENTOS 5)I would like to know if i can move hdd to new machine with amd cpu? 3 hdd (raid 0 on 2 of them)system is on hdd without raid.
View 1 Replies View RelatedI am trying to run though the qmailrocks setup on a centos 5.5 and I am running into an issue when trying to telnet to port 25:
telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
Connection closed by foreign host.
Everything else seems to be working (telnet to 110), and I turned off the firewall entirely, but I still cannot telnet to port 25. I also get a blank error within squirrelmail when attempting to send mail out (ERROR:Message not sent. Server replied: ). I apologize for not going directly to the qmailrocks forum, but they are currently closed down (due to lack of funds). I also am a newbie, so I apologize for the lack of needed information. If anyone has any ideas, please let me know what information you would need.
I have a Dell precision 380 (system specs can be found here: [URL]. My system is set-up in dual boot configuration with Windows Xp x64 on one side of my HD and CentOS 5.3 (64bit) on the other. My system came with 2Gb (2 x 1Gb) of RAM and I recently wanted to upgrade. I bought 2 x 2Gb ELIXER DDR2 667Mhz RAM. I carefully added the new sticks to my motherboard, booted up windows via bios which noticed the new RAM was present. All seemed well.
However, on rebooting the system and entering the CentOS boot phase, after the boot phase (eg starting program... [ok] etc) but before the login screen my screen goes black / blank. My system has an ATI FireGL v3100 graphics card, I checked out the technical info on this and it should be ok on 64 bit linux. (See: [URL])
[Code]....
It seemed that it would be simple enough: take the 'f' option in the expert menu of fdisk to put partitions in order after a gap had been created by a deleted partition and then make corresponding changes in /boot/grub/grub.conf because the root partition was shifted.
Well, it didn't work out that way. No matter what I try, I either see the error 15 at Stage1.5 or the error 28, which is even stranger (file does not fit into memory). All this before I even see a grub menu. It just does not get that far.
Does anyone want to take as stab at guessing what might have happened here and whether I have a chance at recovering without having to reinstall? I can provide concrete data, if anyone would be kind to give it a try. Hoping that this is a known problem and something can be guessed from what I stated here but I can be as specific as needed, just don't want to generate noise if there are no takers.
The server comes up after rebooting and after setting the hostname it starts setting up logical volume management. It says that 2 logical volume(s) in volume group "VolGroupOO" now active But then it starts to check the file system and errors with fsck.ext3: Device or resource busy while trying to open /dev/sdb1 [failed]
***An error occured during the file system check
***Droppping you to a shell, the system will reboot when you leave the shell
Give root password for maintenace
After I log in with the root I get the message mesg: error tty device is not owned by group 'tty' Can the forum tell me how to troubleshoot this issue so I can boot back up again? I have 2 harddrives in this server and only 1 drive was detected when I first installed CentOS. The error first appeared when I mounted the 2nd drive at the mount point /UserGeneratedData. drive was formatted with ext3 before mounting and did not have any data on it I don't want any software RAID if thats what seems to be going on with "VolGroup00"
I have a Sony Vaio PCG-5A1N (built for Japan) which has a malfunctioning CD-ROM. The bios doesn't support USB external CD-Drives and it doesn't have any USB boot either.The only method, I am left to work with is the PXE boot. I have finally setup a PXEBOOT on another CentOS server and everything works fine all the way to choosing language etc....but after it grabs images/stage2.img this is what it gives me:
loader received SIGSEGV! Backtrace:
[0x8048cf4]
[0x300420][code]...
Is this caused by the different version numbers? Is lvm2-cluster going to be updated soon?
[root@localhost ~]# yum install lvm2-cluster
Loaded plugins: dellsysidplugin, fastestmirror
Loading mirror speeds from cached hostfile
[code].....
I just upgraded by box from Fedora Core 9 to Centos 5.2. Finally!I have a 500GB SATA drive, it's partitioned into three equal size slices, hda1 through 3. The old Fedora was on hda1, I installed the new Centos on hda3. I instructed the installer to write the MBR to /dev/hda, not /dev/hda3. Fdisk says I have sector 0 unused.First, the system wouldn't boot - it just looped through the BIOS, rebooting over and over again. The BIOS sees the disk, but it never loaded Grub. I tried re-running grub-install /dev/hda, and not I get a Grub Error 17 after stage 1.5 loads.
I can boot from rescue OK, the grub.conf man menu.lst look fine, it's pointing to "root (hd0,2)". It's either the BIOS that can't find the MBR, or the MBR can't find Grub.When I looked at the disk with fdisk after the install, hda1 was still marked bootable, hda3 was not, so I swapped bootable flags but that has not made a difference. I also appended the new grub to the old grub thinking I could get the MBR (if it is there) to load the old grub and thence find the new Centos, but that didn't work either.Mobo is an old Shuttle AK35.Any ideas? Did I mess up by not telling the system to put the MBR on /dev/hda3? Is there a way to fix this without reinstalling?
I have successfully installed CentOS 5.4, and after choosing it from the GRUB menu, I am getting the following error message:1706-Smart Array Controller Extended BIOS Data Area Memory Corrupted. Int 13h BIOS Cannot Continue - System Halted.I'm using two SAS disks that came along with the server, left the default RAID configuration (1+0) on a P410 controller
View 5 Replies View RelatedIve installed centos freebsd and mandriva but i want to manage grub from my centos and y create successfully a boot load for freebds. But for mandriva it just doesnt work... so how can a create a boot load entry for mandriva from grub centos?
View 1 Replies View Related3 partitions (in order): Windows 7, CentOS and shared data partition.
I need to increase the size of the Windows 7 partition (c:windowswinsxs seems to be something not easily remedied).
GParted didn't work in moving things around (bad sector) so I wiped out its partition (# 2 out of 3) and I was able to increase the size of the Windows 7 partition (I can reinstall CentOS easily and not much work lost).
Except ... no more grub menu (unsurprising). This incantation does allow me to boot into Windows 7.
Is there any way of rebuilding the grub menu short of reinstalling CentOS (5.5)?
I have a laptop that came with Windows Vista (64-bit) installed. I created a new partition and installed XP (also 64-bit) alongside it.Last night I shrunk my XP partition and created another new partition and installed Linux (CentOS 64-bit) on it. I made an error in judgment and didn't allocate enough space, so I need about 10 more gigs for the Linux partition. It boots up and runs, but I need about 10 more gigs of storage for the files I want to keep on the partition (and yes, they have to be on the partition, I definitely need to know how to do this, not a workaround)I went into Vista and shrunk the XP partition by 10 gigs, so now I have 10 gigs of free, non-partitioned space.
As it stands, when I start up the computer I get the GRUB boot loader. I can boot my Linux install or choose "Other" and be taken to the Vista boot loader. From there I can choose XP or Vista to boot.So, my question is... what is the best way to append the 10 gigs of free space to the Linux partition? Is this something I should do inside of Linux? I have the option to do it in Vista, but the partition shows up as "healthy" but without a file system type.I just don't want to screw up the boot loader, partitions or anything else.This isn't my area of expertise, so if anyone could give me a good suggestion or solid answer
have all ways been hiding in the background read not say a thinglets start well i look after 2 dell poweredge 2650 with 12 gig ram installed servers has been running fine onwell i though it was time to upgrade to 5 all went fine till reboot Memory for crash kernel (0x to 0x) not within permissible range ! well what i have been reading this is the norm for now What is mean by ignore it? LoLwell so i did the system keeps boot till i get to this linesbin/mingetty: /sbin/mingetty: cannot execute binary file alot, and it shows. INIT: Id "5" respawning too fast: disabled for 5 minutes ...so maybe its a memory issue so took 8 gig out left 4 in the system now it reboot alls good with only 4 gig of ram installed so is there a way to fix it to use all the ram can i get the system boot on 4 gig and then add the 8gig later on
View 7 Replies View RelatedI am trying to install CentOS 5.2 on an HP rp5700 desktop unit. These units were originally sold as a Point of Sales unit I believe, but HP also markets it as a high life cycle server for SMB market.I tried to load CentOS on this unit via CD (created from downloaded ISO of course). It presents the initial CentOS banner page and waits for the obligatory "enter" to continue. It begins the boot process up to discovering the PCI stuff and just locks up, no response. I have to power down to restart.Since this does not even get to the point of installing. I am at a loss what to do next. Has anyone had a similar issue with other PCs.The boot stops at the lineACPI: PCI Root Bridge [PCI0] (0000:00)
View 3 Replies View RelatedI've Got one Problem with My Computer soon after success installation of when the boot-loader ask me to choose OS at CENTOS 5.4, multi boot boot-loader if i choose windows then computer tries to boot windows but fail and give the error message that there is a problem on reading the hard disk, But when i restart it and start with LINUX then computer start successful with no error message, now i do not know what to do cause i need to use Windows and all my programs are in windows..
View 1 Replies View RelatedI had a sata drive go down on my software raid array a couple days ago..After replacing the defective drive, I rebuilt it using fdisk to set partitions and mdadm to add the drive back into the raid array.After getting md2 to mount to /mnt I copied the /mnt/etc/fstab and /mnt/etc/mdadm.conf to the /etc directory and rebooted..When I boot, my /dev/md2 partition is not mounting to / It is not loading all of the services at boot time it should.. the size of /dev/md2 on / is even wrong.. it should be about 1.3TBwhen I manually mount /dev/md2 to /mnt I can access all of my data, through /mnt/var/www/vhosts and so on.. I am at a loss, why is the machine booting to this craziness?All of my data, that I know of can be accessed when md2 is mounted to /mnt[root@ESS000272 etc]# cat mdadm.conf
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
[code]....
How can I create/boot CentOs 5.3 ram image?I'm looking to create a CentOs ram image that once booted will not access the hard drive.
View 3 Replies View RelatedI had Windows XP Pro 32 bit and CentOS 5.4 installed on my Dell M6400 laptop and life was wonderful. Until I had to reinstall Windows. In the process, I reformated the C: partition of the drive where the Windows operating system was installed. I was careful NOT to reformat anything else. Now I cannot boot CentOS. The drive that has both the Windows and CentOS still shows the same partitions as were there before I reinstalled Windows, namely:
NTFS (C:) 171.82 GB
/boot 102 MB
(F:) 60.96 GB
is where my CentOS partition has all of my linux data and apps. I assume /boot should be the boot partition for CentOS I use Acronis OS Selector to show the partitions to boot. Now CentOS doesn't show as an option even if I go through the process of trying to detect a CentOS boot partition using OS Selector. I have researched this in the forums but have not found anything that was of help. There was a thread from someone who had trouble booting Ubuntu on a system with Windows Vista and CentOS but I did not see anything there that looked like it would help in my situation.