Hi folks,
I am running redhat linux 9(Kernel 2.4.20-8) server on Intel P4 system, with Western Digital ATA 40GB Hard Disk(WD400EB-00CPF0, ATA DISK).
This server is acting as Firewall & Gateway. Running squid & vsftp for local users.
When i power on my system this morning , it shows below message (and as per message i run "fsck /dev/hda" without any argument/switch.
For your information i have added "fdisk -l" & "df -h" (All output prior to system CRASH).
NOTE: i've added /var/log/messages output of 13-04-05 at the END of mail.
Checking root filesystem /============================= 49% /: Inodes that were part of a corrupted orphan linked list found.
/:UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (i.e without �a or �p options)
[FAILED]
*** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell Give root password for maintenance (or type Control-D to continue):
(Repair filesystem)1# fsck /dev/hda1 fsck 1.32 (09-Nov-2002) e2fsck 1.32 (09-Nov-2002) Couldn�t find ext2 superblock, trying backup blocks� Fsck.ext2: Bad magic number in super-block while trying to open /dev/had The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck �b 8193 <device>
#fdisk �l
Disk /dev/hda: 40.0 GB, 40017485312 bytes 255 heads, 63 sector/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Block Id System /dev/hda1 * 1 13 104391 83 Linux /dev/hda2 14 2563 20482875 83 Linux /dev/hda3 2564 2628 522112+ 82 Linux swap /dev/hda4 2629 4865 17968702+ f Win95 Ext�d (LBA) /dev/hda5 2629 4865 17968671 83 Linux
[root@localhost root]# df -h Filesystem Size Used Avail Use% Mounted on /dev/hda5 17G 7.8G 8.4G 49% / /dev/hda1 99M 5.0M 89M 6% /boot /dev/hda2 20G 17G 1.6G 92% /home none 121M 0 121M 0% /dev/shm
Any suggestion how to recover damaged filesystem (here it�s EXT3)?.
Thanks in advance.
Regards, Navneet Choudhary
=====================#tail -300 /var/log/messages|more= [root@localhost root]# tail -300 /var/log/messages|more Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329827840 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329831936 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329836032 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329840128 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329844224 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329848320 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671 Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #19401 47 contains a hole at offset 1329852416 Apr 12 13:06:38 localhost kernel: attempt to access beyond end of device Apr 12 13:06:38 localhost kernel: 03:05: rw=0, want=1098730844, limit=17968671
Apr 12 13:06:38 localhost kernel: EXT3-fs error (device ide0(3,5)): ext3_readdir: directory #1940147 contains a hole at offset 1329856512
=================EOF=================================
__________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250
Navneet Choudhary" <gnu_navneet@yahoo.com wrote:
(Repair filesystem)1# fsck /dev/hda1 fsck 1.32 (09-Nov-2002) e2fsck 1.32 (09-Nov-2002) Couldn't find ext2 superblock, trying backup blocks. Fsck.ext2: Bad magic number in super-block while trying to open /dev/had The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
I think you are trying to run e2fsck on an EXT3 fs. Just try to run 1. fsck /dev/hda1 2. fsck /dev/hda2 3. fsck /dev/hda5
after booting your system( if it still boots ) into init 1 if not boot into rescue mode using the Redhat 9 cd and run the above commands. try your luck. If it is not a hardware fault ( bad sectors in HDD ) and is able to recover it. You may be up and running in 10 mins.
rgds,
rc