Fsck failed with error code 4

Ошибка при загрузке, кратко: fsck что-то находит, но при загрузке всё-равно exit status 4

При загрузке выдаёт:

/dev/sdb1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
(i.e. without -a or -p options)
fsck died with exit status 4
failed (code 4)

Гружусь с kubuntu liveCD, там выполняю sudo fsck -fcyv /dev/sdb1
На всякий случай привожу всё, что выводится:

$ sudo fsck -fcyv /dev/sdb1

fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
Checking for bad blocks (read-only test): done
/dev/sdb1: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****

94139 inodes used (17.29%)
1561 non-contiguous files (1.7%)
92 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 6978/119/0
963168 blocks used (44.25%)
0 bad blocks
1 large file

81193 regular files
7905 directories
55 character device files
25 block device files
2 fifos
405 links
4933 symbolic links (4736 fast symbolic links)
17 sockets
———
94535 files

Причём FILE SYSTEM каждый раз WAS MODIFIED 🙂
Собственно, далее идёт ребут, нифига хорошего не происходит.. 🙁 Система в том же состоянии.

Источник

Исправляем ошибку: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

Недавно столкнулся с ситуацией, когда сервер, работающий под Ubuntu перестал загружаться, просто зависал на сообщении random: crng init done
Далее я попытался загрузиться в Recovery Mode и увидел вот такую ошибку:

/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Полностью ее текст выглядел так:

fsck from util-linux 2.26.2
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/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.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash)
Enter ‘help’ for a list of built-in commands.
(initramfs) _

Предварительные действия

Хорошим решением будет перед следующим пунктом — сделать клон диска с данными (например с помощью clonezilla live cd), чтобы в случае, если команда fsck отработает неверно — иметь возможность их как-нибудь восстановить. И осуществлять все описание ниже действия уже с клонированным диском, чтобы с случае проблем, просто вернуть на место старый диск или же передать его тому, кто сможет восстановить данные.

Решение проблемы

Как видно из текста ошибки, проблема в том, что команд fsck не смогла корректно отработать в автоматическом режиме. Для устранения ошибки, необходимо запустить эту команду в ручном режиме. Для этого в консоли набираем:

/dev/sda1 — это тот раздел, проблемы с которым показаны в тексте ошибки «The root filesystem on /dev/sda1 requires a manual fsck»
После запуска этой команды, будут выводится различные предложения с исправлением обнаруженных ошибок, на каждом пункте необходимо будет нажать клавишу y на клавиатуре. Либо один раз нажать клавишу a и тогда все обнаруженные ошибки будут автоматически исправлены. После окончания работы fsck, необходимо попробовать перезагрузить компьютер и проверить, что ошибок больше нет и все функционирует как следует.

Источник

fsck died with status code 4

During boot my laptop says:

The man page tells me:

The exit code returned by fsck is the sum of the following conditions:

4 — File system errors left uncorrected

When I try to repair the errors as root, fsck says that my disk is clean:

How can I repair my disk?

2 Answers 2

Try the -y option.

-y For some filesystem-specific checkers, the -y option will cause the fs-specific fsck to always attempt to fix any detected filesystem corruption automatically. Some- times an expert may be able to do better driving the fsck manually. Note that not all filesystem-specific checkers implement this option. In particular fsck.minix(8) and fsck.cramfs(8) does not support the -y option as of this writing.

Sometimes fsck shows that a filesystem has no errors, but in reality it has. I had a similar issue once, and if you want to check that filesystem, you have to use force. I’m not sure what type of a filesystem you’re using, but let’s assume it’s ext4:

So, the line you need is:

Hot Network Questions

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.1.14.43159

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

Источник

Debian User Forums

(warning). fsck died with exit status 4 failed! (code 4).

(warning). fsck died with exit status 4 failed! (code 4).

#1 Post by TSerzhO_ » 2013-02-19 10:36

First of all, I want to apologize for two things:
1) I am completely noob in Linux and know just nothing at all.
2) My English is very poor; I can read, but to speak, compose and write, express my minds and my thoughts is just hard for me; my mother tongue is Ukrainian.
For that I’m sorry.
So, I will try to maximally use my vocabulary to get You could to understand what I’m saying about. And also to provide You as much the details as I only can.

My system has stopped to boot at all.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#2 Post by TSerzhO_ » 2013-02-19 10:45

Re: (warning). fsck died with exit status 4 failed! (code 4)

#3 Post by dilberts_left_nut » 2013-02-19 10:49

First, don’t apologise for your language, your english is better than my ukranian (but it is good to know)

The filesystem on your root partition needs fixing before it will boot.
enter the root password then run

Re: (warning). fsck died with exit status 4 failed! (code 4)

#4 Post by michapma » 2013-02-19 11:04

Secondly, don’t apologize for being a noob, it’s impossible to start as a guru. You did a good job of describing your problem and providing enough information for someone to provide help.

These forums might be a good place to learn both technical and creative English.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#5 Post by TSerzhO_ » 2013-02-19 11:06

Thanks, dilberts_left_nut. If You ever need a language help (Ukrainian or russian), then I am here for You. And here too.

So, about my debian problem.
I were trying to type my root password in that moment (where is a «_» symbol: <

>), but then I’ve got nothing. Unfortunately, I’m not at home right now and can’t to tell You, what actually happens exactly.

Ctrl+D — all just the same.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#6 Post by dilberts_left_nut » 2013-02-19 11:09

Re: (warning). fsck died with exit status 4 failed! (code 4)

#7 Post by TSerzhO_ » 2013-02-19 11:12

Re: (warning). fsck died with exit status 4 failed! (code 4)

#8 Post by TSerzhO_ » 2013-02-19 11:20

Re: (warning). fsck died with exit status 4 failed! (code 4)

#9 Post by michapma » 2013-02-19 14:54

When you’re entering your message, at the bottom is an area with two tabs: «Options» and «Upload attachment.» Use the second one. Otherwise, you can host the image online using a free site of your choice.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#10 Post by TSerzhO_ » 2013-02-27 14:56

Sorry, guys, for my reply back are takes so long.
I’m just wanted to say ‘a ‘BiG THANK You» to dilberts_left_nut for help. I did all like You said, and my debian now works again. Thank You a lot.
I have and another big problems, but maybe will post it latter, and hope that You could to help me with it too.
Thanks again.

And 2 michapma
Like I said, when I did all the same like You describes, then I’ve got an error message.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#11 Post by llivv » 2013-02-27 15:27

to use the img tags to post an image you first have to post the image at an image hosting site.
here are links to a few free image hosting sites.
http://imgboat.com/
http://imgsrc.ru/
http://freeimagehosting.net/
http://postimage.org/
http://tinypic.com/
http://imageshack.eu

It may take a few tries to figure out how to link to your images,
but most free image hosting sites give Forum url’s
after you post the image so you can copy and paste the images «Forum url»
into your forum post.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#12 Post by prabhu » 2015-02-04 09:34

I not able to give root passowrd to enter to maintaince mode.

Please help me to fix this please ASAP.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#13 Post by Head_on_a_Stick » 2015-02-04 10:24

prabhu wrote: Dear All,

I not able to give root passowrd to enter to maintaince mode.

Please help me to fix this please ASAP.

Please start a new thread for your problem — be sure to give it a descriptive title both to attract the attention of users who know about the subject and also to help users who have the same problem and are searching for a solution.

Also, read this post to increase your chances of getting help:
http://forums.debian.net/viewtopic.php?p=550848

Re: (warning). fsck died with exit status 4 failed! (code 4)

#14 Post by prabhu » 2015-02-04 12:31

i have the problem similar to mr TSerzhO_

but i not able to provide the root password/

Re: (warning). fsck died with exit status 4 failed! (code 4)

#15 Post by Head_on_a_Stick » 2015-02-04 12:48

Re: (warning). fsck died with exit status 4 failed! (code 4)

#16 Post by prabhu » 2015-02-04 15:57

Thanks for the update,

Its promoting for root password, but from vcenter we are not able to provide the root password.

Is there any other option to fix the issue?

This server is hosted on the EXSi VM server

Re: (warning). fsck died with exit status 4 failed! (code 4)

#17 Post by prabhu » 2015-02-04 16:45

Thanks, i am not able to provide the root password from vcenter server.

Re: (warning). fsck died with exit status 4 failed! (code 4)

#18 Post by mahboobehd » 2016-01-27 23:05

I have the same problem, but when I run fsck /dev/sda1, I get this message:
«Error reading block 5539406 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 1376394. Ignore error ?»

I am running debian_squeeze_i386_desktop.qcow2, and it was working properly before I tried to make a bridge between host system and qemu.

Thank you in advace for the help,
Mahboobeh

Re: (warning). fsck died with exit status 4 failed! (code 4)

#19 Post by kiyop » 2016-01-28 11:23

mahboobehd wrote: but when I run fsck /dev/sda1, I get this message:
«Error reading block 5539406 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 1376394. Ignore error ?»

I am running debian_squeeze_i386_desktop.qcow2, and it was working properly before I tried to make a bridge between host system and qemu.

Your debian_squeeze is booting as the host system, isn’t it?

I wonder if /dev/sda1 has bad sector(s).
I suggest you backing-up important data to a safe place such as a partition in an USB media (removable media).
Can you unmount /dev/sda1?
After backing up all the important data, unmount the partition which contains the copied data, and remove the USB media. Then, you can check /dev/sda1 like

Источник

Centos fsck failed with error code 4 | How to Fix

by Ashwini BS | Nov 21, 2022

Let’s have closer look at how to resolve Centos fsck failed with error code 4, with help of Server management support services. We Bobcares respond with details to all your queries no matter how minor.

How to fix Centos fsck failed with error code 4

In this case /dev/sda2 is my root partition and since it’s mounted even in maintenance mode, attempting to run fsck on it would output:

Running fsck on a mounted file system will most damage to it.

Method 1:

Your best option simply is to boot into another Linux as a different partition. Run fsck manually on the faulty partition. This can easily unmount because no OS is using it.

Method 2: If you cannot boot into another Linux.

Run fsck in dry-run mode. Next pipe the output to make reading more practical:

From there, there will be no critical files damaged and it’s always a gamble to use a corrupted file system. Next proceed to boot for the system to make some backups. Forcing the system to boot, by creating a file named forcefsck and writing “Y” to it. echo y > /forcefsck.

At root no longer works and adding fsck.mode=force on the kernel command line, did not fix the problem as fsck will not fix errors without authorization. ie: if someone enters Yes on the keyboard.

Further, it is possible to fix errors on a read-only file system which can also be used to boot into. Here is the technique:

• Put the root partition into read-only mode. This can be done by modifying the faulty partition’s line on /etc/fstab. But remember your old settings:

• If you’re already in maintenance mode. You may able to remount your file system in read-only mode by running “mount -o remount,ro /” and skipping the reboot.

• Switch to run level1 to minimize the amount of interfering processes. You can skip this step if you’re running the session over SSH: init 1

• Fix the file system by replacing /dev/sda2 with the partition’s device, this should now work. Because the root partition will be in read-only: fsck /dev/sda2.

• Make the root file system readable/writable: mount -o remount,rw /dev/sda2

• Restore your /etc/fstab to its original state.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, your system is now safe to use again. If errors keep occurring, it’s probably a sign that your hard drive is failing and before you lose it completely. You should copy your data to a new one.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник