starting udev:
setting hostname localhost.localdomain: [ ok ]
Setting up Logical Volume Management: WARNING: Duplicate VG name VolGroup:EnIWaZ-hSPA-A4UL-sMnG-TtH8-VI19-GUisUH (created here) takes precedence over g6XttY-3r1M-1vn7-96mA-1jmk-vtI8-YuUPf7
WARNINGuplicate VG name VolGroup:EnIWaZ-hSPA-A5UL-sNnG-TtH8-vI19-GUisUH(created here ) takes percedence over g6XttY-3人M-1vn7-96mA-1jmk-vtI8-YuUPf7
device-mapper:createi哦春天里failed: Device偶然resourcebusy
device-mapper: create ioctl failedevice or resource busy
1 logical volume(s) in volume group "Volgroup" now active
WARNING: DUplicate VG name VolGroup: EnIWaZ-hSPA-A5UL-...............
device-mapper: create ioctl failed : Device or resource busy
3 logical volume(s) in volume group "VolGroup" now active
[ FAILED ]
checking filesystems
/dev/mapper/VolGroup-lv_root: clean, 88768/3276800 files, 837477/13107200 blocks
/dev/sda1:clean, 38/128016 files, 44823/512000 blocks
/dev/mapper/VolGroup-lv_home: clean,11/1310720 files, 126289/5242880 blocks
fsck.ext4: No suck hile or driectory while trying to open /dev/mapper/VolGroup-lv_mylvm
/dev/mapper/VolGroup-lv_mylvm:
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 32fsck with an alternate superblock:
e2fsck -b 8193 <device>
[ 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 mintenance
(or type Control-D to continue):
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-may-2010)
/dev/mapper/VolGroup-lv_root: cleam,80768/32768000 files, 847477/13107200 blocks
e2fsck 1.41.12 (17-may-2010)
/dev/sda1:clean, 38/12016 files, 44823/51200 blocks
e2fsck 1.41.12 (17-may-2010)
The filesystem size (according to hte superblock) is 13107200 blocks
The physical size of the device is 5242000 blocks
Either the superblock or the partition table is likely to be corruypt!
Abort<y>? yes
e2fsck 1.41.12 (17-may-2010)
fsck.ext4:No suck file or directory while tering to open /dev/mapper /VolGroup-lv _mylvm
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 sqap or ufs or something else),then the superblock
is corrupt,and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>