LinuxQuestions.org - Boot Stalling - Manual fsck Required

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Boot Stalling - Manual fsck Required (https://www.linuxquestions.org/questions/debian-26/boot-stalling-manual-fsck-required-4175632238/)

Boot Stalling - Manual fsck Required

Debian-testing with Enlightenment 0.22.1-3 Window Manager

System was operating normally. Powered off. Started the next day and received a repeated Enlightenment pop up saying that there was a problem reading/writing to its .config file. Sorry I didn't think to take a screenshot of that at the time.

Powered off and rebooted. The boot screen displays as normal and the first few lines of the boot sequence run, and then this appears. Obviously, I couldn't take a screenshot so this is hand copied:

Code:

/dev/sda2 contains a file system with errors, check forced.

Inodes that were part of a corrupted orphan linked list found.



/dev/sda2: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

(i.e., without -a or -p options)

fsck exited with status 4

The root filesystem on /dev/sda2 requires a manual fsck



BusyBox v1.27.2 (Debian 1:1.27.2-2) built-in shell (ash)

Enter 'help' for a list of built in commands.

(initramfs)_ <blinking cursor>

How to get through a manual fsck so I can boot and try to figure out what's wrong with Enlightenment? Thank you.

There is probably not a problem with Enlightenment.

You have file system errors. Your problem is that the file system is corrupted in some manner. Needs fixed.

Back your stuff on that partition. Boot to recovery and then run the e2fsck tool.

Code:

$ man e2fsck

I would suggest using just the -p option to start with. You obviously have bad inodes and they should be cleaned up that way.

But your error messages recommend against that so just use -v so it gives you the whole output. Will take awhile.

You could also use the -y option (like -vy) which will be quicker as it will assume you want each thing detected to have an attempted fix done rather than having to OK each one. I prefer to at least start out without the -y option just so you know the extent of the problem.

You can always ctrl + c out of the process and add the -y then and rerun.

@widget: Thank you. "Back your stuff on that partition. " How to? Maybe I should have posted under Newbie Questions :)