Red Hat / Fedora :: Filesystem Check After Power Outage - WARNING: "Running E2fsck On A Mounted Filesystem May Cause SEVERE Filesystem Damage"
May 18, 2011
I am very new to linux, and I have a question regarding the filesystem check (fsck). The power recently went out and when I tried to restart linux the following error appears:
*/dev/sda1 contains file system w/errors, check forced it then goes on to say..
*An error occured during the file system check. Dropping you to a shell; the system will reboot when you leave the shell. Give root password for maintenance (or type Control-D to continue) I wasn't sure what to do, but checked some other online forums and they suggested running fsck manually - so I typed in the root password - and used the command, "fsck -A -V ; echo == $? ==" it then gave the following message
*WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage
*Would you like to continue (y/n)
Again, I wasn't sure what to do so i just checked no. I then manually turned off the computer and was prompted at the beginning to press Alt-3. I was brought to another screen and it informed me one of the drives was degraded and suggested rebuilding the array. I tried doing this, but it still brings me back to the original error of, "/dev/sda1 contains file system w/errors, check forced," and the process continues.
Also, when I tried to rebuild the array, I didn't backup any of the data on our home directory before doing this (which was probably a big mistake). After being prompted to type the root password, I was able to give the ls command and look at all the directories...the home directory where our data was stored was empty and I am afraid I may have lost some information. Is there a possibility that data was lost when I was trying to rebuild using the old drives?
I've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
I was running a somewhat standard install of Ubuntu 9.10, when my drive got pushed into read-only mode,It took an hour or too, but eventually finished. However, now that partition is unbootable, and upon attempting to boot into Ubuntu, it complains about "libsepol.so.1" as missing and starts a recovery shell. In this recovery shell, only certain tools work. ls complains about "libacl.so.1", and the filesystem is still read-only. It completes, much quicker, but the system remains unbootable. I could probably boot into the Ubuntu live-cd to get read-write access, but I wouldn't know what to do.I don't know how I would go about reinstalling the base Ubuntu packages without write access to the hd, or through the live cd.
I have a following problem: Recently my drive with Ubuntu 9.4 has mysteriously stopped working, i.e. when I switch the computer on it informs me that GRUB didn't find the filesystem. Well, I suppose it happens.
First, I though it was due to the drive dying, but I popped it in an external enclosure and HDTune told me the drive was fine. Wanting to recover the files on the drive before reinstalling I first tried to mount it in said external enclosure under Windows (I have Win Ext2 driver installed which used to work just fine). This time, however, drive gets assigned a letter but upon opening it Windows popped up an error saying that the drive was not formatted and whether I would like to format it then.
Unfazed by this streak of failures I tried to mount it under Linux but, alas, to no avail. I might have tried every single -t operator under mount command but it still won't budge and let me mount.
I was running a somewhat standard install of Ubuntu 9.10, when my drive got pushed into read-only mode, so I switched to tty1, ran /etc/init.d/gdm stop, and then ran fsck -y /. It took an hour or too, but eventually finished. However, now that partition is unbootable, and upon attempting to boot into Ubuntu, it complains about libsepol.so.1 as missing and starts a recovery shell. In this recovery shell, only certain tools work. ls complains about libacl.so.1, and the filesystem is still read-only. When I try mount -rw /dev/sda1, it complains about libsepol.so.1 again. I can however still run fsck. I tried running it with fsck -p -f /, and it completes, much quicker, but the system remains unbootable. I could probably boot into the Ubuntu live-cd to get read-write access, but I wouldn't know what to do. I read an interesting suggestion here, but I don't know how I would go about reinstalling the base Ubuntu packages without write access to the hd, or through the live cd.
During the file system check of an ext3 partition at boot I get the following output:
The super-block could not be read or does not describe a correct ext2 filesystem. If the device is still valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate super-block:
I'm then forced to login in as root and given the following prompt:
I'm reluctant to do as advised by the output and run e2fsck -b because it is not an ext2 filesystem.
Although I can still enter runlevel 5, it doesn't seem to recognise mouse and keyboard input in KDE so my system is effectively redundant at the mo. For this reason any short term workarounds are welcome, but a fix is needed. This problem is part of a longer saga to do with recovering a Windows Vista installation which started failing to boot. I have used both Vista and SUSE tools to try and recover my bootloader to no avail, and this has been the result. If more detail about this is needed please ask and I can explain what I have done.
my Fedora 12 does fsck on boot time to time and sometimes it's really annoying having to wait for the check to complete. In Linux Mint pressing <Esc> cancelled the check; however in Fedora this does not work (nor does Ctrl+C nor anything other I've tried). What is the key to cancel the check in Fedora?
as far as i know Debian "Squeeze" has a disk check utility, but you can't run this on a mounted filesystem. Is there a way to trigger this during boot (before filesystem is mounted) ? I can run this once a month to keep filesystem healthy....
I'm a bit of a Linux newbie, but I did manage to set up the following RAID-5 system:1x 500GB system drive on ATA IDE4x 1TB SATA drives in software RAIDLinux = Fedora 13So here's what happened. I set up the system to send me an email every time the mdadm stat file changed, so it would send me emails when in periodically ran a self-test. I was away and noticed that the self-test was going incredibly slow (usually took 8 hours...was on course for taking 250 days!) A colleague decided to just reboot the system.Afterwards, the system would not boot and, while all 5 drives were connected, would stop at an endlessly scrolling error message of: Code: ata4.01: exception Emask 0x0 SErr 0x0 action 0x0
ata4.01: BMDMA stay 0x64 ata4.01: failed command: READ DMA ata4.01: (a bunch of hex numbers)
I'm having the following issue on an appliance using uClinux and MTD to access a NAND flash memory: Although the kernel has Yaffs compiled and it seems able to access the NAND, it doesn't create devices (/dev/mtdblock? and /dev/mtd?):
Code: root:~> dmesg Linux version 184.108.40.206-ADI-2007R1.1-svn (root@ubuntu) (gcc version 4.1.1 (ADI 07R1)) #1 Thu Feb 10 15:37:08 CET 2011 Blackfin support (C) 2004-2007 Analog Devices, Inc. Compiled for ADSP-BF532 Rev 0.5
I installed OpenSUSE 11.1 on a friends computer after having a lot of trouble from ubuntu, and because I use it. It was working great when she got it home, but it locked up randomly and wouldn't unfreeze so she turned it off and when she rebooted She got an error about there not being a file system present and that she needed to run a mount command, which didn't work. After that, now it just says that there is no files system present and you ge tthe basic prompt. I had her run a live cd and run Gpartd and check and repair the partitions, but it did nothing.
I run Windows Vista and Ubuntu 9.10 dual boot. Today while booting windows, it informed me that there was something wrong with my hard disk and it would perform a check, and made some fixes.
Only when I wanted to boot into ubuntu again did I realise that the disk check had corrupted my linux partition. Ubuntu's load screen shows up, but just before the login screen it says that the filesystem could not be mounted.
Is there a way I can fix this? And how do I prevent windows from doing the same in the future?
I've ran fsck -c on the (unmounted) partition in question a while ago. The process was unattended and results were not stored anywhere (except badblock inode). Now I'd like to get badblock information to know if there are any problems with the harddrive. Unfortunately, partition is used in the production system and can't be unmounted.
I see two ways to get what I want: Run badblocks in read-only mode. This will probably take a lot of time and cause unnecessary bruden on the system. Somehow extract information about badblocks from the filesystem iteself. How can I view known badblocks registered in mounted filesystem?
I am trying to do a fsck on my ext3 partition, but so far failed to let the system come up in single user mode and having the partition mounted read only. It says in the kernel parameter that it is read only (RO) but still mounts it RW. A remount with mount -o remount,ro does not work, since / is always busy. what to do to get a fsck done? I don't want to boot into a rescue system, this should be possible on a running system (like Windows does it, when rebooting)
For example we have a PC with Linux and, let's say, ext4. It is connected to another PC with Linux and Samba-shared dir.First PC mounted shared dir of the second one. So it's in the filesystem, for example in "/mnt/000/". What will happen if I unplug the net cable from first PC? Will ext4 on the first PC crash so I'll have to perform fsck? I know that hot unpluging of mounted HDD probably will make filesystem read-only available and generally damaged.
I am trying to figure out a totally odd behavior of the ext3 filesystem mounted in Ubuntu 9.10. There is a Korn Shell script, part of which does the following in the loop:
while ((1)); do mv dir1/file dir2; if [[ ! -r dir2/file ]]; then echo "ERROR" ls -l dir1/* dir2/* exit 1 elif echo "OK" fi done
Given that dir2/file always exists and that I do not move it asynchronously with "&", my script should never hit the "ERROR" statement. The odd thing is that it does, and quite randomly (no pattern at all). However when it does hit the ERROR case, ls -l prints that file is in dir2 and it is readable! I tried using "-e" instead of "-r" test - no luck. I never seen anything like this in 10 years of my programming experience. Same script worked fine on Fedora 11, and yet it wouldn't work on Ubuntu.
I have got arch Linux dual booting with Win XP on my laptop. I have been getting a filesystem check error since yesterday 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.
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.
fsck from util-linux-ng 2.17.2 e2fsck 1.41.11 (14-Mar-2010) /dev/sda1 is mounted. WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you really want to continue (y/n)?
I don't want to cause damage, but I'd rather not go into BIOS.
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
you can refer to this ubuntu thread for context, but i'll sum up what i'm trying to do here to spare the reading. basically i want to be able to schedule a filesystem check with automatic repairs at the next boot time. but i'm not sure if this will try to automatically fix errors which is what i want to do. the reason i want to do this is because i experienced a power outage (the machine was not plugged into an UPS) and i want to make sure everything is ok.