I have a volume on my server that according to tune2fs is "clean with errors", so i'm assuming I either need to unmount the volume and e2fsck it, or reboot and drop into maintenance mode and do itThere aren't any live samba shares off that volume, so i'm thinking I could do it without taking the server down, as this server is only for samba shares, which are on a different volume.Could someone tell me if I'm taking the right approach? I've never done unmounting and mounting before, but I've read it can be done manually without affecting how the volumes are mounted when a server starts. i'll have to look up the commands.
I have a dell PE1750 server which would not boot up after a power failure. I am thrown to a shell for maintenance after showing an error in file system check. The server was running - Red Hat Enterprise Linux AS release 3 (Taroon). Please let me know if I can try to recover from this error by booting from the 1st CD of a higher version of linux like RHEL5. I ask this because I do not have the old media with which the system was setup. Can the use of latest OS CD cause any problem?
If I do a "shutdown -rF now" on a server, it will force all volumes to be checked as it reboots.
My question is, which i can't figure out from reading the man pages for e2fsck and shutdown, is what switches does it use when it automatically runs an e2fsck on each volume? i'm assuming a -y since it never prompts, but what else? is it physically checking the entire disk for bad blocks, etc etc?
We had to reboot a server in the middle of a production day due to 99% iowait (lots of processes in deep sleep waiting for disk iops). That's never happened to us before. It had been 363 days since the last fsck, so it started automatically on reboot. It hung at 4.8% on a 2TB LVM2 volume for about an hour. I killed the fsck and rebooted the server. The second time, it went past that point and is currently at about 62%. First, what causes e2fsck to hang like that? Second, is there any danger in killing e2fsck, rebooting, and starting it again?
Other than when there are errors in the messages log or when you have file system problems, when should you e2fsck volumes? I have a lot of volumes that have 500GB to 1TB of data on them, and it takes quite a while to e2fsck them, so wondering if its something that should be done regularly, or only when there are actually problems.
Why does an e2fsck restart itself after a while, does it get to a certain number of errors than has to start over from the beginning? are there any tweaks or switches you can use to make it run more efficiently?
I have two volumes, both with 800GB total used on them. lets call them /vol1 and /vol2. /vol2 is just a cron'd rsync'd copy of a folder on /vol1 which is a live share for many users.If I temporarily suspend the cronjob doing the rsync's from /vol1 to /vol2, is it safe to unmount and e2fsck /vol2, then remount it somehow?
Both /vol1 and /vol2 say the filesystem state is not clean when i do a tune2fs -l on them both. According to tune2fs both will check themselves upon restart, but if I can do /vol2 since it isn't the live data beforehand, that will cut my downtime in half the next time i restart the server.But I also wonder that if I can do this, then i remount /vol2, will the "not clean"-ness of /vol1 just be rsync'd back over to /vol2 the next time the rsync runs?
I know if I do a shutdown -rF now, it will perform an e2fsck on all my volumes with the -y switch. But if I just want to check one of the volumes rather than all of them, and have it use the -y switch so it will automatically answer yes to everything, how can I do that?I'm using RHEL, and have a huge volume I need to run a check on, and I dont want to sit there for the next 24 hours hitting the Y key every time it finds a problem ;-)
If I umount both of them, can I run an e2fsck on each at the same time through 2 putty sessions, or will that not really gain me anything from doing them one after another?
I have a heavily used file server that I want to restart, then if it requires e2fsck's on any volume to run them after it restarts. The only problem is that the server is rarely rebooted, and they said it might kernel panic because its been so long. I've heard there's a way to have it go past the kernel panic if it does happen, but I'm not sure how to do that or the other stuff.If it was a Windows server, I would schedule a shutdown with the force switch, and have the chkdsk's already scheduled for each volume on reboot. But for RHEL, I really don't know.I'm hoping this can be done, so that way I can have it kick off at say 7am, then when I get in at 8am it will probably be near the end of the e2fsck's so I can see what's going on.
I want to perform an e2fsck with the y switch (so I dont have to answer yes to every question) on two volumes on a server the next time I restart it. I don't want to do a shutdown -rF because 1) I dont want to check the other volumes and 2) it seems when I do that, the e2fsck doesn't keep restarting itself over and over to fix all the problems. Seems like it runs once, then if it fails it drops you to the repair console in single user mode. I'd rather just have it start the check that will keep repeating over and over right away, because I know it'll take more than one pass.
If I issue a shutdown -rF now, it will force e2fsck's on all the volumes when it reboots. But once the checks automatically finish, does it restart normally? I want to run e2fsck's on all my volumes, but dont want to stay the probably 5 hours it will run, so hoping someone knows for sure what happens.
I have a 14TB raid, file system is read-only and I am trying to run e2fsck -B -p -C -v -y /dev/sdb1, it goes through, but fails and says bad block/inode or fails to transfer, something like that.Is there a way I can get this to run successful, this is a production storage server, its critical.
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 have Squeeze (2.6.32-5-686) installed on sda and have an additional disk sdb.For some reason 'dmesg' gives me always this message for sda1 (after a reboot):
Feb 14 12:29:03 arkiv-x kernel: [ 448.349949] EXT3 FS on sda1, internal journal Feb 14 12:29:03 arkiv-x kernel: [ 448.470411] loop: module loaded Feb 14 12:29:03 arkiv-x kernel: [ 448.653327] kjournald starting. Commit interval 5 seconds
My son's netbook with 10.10 netbook remix failed to boot. Using the Live install CD and Gparted I couldn't repair the EXT4 filesytem. The error reported was:
e2fsck : Device or resource busy while trying to open ...
After trying many solutions and web searching I decided to try a different live CD and tried Knoppix 6.4.4
Using the command interface I typed e2fsck -v -f -y /dev/xxxx (xxxx = your device). This worked first time and the machine rebooted without hesitation.
We have an old server running, and I decided to run fsck.ext3 -n on the disk to check it (while it was running). Turns out it reports lots of errors - not a good thing.
The weird thing is that when booting up a rescue cd and running fsck.ext3 on it, it says there are no problems with it. The filesystem is marked clean. Forcing a check with -f turns up nothing.
Now, when booting it from disk, fsck complains about an unclean file system that has not been checked for like 50000 days (obviously an error). Running e2fsck -n /dev/sda2 turns up errors again - not necessarily the same ones as the last time.
This makes me wonder: Can running e2fsck on a mounted file system cause errors? I ran with -n which is not supposed to do anything, just doing a read-only check. On the other hand, I heard checking a live file system might throw erros since the files being checked might change while bign checked, thus causing false positives.
Can the old version of e2fstools (1.38, approx 2005) mean non-existing errors are shown? Both the rescue cd and the system use this version.
In any case - why would the file system report errors on boot-up when the rescue cd just said it was ok? It should have been marked clean by now.
For laughs, I shut down the system and booted Knoppix which has a quite recent version (1.41.12, May 2010) of e2fstools. It showed no errors on the file system.
What do you think - are there errors or not on the file system?
The system is actually running Suse, but this is not about Suse specific things - just general Linux tools. And I use Ubuntu personally.
In this case what is the return value of mount. I want to run e2fsck only when either mount fails or mount succeeded but with errors . Is there some way to detect this situatin "mounting fs with errors" in code/script .
I had left a small windows partition for some programs like MS Office, (I'd failed to install it with wine :-( ) so I was dual booting OpenSUSE 11.3 & Vista. When I decided to replace Vista with Win 7, the grub was missing, I formated the Vista partition, then tried to boot into SUSE before installing win 7. there was some command line, that i tried the instructions I had found on the forums so I typed
grub find /boot/grub/menu.lst and I got (hd0,1) so I root (hd0,1)
[code]....
I got an error about missing (hd0,1), when I pressed enter I got a menu not the one I was used to. When I chose to boot OpenSUSE 11.2 or the failsafe I got error 17 "cannot mount partition" so found a bit of assistance from the following page: How to fix GRUB after Windows breaks it, and how to edit the GRUB menu - Super User when I press "e" and change root (hd0,1) to (hd0,2) then boot by pressing b, I get the usual SUSE boot screen, then the bootup process stops with some text displayed on the screen. there was a lot of text but the following is what I jotted down: the superblock could not be read or does not describe a correct ext2.
superblock corrupt e2fsck with an alternative superblock e2fsck -b 8193 fsck failed. Mounting root device read-only
I (through TeamViewer) helped my mother (who is in Spain) updating her laptop to 10.10. I was of course doing this while doing other things at work, and managed to replace the Grub installation. Now the machine won't boot. It stops in Grub Rescue.After having a look at the Grub Rescue Mode Megathread I made her type the command
Code:
ls
with the result that it only detects HD0
The previously mentioned thread then says:
Quote:
If all you get is (hd0) you most likely have a partition table or disk error. Seek assistance elsewhere! (fsck, e2fsck, TestDisk, etc.) It used to be (at least) two partitions on the disk, one with Win 7 and one with Ubuntu 10.04. I need to tell her (over the phone) to type in order to make the computer boot again? The laptop is, by the way connected to the Internet. Normally I am so careful when doing stuff like this, but today, I messed it up. And of course it had to be my 2500km's away mothers machine...
I have Ubuntu 10.10 installed (installed xubuntu on top and that is what I run but should not be an issue) on a laptop and it runs fine but I am giving it to my daughter so I wanted to install windows as well, and dual boot, so she could play a couple of games that she has. When I booted with gparted cd it shows the information icon beside my partition (have 2 one swap sda1 and one for ubuntu sda2) and everything I attempt to do tells me the superblock and all backups are bad. I am not sure how this can be since the system boots and runs fine.
In gparted I can't run dumbe2fs or e2fsck without getting the error but when I do dumpe2fs in the system it seems fine. I am pretty sure I used ext2 or ext3 as a filesytem as it is an older laptop so ext2 is what I usually run with. Maybe I just let ubuntu install whatever it wanted this time, I can't remember for sure which I chose during this install. have been backing up all the data to move it off anyway so reinstalling won't be a big issue. I had checked out how to reinstall grub2 after doing the windows install so thought I was all prepared but apparently I was not that prepared.
Recently installed Centos 5.6 in order to install Plesk on. Not familiar with Linux partitioning so left the default values at install with a few GB of unpartitioned space left free. Followed the instructions on the Plesk installation manual for adding a seperate partition for /tmp - [url]
Then later on I couldn't get in to the server locally via the GUI (which was already switched on), it just had a black screen so I powered the machine off. It then wouldn't boot back up. When it got to e2fsck I got a [Failed]. I also got the same message as in this thread.
I'm now at a remote location. When logging in as root and trying to run fsck to find and fix any disk problems a remote engineer has found that it won't unmount the partitions so I can't really run fsck on it. He's forced the machine to boot for me and I have SSH access but if I reboot the machine I'm quite sure I won't be able to get in again from here.
I have centos 5.2.....i get this error while booting...the total hard disk is about 1160 GB....This server is used for file share....it has lots of datas........is it recommended to run fsck.....i am afraid that i will lose datas....is there any way to sort this issue....logs and fstab details are as follows
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.
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?
Scenario:A - Local Unix machineB - socks proxy server port 1080C - remote mysql server port 3306I want to connect to the remote mysql server(C) from local unix machine(A) using sock proxy(B).
I want to run rsync on server A to copy all files from Server B when they are newer than 7 days.(find . -mtime -7) I don't want to delete the files on Server B.
