Виртуалка на Xen созданная когда-то через xen-create работала, работала, а после перезагрузки Dom0 перестала грузиться, померла ФС и не лечится никак. Что с этим можно сделать?# mount -o loop disk.img /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# tune2fs -l disk.img
tune2fs 1.42.5 (29-Jul-2012)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 52e27524-ea2f-4d5e-9f09-a805aed0566c
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 262144
Block count: 1048576
Reserved block count: 52428
Free blocks: 936221
Free inodes: 254279
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 255
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Mon Jun 3 15:29:56 2013
Last mount time: Mon Jun 3 15:29:58 2013
Last write time: Tue Sep 17 10:40:31 2013
Mount count: 1
Maximum mount count: -1
Last checked: Mon Jun 3 15:29:56 2013
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: dc648614-c666-43c8-be63-b04c8e1492cc
Journal backup: inode blocks
# fsck.ext3 -pf disk.img
disk.img: Superblock has an invalid journal (inode 8).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
disk.img: Group descriptor 0 marked uninitialized without feature set.
FIXED.
disk.img: Note: if several inode or block bitmap blocks or part
of the inode table require relocation, you may wish to try
running e2fsck with the '-b 32768' option first. The problem
may lie only with the primary block group descriptors, and
the backup block group descriptors may be OK.
disk.img: Block bitmap for group 1 is not in group. (block 1026)
disk.img: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
# fsck.ext3 -y disk.img
Group descriptor 28 marked uninitialized without feature set.
Fix? yes
Block bitmap for group 29 is not in group. (block 524301)
Relocate? yes
Inode bitmap for group 29 is not in group. (block 524317)
Relocate? yes
Inode table for group 29 is not in group. (block 530976)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
Group descriptor 29 marked uninitialized without feature set.
Fix? yes
Block bitmap for group 30 is not in group. (block 524302)
Relocate? yes
Inode bitmap for group 30 is not in group. (block 524318)
Relocate? yes
Inode table for group 30 is not in group. (block 531488)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
Group descriptor 30 marked uninitialized without feature set.
Fix? yes
Block bitmap for group 31 is not in group. (block 524303)
Relocate? yes
Inode bitmap for group 31 is not in group. (block 524319)
Relocate? yes
Inode table for group 31 is not in group. (block 532000)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
Group descriptor 31 marked uninitialized without feature set.
Fix? yes
disk.img contains a file system with errors, check forced.
Resize inode not valid. Recreate? yes
Pass 1: Checking inodes, blocks, and sizes
Inode 2 is in extent format, but superblock is missing EXTENTS feature
Fix? yes
Journal inode is not in use, but contains data. Clear? yes
Inode 131080 has an invalid extent
(logical block 0, invalid physical block 10004373, len 1)
Clear? yes
fsck.ext3: e2fsck_read_bitmaps: illegal bitmap block(s) for disk.img
disk.img: ***** FILE SYSTEM WAS MODIFIED *****
e2fsck: aborted
disk.img: ***** FILE SYSTEM WAS MODIFIED *****
Вариант для распечатки
