similar to: DomU goes into fsck error at boot up.

Hey all, Had a power failure and subsequent ext3 disk corruptions. Attempting to fix, but not working. Its a 120 gig IDE disk, 3 partitions. /boot, /, and swap. Basically can't boot up since the box can't get to the system files in /usr/ or anything. So I'm booting off of a FC2 disk 1 in recovery mode and trying to fix the filesystem with e2fsck The boot partition cleaned up

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your

Guys, The other day while working on my old workstation it get frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh install. It seems that the

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

Hi all, On my slackware 7.1 system, in rc.S fsck is started. In fstab there's the following line: /dev/hda2 / ext3 defaults,noatime 1 1 from the readme I figured that I should put the line append="rw rootflags=journal=102" in lilo.conf The system boots up, but I get the error message that the root partition is already rw. Should I just skip the filesystem

Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ====================================================================

Can anyone point me in the right direction for correcting errors on an HD when using LVM? I've tried e2fsck and indicates bad block. I've tried with -b 8193, 16384, and 32768 and no good. I've found some info about reiserfsck on google, but this utility doesn't seem to be included in Centos4.3. I did find it on my old FC1 box. I am thinking now I really should have went with

Guys, The other day while working on my old workstation it got frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) -------------------------- /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh

While I untar a large archive on xfs , ext3 (ver 1.3 and ver 1.4) file systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while untarring. The same tar file when untarred on a i386 machine works properly. ERROR: -------------- tar: Skipping to next header gzip: stdin: invalid compressed data--crc error tar:

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'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.

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, 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