similar to: unattended reboot/fsck

Hi how can i do this? i have a headless server that i want to do fsck but i know fsck need human intervention how can i make fsck to select yes in all questions. -- Regards, Mark Quitoriano, CCNA Fan the flame... http://www.spreadfirefox.com/?q=user/register&r=19441 -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey folks, I searched the list archives and found this : echo "AUTOFSCK_TIMEOUT=5" > /etc/sysconfig/autofsck echo "AUTOFSCK_DEF_CHECK=yes" >> /etc/sysconfig/autofsck http://lists.centos.org/pipermail/centos/2006-November/029837.html http://lists.centos.org/pipermail/centos/2009-September/thread.html#81934 Will this do all disks? I want to do a reboot of a couple

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are

Hello, This may be a slightly rambling and inexpert question from point of view of the learned folks on this list - feel free to go and read something more interesting, but I am curious and a little alarmed about a recent event. I am running Linux from Scratch ("LFS"), under a locally compiled Kernel 2.4.20 (SMP). The root filsytem was created as ext2 and converted to ext3 with an

Hi Guys, I have a xen set up with two domu VM''s. One of these VM has recently crashed and was running lot of web services. When I tried to xm shutdown and xm create -c domainname, it directly starts fsck and ends up with the following: INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd[    2.724077] udevd version 125 started . Synthesizing the initial hotplug

On 2015-01-07, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > Of course, the other possibility is simply that you've formatted your > own filesystems, and they have a maximum mount count or a check > interval. If Les is having to run fsck manually, as he wrote in his OP, then this is unlikely to be the cause of the issues he described in that post. There must be

Dear Ted, I upgraded e2fsprogs and util-linux to the latest versions, as per the instructions on the "ext3 for 2.4" page, to make the switching between ext2-only and ext3-enabled kernels seamless. Now that if the filesystems have not been unmounted cleanly, due to a power failure for example, "fsck -A -a" cannot continue after checking the root filesystem on reboot, issuing

Hi, Is it possible do have fsck to run automatically [without operator intervention], if it was not a clean shutdown. Right now, somebody has to bring a monitor & keyboard and say Y, if not it will not run and verify the drive. This is for remote headless servers. -- Thanks http://www.911networks.com

Dear All My CentOS server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings : #fsck -s /dev/hda3 But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

Hi, we have CentOS ftp server (vsftpd) which has a lot of users who are writing and reading a lot of small files from/into its own accounts (and other servers - using samba client - are reading these files and putting them into outside database). Since this server is under heavy load its availability is important. >From time to time we "crash" this server (don't ask why ...) but

Hi All. I have a CentOS server: CentOS 5.6 x86_64 2.6.18-238.12.1.el5.centos.plus e4fsprogs-1.41.12-2.el5.x86_64 which has a 11TB ext4 filesystem. I have problems with running fsck on it and would like to change the filesystem because I do not like the possibility of running long fsck on it, it's a production machine. Also I have some problems with running fsck (not enough RAM, problem with

Hi, can anyone give me an example of when an fsck would repair something that the ext3 driver would not? with full "data=journal" journaling, would fsck ever need to be run if all the partitions were ext3? the ext3 mini-howto refers to "certain rare hardware failure cases (e.g. hard drive failures)" that would require a filesystem check, but doesn't go into details.

Hey! I have some RHEL6 hypervisors and the VMs are in raw qemu image files in a local raid array linux raid + lvm + ext3. When a kernel update is installed a reboot is necessary, usually it has been more than 180 days since the last reboot and the file system is fsck'd and this takes 2-3 hours. I am curious to know if there is any documentation that addresses the pro's and con's of

Hello Everyone, I just ran fsck.ocfs2 on /dev/drbd0 which is a one gig partition on a vm with limited resource (100meg of ram). I am worried that the process crashed because it has not responded in the past hour or so? fsck.ocfs2 /dev/drbd0 fsck.ocfs2 1.6.4 [RECOVER_CLUSTER_INFO] The running cluster is using the cman stack with the cluster name ASTCluster, but the filesystem is configured for

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Thanks for a great file system! I have a two-node cluster working as a HA NFS server. This system has worked fine for almost a year, but recently I found that an ocfs2 file system had been corrupted and needed to be repaired with fsck.ocfs2. Even though I don't think that any data was lost I found that 4 of my 14 ocfs2 partitions had some errors which were corrected by fsck.ocfs2. I then

I'm trying to do an fsck on an ext3 partition but I'm seeing abysmally slow disk throughput; monitoring with "dstat" (like vmstat) shows ~1200-1500KB/s throughput to the disks. Even with 24hrs of fsck-ing I only get ~3% (still in pass1). The filesystem is ext3 running "e2fsck -C0 /dev/sda3" and about 3.7TB on an x86_64-based system with 4GB RAM. e2fsprogs is 1.41.9.

Hello I have a newbie question, given a centos 5 installation, An 5 very large disk arrays ( 2.5Tbytes each ) - Is there a way to suspend or stop the fsck during the boot up? The system seems to pick the most inopportune time to decide to reach the check count limit... and with this many disks, a reboot takes several hours... which is an eternity when your boss is looking over your shoulders

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from