Hi, I have used installed a centos 4 distribution in my PC for a few months which was quite good. However, the system failed to start last week and shown the following message on startup: //---------------------------------------------------------------------------------- booting 'CentOS (2.6.9-5.0.5.EL)' root (hd0, 0) filesystem type is ext2fs, patition type 0x83 kernel /vmlinuz=2.6.9-5.0.5.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1400, size=0x15cbd4] initrd /initrd-2.6.9-5.0.5.EL. img [Linux-initrd @ 0xfdfb000, 0xeee2bd bytes] Uncompressing Linux.... ok, booting the kernel. audit(1119364802.006:0): initialized Red Hat nash version 4.1.18 starting File descriptor 3 left open reading all physical volumes. This may take a while.... /dev/hdc: open failed: No medium found /dev/hdd: open failed: No medium found Found volume group "VolGroup00" using metadata type lvm2 File descriptor 3 left open 2 logical volume(s) in volume group "VolGroup00" now active File descriptor 3 left open EXT3-fs: unable to read superblock mount: error 22 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! //---------------------------------------------------------------------------------- I have tried to 1) linux rescue 2) skip mounting and go to command prompt 3) enable lvm and tried fsck for the volumes (one is empty volume? and another failed) 4) run fdisk to list devices 5) fsck.ext3 the devices or the LVs 6) run fsck again and specify the superblock number as suggested (from the prompt and "mke2fs -n /dev/hda2) but all failed for /dev/hda2 Fyi, I remember I have choosen to put everything (except /boot) under / during linux installation and the file system is ext3. I really want my data recovered. Please help. The actual screen dump is as below. Thanks, VOA ------------------------------------------------------------------------ #lvm vgchange -ay 2 logical volume(s) in volume group "VolGroup00" now active #lvm pvscan PV /dev/hda2 VG VolGroup00 lvm2 [76.56 GB / 32.00 MB free] Total: 1 [76.56 GB] / in use: 1 [76.56 GB] / in no VG: 0 [0 ] #lvm lvscan active '/dev/VolGroup00/LogVol00' [76.03GB] inherit active '/dev/VolGroup00/LogVol01' [512.00 MB] inherit #fdisk -l device boot start end blocks id system /dev/hda1 * 1 13 104391 83 linux /dev/hda2 14 10011 80308935 8e linux LVM #fsck -f /dev/VolGroup00/LogVol00 fsck 1.35 (28-Feb-2004) WARNING: couldn't open /etc/fstab: No such file or directory e2fsck 1.35 (28-Feb-2004) fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00 Could this be a zero-length partition? #fsck -f /dev/VolGroup00/LogVol01 fsck 1.35 (28-Feb-2004) WARNING: couldn't open /etc/fstab: No such file or directory fsck: fsck.swap: not found fsck: Error 2 while executing fsck.swap for /dev/VolGroup00/LogVol01 #e2fsck /dev/VolGroup00/LogVol00 e2fsck 1.35 (28-Feb-2004) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00 Could this be a zero-length partition? #e2fsck /dev/VolGrup00/LogVol01 e2fsck 1.35 (28-Feb-2004) couldn't find ext2 superblock, trying backup blocks.... e2fsck: bad magic number in super-block while trying to open /dev/VolGroup00/LogVol01 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 alterate superblock: e2fsck -b 8193 <device> #fsck.ext3 /dev/hda1 e2fsck 1.35 (28-Feb-2004) /boot: clean, 38/26104 files, 15417/104388 blocks #fsck.ext3 /dev/hda2 e2fsck 1.35 (28-Feb-2004) couldn't find ext2 superblock, trying backup blocks.... fsck.ext3: bad magic number in super-block while trying to open /dev/hda2 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 alterate superblock: e2fsck -b 8193 <device> #e2fsck -b 8193 /dev/hda2 e2fsck 1.35 (28-Feb-2004) e2fsck: bad magic number in super-block while trying to open /dev/hda2 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 alterate superblock: e2fsck -b 8193 <device> #mke2fs -n /dev/hda2 mke2fs 1.35 (28-Feb-2004) max_blocks 4294967295, rsv_groups = 0, rsv_gdb = 1024 Filesystem label = OS type: linux block size=4096 (log=2) fragment size=4096 (log=2) 10043392 inodes, 20077234 blocks 1003861 blocks (5.00 %) reserved for the super user first data block=0 maximum filesystem blocks=20971520 613 block groups 32768 blocks per group, 32768 fragments per grup 16384 inodes per group superblock backs stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 ****** i have tried all the alternate blocks, but the results were them same********************* #e2fsck - b 32768 /dev/hda2 e2fsck 1.35 (28-Feb-2004) e2fsck: bad magic number in super-block while trying to open /dev/hda2 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 alterate superblock: e2fsck -b 8193 <device> #mount -o errors=continue /dev/hda2 /sysimage mount: Mounting /dev/hda2 on /sysimage failed: device or resource busy #mount -o errors=remount-ro /dev/hda2 /sysimage mount: Mounting /dev/hda2 on /sysimage failed: device or resource busy #mount -o errors=continue /dev/VolGroup00/LogVol00 /sysimage mount: mounting /dev/VolGroup00/LogVol00 on /sysimage failed: invalid arguement #mount -o errors=continue /dev/VolGroup00/LogVol01 /sysimage mount: mounting /dev/VolGroup00/LogVol01 on /sysimage failed: invalid arguement #mount /dev/VolGroup00/LogVol01 mount: cannot read /etc/fstab: no such file or directory 相片電郵測試版一個郵件就可以傳送過百張相片! -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list