hi all,
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i am hitting following filesystem check error messages :
******************************************************
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
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 think 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
/boot
(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 of windows server or kernel configs missing or how to solve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i am hitting following filesystem check error messages :
******************************************************
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
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 think 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
/boot
(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 of windows server or kernel configs missing or how to solve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal