SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have dual booted slack along time and last time i tryed to boot i got a strange error about corrupted file system forced check and it says theres an error and puts me in single user mode
now i installed with the ext2 option and it said there is some error with that and it was trying to boot it as read only so i restarted and and at boot: i mounted the drive as rw and when it got to the part taht errored before it gave me some messagea bout the drive already being rw even though right above it it said it was ro and then i hit enter and it works fine
I looked on the slack disc to see if i could reinstall the system files w/o re installing the whole thing but couldnt find anything
i boot from a floppy and its slack 10.1
is there a way to fix this? has anyone else got this error?
are you still getting an error when you boot normally?
as far as the read-write stuff goes, i believe the root filesystem is mounted read-only while the kernel is loaded into memory and then unmounted and re-mounted read/write. so if you initially mounted it read/write i can understand it complaining when it came to the part where it is supposed to switch from ro to rw that it was already rw. but anyway.
it's possible that there was an error, and that fsck fixed it (when the kernel detects an error it always tries to run fsck, which i gather is what you went to single-user mode for), and that now you can boot normally again. of course, if you still can't boot normally then i'm wrong and you should post exactly how far you get during boot and which errors you get.
well i went through the same steps i did about 10 times which was just normal boot wait for it to error and restart itself and log me in single mode but this time after doing the forced checked it said it was fixed, rebooted itself, and its working normal now
I really have no idea how it fixed itself but it messed up before on at least like 10 or 12 boots but now its fixed thanks for posting the help
Any particular reason your using ext2 file system? What is wrong with using Reiserfs it is far better.
Sound like you ext2 is messed up pretty bad. If you google on the net there is some long complicated process which you can do to try and fix it. To long and complicated for me to tell you here. There are no gaurentees that it will recover all the files either, some may be destroyed and unrecoverable.
posting the output of fsck would be great, also, when you reformatted and installed again, did you do a quick format, or format while checking for bad sectors? It might be a good idea to rerun fsck again, and have it look for any bad sectors, I don't know the exact syntax for that, so do a man fsck It might be that your hard drive is going out on you, which is pretty much the worse case scenario, but I hope thats not the case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.