i'm aiding and abetting fsck on boot not doing a thing for me
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.
ok ... so i reboot the system because i have successfully repaired my file system, eh? no. this is classic sisyphus. i tried umount and fsck and it comes back saying the disk is clean. everytime i reboot, the fsck "cannot continue" comes back like i laid it out for you (above).
i'm not averse to getting dirt under my fingernails here, but this fscking in circles thing is getting me down. i'm inclined to remove that whole fsck check line from that initsys file where it's hiding out.
Ok, I'm not familiar with thiz linux at all. In fact, I've only HEARD of it... Anyway, I'll make a couple suggestions (in other words, use at your own risk... )
What I know of fsck is, first and foremost, it's NOT supposed to be run on a mounted filesystem. That appears to be your problem:
Checking root filesystem
/dev/hda2 is mounted. e2fsck: Cannot continue aborting.
So, my first thought would be that maybe the installed boot scripts are doing things out of order. That is, perhaps they're mounting the partitions before deciding whether to run fsck. Or perhaps they intentionally mounted them, but forgot to unmount them before running fsck.
I don't know. Like I said, that would be my gut reaction.
If it works just like you want, then great! But be careful, it looks like that command will make your root filesystem read-only all the time. That might not be what you want. Then again, there may be another command in the scripts to remount it read-write later. let me know if it's good as-is or if we need to work on it some more.
as far as i can tell (and i been runnin' linux for about 5 minutes)it's good as it is ... the /etc/rc.d/rc.sysinit script does a little shuck and jive a further down and announces it's mounting the root fs as "rw" ...
perhaps i'll come back crying in five weeks when the fs is corrupted beyond belief, but the fsck with it (talkin' 'bout the rootfs here, son) mounted "ro" comes back clean.
i guess i'll walk tall 'til i get kicked where it counts, eh?