similar to: run fsck manually

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

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

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

Hello, We are running units in the field that are headless. Sometimes we get units returned that we when we boot them up have some type of filesystem inconsistency that the default preen doesn't fix but running fsck -y does. I want to eliminate the -p (preen option) and always do the -y option anyone know where to make this change? Thanks, -- Stephen Clark *NetWolves* Director of

hi , guys: when i reboot the server today ,the screen displays this ; --------------------------------------------------------------------------------------- Setting hostname xxx [OK] Your system appears to have shut down uncleanly Press Y within 1 seconds to force file system integrity check... Checking root filesystem /dev/VolGroup00/LogVol 00: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

For those who haven't seen my several previous postings about problems with this (now not quite so) new PC, I have an ASUS P5N32-SLI Deluxe motherboard. The boot drive and primary filesystems are on an SATA disk and I'm having no problem with that. However, I recently plugged in a couple of IDE drives salvaged from my old PCs and I'm running into trouble with one of those. The drive

Hello, Yesterday evening this box crashed and, for once, ext3 was not able to recover automatically. There was an "unexpected inconsistency inode xxxxx has imagic flag set" error and the system would not boot. I fscked from my rescue disk and I guess 20 or 30 errors were fixed by me just selecting "y" at the prompt. The system then booted and, so far as I can tell, the only

Dear All My server got inconsistency from sudden power cut that I fixed it with #fsck -fvy /dev/hda at the maintenance prompt . But after reboot, one of the installed applications is preventing it from booting up (as can be seen in the boot up process list). Can you please let me know how can I remove it from the boot up list to reach the root user prompt and then re-install it again ? Thank you

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:

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

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

Hi there, I am newbie and recently started using btrfs. Now facing a weird problem. FWIW, I am on archlinux, kenel v3.8.0, having Btrfs v0.20-rc1. After an abnormal reboot, getting these errors while boot: systemd.fsck[289]: checking extents systemd.fsck[289]: checking fs roots systemd.fsck[289]: checking root refs systemd.fsck[289]: found 23728128 bytes used err is 0 systemd.fsck[289]: total

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

Robin, To me, anyone else includes the kernel of the current node. Well, if it is unclear the man page should be revised. Also a big warning message on ocfs2.fsck would be nice, after all we all make mistakes. But this is only my two cents. Running fsck on any journaled filesystem will replay the journal. This will cause corruption if the filesystem is mounted read/write, even if the

Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.

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}

Box with Redhat 7.1 and kernel 2.4.20 has a hardware RAID (about 750 gigs data) attached via an Adaptec 29160 LP card... I began seeing numerous SCSI errors in my logs for our external hardware RAID and input/output errors on test attempts to copy files via cp. Rebooted and immediately saw the errors as the disk was initially accessed by the Adaptec driver. The RAID controller did not

I usually shutdown computer for night (could probaly use software shutdown, but have not yet studied it). In that case, the disk is checked quite often with default settings, usually in those cases I am in hurry and want computer to start up fast :-). One alternative would be trying to run fsck at shutdown if fsck is due in a few mounts. One could abort that if one wants computer to shutdown

In the last month - definitely after going to 5.5 - I've tried to fsck a drive (340 days, or some such, unchecked). 960G RAID 5, I *think*, possibly serial port attachment to a JetStore RAID array. Every time I try, it gets to 70.0%, and stops. As in, I left it run last night, having started it late afternoon, and around 23:00, it was still exactly there, not even .1% more. On that, I also had

I am working on a Red Hat 7.2 system which has been upgraded to the 2.4.9-13 kernel RPMs. The my machines has RPM e2fsprogs-1.23-2 installed but the upgrade from ext2 to ext3 was done manually rather than accepting the offer in the 7.0 to 7.2 upgrade. I did this by running tunefs2 -j on two partitions. I have had some problems following the instructions in the ext3-usage.html