[SOLVED] Filesystem check failed on LVM partition...

My server experienced a power outage last night, and I noticed today that it wasn't booting correctly. Apparently, the storage partition, /dev/mapper/VolGroup00-lvolstorage fails the filesystem check. The first time I booted into it, I ran a manual check and answered (y) to the questions. Now when booting, it quickly displays a bunch of numbers and that scrolls for a little while (goes too fast to understand what they are...). Then it says:
####Filesystem Check Failed####
Please repair manually, blah blah blah
I'm not really sure what to do. Running fsck does the whole numbers scrolling across the screen thing again, finally asking if I want to clone multiply-claimed blocks... =/ I don't want to answer yes anymore until I get someone's input. <_<
EDIT: It said before that there are 81 inodes containing multiply-claimed blocks... Then it said a certain large file (inode #20) has 27818 multiply-claimed blocks shared with 24 other files, and it then lists other files.
Last edited by XtrmGmr99 (2010-05-21 14:14:25)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

Similar Messages

[SOLVED] Filesystem check failed - All seems normal

Yesterday i turned of my computer after it had been on for a week or so and this morning i can't get it to boot.
While booting, on the filesystem check stage, it reports all filesystems as clean, but then says [FAIL], and gives me access to the maintenance shell.
- I booted the system with a Gparted live cd and did a check on all partitions on all disks. It reported no errors.
- in fstab I commented out the external disk and the internal one which doesn't contain any system partitions, still the same.
- I remounted root rw in the maintainance shell, and did a full system upgrade (last kernel upgrade was applied) ... still no cookies...
- I also tried to mount all the partitions in the maintenance shell. All were mounted without an error, and as far as i can tell all data was there and browsable at least.
- I tried to boot with a /forcefsck file and the checks were all done without any messages, after which it failed as usual.
Also i tried fallback (before the upgrade), which as you can guess by now, also gave the same error. The message about the filesystem check failing is not giving me any useful information. All it does is list the partitions saying every partition is clean, and then says the filesystem check has failed.
As you can probably tell, I did all the steps I could find on the forums that looked it could solve my problems, and I've hit a dead end. If I knew which partition had the problem I could move the data and format it. Could this be a hardware error?
Thanks in advance for any help offered
Last edited by vexxor (2009-07-28 11:04:02)

KimTjik wrote:Maybe a stupid question, but it's not that some partition is totally full?
Nope. I just checked.
Funny thing. In the maintenance console, when i do a "mount -a", I can navigate to the now mounted directories, but I can't see the mounted partitions as an output of either "mount" or "df".
I figured this out when I was checking if the disks were full. Root gets shown, and its on 53%. Just in case i deleted about 20GB of stuff from the media partition, but the problem remains.

[Solved] Filesystem check failed - manual repair too

Good Evening.
Recently my Arch box hang up and I had to reboot forcefully. I expected to get a filesysem scan. The messages on bootup say, that the filesystem check failed and I have to repair it manually. The exact error message is similar to http://bbs.archlinux.org/viewtopic.php?id=89394.
Then I log into the maintenance shell and try to run fsck -pck /dev/sdXX. But that doesn't work because it complains that the filesystem is no ext2-fs or the superblock is corrupt. I should try one of the backup superblocks. To figure out the backup superblocks, I tried mke2fs -n /dev/sdXX but that does not work either. Now it complains that /dev/sdXX does not exist! I looked in /dev and the partitions really don't show up. Where are they? I mean, the maintenance shell works on the / partition, or does it?
To cut a long story short, I can't check my partitions and I don't know any other way how to fix the problem. The next ArchLive CD is 500 km away.
I appreciate any help.
Greetz,
haunted
EDIT:
Ok, I solved the problem as I got my ArchLive CD. If it's to anybody's use, that's the procedure I went through:
I inserted the CD and booted from it. I ran the e2fsck several times. First I did an overall check (e2fsck -v /dev/sdaX) on my Arch partition which I had to do manually i.e. type "y" to every inconsisteny found, then updated the badblock list (e2fsck -vc /dev/sdaX) and checked the partition again.
I rebooted the system without the CD to look if I succeded repairing the hdd. Eventually I deleted the /sys mountpoint in the procedure and had to create it again via ArchLive CD. After the next reboot it complained that the superblock's timestap was written in the future. Rebooting with the CD again, checking again and rebooting without CD again.
It wasn´t of any use and Arch complained again. Then I simply rebooted the system (without CD) again and on start up it stopped complaining and did a normal check on the Arch partition, completed the check and went on loading as normal. System repaired.
Last edited by hauntergeist (2010-02-08 11:11:59)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
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
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

[Solved] Filesystem check failed after removing harddrive

I have a harddrive in a arch computer which is not listed in fstab and not used as root, boot or home. I want to remove it from the computer, but when I try this I get the error filesystem check failed. I get the option to repair, and then get logged in as root. Here I can see my ordinary boot, root and home with fdisk -l. How can I tell the computer that there is nothing wrong, that I dont want use that disk? I searched the forum for this error and found a recommendation to use e2fsck, but since the error is because of the removed disk I cant do that.
Last edited by heptapod (2011-04-28 07:51:23)

Always use persistent block device naming to prevent this.
https://wiki.archlinux.org/index.php/Pe … ice_naming

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

[SOLVED] Filesystem check failed

Hi all,
i've just upgraded the system, but when rebooting it gives me that error on sda5 (the linux partition) and suggests me to repair manually and reboot! what should i repair? can you please give me any suggestion?
Thanks in advance
Last edited by virusso80 (2010-01-15 15:48:04)

guisacouto wrote:
it seems like today is broken filesystem day.. LOL
I had this problem too in my laptop and that fsck solved it very well!
unfortunatly I cannot say the same thing about the external hard drive that is connected to the desktop which has a fat32 filesystem corrupted.. I'm trying to find some courage to format it, because testdisk can only recover the files with some default name.. thats not good enough because 320GB of music, movies and documents isnt very usefull without the real names.. x| I guess this is just not my day
regards!
There's a /sbin/fsck.vfat as well.

[Solved (initscripts-splash plroblem)] Filesystem check failed

Hello, my arch i686 sudently doesn't boot.
At system start, after loading kernel, the boot process stops and says "FILESYSTEM CHECK FAILED" give root password for maintenance or control+D for restart.
My root partition (dev/sda2) is reiserfs formated, and arch updated this week.
After reading a while I booted with Arch install CD and tried the follwing:
fsck.reiserfs --check /dev/sda2
fsck.reiserfs --fix-fixable /dev/sda2
fsck.reiserfs --rebuild-sb /dev/sda2
fsck.reiserfs --clean-attributes /dev/sda2
But no errors were found or fixed, so I can't boot arch yet.
Are there any other way to fix the filesystem?
can filesystem check be skipped?
please help
Last edited by juan_sck (2008-10-13 11:09:17)

Mektub wrote:
Could it be that it is anoter partition that is giving trouble ? Ot do you only have /dev/sda2 ?
Or start in sinle-user. At the grub boot menu, select the option that lets you edit the kernel parameters.
Add either a '1' or 'single' to the end of the kernel parameters, then continue booting up.
Mektub
of course I know where I installled Arch.
pointone wrote:There should be a more descriptive error message above where it says "filesystem check failed" describing WHY the fsck failed.
No, just system check failed. Even more, my filesystem was perfectly, it was a problem with initscripts-splash
iDeJ wrote:
i had a similar problem after the last pacman -Syu, basicly the bootsplash-initscripts are not compatible with latest udev
maybe it helps
http://bbs.archlinux.org/viewtopic.php?id=56604
I don't think installing a year old initscripts package would solve it, but you were very helpful.
Finally I could solve it with the recovery console:
After the error message I typed root password to log in, then remounted root partition for r/w:
mount -n -o remount,rw /
Finally I had to remove the package initscripts-splash and install initscripts form core.
ifconfig eth0 up
dhcpcd eth0
pacman -Syu
pacman -Rs initscripts-splash
pacman -S initscripts
exit
**You should make a backup of rc.conf before installing initscripts, because installing initscrips will overwrite it (and a few other files i hadn't modified), and pacman was supoussed to back it up, but it didn't
thanks for your help.

Filesystem check failed after running upgrades [Solved]

I have a new arch installation with /home, /tmp, /var, and /usr mounted on an LVM partition. After running the updates I get a "Filesystem Check Failed" error message. It then dumps me into the terminal in read-only mode, giving me the option for read/write... which doesn't matter, because without access to vi (which is on /usr o the LVM partition) I can't access anything anyway. / and /boot test clean, but it's not recognizing the LVM. Any help would be appreciated.
Last edited by 2handband (2011-01-22 19:21:17)

Figured it out... the miserable thing couldn't make up it's mind which drive to label sda.

Filesystem check failing; can't enter maintenance shell. [SOLVED]

Originally, arch wouldn't let me log in, complaining of an incorrect shell entry. (This is a recently re-setup system of mine, so I only have a root account.)
So I booted into the LiveCD, mounted my root partition, and editted /etc/passwd so that it pointed to the correct zsh path. But I rebooted without thinking, and without unmount. DOH!
Now Im getting the "FILESYSTEM CHECK FAILED: Please repair manually and reboot" error on boot, constantly. I've gone into the Live environemt again, and fsck the partition - didn't help.
Ideas? I've seen a recent topic similar to this one, but couldn't find help in it.
Last edited by pritchard92 (2009-09-28 21:49:34)

Thank you for the reply.
However, after many more reboots, it finally checked the disk, and is now working.
Thanks.

Filesystem check failed, root partition not found

Hi all,
Since yesterday I receive the following error message when booting into Arch:
:: Mounting root filesystem read-only [ OK ]
:: Checking filesystems [BUSY]
/dev/sda4: no such file or directory
*************** FILESYSTEM CHECK FAILED *******************
* Please repair manually and reboot ...
The device /dev/sda4 is my root partition, which is - after entering the root
password - mounted as /dev/root. Checking the partition with 'reiserfsck
/dev/sda4' does not give any error or warning messages. I can also
successfully remount and access it with 'mount -n -o remount,rw /'.
'ls -l /dev/sda*' gives me the following:
brw-rw---- 1 root disk 8, 0 Apr 28 16:32 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 28 16:32 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 28 16:32 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 28 16:32 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 28 16:32 /dev/sda4
So the device itself seems to be there. Rebooting doesn't help, neither does
using older, working kernel versions.
I also checked other topics on similar subjects, but I couldn't find any solution.

Hmm, it doesn't work even with the UUID. But the error looks similar:
Failed to open the device UUID=672f076e-131c-4220-81ba-b30639ef9285: No such file or directory
But when I call rc.sysinit manually directly after entering the root password,
everything works fine. It does work with sda as well as uuid notation.
I manually added some code before the output of the '*** FILESYSTEM CHECK FAILED ***' message:
ls -l /dev/sda*
sleep 1
ls -l /dev/sda*
The result was:
ls: cannot access /dev/sda*: No such file or directory
brw-rw---- 1 root disk 8, 0 Apr 30 09:12 /dev/sda
brw-rw---- 1 root disk 8, 1 Apr 30 09:12 /dev/sda1
brw-rw---- 1 root disk 8, 2 Apr 30 09:12 /dev/sda2
brw-rw---- 1 root disk 8, 3 Apr 30 09:12 /dev/sda3
brw-rw---- 1 root disk 8, 4 Apr 30 09:12 /dev/sda4
So it seems that the devices are really not yet created. Is it a udev problem?
I am not aware of changing anything udev specific, maybe an updated version?

"FILESYSTEM CHECK FAILED" - fresh install, clean partition

Hi,
I just installed Arch on my Asus EEE 701SD. Since GRUB is extremely slow (takes about 30-45 seconds from "loading..." to menu) I've set up my /boot on a separate flash drive. However, booting the new installation gives me the "FILESYSTEM CHECK FAILED" + maintenance shell. I've tried running fsck with various options but none of it has helped. Apparently, the partition is clean so I'm not quite sure what's going on. Any suggestions?
Cheers:)

The hook "usb" should work too, so I don't think we're on the right track here. But since it doesn't hurt you can add the actual kernel modules to the modules= line:
usbcore ehci-hcd (and/or uhci-hcd) usb-storage and maybe the filesystem used (and it's dependencies like ciphers).
Greets,
demian
// I guess I'm a slow typer. Why don't you show us your /etc/fstab?
From what you've written the system shouldn't be able to boot since there's no fstab entry for /boot. Maybe I misunderstood you.
Last edited by demian (2010-06-07 23:00:48)

Filesystem check failed. with UUID, SATA, fsck -f doesn't res [SOLVED]

It appeared right on the first boot.
Things I tried:
reinstalled Arch
fsck -f
checked fstab - all mountpoints in UUID
system was installed with AHCPI enabled and running
system boots like this:
Bringing up loopback interface [done]
Mounting Root Read-only [done]
Checking Filesystems [busy] linuxroot: clean, 110927/327680 files, 744572/1310384 blocks
[fail]
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.
Its a Sata-HD
It has 4 partitions and had Vista preinstalled using the first 3. on the last patitions (sda4) i put /. home and swap are on a USB-HD
EDIT
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=3f247afa-7966-4472-aea3-d65199b769b3 swap swap defaults 0 0
UUID=735b5356-141f-4ee5-a5cf-4ca82dd6809b /home ext3 defaults,noatime 0 1
UUID=cc6b9a82-b403-4fce-94b7-a939e85fbd17 / ext3 defaults,noatime 0 1
Last edited by capoeira (2010-05-27 21:03:23)

Factory wrote:Are you positive those are the correlating uuids for the appropriate drives? On my desktop my sd*#s like to switch themselves after an install.
yes, the UUIDs were generated by the installer, and I can manualy mount them with "mount /dev/sda4", "mount /dev/sdb2"
EDIT: I duble checked that, UUIDs OK
Inxsible wrote:
capoeira wrote:It has 4 partitions and had Vista preinstalled using the first 3. on the last patitions (sda4) i put /. home and swap are on a USB-HD
Probably a dumb question, but you do have your USB HD plugged in when you boot up, right?
sure I do
Last edited by capoeira (2010-05-27 18:39:28)

Filesystem check failed - Linux won't boot

I did a search on this forum, and this error ("Filesystem check failed") comes up a few times, but always after its user resized his partitions or did something to his fstab. Which is not my case.
For two days, I've been getting this error at boot. Just before getting the error, I can see that both my / and /home partitions are checked and raise no errors. However, when it gets to my /boot partition, I get the following message.
Filesystem mounted or used by another program ?
I have no clue as to what's happening. My current partitions, for the record, are
/boot /dev/sdb1 ext2
/ /dev/sdb2 ext3
/home /dev/sdb3 ext3
If you need any other info to help my solve my problem, just ask. Thanks !

4th attempt to restore successful!
Will attempt to verify disk and make second attempt to install Mavs.

Filesystem check failed + accidental /boot deletion

Yesterday I rebooted my PC and suddenly Arch started complaining about "Filesystem check failed", just like stated by the OP in this thread https://bbs.archlinux.org/viewtopic.php … 00#p941200
The problem was with two partitions: /boot and /home. I tried to no avail to manually fsck them using the maintenance console and e2fsck as well as the forcefsck command but it didn't work.
I didn't try any LiveCD back then but since I saw that in that thread the OP solved his problem by deleting some folders located at /media:
Fixed the problem.
The /dev/sda2 and /dev/sda5 were being mounted in the wrong place.
Instead of being mounted in /home and /boot as per /etc/fstab, they were being mounted in new directories in /media called /media/usbhd-sda2 and /media/usbhd-sda5. Upon deleting those folders, everything has gone back to normal.
I have no idea how those new folders got created...but problem solved now.
Thanks for the help, guys
Samsom
Problem is I didn't think at all when I read this post and went right away to delete the problematic folders (the post itself didn't exactly explain how the OP managed to unmount the partitions and then proceed to delete the folders, my umount commands didn't work so it wasn't crystal clear to me how he managed it, my bad tho for not checking what I was deleting).
Luckily, I think I only managed to delete partially my /boot folder (thus GRUB now complains and doesn't boot any system). So now my question is, is there a way to restore my /boot folder without a full system re-install?
Thanks in advance.

But what is the command? mkinitcpio -p kernel26 ? Also how do I fix this grub issue? I'm assuming grub created a default menu.lst after I copied the config files and setup the hd0 but I actually don't recall checking that.
Just re-did all steps including rebuilding the kernel, I still can't get the boot menu when I reboot. It goes directly to grub console.
I checked the generated menu.lst, it lists my root as the device where /boot partition is and the kernel line root enrty is defined for the arch system I want to boot :\
Last edited by Grimn (2011-05-31 17:50:02)

[SOLVED] Filesystem check failed on LVM partition...

Similar Messages

Maybe you are looking for