Find the answer to your Linux question:
Results 1 to 3 of 3
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Checking root filesystem fails

    hi all,

    I am running a CentOS base VM on top of Hyper-V server.
    When i added SCSI controller(earlier it was ide controller) support with new kernel and install them in VM after reboot, i am hitting following filesystem check
    error messages :
    ************************************************** ****
    Setting hostname hostname:
    Checking root filesystem
    The superblock could not be read or does not describe 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>

    : No such file or directory while trying to open /dev/hda2

    *** An error occurred during the filesystem check.
    *** Dropping you to a shell; the system will reboot
    *** When you leave the shell.

    ************************************************** ***
    Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :

    (Repair filesytem) 1 # mount
    /dev/hda2 on / type ext3 (rw)
    proc on /proc type proc (rw)

    (Repair filesystem) 1# cat /etc/mtab
    /dev/hda2 /ext3 rw 0 0
    proc /proc proc rw 0 0

    (Repair filesystem) 1# df
    Filesystem 1K-blocks used Available Use% Mountedon
    /dev/hda2 4%

    I thin for all above command there should be /dev/sda2 instead of /dev/hda2.

    Also my fstab , and fdisk -l looks like ok for me.
    (Repair filesystem) 1# cat /etc/fstab
    LABEL=/ / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    LABEL=swap-xvda3 swap swap defults 0 0

    (Repair filesystem) 1# fdisk -l
    Device Boot Start End Block Id System
    /dev/sda1 * 1 49 98535 83 Linux
    Partition 1 does not end with cylinder boundary.
    /dev/sda2 49 19197 39062500 83 Linux
    Partition 2 does not end with cylinder boundary.
    /dev/sda3 ......
    Partition 3 does not ......
    /dev/sda4 ......
    Partition 4 does not end ....

    (Repair filesystem) 1# e2label /dev/sda1

    (Repair filesystem) 1# e2label /dev/sda2

    (Repair fielsystem) 1# ls /dev/sd*
    /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4

    (Repair filesyatem) 1# ls /dev/hd*
    ls: /dev/hd*: No such file or directory

    Kindly suggest any configuration or kernel configs missing or how to solve this issues

    Many many thanks for your reply. Please ignore any spelling mistakes because it is hand written.

    thanks & Regards,

  2. #2
    Linux Guru Lakshmipathi's Avatar
    Join Date
    Sep 2006
    3rd rock from sun - Often seen near moon
    Try running
    fsck.ext3 /dev/sda2
    when it dropped you to the shell
    First they ignore you,Then they laugh at you,Then they fight with you,Then you win. - M.K.Gandhi
    FOSS India Award winning ext3fs Undelete tool Online Linux Terminal

  3. #3
    Running fsck.ext3 /dev/sda2 or fsck.ext3 /dev/sda1 will/might resolve this temporarily but I am just looking for root cause of this problem?


  4. $spacer_open

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts