Upgraded two systems yesterday without problems but now have a strange problem with a third. The upgrade went well I think but the kernel hasn't upgraded. Its installed and grub.conf has it listed as the default but after a reboot ( many times now ) the kernel version is unchanged.
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
I've upgraded from 9.10 to 10.04 and everything works fine but. I use skype (2.1.0.81) a lot and I can make calls and receive them as normal with normal mic/sound levels. When I get a notification the sound is so faint its almost inaudible. Clicking "Test sound" in notifications has the same effect - almost inaudible sounds (I thought they were not working at all until I turned the volume right up).
I tried completely removing and reinstalling skype through synaptic to no avail. All the Sound devices in skype are set to "PulseAudio Server (local)" - there are no other options coming up. "Make a test call" works fine and the skype sounds are all at the expected level. Real calls are fine too, so long as I notice them and respond. "Make a test sound" is silent.
Likewise, testing the event in Notifications plays the sound really quietly. Allocating different sounds makes no difference - the level is still really low so I can't work around the problem that way. Anyone know how I can correct the ringer volume without blowing out my eardrums on an actual call?
Today I upgraded from 10.04 to 10.10 and I notice that the rename function is different from before. Now it select all the filename including the extension while before it select only the filename. How can I fix this problem? It's very uncomfortable rewrite the extension everytime or remove the extension from the selection.
I upgraded from 9.10 to 10.04 without any visible issues. But after a few days system started to behave strange - first it shows the message that gnome-power-manager is not correctly installed on login screen. The it wasn't able to log in even - so I found that problem might be that it shows not enough space on the root partition.This is really strange for me - I do not have any special data there.
See what I have after df command: /dev/sda2 9614148 8618864 506908 95% / none 1024128 360 1023768 1% /dev
I upgraded a linux box from Koala to Lucid, and everything seems ok except at boot I occasionally get an error mounting some partitions. Here is the boot.log:
Code: fsck from util-linux-ng 2.17.2 /dev/sdb1: clean, 316325/17965056 files, 5723474/71844680 blocks udevd[402]: can not read '/etc/udev/rules.d/z80_user.rules' mount: /dev/sdb1 already mounted or /backup busy mount: according to mtab, /dev/sdb1 is mounted on /
I just upgraded my 9.10 on my laptop to 10.04. I seems to have gone well except for one annoying problem. when I boot up I get a large X for the mouse pointer instead of the normal arrow. When I start an application it will not go to full screen and there are no close/minimise/maximise options. Nor can I get to the top or bottom menu bars.
I can cure this on a temporary basis by right-clicking on the desktop and changing the visual effects from none to normal. The problem is that it does not stick. Each time I boot up I have to make this change.
I recently upgraded my Ubuntu from 9.10 to 10.04 and now it's messed up my Windows Vista partition. When I try to load Windows it boots to a strange login menu with low resolution. It then takes me to a screen with options like Repair/Fix, Recovery, Complete Recovery... I'll click Repair and and then it will say No errors found, Shut down, Restart.
I recently reinstalled CentOS, and after a ton of updates, I'm just about finished getting things set up again. However, today I've noticed this really interesting message whenever I run yum. Just for demonstration, I'm going to remove gnome-screensaver, since I prefer the Xscreensaver anyway. This is the complete output, with the strange message highlighted;$ sudo yum remove gnome-screensaverLoaded plugins: fastestmirrorSetting up Remove ProcessResolving DependenciesThere are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
--> Running transaction check ---> Package gnome-screensaver.i386 0:2.16.1-8.el5 set to be erased --> Finished Dependency Resolution
Strange line of text appeared on open gedit page on first use after upgrade from 10.04 t0 10.10. I was reading something and copypasting the odd bit onto a gedit note: left the room, returned to find blank page except for "nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn". Then I saw that it was just the tail-end of a longer line which had stretched the page width to max, and by deleting backwards I arrived beneath my intact notes. The line was "I[my bolding]nnnnnnnnnn...nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnby v9898". I googled v9898. And there's a v9898. com. It provides something for Windows systems.
I am currently seeing strange files in the folder structure on one of my servers * CentOS release 5.5inal)* #1 SMP Tue Jan 4 17:11:58 EET 2011 x86_64 x86_64 x86_64 GNU/LinuxThe files in question are as follows : -rw-r--r-- 1 root root 117 Feb 3 16:57 -z present in too much random directories when i list a file structure even in a directory i have not been in there is such a file in it.Has anyone ever encountered this type of factor and if possible i would like some advice on dealing with the removal of these files and rectifying the settings that are making them / creating them.
I have CentOS 5.5 running as a desktop, on Live USB with persistent overlay. It's been working great since January. However yesterday I noticed something strange. Almost all the binary files, including those under /bin, /sbin, /usr/bin, and /usr/sbin, have been modified, compared to the originals in squashfs.img (I mounted squashfs.img and did a "diff -r" comparison). The timestamps all remain the same, but the sizes of the binary files have been increased by a typical 1 - 3 KB.
The system has never been updated, other than a few minor package installations via yum. It's running behind a firewall with no services except an SSH server on a non-standard port. Checks on log files etc. didn't find anything suspicious, and chkrootkit turned up nothing.
vmware virtual machine, the system is centos 5.4 want to upgrade the kernel 2.6.32. make menuconfig is based on the default. make; make modules_install; make install no problem, reboot the system to choose a new kernel, new kernel can not boot, the following is vastly map, right in the / boot directory, there is no 2.6.32 of the config files, do not know how the matter , in the compilation before I put / boot directory of the original system config files to the source directory cp The following is the contents of the screenshot
I had Windows Vista and CentOS 5 running on my laptop. But when I upgraded to Windows 7, I think that CentOS is erased as now I am not getting the screen asking me which OS to boot. Now it directly boots Windows 7 only. Kindly tell me is the CentOS erased from my system, if not then how do I get it back and use it.
I was checking my server and found a /net directory with nothing visible inside. The mysterious directory is /net and I checked to make sure nothing was mounted to it: [root@mysql /]# mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
I had an odd thing occur after a fresh install of Ubuntu 10.04. I installed Windows 7 on its partition, and all went fine. Then I installed Ubuntu on its partition and everything was as it should be. Then I did the Ubuntu updates and now my boot window looks like this ... I can click on any of the Ubuntu logins and it takes me to the same place.
I did a minimal install of Fedora 13 (i686), added X Window & LXDE groupinstalls, and xorg-x11-fonts-base, switched to level 5 in /etc/inittab.When rebooting, the First Process indeed starts, but any character seems to be replaced with squares. What am I missing ?
I have just upgraded a CentOS 5.2 box to Centos 5.3
I did have a bridged networking setup for Virtualbox which worked well. eth0 was bridged with br0. br0 boot protocol was DHCP and it sent its DHCP_HOSTNAME to the windows DHCP servers.
since the upgrade the br0 does not get an address but the eth0 does. I found that the scripts in /etc/sysconfig/network-scripts/ifcfg-* are getting rewritten.
I figure I may not need to have a bridge any more so I stripped that out to try to get a simple network setup working. I now just have eth0. I edited /etc/sysconfig/network-scripts/ifcfg-eth0 so that it looked like this,
I use Debian Lenny on desktop. On bootup I get this strange message
Code:
Question one: what is hub 2-0:1.0? A utility? A library? A module?
Queston two: what does "enumerate" mean in this context?
Question three: I can't figure out what "port" is meant: a networking port something on the motherboard one of several I/O port/connector/sockets on the back of the computer? (Hope you know what I mean--- you stick USB connectors into them to connect your computer to a USB device, such as a USB mouse.) the one and only networking port/connector/socket on the back of the computer.
Possibly relevant: I sometimes but not always have a USB cable connecting my printer to one of the USB ports/connectors on the back of the computer at boot time. But the message always refers to "port 1", never 2,3,4. due to lack of options for getting on the Net, I use an Actiontek router which demands to be given 192.168.0.1 which would otherwise be taken by my computer, which instead gets 192.168.0.2. (Grasping at straws...)
I recently installed Antix Mepis 8M on Dell Latitude D410 laptop. Everything is fine except that at boot I get the following weird message: pci 0000:00:1e.0: BAR 7: can't allocate I/O resource [0x10000-0xffff]
It doesn't noticeably slow down the boot and everything works fine once running, but I'm curious to know what it might be and whether it could possibly represent trouble in the future.I googled it and found this: http:[url].....But there is no associated solution, and other results are largely reposts of this query.
I want to upgrade kernel to 2.6..36 from 2.6.18 of CentOS 5.5. The make process is successful but prompt "could not find filesystem /dev/boot " after reboot.
Some articles suggest to edit file .config and set CONFIG_SYSFS_DEPRECATED_V2 to 'y' and re-make kernel. However, the problem still stand there after reboot again.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
I 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.
I 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?
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
there is a bug on the quad core B2 opteron cpu there is a beta patch available , but only for for 2.6.24 kernel i am very happy with my centos, and i would upgrade the kernel to try this patch i am new on linux, so i need a precise tutoriral to upgrade and keep the actual configuration of the kernel
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
Ive 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?