Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Now I got this error fixed by simply switching around my boot order of my hard disks in my BIOS.
I have had this error on two occasions it seems to come from booting from the harddrive that doesnt contain the boot loader and or the MBR being corrupted on the first hard drive.
What I wanted to ask here is that the computer i just recovered from this on is a in house server never has anything hooked to it mainly serves repositories for my development. I sent it down for reboot and upon coming back up this was the error.
Could anyone give me some insight as to why this would happen out of the blue like this.
Well to be honest that is all the information the OS will print. I have seen threads like this before where the helpee catches flak for a incomplete error report but that is the first thing that displays on the screen when it happens. Though all hard disks appear to be in working order in this case it could have been caused by an unexpected shutdown that some how corrupted the MBR on the first harddrive. switching to the harddrive with the root operating system allowed the system to boot.