I am hosting a few customer servers now, all of which are virtual machines running on a CENTOS 5.x host. Each Centos host has a couple of extra drives. When I formatted them ext3 they automatically had a schedule of a full forced fsck after 6 months. Do I really need to do that check regularly? It results in a fairly large outage since my disks are each 1TB and there are up to three extra drives on each server. I try to reboot these servers every 6 months but this part adds a large amount of time to a routine reboot.
I had a server with CentOS 5.5 and Asterisk fail today most likely due to the power failure. I guess the stupid electrician turned the power ON and OFF multiple times while changing the burned out fuse without unplugging the PBX. It was set in CMOS to power back on when there is power outage so my two HDDs which were set in RAID-1 now shot.
Trying to start the system and it goes through some check and fixes and then tells me to do Ctrl+D or enter password and run fsck. I have tried both methods and I don't think they yeild anything.
Ctrl+D reboots and same store again with the system fixing and asking me to Ctrl+D again. Putting the password and doing "fsck -y" gives many errors and it fixes it and then it just keeps looping. I am afraid this is making it worst than better. So, after few loops I did few more restarts and just give up. Took out the HDDs and installed new ones and install CentOS+Asterisk so business runs as usual on Monday.
However, I am kind f*ked if I don't get the files out of these HDDs. This is my first time using fsck and also encountering this type of a problem. What is the normal procedure when fixing inodes misplaced in a case like this? and what should I do to at least be able to grab my files?
I have already connected one of the drives to Windows and used Disk Internals (which maps Linux drives) but I see only folders with no contents except for /tmp/ which has contents. While the HDDs were in the system I could actually browse files and they were fine. I am really keen to get the drives fixed but I am also afraid that bad usage of fsck might replace lots of files and burn it all.
I am running 9.04 Server (standalone). It had been running fine since I installed in last autumn. Upon reboot, fsck of the root filesystem was forced and it hangs at the same point (16.5%) every time. I was able to break out somehow with cntl-alt-del but the boot was to a read-only filesystem. So I couldn't disable the forced fsck. Instead, I tried to fsck there. It started, but hung. I couldn't do e2fsck -v as it needed the device and, although I worked on UNIX systems for decades, I am not familiar with the /dev/mapper stuff.
Looking at other threads, all involving the desktop GUI Ubuntu, I tried some of the suggestions. Went into the BIOS to see what I could disable. I killed the serial port and similar. (Some said that onboard modems interfered with the checks in /dev.) I also tried to boot from my original installation disk. That does work.The suggestion is to choose "Try without any change to your computer". The problem is that is not available on the server installation, apparently only the desktop (GUI). I had install, check CD for defects, test memory, boot from first hard disk, and something like repair or recover a broken disk. I started the last of them, as it seemed to be the only option. It failed because it couldn't get a dhcp address. I could manually configure it (as it is hard addressed anyway), but I didn't want to start screwing up configurations not knowing where it was going, whayt it would ry to do, and risk losing months of hard work.
Without help, I think I will be forced to install the OS on a second drive, use that install to fsck the original filesystem on the original disk, edit the fstab (or whichever has the config) on the original disk to disable fsck, and return to the original boot.I am building this server for a nonprofit and have put in many hours writing mysql/perl apache cgi code for them as a free service and hate to lose it all and set back everything.
I am attempting to run a fsck on a number of large ext3 filesystems. I am doing this proactively because I want to minimize reboot time and the filesystems are past the interval time of 6 months. When I run the command " fsck -f -y device" I get the following error on all of the filesystems-
fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) fsck.ext3: Device or resource busy while trying to open /dev/mapper/mpath0p1
Is it possible to run fsck on the root file system? My Ubuntu 10.04 seems to be checking it's fs at boot... It shows that the file system is in use and can get severely damaged! Or the only possibility is to run it from a live CD?
I've got a system that has given me problems since day one. It's my oldest kids computer and she seems to open about twenty tabs in Firefox. The computer will freeze and she'll manually hold down the switch to reset. I've instructed her to please stop shutting it down manually but kids never listen.So anyway the thing reboots into initramfs. Seems unable to do anything with the hard disk. Now heres where I run into problems. In the past I've removed the drive and put it into one of my other Ubuntu boxes then ran fsck. fsck always recovers the journel quickly and I pop it back in and all is well.First question or situation if you will. I have tried left and right to get fsck to work from the livecd. If I let the livecd boot up and open a terminal fsck /dev/sda1 comes back with device or resource busy. Apparently the livecd get stuck automounting and causes problems.
I'm really tired of putting this thing in another box. I tried downloading knoppix but it wouldn't burn off for some reason. I've tried booting into rescue mode, but that seems to be missing from the livecd these days?Can I boot into single user mode somehow? Kill off some process that is causing the resource to be busy? I'm thinking once I maybe flagged the drive as dirty and had it clean itself on reboot.. will the livecd pick up on that?ok.. so thats the first situation.. second is upon recently fsck doesn't fix the problem. The drive recovers just fine, but after using the computer for a short while the drive will somehow magically mount as read only.. and then programs will freeze and shutting down is hard to do.
I would like to know if there is a way to do an unattended check on the root file system on my servers, *and* send emails in case of errors.
I know you can schedule a root file system fsck during boot time - but the root file system will be mounted read-only - so if fsck finds any problems - it can't email away a warning, or write the result to a file - or can it?
Essentially I would like my servers to do a self-check of the root file system periodically - and to email me if it fails. I just can't think of a way to get it done.
I have a 2TB file-system and when the machine reboots it fails the fsck, halts and goes into maintenance mode.Stats: I have have RHEL 5, 2.6.18 kernel, the file-system is an ext3. The file-system is on an EMC AX4 connected with fiber channel HBA.So far my reading tells me this should work because under 2.6 4TB is OK. Any ideas why this fails?If I take it out of the fstab file and mount it manually the boot is OK and the file-system behaves well. I can change the fsck check option in the fstab to 0 but I don't think I should have too. Everything I read says that 2TB ext3 file-systems are OK.
I have a serious problem in booting centos 5.4 x86 as shown in the attached picture.I tried to backup before using fsck command, but I could not make a backup of damaged lvm on hard drive.First I made a rescue centos at virtualbox, and installed centos 5.4 x86 on virtual hard disk.And I attatched damaged hard drive. S I can see this damaged hard drive's lvm as attached picture.Please let me know how to backup my files and to use "fsck.ext3 --rebuild-tree using livecd".
I'm running an Acer Aspire 1830T-3721 dual-booting Windows 7 with Ubuntu 10.10 (Desktop).
Background: So first I dropped my laptop a couple feet while Windows was running. The laptop immediately shut off and then tried to boot. Booting Windows results in an unfortunate "Windows has encountered a problem communicating with a device connected to your computer. The error can be caused by ... faulty hardware ... Status: Oxc00000e9 Info: An unexpected I/O error has occurred." But Ubuntu booted fine, and could access my NTFS files fine, so I was trying to work on the problem from there. I try a few utilities, looking at the partition table, etc without actually applying any changes.
Then I run a fsck on the drive. It loudly warns me that if I continue on a mounted drive, then I'm going to mess things up. In a moment of stupidity I push on, thinking that surely it would ask me for more configuration, or confirmation, before actually starting. The fsck runs for about 1 second before I Ctrl-C it, running some preliminary stuff and then just starting pass 1.
After this, Ubuntu won't boot anymore. Instead, it hangs just after the init-bottom script runs. If I boot with init=/bin/bash, I can get to a shell, and see that my file system is still there, but not sure what else to do.
I've been running off of a SysRescCD LiveCD, from which I've looked at the drive with testdisk. Testdisk reports that "the hard disk seems too small" while showing me the partition table.
I ran a fsck on the Linux partition; it fixed a bunch of things. There has been no apparent effect on the boot behavior.
I can access all my files, back them up, and reinstall Ubuntu, but I'm hoping there's a better solution, perhaps one that will also help me repair my Windows installation (but I'm looking at one problem at a time here).
16GB RAI've been running the Debian-based Proxmox VE on it for six months or so with no problems.Today I loaded Centos 5.5 x64. During a reboot, the file system crashed and fsck couldn't repair.I loaded it again, did all the updates, and loaded my applications. On about the third reboot, it crashed again and fsck couldn't fix it.I don't really know where to begin. I doubt seriously that any hardware has went bad since yesterday.
I have Ubuntu 9.10 installed on my HP desktop, but I'm running an older version (8.10) on a live CD so I can at least get online to ask for some When I tried to log on earlier it went to a command prompt and said the 'file system check failed' and to run fsck manually. I entered 'sudo fsck' at the prompt and I selected "y" to fix all the bad inodes, when it was complete it told me to restart, I then entered 'sudo restart' at the prompt and it said 'sudo uuid unknown'. I have not installed anything recently and I'm not sure what to do.
I have a problem partitioning an Hard Disk Drive on a server, and I hope someone can help me with this. Here is the system configuration: Operating System Linux localhost.localdomain 22.214.171.124-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Hardware: RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
The system mounts one hard disk (120 Gb) with the OS, and four 1.5Tb Hard Disks mounted on RAID 10 for a total of ~3 Tb I need to create several partitions on this RAID drive, but I have some trouble doing it. I need a total of 10 partitions of different sizes:
I've installed Debian Lenny from USB with the small 8MB netboot image. I only chose "Standard system" in Tasksel during install, to get a clean, minimal install. I also chose for LVM and a separate partition for /home. I have one 1.5TB SATA drive in this machine.
Now everything seems to install just fine, but when I reboot I get the following error:
fsck.ext2: No such file or directory while trying to open /dev/sdb1
I get offered to enter a maintenance shell, or press CTRL-D to resume booting. When I do, the system boots fine and nothing seems wrong. But it is inconvenient, because I can't reboot the machine without physically going to it to press CTRL-D on the keyboard
I have googled for this error and it is mentioned on several forums, but they were all related to other things specific to their installs/machines.
(ps. the only slightly strange thing during install is that the Debian installer included my 1GB USB thumbdrive when it shows all the drives and the partitions before formatting. I removed the USB thumbdrive directly after install, but if I plug it in, I still get the error)
These are the errors during boot: code....
I've only installed Debian on my laptops, which never had any problems.
just start Ubuntu 9.04 said: File system chek failed a long is beging saved /var/long/fsck/checkfs if that location is writable Please repair the file systmen manually A maintenance shell will now be started Ctr+ D terminate this shell and resume system boot. Give root password for maintenance or type Control +D to continue. I did Ctr+D , and after login said , that can not find /home. I starte with the live cd:
I have my drives set to run fsck on boot up. This is the default setting for Fedora but if there is a problem it prompts me to run fsck manually. Is there a way to have Fedora just run fsck and fix any errors it finds on boot up?w in Debian distros you can put FSCKFIX=yes in the /etc/default/rcS file to do this. But I can't find the equivalent on Fedora.
I forced a fsck on the next boot by.Code: sudo touch /forcefsck.Where did the results go?/var/log/fsck/checkfs and /var/log/fsck/checkroot both read "(Nothing has been logged yet.)" Am I to assume that if there are no errors nothing is written to the log files?
Every 32 boot ups, the fsck runs automaticall on my drives.Iould like it to run at shutdown and was looking for a solution.I saw an app call autofsck but not find it in synaptic.Can someone help me find a solution to this. I am running a laptop with 9.10 and a desktop with 8.10.
I go to bed and my computer is fine and working. I come home from work, no signs of a power outage, and my computer has errors regarding a corrupt disk. Drops to Cmd prompt. My problem is that I want to do the proper recovery on it, and my googling doesn't seem to help. All I see is stuff about how FAST fsck is, but no one wants to talk about how to use it. Besides, I better check with people before I mess everything up.
I have the FC12 install disk I used loaded up now, at the cmd prompt. I have my system mounted, an EXT4 LVM. Do I unmount and then run fsdk.ext4 -fp /dev/mapper/vg_mysys-lv_home ? (lv_home is the one reported as corrupt during boot)
I am using bootchart to investigate the slow booting of ubuntu 10.04 and I found that fsck process is called every time in the booting for around 5 seconds even the screen does not show any hard disk checking, is that normal ?