Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum

Sparkylinux gameover no longer boots up

Started by ark781, August 15, 2018, 12:52:55 AM

Previous topic - Next topic


This is the following that comes up:

(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires manual fsck

Then I typed 'exec fsck' this was the reply:

/dev/sda1 contains filesystem with errors, check forced.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found

What do I do from here?


Have you looked at

man fsck is not the easiest to read, but will have solid info. 

search engines

old but quote below is wise
QuoteWhich makes sense as common knowledge tells us that running fsck on a mounted file system will most likely do more damage to it.
The best option

Your best option is simply to boot into another Linux, be it on a different partition, a USB drive or a CD and run fsck manually on the faulty partition, which can easily be unmounted if necessary because no OS is using it

So, on another machine download a rescue iso, Sparky's or any other one.   Put it onto a usb.  Read up and see if anyone else replies. 

And think over whether the probable cause is in the hard drive or something that you did. 
"smartctl" can give you info as to the overall health of you hard drives.  "man smartctl"  would give you the proper flags. 

root@raunes:~# smartctl /dev/sda -H
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.14.0-0.bpo.3-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,

SMART overall-health self-assessment test result: PASSED

smartctl has to be run as root (or in sudo) .  It might not work for you in grub rescue mode, as it is your /root that is affected. It is a gentle test to see if you might need a new drive.

peace out, Mark

Search forum for "More info easier via inxi"    If requested -  no inxi, no help for you by  me.

View the most recent posts on the forum