I was using my Ubuntu 2015.04 (with ecryptfs-encrypted user home) laptop normally when suddenly, the hard drive became read-only.
I rebooted and now it is stuck on this:
[ 0.703206] ACPI PCC probe failed.
starting version 219
error: /dev/sdb: No medium found
error: /dev/sdb: No medium found
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default or ^D to
try again to boot into default mode.
root@nico:~#
Interesting part of the system logs:
-- Unit systemd-fsckd.service has begun starting up.
system-fsck[475]: /dev/sda1 contains a file system with errors, check forced.
kernel: ACPI warning: \_SB_.PCIO.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
kernel: ACPI warning: \_SB_.PCIO.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
kernel: thinkpad_acpi: EC reports that Thermal Table has changed
system-fsck[475]: /dev/sda1: Inodes that were part of a corrupted orphan linked list found.
system-fsck[475]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
system-fsck[475]: (i.e., without -a or -p options)
system-fsck[475]: fsck failed with error code 4.
system-fsck[475]: Running request emergency.target/start/replace
systemd[1]: system-fsck-root.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start File System Check on Root Device
-- Subject: Unit system-fsck-root.service has failed
I am not sure whether it is an ACPI or a disk problem. I tried updating to the latest BIOS my Lenovo Thinkpad T520, but it does not boot better.
How to fix this problem, or if the disk is dying how to at least export the data from my encrypted home to an external drive?
fsck /dev/sda<number>
and press enter (look for the<number>
from your logs based on the directory that contains the file system errors)y
to all the errors to fix themexit
In Terminal
sudo -i
(if not a root user, otherwise skip this)Look for your root drive.
I use Kali Linux in raspberry pi so mine looks something like
mmcblk0p2
instead ofsdb1
... See for yours.fsck -y /dev/mmcblk0p2
poweroff
I've had the same issue. I've created a image file from a working Raspbian SDCard using Win32DiskImager. When I ran pishrink, the tool gave me the "orphaned inode list" error. So I followed the suggestion from Rocky Inde and executed fsck. It encountered and fixed some errors so I ran pishrink again and it worked! Thanks Rock Inde.
If you got this far and are still confused how to do it, I've created a script, partly based on pishrink, to fix these "orphaned inodes". You can check the script source at
https://github.com/gmenezesg/fix_orphaned_inode_list
Usage:
Script: