Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I've recently had some issues with my file systems. I rebooted [as I do once in a while, despite running Linux], and it booted into a recovery console, as one of my file systems was not clean.
The file system in question is a RAID10 [4x250] setup with an ext3 partition on it. The array builds successfully. The fsck fails with the error message: "The root inode is not a directory". I'm not all that fluent with Linux in general, so I resort to asking questions like this. Is there any way to recover my data ?
My system is a Gigabyte GA-P35-DS3R, e8400, 4GB DDR2 800, XFX 8800GT, everything's at stock speeds [I know, what kind of geek am I ?]. The drives in question are Seagate 250GB SATA IIs. The system boots fine if I remove the array in question from the fstab, but I can't see any way to recover the data on it. I have limited backups [perhaps 60% of the data], but they are not organized, and I'd rather not have to re-organize them again.
The 'clear inode' question was not an option that I have seen. I was instructed to try 'fsck -y' as there are several thousand errors, and this fails [and aborts] on the root inode error. I was looking for perhaps a more robust way to do this, if possible ?
As for routine backups, we've done them in the past, but we seem to keep killing machines, or getting general file system corruptions like this. Not sure the best way around that.