Page 1 of 1

Boot Stalling - Run fsck Manually

PostPosted: June 19th, 2018, 2:57 pm
by llewellen
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: Select all
/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.

Re: Boot Stalling - Run fsck Manually

PostPosted: June 20th, 2018, 9:49 am
by cynwulf
As it's the root fs, you're probably going to need to run fsck from a different OS instance. I suggest a live cd/usb or perhaps the installation media has such functionality?

The bigger problem for you, is the underlying cause. You might want to backup your important file and have a look at the hard disk's SMART data...

Re: Boot Stalling - Run fsck Manually

PostPosted: June 20th, 2018, 4:17 pm
by llewellen
cynwulf wrote:As it's the root fs, you're probably going to need to run fsck from a different OS instance. I suggest a live cd/usb or perhaps the installation media has such functionality?

The bigger problem for you, is the underlying cause. You might want to backup your important file and have a look at the hard disk's SMART data...


Sorry, with my neophyte lack of knowledge, I don't understand (a) how can I work with/edit the existing corrupted files on my hard drive from a live USB ; and (b) how to backup files if I can't boot to get at them.

Re: Boot Stalling - Run fsck Manually

PostPosted: June 21st, 2018, 12:50 am
by Randicus Draco Albus
A live system will let you see the file system on the hard-drive and access the files. Any Linux live CD should work.

Re: Boot Stalling - Run fsck Manually

PostPosted: June 21st, 2018, 1:06 am
by llewellen
Randicus Draco Albus wrote:A live system will let you see the file system on the hard-drive and access the files. Any Linux live CD should work.


Thank you, I don't have one at hand but I will download one this evening and give it a try.