Linux file system check failed

Arch Linux

You are not logged in.

#1 2017-02-28 13:00:41

[Solved] Failed to start file system check on /dev/disk/by-uuid

Hello, today i start my arch and i have this error : Failed to start file system check on /dev/disk/by-uuid/.
Help me please !

Mod note: Replaced image with url. Please see the CoC regarding acceptable image sizes. — WorMzy

Last edited by ZoneHacker (2017-02-28 17:07:27)

#2 2017-02-28 13:47:04

Re: [Solved] Failed to start file system check on /dev/disk/by-uuid

Hi there and welcome ZoneHacker

Be aware of my Newbie Powers

#3 2017-02-28 14:20:47

Re: [Solved] Failed to start file system check on /dev/disk/by-uuid

And once you’ve read through the articles linked by olegabrielz, please post your /etc/fstab

BTW, for logging in, have you considered the fact that the terminal might be set to use the US-english keyboard layout (for typing your password)?

#4 2017-02-28 16:06:38

Re: [Solved] Failed to start file system check on /dev/disk/by-uuid

Hello sorry for the picture. I can log with my password it’s not a problem
This is my fstab

#
# /etc/fstab: static file system information
#
#

# /dev/sda3
UUID=437e276f-3c26-4782-909d-fb90c33b6e35 / ext4 rw,relatime,data=ordered 0 1

# /dev/sda1
UUID=2f48b5eb-3692-419b-ada6-d1842631c6f2 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 2

# /dev/sda4
UUID=06618d7a-0b70-4ccd-9953-5deae8c8e009 /home ext4 rw,relatime,data=ordered 0 2

# /dev/sda2
UUID=5ecb6872-9ab9-4a69-a989-acd3dea270b1 none swap defaults 0 0

Last edited by ZoneHacker (2017-02-28 16:07:52)

Источник

Arch Linux

You are not logged in.

#1 2010-01-23 07:49:22

Filesystem check failed (SOLVED)

Hi,
I have been getting a filesystem check error since yesterday now and am unable to start Arch. Upon googling and searching the arch fora, I came upon some advice which I tried which has not worked yet. Hence the new post.

Basically, I was attempting to print something off and accidentally chose a printer that was not connected to my laptop. After half a minute or so, it repeatedly started giving me notifications that the printer was not connected. in excess of 200 messages that the printer was not working which continued to pop up despite me canceling the print job. The whole system got really sluggish (for the first time in the last year) and I had to restart the laptop upon which the boot messages appear.
It gets to the point where its loading the various filesystems. It mounts root and says it fine. Then it says

In my system,
/dev/sda3 is root
/dev/sda2 is boot
/dev/sda5 is home

I tried fsck which tells me that home and boot are still mounted.
So I booted up using an Ubuntu Live CD and checked and repaired each file system which it successfully did. Upon rebooting into Arch, I am getting the same message.
I have not installed anything new and had upgraded the whole system a few days before the problem started.
Not sure where to go from here.
Any help, please
Thanks

Last edited by samsom (2010-01-24 22:42:41)

Источник

Arch Linux

You are not logged in.

#1 2011-07-02 14:23:33

[SOLVED]Filesystem Check Failed 🙁

Currently I have two harddrives, sda and sdb.
All my main fails are on sda, and when arch checks that harddrive it comes clean.
I just formatted part of my sdb, as ntfs for windows.
Previously my computer mounted both sda and sdb.
Could the problem be that I am mounting sdb as a whole instead of soley sdb1?
But my error occurs when it says .
«/dev/sdb1 is mounted. e2fsck: Cannot continue, aborting.»

I tried umount /dev/sdb, then hit ctrl+D it restarts but runs into the same error.
I also tried
umount /dev/sdb
But my output says..
«umount: /dev/sdb: not mounted»
And when i try manually checking the disk with e2fsck or fsck it says my harddrive it still mounted

my fdisk -l looks like

my cat /etc/fstab looks like this

By the way all the code wasn’t copied and pasted so there might by some typos.

If someone could please give me some steps in the right direction that would be great.
I’m still a newb at this!
Thanks

UPDATE:I also tried running umount and fsck in single user mode, but it still says the filesystem is mounted and umount says its not mounted.

Last edited by Jabrick (2011-07-02 18:26:58)

#2 2011-07-02 15:34:28

Re: [SOLVED]Filesystem Check Failed 🙁

/dev/sdb is a disk, not a partition. You cannot (un)mount a disk.

Check /etc/udev/rules.d for any rules that might be automounting partitions.

#3 2011-07-02 16:20:17

Re: [SOLVED]Filesystem Check Failed 🙁

Ok I tried fsck /dev/sdb1 in single user mode and it still says it is mounted. I did use the umount command.
Whats going on.

When i do vim /etc/udev/rules.d this is what i get

$
» Quick Help: :help -:go up dir D:delete R:rename s:sort-by x:exec
«===============================
../
11-media-by-label-auto-mount.rules

UPDATE: When typing init 1 there is an error at.
Error creating persisten state file; filename=’/var/lib/syslog-ng/syslog-ng.persist-‘, error=’Read-only file system (30)’
I don’t know if that helps

Last edited by Jabrick (2011-07-02 16:29:41)

#4 2011-07-02 16:27:53

Re: [SOLVED]Filesystem Check Failed 🙁

replace in fstab «/dev/sdb1» with correct uuid and problem most likely will be solved

O’ rly ? Ya rly Oo

#5 2011-07-02 16:29:55

Re: [SOLVED]Filesystem Check Failed 🙁

Ok I tried fsck /dev/sdb1 in single user mode and it still says it is mounted. I did use the umount command.
Whats going on.

When i do vim /etc/udev/rules.d this is what i get

$
» Quick Help: :help -:go up dir D:delete R:rename s:sort-by x:exec
«===============================
../
11-media-by-label-auto-mount.rules

Yes, and that rules file is what’s mounting /dev/sdbX automatically. Either adjust it to only catch sd[c-z] or delete it.

#6 2011-07-02 16:37:05

Re: [SOLVED]Filesystem Check Failed 🙁

replace in fstab «/dev/sdb1» with correct uuid and problem most likely will be solved

Sorry I’m sure what you mean by that. but it seems like you are confident in your anwser!!
I will give you what my fstab UUID says.

UUID=5a672a8d-2350-4622-8d82-eea696a9b08a /boot ext2 defaults 0 1
UUID=867aabe0-b714-462d-b093-07c4e7ed8876 /home ext4 defaults 0 1
UUID=cdee52e2-d656-4ea7-8a89-aa151cb5180b / ext4 defaults 0 1
UUID=e59b40d7-358a-48c8-8199-cc39ad6e64a5 swap swap defaults 0 0

So do you suggest on the third UUID i input /»dev/sdb1″?
Please get back to me as I do not want to destroy or lost all my data!

UPDATE: Or should i input /»media» on the third line. Is that it. waiting anxiously.
UPDATE2: I read the fstab arch wiki, and it seems that the default option for /dev/sdb includes automount.
What I’m confused is that /dev/sb1 is a linux partition, shouldn’t it should be left as default? Am I correct to rule this
out? Just trying to give me info, as my computer is down At least I’m learning

Last edited by Jabrick (2011-07-02 17:12:39)

Источник

Linux проверка файловой системы и диска

Полностью ошибка обычно выглядит следующим образом:

Filesystem check failed.
Please repair manually and reboot. Note that the root file system is currently mounted readonly. To remount it read-write type: mount -n -o remount ,rw /
When you exit the maintenance shell the system will reboot automatically.

Увидеть ее можно в консоли при старте сервера. Если проверен быть не может диск или раздел с основной загрузочной записью — система не запустится.

В этом случае нужно загрузиться с live-CD или загрузочного USB устройства и вручную запустить проверку.

В случае с VDS/VPS часто предусмотрена VNC консоль и возможность загрузки с внешним ядром. Внешнее ядро в таком случае заменяет live-CD/USB.

Запустив сервер нужно проверить список разделов, сделать это можно используя df -h или просмотрев список в /etc/fstab

Использование fsck для проверки файловой системы

Далее запускаем утилиту fsck (File System ChecK) передавая ей имя партиции или устройства обнаруженного в /etc/fstab

При больших объемах данных процесс проверки может занять какое-то время. Ключ -y означает yes, т.е. положительный ответ нужно давать на все вопросы, которые в возникающих диалогах задает утилита.

Когда все разделы проверены сервер следует перезагрузить командой reboot. Существовавшие ошибки таким образом будут исправлены.

fsck можно запускать при загрузке системы автоматически или каждые N-монтирований раздела.

Источник

Arch Linux

You are not logged in.

#1 2016-10-22 09:17:58

filesystem check failed. run fsck manually

Hi guys,
after a crash I rebooted the PC and when I turn on it says:

, I have this loop in output:

and the loop starts..

can you help me?
thank you

#2 2016-10-22 09:23:09

Re: filesystem check failed. run fsck manually

blk_update_request: I/O error, dev sda, sector 84940851
Buffer I/O error on dev sda3, logical block 8389126, async page read
Error reading block 8389126 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan

The above looks like a hardware error — perhaps your disk is on it’s way out.

You should try booting from a usb/cd boot disk to run a smartctl test — see.
https://wiki.archlinux.org/index.php/S.M.A.R.T..

Last edited by paulkerry (2016-10-22 09:24:43)

#3 2016-10-22 12:24:29

Re: filesystem check failed. run fsck manually

ok, I-m running Kali linux and this is the output of a smartctl test:

thank you very much

#4 2016-10-23 15:59:22

Re: filesystem check failed. run fsck manually

You want to run some tests as it mentions on the above link — in your case of /dev/sda

and then review and post here the full output of

paying particular attention to the lower areas of the output where the SMART logs sections are given.

BTW — I’m unsure in what way you are using «Kali linux» (perhaps as a rescue medium?), but note that Arch Linux is the only O/S supported within these forums.

#5 2016-10-24 15:41:14

Re: filesystem check failed. run fsck manually

You want to run some tests as it mentions on the above link — in your case of /dev/sda

and then review and post here the full output of

paying particular attention to the lower areas of the output where the SMART logs sections are given.

BTW — I’m unsure in what way you are using «Kali linux» (perhaps as a rescue medium?), but note that Arch Linux is the only O/S supported within these forums.

hi, I am using Kali because it is the only distro I have on DVD to use as LIVE DVD.
this is the output of:

thank you very much

#6 2016-10-24 20:31:55

Re: filesystem check failed. run fsck manually

OK about the Kali bit, but the command you have posted above is different to those what I suggested. When you do the «-t short» or «-t long», smartctl will tell you how long the test will take, after which run the «-a» and post the full output.

#7 2016-10-25 11:02:03

Re: filesystem check failed. run fsck manually

OK about the Kali bit, but the command you have posted above is different to those what I suggested. When you do the «-t short» or «-t long», smartctl will tell you how long the test will take, after which run the «-a» and post the full output.

ok, now I understand..this is the output>

#8 2016-10-25 18:29:28

Re: filesystem check failed. run fsck manually

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 7196 195720205
# 2 Extended offline Completed: read failure 90% 7194 88465345
# 3 Short offline Completed: read failure 80% 7194 140698270

these lines show that your disk is failing or has failed around those LBA areas, which is more than likely the reason why your fsck is looping.

If you need files from the disk, you could try a rescue with something like ddrescue ( https://www.archlinux.org/packages/?q=ddrescue )

If it’s still under warranty, it should be replaced due to those errors otherwise you’ll just have to get a replacement.

#9 2016-10-25 19:55:27

Re: filesystem check failed. run fsck manually

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 7196 195720205
# 2 Extended offline Completed: read failure 90% 7194 88465345
# 3 Short offline Completed: read failure 80% 7194 140698270

these lines show that your disk is failing or has failed around those LBA areas, which is more than likely the reason why your fsck is looping.

If you need files from the disk, you could try a rescue with something like ddrescue ( https://www.archlinux.org/packages/?q=ddrescue )

If it’s still under warranty, it should be replaced due to those errors otherwise you’ll just have to get a replacement.

sorry, you’re saying that the hard disk is burned?

#10 2016-10-25 21:07:10

Re: filesystem check failed. run fsck manually

Yes. Secure your data. Now.
Preferably from some life system (kali), NOT booting from the broken device, NOR chroot into it. Just use it as some data source and copy everything relevant to some other medium.

> 9 Power_On_Hours 0x0012 084 084 000 Old_age Always — 7196
And if you didn’t smash it or something, that should still be on warranty?

#11 2016-10-25 21:47:38

Re: filesystem check failed. run fsck manually

all my revelant files are on cloud, so I tryed to format it but it gives me an error.
I tryed to install kali also but it gives me errors.
so I can say I must change hard disk.
it is not on warranty so I have to buy new one..
is there some other thing Can I try?

PS: what means the string you posted?

Last edited by DarkPassenger (2016-10-25 21:47:53)

#12 2016-10-25 21:58:12

Re: filesystem check failed. run fsck manually

It has been on power only for 7196 hours so far. That’s not too much. (But of course if you only use the system occasionally, this can mean 10 years 😉

#13 2016-10-25 22:06:46

Re: filesystem check failed. run fsck manually

It has been on power only for 7196 hours so far. That’s not too much. (But of course if you only use the system occasionally, this can mean 10 years 😉

no, I use PC 10-20 hours at day..
it is impossible..mmm.
I changed my HDD 2 years ago..
is it possible that the timer went to 0 when I formatted HDD before installing archlinux last time?

Источник