Errors reading block 1231417 (Input/output error).
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/sda2 requires a manual fsck
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
This is caused by a consistency error on the partition containing the root file system. It is often triggered by improperly shutting down the machine.
The general fix is:
# Replace <partition> with that specified in the error (e.g. /dev/sda2).
(initramfs) fsck <partition with error>
Enter Yes(y) to all prompts. Once complete, you will again be presented with the (initramfs) prompt.
# Reboot the machine.
(initramfs) reboot
You may have an issue with package manager upon reboot. In this case:
$ sudo apt-get update && apt-get clean && apt-get update && apt-get upgrade
Members of the Ubuntu community using SSDs (solid state drives) have reported this problem numerous times; this points to a potential bug in Ubuntu.
@mpb Thank you very much. I solved my issue with your method.
Thankyou so much, my problem got solved !!
Thanks, this works and issue got resolbed
Thanks for the solution.
But after reboot the command $ sudo apt-get update && apt-get clean && apt-get update && apt-get upgrade didnât worked. Iâm was getting the error E: Error reading the CPU table.
So I found this solution to repair the âapt-getâ:
Thanks and hope it will help someone.
It worked for me too. Thanks.
This perfectly worked.
Thanks.
It worked well, but system is not rebooting. What should i do?
I entred yes but it wonât complete it stays in printing y only
yes itâs own command that for some reason(donât hesitate to tell me if you know) just prints y several times a second
Thank you thats work for me too
Be careful of this. It is fine to do to get up and running. But concerning.
If you need to do a fsck to get it back:
- Do a backup of that partition
- Install âsmartmontoolsâ:
$ sudo apt install smartmontools - Run smartctl to check the health of that drive, it may be failing and perhaps should be replaced.
$ sudo smartctl -x /dev/
Example:
List the drives
$ lsblk
Just run smartctl on the drive, not the partition
$ sudo smartctl -x /dev/sda >& smartctl-sda.txt
$ sudo smartctl -x /dev/nvme0n1 >& smartctl-nvme0n1.txt
Example lsblk:
$ lsblk
sdb 8:16 0 1.8T 0 disk
ââsdb1 8:17 0 1.8T 0 part /mnt
sdc 8:32 0 1.8T 0 disk
ââsdc1 8:33 0 512M 0 part /boot/efi
ââsdc2 8:34 0 931G 0 part /var/snap/firefox/common/host-hunspell
/
nvme1n1 259:0 0 931.5G 0 disk
âânvme1n1p1 259:1 0 931.5G 0 part
nvme0n1 259:2 0 931.5G 0 disk
âânvme0n1p1 259:3 0 931.5G 0 part
And you would juse use the âsdbâ, âsdcâ, ânvme0n1â, ânvme1n1â from the above list.
The âinfo errorsâ you can ignore generally. if it PASSES, media errors, etc are the main concerns or temperatures on NVMes sensor 3 is often unreliable for temperature, but 1,2 are useful.
fsck is normally needed on âungracefulâ shutdowns, and is automatically run. However, if the damage is bad enough it may not self-recover. That is why you may need fsck. files/inodes not recovered are placed in the file system mounted in the base:
For example:
ââsdc2 8:34 0 931G 0 part /var/snap/firefox/common/host-hunspell
/
The mount would be â/â and files would be stored in â/lost+foundâ