Linux failed to start file system check

Arch Linux

Hey all, when i try to boot into arch i get a black screen that says Starting version 241.7-2-arch
/dev/sda6: clean, 109564/1638400 files, 1262548/655360 blocks
Thats all normal more or less, i usually get something like that on starting, but this time theres more:

[FAILED] Failed to start File System Check on /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78
See ‘systemctl status «systemd-fsck@dev-disk-by and then a really long number separated by backslashes
[DEPEND] Dependency failed for /home
[DEPEND] Dependency failed for Local File System
Then a bunch of green [ OK. ] lines
Then
You are in emergency mode. After logging in, type «journalctl -xb» to view system logs, «systemctl reboot» to reboot, «systemctl default» or «exit» to boot inti default mode. Give root password for maintenance
(or press Control-D to continue):

Ive logged in with root and tried out all the options to no avail. I cant understamd most of whats in the logs and everytime i reboot it just brings me here again.
Heres an image if you need it:
https://pasteboard.co/I3HZpEv.jpg
Thanks!

Last edited by promitheas (2019-03-03 13:51:45)

#2 2019-03-03 13:45:05

Re: [SOLVED] Failed to start File System Check on startup

There’s a problem w/ your home partition.
Check whether /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78 is there as well as the systemctl status (or attempt a manual fsck on the device)
Also log your desired partition scheme (/etc/fstab, fdisk -l and lsblk)

Something like https://grml.org/ is maybe more convenient to deal with this kind of issue than the systemd emergency shell.

#3 2019-03-03 13:51:21

Re: [SOLVED] Failed to start File System Check on startup

There’s a problem w/ your home partition.
Check whether /dev/disk/by-uuid/21c2f987-a247-4254-97e0-a7f53db9af78 is there as well as the systemctl status (or attempt a manual fsck on the device)
Also log your desired partition scheme (/etc/fstab, fdisk -l and lsblk)

Something like https://grml.org/ is maybe more convenient to deal with this kind of issue than the systemd emergency shell.

I am a total moron. Without realising it, i was trying to run fsck on the root partition instead of home. Your comment woke me up. Fixed, thank you!
After i check if everything is fine i need to grab some sleep

Источник

How to permanently fix fsck check failing during boot

My laptop is an ASUS FX505DY. I bought it without any OS and installed Ubuntu 19.10, then upgraded to 20.04 a few months later (no dual-boot). From time to time, the system doesn’t boot normally and goes into «emergency mode» (it’s actually the 3rd time after about 1 year of use). Each time the cause is fsck failing to check /home partition. journalctl gives me:

oct. 30 12:19:44 poulpito systemd-fsck[624]: fsck failed with exit status 4. oct. 30 12:19:44 poulpito systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/91e9d404-4089-4b8d-af58-5aebcd76b5a0. 

1. Why file system get corrupted on this partition? Could it be a hardware problem? Do I need to change some parameters or configuration or switch to ext3? I’ve run smartctl -t short /dev/sda4 in recovery mode and no error were reported.
2. /home is on a sata HDD where I also have /var , /tmp and swap partitions. I never get any fsck check problem for these. Perhaps because the boot sequence just doesn’t check these partitions? Or corruptions really happen just on /home ?
3. The last time I had to run fsck.ext4 , I got these questions:

• pass 1: inode seems to contain garbage and inode passes checks, but checksum does not match inode , actually 16 messages of these kinds with contiguous inode numbers
• pass 2: entry » in () has deleted/unused inode (inode numbers suggest that it is a mere consequence of inodes cleared during pass 1
• pass 4: inode ref count is , should be (again, seems to be just a consequence of pass 2)
• pass 5: inode and block bitmap differences, free inodes/free blocks/directories count wrong Does this mean that I lose some data? Since all impacted inodes are related to application files in $HOME/.config/ or $HOME/.local/ , I don’t see directly the effect of a missing or corrupted file.

1. How do I prevent the file system to be corrupted?

EDIT 1: Here is a screenshot of SMART data window in Disks app.

smartctl gives roughly the same data in english:

SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1350 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 670 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 2224 10 Spin_Retry_Count 0x0033 113 100 030 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 509 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 48 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 24418 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 19/42) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0 222 Loaded_Hours 0x0032 096 096 000 Old_age Always - 1931 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0 224 Load_Friction 0x0022 100 100 000 Old_age Always - 0 226 Load-in_Time 0x0026 100 100 000 Old_age Always - 263 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0 254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2218 - 

EDIT 2: and another screenshot for gparted.

EDIT 3: As suggested, I’ve upgraded my BIOS firmware. Well, the upgrade went fine and didn’t break anything. For sure, it’s better to have firmware up-to-date in any case. But I must confess that I don’t understand how the BIOS could be responsible of FS corruptions on a single partition of my HDD and I can’t see any way to verify that the problem is really solved. I give up for now and I’ll update this post if the problem happen again. UPDATE: the same error occurred again about two months after original post and BIOS update.

EDIT 4: More details, as requested by @heynnema

$ free -h total utilisé libre partagé tamp/cache disponible Mem: 7,7Gi 2,3Gi 3,8Gi 49Mi 1,5Gi 5,0Gi Partition d'échange: 15Gi 0B 15Gi 

$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # #      # / was on /dev/nvme0n1p2 during installation UUID=cbee80f8-6637-44e3-8dbd-7f710be58e54 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=E06D-1632 /boot/efi vfat umask=0077 0 1 # /home was on /dev/sda4 during installation UUID=91e9d404-4089-4b8d-af58-5aebcd76b5a0 /home ext4 defaults 0 2 # /tmp was on /dev/sda2 during installation UUID=51e800d3-f199-490a-bb7a-d2f49635e71c /tmp ext4 defaults 0 2 # /var was on /dev/sda3 during installation UUID=da892f2f-b8d2-47f5-a5e7-30e779fe9d2c /var ext4 defaults 0 2 # swap was on /dev/sda1 during installation UUID=7317598f-60e6-475e-a7d0-38503bac42fc none swap sw 0 0 

Источник

Failed to start File System Check on

A couple hours ago tried to start my Ubuntu laptop after a few months without using it and I found myself with this: I’m far from understanding what’s exactly happening here. Does anyone know how to troubleshoot this?

2 Answers 2

My guess for your situation would be that environmental changes have affected you HDD. So from the error message from journalctl -xb which points to file inconsistencies and the instruction to run manual file check. Use the fsck command to correct this error:

And simply accept all the options give during the process. Then reboot you system.

sudo fsck /dev/sda1 sudo fsck /dev/sda2 sudo fsck /dev/sda3 sudo fsck /dev/sda4 

And I accepted everthing with y (yes)

If you want to accept all automatically you can use ihmo the -y -flag:

You must log in to answer this question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.14.43533

Ubuntu and the circle of friends logo are trade marks of Canonical Limited and are used under licence.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник