LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-29-2005, 08:52 PM   #1
tgo
Member
 
Registered: Dec 2004
Posts: 125

Rep: Reputation: 15
strange problem


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?
 
Old 03-29-2005, 10:11 PM   #2
onelung02
Member
 
Registered: Oct 2003
Location: utah
Distribution: Slackware 10.0, Gentoo 2006.0
Posts: 289

Rep: Reputation: 30
Maybe a post with the exact errors would better help to remedy the situation.

-onelung
 
Old 03-30-2005, 07:54 PM   #3
mcd
Member
 
Registered: Aug 2003
Location: Denver, CO
Distribution: CentOS, Debian
Posts: 825

Rep: Reputation: 33
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.
 
Old 03-31-2005, 04:45 PM   #4
tgo
Member
 
Registered: Dec 2004
Posts: 125

Original Poster
Rep: Reputation: 15
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
 
Old 03-31-2005, 04:56 PM   #5
chbin
Member
 
Registered: Mar 2005
Distribution: slackware-current
Posts: 379

Rep: Reputation: 31
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.
 
Old 03-31-2005, 04:57 PM   #6
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
any chance your partition is ( nearly ) full ?

egag
 
Old 03-31-2005, 05:01 PM   #7
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,180

Rep: Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377
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.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
strange, strange alsa problem: sound is grainy/pixellated? fenderman11111 Linux - Software 1 11-01-2004 05:16 PM
strange problem :) salmanucit Linux - Software 1 07-23-2004 06:47 PM
wx-config problem strange problem plz help glacier1985 Linux - Software 4 07-26-2003 05:20 PM
A strange problem... lokee Linux - Software 1 03-30-2003 09:43 AM
Very Strange Problem tengj6 Linux - Networking 3 03-06-2002 08:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration