Ask Your Question
1

Failed to start file system check / emergency mode

asked 2018-12-17 10:09:02 -0500

Samurai gravatar image

updated 2018-12-17 12:09:49 -0500

When I boot the system it fails system check and goes to emergency mode.

[FAILED] Failed to start File System Check on /dev/mapper/frdora-home.
See 'systemctl status "systemd-fsck@dev-mapper-fedora\\x2dhome.service"' for details.
[DEPEND] Dependency failed for /home .
[DEPEND] Dependency failed for Local Files Systems .

[root@localhost ~]# systemctl status "systemd-fsck@dev-mapper-fedora\\x2dhome.service"
systemd-fsck@dev-mapper-fedora\x2dhome.service - File System Check on /dev/mapper/fedora-home
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static; vendor present: disabled)
Active: failed (Result: exit-code) since ... 9 min ago
Docs: man:systemd-fsck@.service (8)
Process: 783 ExecStart=/usr/lib/systemd/systemd-fsck /dev/mapper/fedora-home (code=exited, status=1/FAILURE)
  Main PID: 783 (code=exited, status=1/FAILURE)

... systemd-fsck [783]: /dev/mapper/fedora-home: Inode 7997586 extent tree (at level 1) could be shorter. IGNORED. 
... systemd-fsck [783]: /dev/mapper/fedora-home: Inode 10092920 extent tree (at level 1) could be narrower. IGNORED.
... systemd-fsck [783]: Error reading block 33030151 (Input/Output error) while reading I node and block bitmaps.
... systemd-fsck [783]: /dev/mapper/fedora-home: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
... systemd-fsck [783]: (i.e
,without -a or -P options)
... systemd-fsck [783]: fsck failed with exit status 4.
... systemd-fsck [783]: Running request emergency.target/start/replace
... systemd [1]: systemd-fsck@dev-mapper-fedora\x2dhome.service. service: Main process exited, code=exited, status=1/FAILURE
... systemd [1]: systemd-fsck@dev-mapper-fedora\x2dhome.service. service: Failed with result 'exit code' .
... systemd [1]: Failed to start File System Check on /dev/mapper/fedora-home.

Would appreciate any help.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2018-12-17 15:21:13 -0500

Samurai gravatar image

updated 2018-12-17 15:22:30 -0500

Wasn't sure whether it was an issue with the hard drive or some corrupted files. Ran the following command:

fsck -c -f /dev/mapper/fedora-home

Yes to ignore errors and force rewrite. It took some 30 minutes to check the blocks and found some errors. Asked for permission to fix the blocks, some could be shorter or narrower and some cloning, etc. After that system booted successfully.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2018-12-17 10:09:02 -0500

Seen: 1,029 times

Last updated: Dec 17 '18