System uncleanly shut down, ran e2fsck, very slow start & slow desktop
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.
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.
System uncleanly shut down, ran e2fsck, very slow start & slow desktop
I'm running Fedora Core 1 on my laptop, dual booted with Windows XP. Using filesystem ext3. I'm at work and don't have the installation CDs and (foolishly) don't have a copy of my recovery boot disk.
This morning when I started Fedora, a message appeared during startup that the machine has shut down uncleanly. I could swear that I shut it down normally last night, but must not have. I chose to force a system filecheck. The filecheck showed "1.9% non-contiguous" and things seemed to be fixed.
I rebooted, but the startup the system takes a long time to start the system logger, NFS statd, cups, sendmail, and sm-client. It takes about 3 to 5 minutes to start each of those processes, and it now takes about 25 minutes total to boot to the screen for user login. I could (and really should) shut down sendmail and sm-client, as I do not need them, but I believe I need at least NFS & cups (sometimes) to run. Once I logged in and started KDE, it was so slow that it was unusable.
I spent the morning searching the Web & Usenet and found recommendations (including "Fedora Core 1-Newbie Help Please" and "Unclean shutdown from power failure... filesystem check errors" from this forum) for running e2fsck on the drive/partition. I had no luck trying to do that initially, since it's not a good idea to run e2fsck on a mounted drive and I couldn't unmount it properly or mount it in read-only mode. I booted up Knoppix and ran e2fsck on my unmounted partition and got the following:
207812 inodes used (27%)
3905 non-contiguous inodes (1.9%)
# of inodes with ind/dind/tind blocks:
10713/67/0
1152985 blocks used (75%)
0 bad blocks
0 large files
I rebooted into Fedora and it is still slow in starting the processes I listed above.
I'm faily new to all of this, but it would appear to me that it's not a filesystem problem, or at least not a problem that I know of/understand. I attempted to search for mor information, but am not sure where to go from here or what I should even be searching for. I would appreciate any help or even a nudge in the right direction. Thank you.
brahthepoet: might be config issue? check all ur system and my favorite;http://tldp.org/HOWTO/HOWTO-INDEX sections 4.1.4 +4.2.1. hopefully it in there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.