Software :: Filesystem Corruption - Ext3-fs Group Descriptor Corrupted - No Inittab
Mar 3, 2011
When I rebooted my system (RHEL 5.3 x86_64), I got the following error when it was booting up:
Code:
Full screenshot of the bootup error messages here: previous bootup error
So to try and fix this, I booted from the OS disk and did a linux rescue.
Here's some of the results of the commands I did:
Code:
Here's a screenshot of the output from fsck after it's done, notice it says 0 bad blocks but the system was modified:fsck results
I then reboot but now I get the errors:
Code:
Full screenshot of the startup errors I get now here: current bootup error
Does anyone have any ideas on how I can fix this? Was the fsck I did initially the correct thing to do to fix that initial group descriptor error or did I make things worse?
i have an external harddrive, hooked up by usb. /dev/sdb it came as a fat drive (sdb1). when i realized, i had copied 250 gb to it already. so, i made a new ext3 (sdb2) partition, copied the data from the fat to ext3, and then deleted the fat drive and moved the ext3 it with gparted. it mounted fine after it was moved, but after i tried to resize it, which didn't work, it will not mount.
I have been having problems with filesystem corruption on my eeepc 1000H for a long time now. I have tried using different filesystems, kernels and distributions (arch, slackware) to no effect. I am starting to grow suspicious that this problem lies somewhere else, as I haven't seen anyone else having similar problems in such a variety of scenarios.
I have tried testing my ram using memtest86+, didn't come up with anything after a full run through. I also have tried using e2fsck -c to check for bad blocks, it finds none. I had a go at using smartctl but wasn't really sure what I was doing. I did a long test and it came up with nothing anyway.
This problem is in addition to the problems I've been having with my intel graphics chip and KMS. A lot of the time there are lockups when booting into X, which can only be gotten out of by a hard reset. This is sometimes what causes the original filesystem errors. I've stopped messing around with KMS for now to eliminate this but my current system in unbootable. I'm guessing my disk is wrecked but have as yet seen no definitive proof. Can anyone recommend anything that I should do?
I am currently on ext4 with a custom kernel 2.6.33-rc6 (the stock kernel shipping with slackware does not have the elantech extension for psmouse included). When I was using arch, I was just using the stock kernels.
I have been using CentOS 5. for around 3 months. It was all fine and was having a pleasant experience using CentOS. Today when i turned on my computer and booted CentOS i am having the below error: Grub comes up, allows me to select CentOS 5.4 kernel image. and displays RedHat Nash version: and then the below error occurs:
I've been tasked with fixing a Red Hat system that dies with a kernel panic during the boot stage:
Code:
EXT3-fserror (dev sda1): ext3_check_descriptors: Inode bitmap for group 4 not in group (block 67239937)! EXT3-fs: group descriptors corrupted! mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
I can boot into a Rescue CD, but I'm a bit out of my element because I don't use EXT3 myself, and I've never had to repair a corrupted file system before.
I'm COMPLETELY new to linux. I"m running Ubuntu 9.10 and TRYING to install Devede. I have tried the Terminal, Synaptic Manger, and the Add/Remove and still keep getting this same error. I'm running a regular 32 bit Pentium 3 process to test if I like Linux or not. this is what it says: E: /var/cache/apt/archives/libavcodec-extra-52_4%3a0.5+svn20090706-2ubuntu3_i386.deb: corrupted filesystem tarfile - corrupted package archive this is not a DUAL boot computer either.
I have a problem, my filesystem seems to show random corruption. For example:
[Code]....
This has happened to many files, they suddenly contain random garbage. Fsck seems to say the filesystem contains no errors I tried to run it multiple times.
While trying to boot into the normal user the system aborts the login and tells me that /home does not have write permission.
The login manager gives:
Code:
If I log in as root and do a
Code:
Or to open some files, it works and no problem seems to exist.
All this happened for the first time after running luckybackup to fusion the old files of one home directory under EXT4 with the new files from my notebook (ext3, Opensuse 11.1 KDE3) in order to come to a unified home. But then the system did not boot any more. I tried to change the owner but some files did not have write access (not even as root, "the file does not exist"). So I thought I might have a a file system problem.
So I thought: unmount the /dev/sdb1 and then do a fschk on it. Runs and was perfect. So I did run it with forcing to control inode per inode.
No error.
So I thought: you screwed up the system. I then decided to reinstall OpensSuse11.3 from the scratch and create the same user for home. I formatted the rest (/swap /boot /root) and left only /home. Installation runs brilliantly, all ok, it comes to the login..................
I have a problem, my filesystem seems to show random corruption. For example:
[code]...
This has happened to many files, they suddenly contain random garbage. Fsck seems to say the filesystem contains no errors I tried to run it multiple times.
I'm trying to RMA a month old SSD, and they're giving me a hassle about it. The drive currently seems to work just fine, but I'm 95% sure that a few blocks went bad and corrupted some data about a week ago. I was able to mostly recover the data and correct for the bad blocks, but I don't really trust the drive anymore.
I'm running an up to date Debian Squeeze install with ext4 on this drive. My system started doing some bizarre things, to the point that it was unusable, so I rebooted it. As it was booting up, it complained about needing an fsck, which found dozens of non-trivial errors that it was mostly able to fix. It then proceeded to boot normally, except the drive mounted itself as read only (due to errors). Another fsck turned up a similar number of problems. This happened a couple of times before I ran fsck with '-c', which is supposed to scan for and work around bad blocks. That seemed to fix the problem, it hasn't given any more problems since then.
The manufacturer is refusing to RMA the drive unless it's completely unmountable right now this minute, saying that it was a one time problem that could have been caused by anything. Am I right in thinking that the problem has to have been with the drive if 'fsck -c' fixed it, or could something else be going on? If it was the drive, am I somehow being unreasonable in asking for a new one while the current one is "working"?
I am using Ubuntu since release 8.10, but it is first time when i can`t solve problem
when i tried to create new NTFS partition on unallocated disk space with Paragon Partition Manager (damn, that was stupid). Process was aborted with error (later i finally made it with Gparted without problems)
After reboot mine Ubuntu say:
Code: Errors were found while checking the disk drive for /
Press F to attempt to fix errors, I to ignore, S to skip mounting or M for manual recovery. I pressed "F" but that had help only for a boot and doesn`t really fix error :`(
Later i booted from liveCD and had checked partition (/dev/sdb1; file system - ext3) with gparted (result - aborted fixing process with error) Now i can`t even boot from that partition and even mount it from other linux system.
I have a second HD partitioned and formated to EXT4, the whole capacity. It was mounted to a directory in my home folder I'm getting an error that it cannot be mounted.
Running "dmesg | tail" i get this: (rigt now the HD is connected to the computer using a USB adaptor)
I'm hoping, now that I've recovered my partition tables, how to rebuild my LVM volume group. The trouble is that one of the volumes lost its partition table, and after rebuilding the table, LVM can no longer identify the drive. I'm trying to rebuild the 'fileserver' volume group.
pvscan produces the following: Couldn't find device with uuid 'jsZAMq-LSa1-87Zb-WoGs-oi6v-u1As-h7YZMl'. PV /dev/sdc5 VG dev lvm2 [232.64 GiB / 0 free] PV unknown device VG fileserver lvm2 [1.36 TiB / 556.00 MiB free] PV /dev/sda1 VG fileserver lvm2 [1.36 TiB / 556.00 MiB free] Total: 3 [2.96 TiB] / in use: 3 [2.96 TiB] / in no VG: 0 [0 ]
I'm trying to install a package (mythTV backend - but im sure the package is not at fault) and I keep getting this errorcorrupted filesystem tarfile - corrupted package archiveNew build - ubuntu lucid 32bitI think it might be a hardware fault memory/hardrive/motherboard or somthing to do with an error in /home/ partition filesystem.To be honest im not sure and its driving me mentalWould consider anyones input on possible causes of a Corrupted filesystem. Tried complete deleting (including cache) and reinstalling the package.force fskchk , restarted = nothing.Error checked the harddrive = nothingfrustrated as this is only the latest error in a series of problems ive been having with ubuntu on this build.
I've searched the internet all over, but somehow I didn't find a solution (I REALLY hope there is one :/). Of course I might have missed something, I found a lot of similar, but not quite identical problems.Today, when I tried to start up my system I was quite shocked, as my Ubuntu 10.10 didn't boot. The error I got was "No init found. Try passing init=bootarg".I didn't have any problems booting Windows XP, which I had installed alongside Ubuntu, so I burned a Live CD and tried to find out what was the matter.
As it appears, my Linux partition (/dev/sda5) is broken. I can't access it via Nautilus, as I always get a "A job is pending on /dev/sda5" error. Mounting it via terminal doesn't seem to work either.When trying to check the filesystem, either in Disk Utility or in GParted, I instantly get an error that the "device is busy" and (again) that "a job is pending".I tried to set a boot flag on /dev/sda5 (it wasn't there before), but this didn't help neither with accessing the partition from the Live CD norI tried to run the boot info script I found somewhere in a forum post, but it is just hanging itself up as soon as it starts checking /dev/sda5.
And "sudo mke2fs -n /dev/sda5" just gives me a "/dev/sda5 is apparently in use by the system" error.By the way I did all these steps just byollowing advices in other threads, so I do not necessarily understand what I did there.e .. is there a way I can get my files back? I would really, really hate having lost all that since my last backup is 3-4 months old (yeah, yeah, I know) and I have some quite rtant data on that filesystem.While there seems to be a big problem in that NOTHING seems to be working, GParted still recognizes the partition and how much of the disk space is in use .. so not everything can be lost - or am I wrong?
My filesystem crashed/corrupted. When i start my machine i see the following messageTarget filesystem doesn't have /sbin/init.No init fount. Try passing init= bootarg.BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built in shell (ash)Enter 'help' for a list of build in commandsAfter googleing, found that i need ti run fsck on my partition (/dev/sda5)I used a Livecd and logged in the single user mode and tryedfsck /dev/sda5But i get fsck.ext4: Device or source busy while trying to open /dev/sda5Filesystem mounted or opened exclusively by another program?When i do lsof | grep sda5I see
When installing fedora 10 from scratch on an acer aspire one 150L, which filesystem should be used? ext2 or ext3? a basic explanation of the reason would be great too.
I was running ubuntu as a live cd and I wanted to format my pen drive into an ext3 filesystem. I put in sudo mkfs /dev/sda1, but know im thinking that sda1 was my HDD!! I removed the cd from my computer, and it wont boot up into windows anymore!The only thing that is giving me hope is that the mkfs took about 1 min to format whatever it was formatting (my pen drive or my hdd!!) and my hdd is 500gb big. Is there anyway that I could have accidentaly formatted my HDD?
I run an upgrade and an update on a lucid lynx beta 2. --- got no problems. but about the filesystems i have some questions because it seems for me that at every system boot the system will run an fsck. somtimes it's shown up, somtimes not. but in /var/log/messages and in syslog
I have always following messages ( occured in beta 2 too ).
But first before i continue - here my disk layout:
And here my filesystem types:
This is my problem because those values are seems to be static ! ( note: this partiton is mounted but not in use ) and last not least: the drive is an external usb scsi disk. but on the other side lucid lynx is running fine on my box.
I was looking in a dir I haven't used for a while (I use it for data storage) and found a directory was repeated - that is, two directories with the same name. I renamed one of them, on the assumption that one of them has a non-printing character in its name, and that worked without a problem, but ls -i lists their inodes as the same. ls -l says they both have two inodes (. and ..), and the files they contain have the same names. The inodes of the files is the same (that is, the inode of a file in dir A is the same as the file of the same name in dir B.) Each file in each dir is listed as having only one inode, but it's the same as that in the other dir.
I'm wondering if anyone knows what will be Squeeze's default filesystem. Will it be the proven ext3 or the newer (sometimes faster, sometimes slower) ext4?
I currently have ext4 and I have nothing to complain about. In fact, my overall experience has been very positive. Ext4 is definitely faster when fsck runs during boot.
What would be the cons of having ext4 as default in Squeeze?
I've ran fsck -c on the (unmounted) partition in question a while ago. The process was unattended and results were not stored anywhere (except badblock inode). Now I'd like to get badblock information to know if there are any problems with the harddrive. Unfortunately, partition is used in the production system and can't be unmounted.
I see two ways to get what I want: Run badblocks in read-only mode. This will probably take a lot of time and cause unnecessary bruden on the system. Somehow extract information about badblocks from the filesystem iteself. How can I view known badblocks registered in mounted filesystem?
I have a external HDD with eSATA and USB connectors available. I want to use this HDD to store my backups. The HDD should be encrypted (my main system is as well).
So here is what I did so far: 1) I used the following code to create the encrypted LUKS partition with EXT3 Filesystem: Code: cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/sdb1 cryptsetup luksOpen /dev/sdb1 luks mkfs.ext3 /dev/mapper/luks The system always hang when I executed the "mkfs.ext3..." command, so I switched the HDD from eSATA to USB and then it worked fine.
2) When I switched on the ext. HDD the first time, the drive was recognized automatically and Nautilus asked for the password. I typed it in as checked the checkbox to remember the password in the future. For the backup I use a nice script that I found in another forum, where I can define a mountpoint and then the script will check for previous backups and only make a incremental backup based of the latest version. The script also mounts the drive automatically. In order to always have the same mountpoint, I want to make an entry in the /etc/fstab using the UUID of the ext. HDD.
Whatever I tried, it doesn't work. What am I doing wrong? Here is my current /etc/fstab Code: # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # / was on /dev/mapper/ubuntu-root during installation UUID=2ea47421-73ce-4c66-9606-8a1db81ae640 / ext3 relatime,errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=dbdeb793-1d4e-43ea-8986-7b37fdbc9674 /boot ext3 relatime 0 2 # /home was on /dev/mapper/ubuntu-home during installation UUID=42702091-83e6-43eb-aad1-108f43eedf9d /home ext3 relatime 0 2 # swap was on /dev/mapper/ubuntu-swap during installation UUID=e225bcf9-908b-4226-a963-6b02ee658df1 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 # Eintrag wegen iPhone none /proc/bus/usb usbfs devgid=125,devmode=666,nodev,nosuid,noexec 0 0 # external HDD UUID=913977f7-8fa6-416f-af79-b5f913b68f53 /media/backup-hdd ext3 noauto,users 0 0 I made the "none /proc/bus/usb..." entry because it was recommended to ensure correct behaviour of the iPhone. Not sure if I need it though.
I created the mountpoint with this command: Code: sudo mkdir /media/backup-hdd Now it seems the mountpoints owner is not root - strange right? Code: 2 4 drwxr-xr-x 3 michael michael 4096 2010-01-15 02:45 backup-hdd How should I mount this drive correctly? It will be automounted as every USB device, but that should not be the case. I want the script to mount and unmount the drive.
I just got a new hard disk so that my "/" and "/home" partitions would be located at their own separate drives. All was well until i tried to expand my "/home" partition to fill up the entire drive that used to also have the "/" and swap partitions on there. Let me sketch the before-and-after scenario in GParted,
Before:
What actually happened after:
Gparted gave an error prompt after which i found out that the entire ext3 partition (/home) had been moved to the left but not yet expanded to the right, which is of course not a problem. However, for some reason it has labelled the entire ext3 partition as a swap partition!
I'm still running ubuntu from the usb flash drive, because i dont want to risk that the (120GB) swap area will actually be used and cause my data to be lost.
I guess my question is, can i relabel the swap partition as ext3 like it was before without formatting (ie without losing data)?
Here's the output of "fdisk -l", which doesn't show the swap area (the drive in question is "/dev/sdb"):
I have installed ubuntu to my pc. i made 3 partitions. one for system, one for data and one for swap. two of them were ext4. after some time i have reinstalled ubuntu again. but this time i didn't put to format the second partition, but just mount it using ext4. after that i cannot open my files. checked with gparted shows that 2GB used, but with df 188MB. and in properties writes ext3/ext4 filesystem. i used chown, chgrp but didn't help. please help, these data are ver important. i cannot lose them.
We have 3 RH5u4-64 servers. Server 1 is a standalone server. Servers 2 & 3 are clustered filesystem servers running Veritas CFS 5.0mp3.
Server 1's filesystem is EXT3 and was cloned from a Sun server running Veritas 5.0mp3-VXFS. Filesystem size returned from 'du' 'df' show about 428GB on both the Linux Standalone Server(EXT3) & the Sun Solaris Servers (vxfs).
We then cloned Server 1's filesystem (EXT3) to the 2-node CFS servers. Cloning was successful, but the filesystem sizes returned by 'du' 'df' show 128GB. Block Size for the EXT3 filesystem is 4k while blocksize for the VXFS filesystem is 1k.
Where did that other 300GB go?
I can see VXFS/CFS being slightly more efficient than EXT3 because it's been around much longer, but that can't possibly account for the vast difference.
