Error Mounting /dev/root Centos
Contents |
existing CentOS5 system to run with a new motherboard Issues related to hardware problems Post Reply Print view Search Advanced search 6 posts • Page 1 of 1 tsm22 Posts: 2 Joined: 2012/12/13 could not find filesystem /dev/root redhat 18:21:37 [SOLVED] Getting existing CentOS5 system to run with a new m Quote switchroot mount failed no such file or directory redhat Postby tsm22 » 2012/12/13 18:34:42 Hello,We have a CentOS 5 server running a wiki and the motherboard has recently given up, setuproot: error mounting /proc: no such file or directory the board has been replaced but now the OS will not boot. The following error reports on booting;'Red Hat nash version 5.1.19.6 startingReading all physical volumesNo volume groups foundVolume group "VolGroup00" not foundUnable to no fstab.sys mounting internal defaults centos access resume device (/dev/VolGroup00/LogVol01)mount: could not find filesystem '/dev/root'setuproot: moving /dev failed no such filesetuproot: error mounting /proc: no such filesetuproot: error mounting /sys: no such fileswitchroot: mount failed: no such fileKernel panic - not syncing: attempted to kill init! 'The disk seems to be partitioned into sda1 and sda2, sda 1 contains grub and what look like kernels? (used rescue disc to browse the file system)I understand
Unable To Access Resume Device (/dev/volgroup00/logvol01)
that having changed the hardware various parts of the OS need updating, but I am not sure what and how.Thanks for any help. Top gerald_clark Posts: 10594 Joined: 2005/08/05 15:19:54 Location: Northern Illinois, USA Re: Getting existing CentOS5 system to run with a new motherboard Quote Postby gerald_clark » 2012/12/13 21:16:58 The hd controller on the new motherboard is not supported by the drivers in the initrd. Boot the installation DVD in rescue mode.Follow the onscreen instructions to chroot to the root filesystem on the HD.Run mkinitrd for the kernel installed in the /boot partition. Top AlanBartlett Forum Moderator Posts: 9296 Joined: 2007/10/22 11:30:09 Location: ~/Earth/UK/England/Suffolk Contact: Contact AlanBartlett Website Re: Getting existing CentOS5 system to run with a new motherboard Quote Postby AlanBartlett » 2012/12/14 04:34:43 To expand on Gerald's precise answer, I will just mention that there is an appropriate page in the CentOS wiki --Creating a New Initial RAM Disk Top tsm22 Posts: 2 Joined: 2012/12/13 18:21:37 Re: Getting existing CentOS5 system to run with a new motherboard Quote Postby tsm22 » 2012/12/14 17:29:51 Thanks for the help, all running again now. Top AlanBartlett Forum Moderator Posts: 9296 Joined: 2007/10/22 11:30:09 Location: ~/Earth/UK/England/Suffolk Contact: Contact AlanBartlett Website Re: [SOLV
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org >
Mkinitrd
Fedora 23/24 > Using Fedora mount error - error mounting /dev/root on sysroot as ext3 : invalid argument FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red http://www.centos.org/forums/viewtopic.php?t=24681 Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 1st January 2009, 02:17 AM marko Offline Registered User Join Date: Jun 2004 Location: Laurel, MD USA Posts: 6,942 mount error - error mounting /dev/root on sysroot as ext3 : invalid argument http://forums.fedoraforum.org/showthread.php?t=209411 After updating to the current 2.6.27.9-159.fc10.x86_64 kernel I can't boot it due to getting a mount error: Quote: mount: error mounting /dev/root on sysroot as ext3 : invalid argument Note this PC is not using LVM and I'm using AHCI I've tried several things I've found on google but none worked: 1) make a file /etc/sysconfig/mkinitrd containing: Code: MODULES="scsi_wait_scan" and run Code: mkinitrd -v -f /boot/initrd-2.6.27.9-159.fc10.x86_64.img 2.6.27.9-159.fc10.x86_64 2) added to the grub boot line: mod_scsi.scan=sync 3) finally I noticed after trying "2" that I could see a error about the mount argument "norelatime" being invalid, but the mount man page says that's still supported ? I want norelatime to reduce file system writes when I just look at files. Last edited by marko; 1st January 2009 at 02:27 AM. marko View Public Profile Find all posts by marko #2 1st January 2009, 02:41 AM leigh123linux Guest Posts: n/a I think you have the wrong option , it should be relatime Code: # # /etc/fstab # Created by anaconda on Sun Nov 30 01:40:43 2008 # # Accessible filesystems, by referenc
Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie Won't mount /dev/root on /sysroot during http://www.linuxquestions.org/questions/linux-newbie-8/won't-mount-dev-root-on-sysroot-during-boot-907463/ boot... User Name Remember Me? Password Linux - Newbie This Linux forum is http://unix.stackexchange.com/questions/29435/kernel-panic-cant-find-root-filesystem-error-mounting-dev-root for members that are new to Linux. Just starting out and have a question? If it is not in the man pages or the how-to's this is the place! Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you error mounting will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | no such file Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 10-10-2011, 04:13 PM #1 Promo_Sam LQ Newbie Registered: Oct 2011 Location: Orlando Distribution: RHEL Posts: 6 Rep: Won't mount /dev/roo
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Kernel Panic - Can't find root filesystem / error mounting /dev/root up vote 3 down vote favorite From here: http://fedoraproject.org/wiki/Common_kernel_problems#Can.27t_find_root_filesystem_.2F_error_mounting_.2Fdev.2Froot A lot of these bugs end up being a broken initrd due to bugs in mkinitrd. Get the user to attach their initrd for their kernel to the bz, and also their /etc/modprobe.conf, or have them examine the contents themselves if they are capable of that. Picking apart the initrd of a working and failing kernel and doing a diff of the init script can reveal clues. To take apart an initrd, do the following .. mkdir initrd cd initrd/ gzip -dc /boot/initrd-2.6.23-0.104.rc3.fc8.img | cpio -id I wish to understand what exactly is being done here. What has initrd to do with anything? Where are we supposed to create the directory initrd? linux kernel compiling kernel-panic share|improve this question asked Jan 19 '12 at 10:04 Aquarius TheGirl 60031339 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted An initrd (short for “initial RAM drive”) is a filesystem that's mounted when the Linux kernel boots, before the “real” root filesystem. This filesystem is loaded into memory by the bootloader, and remains in memory until