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.
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
[Code]....
I can't boot the 2.6.35-22 kernel, since I get the "Error 16: Inconsistent filesystem structure" every time. However, the previous kernel I have installed, 2.6.32-25, is booting without a problem, so I'm forced to use that until this problem is solved. What can I do?
View 2 Replies View RelatedI have successful tar an existing CentOS 5.2 partition from Fefora10. The idea is to move a working CentOS 5.2 reside in an internal hard drive to a portable hard drive. I know how to edit a stencil in menu.lst to boot the clone CentOS5.2. During boot, I encountered
Red Hat nash version 5.1.19.6
mount: could not find filesystem /dev/root
setuproot: moving /dev failed No such file or directory
setuproot: mounting /proc: No such file or directory
setuproot: mounting /sys: No such file or directory
[Code]...
today I upgraded (yum update) one of my Dell Poweredge Server from 5.2 to 5.3. After rebooting the system first seems to start normal but then the following Error Messages appear:
Apr 5 14:28:26 srv_1 kernel: I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x668000008 ("xfs_trans_read_buf") error 5 buf count 4096
Apr 5 14:28:26 srv_1 kernel: attempt to access beyond end of device
Apr 5 14:28:26 srv_1 kernel: dm-0: rw=0, want=27514634256, limitfs]
[code]....
Booting with a rescue disk and doing a xfs_repair solves the file system Problems but moved a lot of files ( at least /usr/bin and /usr/lib completly) to "lost+found"... I tried the update with a spare 5.2 Server (different Hardware), and ended up with exactly the
same effect and error message. Both systems are running XFS as root File system on an LVM Disk.
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0b.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 0c)
And the Intel one, makes the problems with the new kernel.
I'm not a complete newb, or a seasoned hacker. I can't figure out what's up with this, I keep getting this message when I try to apply updates. [('installing package kernel-2.6.35.12-88.fc14.i686 needs 17MB on the /boot filesystem', (9, '/boot', 16985088L))]
View 6 Replies View RelatedThe server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
# cat /etc/grub.conf
default=0
timeout=20
[code]....
Upgraded from 11.1 to 11.2 using GUI (YaST and Wagon)
Machine stops on boot and says:
fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount, rw /
Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work.
Give root password for login:
I write: mount -n -o remount,rw /
And then reboot with CONTROL-D.
I've decided to give ubuntu another test drive now that I got a bigger and better desktop. I downloaded the latest version of ubuntu, loaded it into my usb stick and booted from it. I then clicked on the install icon on the desktop to start the installation. Everything was going ok, until I came to the partitioning part. I had already (on windows 7) created a separate partition for ubuntu which is 56GB. So I chose "manual partitioning" and selected the ubuntu partition as /home and began the installation.
Everything seemed to have went well, the window suddenly closed and then nothing happened. I waited for 15mins and still nothing happened. I decided to restart and see what happened, but I discovered that I couldn't boot into windows anymore. It said something about intel boot manager cannot find filesystem. So I decided to boot back from the usb and see if I can reinstall ubuntu, I came to the partitioning part and all the drives were gone, I couldn't see anything, it was blank.
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
View 5 Replies View RelatedAfter upgrading and restarting my laptop, The purple splash screen hangs, and the terminal gives this message.
Code:
Also the boot menu does not show (I cannot open the recovery mode)
I am running Fedora 13 in VMWare. I tried doing a software update and I get this error message when tring to install the updated kernel:
Test Transaction Errors: installing package kernel-PAE-2.6.33.6-147.fc13.i686 needs 6MB on the /boot filesystem
how to increase the memory space required for installation.
I did the "yum update" today, the process was doing well but, the follow error appears:
Transaction Check Error:
installing package kernel-PAEdebug-2.6.31.12-174.2.3.fc12.i686 needs 9MB on the /boot filesystem
Look:
Code:
Transaction Summary
==================================
Install 10 Package(s)
Upgrade 33 Package(s)
Remove 1 Package(s)
[code]....
I've upgraded kernel 2.6.27.48-0.2-default to 2.6.27.54-0.1.1 on openSUSE 11.1. Before I tried to upgrade to 2.6.27.48-0.3-default where I encountered the same issue. After reboot it can not find the modules for 2.6.27.48-0.2-default which puzzled me to no end. Now I have found that the /boot which is on separate partition of ext2 type is not mounted. The mount command does not recognize ext2 and xfs anymore.
Clearly the initrd does not have the right modules. Since this is standard zypper up process I would expect this to work without issues since it has worked until the 2.6.27.48-0.2-default kernel without issues. Has something changed with the last 2 kernel versions that requires some extra actions from me and if so what do I have to do.
I compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
View 1 Replies View RelatedIn order to not post into the wrong forum, I am wondering if an issue related to performing a PXE based NFS install can be posted here, or does it belong in the networking forum? Seems that I've seen both, and I've done several searches using parameters/error messages that I'm seeing and can't seem to find a post that relates.
I have results of "./getinfo.sh network", and other necessary config file info ready to post, but want to make certain on correct forum.
I am running yum update and it thinks 2.6.18-128.1.10.el5 is the latest kernel, even though its really 2.6.18-194.3.1.el5
Code:
[localdomain ~]# uname -a
Linux localdomain 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux
[localdomain ~]# yum update kernel
[code]....
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2
2 logical groups in VolGroup00 now active
mount: error mounting /dev/root on /sysroot as ex3t: No such device
setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
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?
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
View 2 Replies View RelatedI just installed a fresh CentOS 5.2 32bit system. I used "The Perfect Server" server document from Howtoforge and went through those steps and then added Webmin administration console. I then tried to install VMware Workstation 6.5 onto the system. I downloaded the latest VMware bundle, ran it and everything went fine. I then try to run vmware and I get the following messages
C header files matching your running kernel were not found
Before youcan run VMware Workstation, several modules must be compiled and loaded into the running kernel
Kernel Headers 2.6.18-92.1.22.el5.centos.plusPAE
Kernel headers for version 2.6.18-92.1.22.el5.centos.plusPAE were not found. If you installed them in non-default path you can..
My laptop threw a wobbly recently (same time as kernel update?) I have got it to find the old kernel, but it still won't boot.It's a 11.3 install, dual-booted with XP. The /boot partition is in the root partition - sda7. Why is it trying to mount sda7 as swap? (not in fstab like that)
View 2 Replies View RelatedI have an Nvidia graphics card,... actually I manage several workstations that run centos and have an nvidia video card. I also have a personal computer with ubuntu and an nvidia network card.
I would like to do a regular automatic update of those Centos workstations. (With a pilot group to test and then a full roll-out). Until oktober 2009 no major difference in automatic updating ubuntu and centos (apart from the differences between apt and yum):
After a kernel upgrade, the systems can not boot into it's Xorg gui, because the nvidia driver must be rebuild (=not recompiled, because this is partially object code, the driver is not opensource).
But from ubuntu 9.10 onwards, the kernel update process checks for the presence of propietary drivers like those of nvidia and does a rebuild on the reboot, so that the system can succesfully boot into the xorg GUI (and gdm or kdm) My question is: Are ther any plans for Centos to do the same, this would relief me from some upgrade hassle for the Centos workstations that I manage. Or does anyone know about a (good) automagic workaround?
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 dual boot Ubuntu 9.10 and Windows XP. I booted into Ubuntu 9.10 and upgraded to 10.4 and upon reboot Ubuntu could not find the boot partition, it reported only /dev. I restarted my pc and and selected Windows and, fortunately, I was able to boot into that OS.
View 1 Replies View RelatedCan't boot after upgrade to 2.6.31-19 kernel. Boot procedure stops on "Mounting root file system..." stage with message:
/init: line 218: syntax error: 0xhda1.
I updated ubuntu and installed the latest linux kernel. I rebooted back into ubuntu, then finished up some work and went to reboot into windows 7. The "starting windows" logo comes up then it blue screens and says "cannot boot %hs missing" (hard to read because it flashed on the screen then reboots).I ran startup recovery but that didnt do anything. I also tried downgrading the kernel but that didnt change anything.
View 6 Replies View RelatedI applied the Kernel update that showed in the updater via the GUI.It now won't boot anymore.Memory for crash kernel (0x0 to 0x0) notwithin permissible range.WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
View 2 Replies View RelatedI'm new to fedora and when I boot from a cd I get the message: could not find kernel image. I currently have windows xp and my motherboard is and ix38 quad gt if that helps.
View 2 Replies View Related