When I rebooted my system running 64-bit Mint 19.1 a console appeared on the screen with the following message :
/dev/sda1 contains a filesystem with errors, check forced.
/dev/sda1 : UNEXPECTED INCONSISTENCY ; run fsck MANUALLY
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
BusyBox v1.272 (Ubunt 1:1 272-2ubuntu 3.2) built-in shell (ash)
Enter'help' for a list of built-in commands.
(initramfs) _ [prompt]
Where do I go from here (hope I'm not forced to reinstall, as it's been a while since I performed a manual backup)....
Henri
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason:Topic automatically closed 6 months after creation. New replies are no longer allowed.
I would start by following the instructions in the console:
/dev/sda1 : UNEXPECTED INCONSISTENCY ; run fsck MANUALLY
Open a terminal and run fsck and post the results in your reply.
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
Larry78723 wrote: ⤴Sat Apr 13, 2019 7:04 am
I would start by following the instructions in the console:
/dev/sda1 : UNEXPECTED INCONSISTENCY ; run fsck MANUALLY
Open a terminal and run fsck and post the results in your reply.
Thanks for your speedy reply, Larry, ! That's precisely my problem - as the system refuses to boot, I can't access a terminal. When I try running fsck after the (initrams) prompt in the console, the information I posted above, i e, that /dev/sda1 contains a file with errors and that I should run fsck MANUALLY, appears again. The point is that under the circumstances, I've been unable to find any way to run fsck manually....
Henri
Last edited by mhenriday on Sat Apr 13, 2019 8:58 am, edited 2 times in total.
Larry78723 wrote: ⤴Sat Apr 13, 2019 7:04 am
I would start by following the instructions in the console:
/dev/sda1 : UNEXPECTED INCONSISTENCY ; run fsck MANUALLY
Open a terminal and run fsck and post the results in your reply.
+1
And also I would grab a usb drive and try to backup whatever you can from that drive.
Boot with a live usb and run fsck. What I mean by live usb is the linux mint disk you used to install.
mhenriday wrote: ⤴Sat Apr 13, 2019 7:23 am
I've been unable to find any way to run fsck manually....
Start a live session and use lsblk to identify the correct drive, then do the fsck from there.
Thanks for your reply, catweazel ; now we\re getting somewhere ! I had simply forgotten the option of booting from a flash drive (which is not without its problems, as the keyboard is then attuned to English, rather than the Swedish I generally use ; thus I find myself frequently typing the wrong characters). When I run lsblk in a terminal, the following is displayed :
lsblk_20019-04-13_2-32-11.png (18.18 KiB) Viewed 2648 times
But how do I then run fsck «from there» (which I interpret to mean from /sda1). If I simply enter fsck after the prompt, I get :
fsck-kommando_2019-04-13_12-48-48.png (3.66 KiB) Viewed 2648 times
mhenriday wrote: ⤴Sat Apr 13, 2019 8:57 am
But how do I then run fsck «from there» (which I interpret to mean from /sda1). If I simply enter fsck after the prompt, I get :
mhenriday wrote: ⤴Sat Apr 13, 2019 8:57 am
But how do I then run fsck «from there» (which I interpret to mean from /sda1). If I simply enter fsck after the prompt, I get :
Alas, catweazel, the following is what appears in a terminal when I run fsck /sda1 :
the first attempt without mounting my SSD ; the second after doing so. Again not much help....
What I am wondering is if - and in that case how - I can use Timeshift to resolve the problem by going back to, e g, a previous snapshot and restore from there. Any suggestions ?...
mhenriday wrote: ⤴Sat Apr 13, 2019 10:30 am
Any suggestions ?...
Yes. Read the page at the link I gave you. I don't see how you could miss the instruction it gives: fsck /dev/sda1.
My most profound apologies, catweazel ; not my best day, I'm afraid. But after booting from a flash drive and then running sudo fsck /dev/sda1 in a terminal from there and (carefully) following instructions, /sda1 was repaired and I could reboot from my SSD. Many thanks for bearing with me !...
mhenriday wrote: ⤴Sat Apr 13, 2019 12:15 pm
Many thanks for bearing with me !...
Following that scare, you may want to backup your treasured stuff.
Cheers.
Have done. But again, I wonder if, in the event, this simple (when, that is, one knows how to do it) reparation hadn't sufficed, if Timeshare could have been brought to bear - and if so, just how ?...
mhenriday wrote: ⤴Sun Apr 14, 2019 2:12 am
Have done. But again, I wonder if, in the event, this simple (when, that is, one knows how to do it) reparation hadn't sufficed, if Timeshare could have been brought to bear - and if so, just how ?...
A timeshift restore would not have fixed this issue. Only fsck.
Cheers.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.
mhenriday wrote: ⤴Sun Apr 14, 2019 2:12 am
Have done. But again, I wonder if, in the event, this simple (when, that is, one knows how to do it) reparation hadn't sufficed, if Timeshare could have been brought to bear - and if so, just how ?...
A timeshift restore would not have fixed this issue. Only fsck.
Cheers.
So it seems, given that the error lay in the file system on my SSD, which couldn't be accessed until the error was repaired....
