fsck died with exit status 6
Yesterday i found that my Debian server didnt present a new temperature graph as it has been doing the past months.
Althouh apache was running, but the "shutdown" and "reboot" wasnt recoginsed by the system, but I could run ssh.
So I did a hard reset, by taking the power away, and back again.
The system halts during the fsck, and I got the status 6 in /var/log/fsck/fsckfs "fsck died with exit status 6".
And it prompts me to log in with root acount or Ctrl-D.
When I do that I can run fsck, it seams to be "exit status 6" at the boot partition.
But this is strange, when I exit this mode, the computer go further in the startup procedure. And I can login as before.
Some how it seems to be stopped at 03.45am or somewhere there in time.
As far as i know, I havnt been doing anything that can be casusing this trouble.
So please, can anyone help me where I should start looking for a solution.
Then boot from an install CD/live cd and fsck the unmounted partitions from there.
I have been readingat the wiki link you suggested.
I have also done some more troubleshooting.
Somewere around this first trouble point (I think it was after the trouble witch fsck err 6) I did a
That is fixed now. And the problem I have now is "update-rc.d"
This is what I know:
I have had a few diffrent troubles. And it seams to be the same fault reason. (but I dont know that for sure in a professional way)
Cron dont start when debian boots up.
Apache dont start when debian boots up.
When I run this:
update-rc.d: warning: cron stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none)
When I start apache2, its works as usual, with no errors. Also when I do "update-rc.d apache2 defaults" it runs with no errors.
So somehow it seams to be the next trouble to solve, to get "update-rc.d" run correctly.
At the links below, it seams to be some trouble that is quite simular to mine.
Is it possible that: when I disconnected the usb-drive, I "created" the fsck error 6" trouble.
And then I ran apt-get update, and upgrade.
By this action it caused me further trouble, the "update-rc.d" trouble?
But when I boxed "#" in /ect/fstab the USB-drive I got the system further running, and then I noticed the trouble that the apt-get upgrade, update give me?
Wow, this were a lots of same info written in diffrent versions in this post.
I might be needing to re-write the "english" in this post... Ill consider that...
|All times are GMT -5. The time now is 07:50 AM.|