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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Have a volume that i'm running e2fsck on and it keeps restarting, finding more stuff, restarting, over and over. it hasn't made it past Pass 1 yet.
I'm assuming after every pass its in better shape than it was the previous one. Is there a way to have the server start up and not force a check on it and mount it, even though it will probably say its still dirty?
Do you have a forcefsck on your root partition? If so, remove it. Also, you could comment out the e2fsck line in /etc/rc, if it is there. However I do recommend not doing this....
I think you are deep into the brown smelly stuff . . . e2fsck makes great big waves in that as it passes by :-/.
Boot on an installation disk, if you want my advice, and have a look from there. You can do run e2fsck from there. I would start by running badblocks
badblocks -p 1 /dev/whatever_It_Is
You can safely try
mount -o ro /dev/whatever_It_Is /mnt
ls /mnt/lost+found
That should show you an empty directory. I bet it won't. If it picked up a lot, run another pass.
Then try e2fsck. Your disk sounds snookered. get the data backed up - never mind reinstalling.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.