Linux - NewbieThis Linux forum is 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!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you 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.
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.
First time posting here so be gentle. I'm very very new when it comes to linux but I'm handy with google so normally I can weasel my way out of any issue I run into. I've been working on this problem all day and I haven't been able to come up with a solution, so I figured I'd leave it to the professionals to solve. Here's my problem:
Reading all physical volumes. This may take a while...0
Found volume group "VolGroup_ID_1176" using metadata type lvm2
3 logical volume(s) in volume group "VolGroup_ID_1176" now active
mount: error mounting/dev/root on /sysroot as ext3: Device or resource busy
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Let me know which other files you need to see in order to get a better grasp on the configuration of my system. Like I said before, super noob here.
Did you happen to change the boot volume name? Try booting with the cd and select boot from hard drive. See if it boots then. If it does you need to recompile and new kernel and install it. What kernel is it using?
I didn't change the boot volume name, but the converter changed the configuration automatically so /boot is located on sda1 and / is on sdb1. On the old physical machine the configuration was one device (sda) with /boot on sda3. Willing to bet this is where the problem lies, either this or the LVM config.
Originally Posted by AuroraZero
Try booting with the cd and select boot from hard drive. See if it boots then.
You'll have to be a bit more specific, how do I boot from the hard drive after booting from the cd?
Originally Posted by AuroraZero
If it does you need to recompile and new kernel and install it. What kernel is it using?
Should be an option when the disc runs to boot from HD instead of the Disc. If the program did not change the boot volume correctly there is the problem. The machine is using the /boot on /dev/sda3 to boot the machine and when it tries to mount on that drive it can't because you are using it to boot off. That is why you are getting the error device or resource busy because it is using it to boot from.
I am not the most familiar with the LVM config but I would assume you could change the mount point for /sysroot from someplace within its config options. I would change the mount point to /dev/sdb and see if it will mount the volume there and continue to boot or create a new partition to mount /sysroot only into.