similar to: machine with many filesystem errors

I just came back after being out for the evening. Apparently there was a power failure long enough to discharge the UPS completely on my Linux box. After powering back up, I received notice that the / filesystem needed "manual fsck"ing. I booted off CD and attempted to fsck. Unfortunately, everything I've tried has proved futile and I'm _desperate_ for some help. I've

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

Hi, I have a 20GB partition on a hard disk that just developed bad blocks. Fortunately, I had backups for the most important data on it, but I'd like to recover some files that were too large to backup. When running 'e2fsck /dev/hdc3', I get the following message: e2fsck 1.27 (8-Mar-2002) Group descriptors look bad... trying backup blocks... e2fsck: Invalid argument while checking

Hi, I just converted all my hard disk filesystems from ext2 to ext3. This worked perfectly fine for all non-root fs, but I am having trouble converting the root fs, too. Here's what I did: 1. rebuilt my kernel (2.4.20, x86) with ext3 support linked in statically - no module. 2. Added a journal file to my root fs using 'tune2fs -j'. 3. Added 'rootfstype=ext3' to the

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 /

Hi folks, I've been trying to get WINE to run on my new mandrake 8.0 box for _four_ _months_. Every version of WINE gives me: err:dosfs:DRIVE_ReadSuperblock The filesystem is not FAT !! (device=/dev/hda1) when I try to run an app that opens/closes files (e.g. notepad.exe). Software that doesn't use files runs fine (calc.exe) I can read/write to the partition /dev/hda1 just fine...

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

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

I have a project that disk imaging from a cd using isolinux and a dialog gui system, but some users want to setup systems to run automatically. Some can download the development kit, and built an image with a modified script, but others don't have the skills or resources. I've come up with a system that seems to work with both the isolinux.cfg or menu.lst with grub4dos and I believe

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hi I got a strange error, happening on two of my ext3 partitions. What can be wrong? And why does e2fsck error out, instead of displaying an error message? Best regards keld fsck /dev/hda6 fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning... fsck.ext3 for device /dev/hda6 exited with signal 11. also From my dmesg: <1>general protection fault: e7a8 [#3] Modules linked in:

Hi! I have a question about filesystems. I'm running a fairly recent version of WINE from CVS on RH7.1 (Kernel 2.4.6). I have Win98 installed for on a partition. I user WINE to run Quicken2001 and Word97. When I'm running Word, I click on the 'open file' button, a get a message: err:dosfs:DRIVE_ReadSuperblock The filesystem is not FAT !! (device=/dev/hda1)

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) ====================================================================

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11,

Hi all- I corrupted my filesystem by not doing a RTFM first... I got an automated email that the process monitoring the SMART data from my hard drive detected a bad sector. Not thinking (or RTFMing), I did a fsck on my partition- which is the main partition. Now it appears that I've ruined the superblock. I am running Fedora Core 6. I am booting off the Fedora Core 6 Rescue CD in

I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to performance problems with Arkeia Network Backup and AIT-4 tape drives. The backup database is stored on a v4.2 created ext3 partition. When accessing this partition after the downgrade, Centos complains on boot that fsck.ext3: Filesystem has unsupported feature(s) (/dev/sda5) *fsck: Get a newer version of e2fsck! [fail] If I

Hello. I am having a problem with one CentOS 4 box I have installed. It worked perfectly for several days, was used as a gateway on my LAN. After having reached the limit of the disk size by copying stuff from a windows box to a samba shared drive on the centOS box, and after making a reboot, the server didn't come up anymore. Looking at it I was thrown to the repair console and when doing

I had a power-fail this morning, and when I rebooted, /etc/rc.d/rc.boot issued a 'mount -n -o remount,ro /' and then a 'fsck -A -V -a -C'. The fsck failed on my root partition. I know why it failed. It called fsck.ext2 . My root poartition is ext3. My question is, why did it call fsck.ext2? Another question, why was it checked at all? My /etc/fstab contains: /dev/hda1 / ext3

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > I hope this is the right list. I have created an ext2 filesystem and > removed the dir_index feature. I don't know if this kind of experimentation > is going to help me learn something about filesystems or not. Well what is > dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I >

I am familiar with using dd to create a disk image. dd if=/dev/hda1 of=myimge.img However, is there a way to capture the entire disk image into a file. I have 3 partitions: hda1 / hda2 swap hda3 /home and mbr How can I wrap them all into 1 image file. Thanks, Jerry