fsck caused problems
Hello guys,
I wanted to see how fsck works and execute this command when computer was in ordinary working mode (through terminal from GUI), now I cannot start GUI any more adn I can only login as root (root@(none)). Now when I execute fsck it found and correct errors, but when I try to restart with init 6 I get error message "INIT cannot execute /etc/rc.d/rc", something like that... I thought fsck is supposed to fix things, not to screw them up... :( Also, when I use RESET button, again I can only login as root, GUI (KDE) cannot start and every time I execute fsck -p, I get message /dev/hdb1 (this is where mandrake is installed) contains errors, check forced and ....(0.3% nom-contigous).../... blocks What should I do? |
what is the command you used?
i hope you didnt fsck a rw mounted drive, that can cause problems. |
Quote:
Quote:
|
Well, I did just that... I've run fsck on mounted partition because if I'm not wrong that partition is mounted automatically when GUI (KDE) is started. Now when I start computer I can only see login:
I have tried to umount the same partition and run fsck but every time I restart machine and run fsck it finds and fix problems, but no effect. I have two questions: 1. Is it ok just to type "umount /dev/hdb1" from root directory just to unmount /hdb1, when I type that I don't get any error message, just shell again? 2. Whwn I log in as root, and try to restart computer with init 6 I get error message INIT: cannot execute /etc/rc.d/rc and INIT no more process left in this run level |
remount it read-only
Code:
mount -ro remount /dev/hdb1 if that still craps out, try booting off a cd like knoppix and fsck it from that. |
All times are GMT -5. The time now is 12:06 AM. |