Redhat 9 Server Recovery -HELP
Navneet Choudhary
navneetkc at gmail.com
Wed Apr 13 10:46:56 UTC 2005
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).
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/hda
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 at 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
+91 98103 93403
More information about the redhat-list
mailing list