Этот вопрос является продолжением моего оригинала. Ситуация заключается в том, что хост с одним жестким диском должен быть клонирован на жесткий диск большего размера по сети.
Я провел несколько тестов удаленной передачи данных clonezilla live с жесткого диска емкостью 500 ГБ на жесткий диск 1000 ГБ. Второй тест завершился и создал загрузочный диск (CentOS-6), но когда я загружаюсь с нового диска, я получаю следующее:
checking filesystems
/dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000
blocks
/dev/sda1: clean, 47/120016 files, 80115/512000 blocks
/dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks
/dev/mapper/vg_voinet01-LogVol04: clean, 770219/20480000 files,
34881086/8102000 blocks
fsck.ext4: Bad magic number in super-block while trying to open
/dev/mapper/vg_voinet01-lv_log
/dev/mapper/vg_voinet01-lv_log
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 alternate superblock:
e2fsk -b 8193 <device>
/dev/mapper/vg_voinet-lv_spool: clean, 372/614400 files, 171186/2457600 blocks
*** 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 maintenance
(or type Control-D to continue):
** CRITICAL SYSTEM ERROR **
Unable to generate MOTD
The /usr/sbin/fwconsole file is not accessible
You are likely to experience significant system issues.
[root@voinet09 ~]# ll -d /usr/sbin/fwconsole
lrwxrwxrwx 1 root root 31 Nov 26 2016 /usr/sbin/fwconsole ->
/var/lib/asterisk/bin/fwconsole
[root@voinet09 ~]# ll -d /var/lib/asterisk/bin/fwconsole
ls: cannot access /var/lib/asterisk: No such file or directory
[root@voinet09 ~]# ll -d /var/*
ls: cannot access /var/*: No such file or directory
В загруженной клонированной системе я получаю:
df
File system 1-Kblocks Used Available Use% Mounted on
/dev/mapper/vg_voinet01-lv_root
64376668 5057124 56042744 9% /
/sec/sda1 64376668 5057124 56042744 9% /boot
vgs;lvs
File-based locking initialisation failed.
File-based locking initialisation failed.
fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cyclinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002860e
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 60002 4878733536 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Disk /dev/mapper/vg_voinet01-lv_root: 67.1 GB, 67108864000 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000000
Disk /dev/mapper/vg_voinet01-lv_swap: 4143 MB, 4143972352 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff
Disk /dev/mapper/vg_voinet01-LogVol04: 335.5 GB, 335544320000 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000000
Disk /dev/mapper/vg_voinet01-lv_home: 3355 MB, 3355443200 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000000
Disk /dev/mapper/vg_voinet01-lv_spool: 67.7 GB, 68719476736 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000000
Disk /dev/mapper/vg_voinet01-lv_log: 10.1 GB, 10066329600 bytes
255 heads, 63 sectors/track, 8150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000000
Я пробовал это:
mke2fs -n /dev/mapper/vg_voinet01-lv_log
. . .
Superblock backups stored on blocks:
32768, 90304, 163840, 229376, 294912, 819200, 884736, 1605632
e2fsck -b 32768 /dev/mapper/vg_voinet01-lv_log
The superblock could not be read or does not describe a correct ext2
. . .
e2fsck -b 90304 /dev/mapper/vg_voinet01-lv_log
The superblock could not be read or does not describe a correct ext2
. . .
e2fsck -b 163840 /dev/mapper/vg_voinet01-lv_log
e2fsck: Invalid argument while trying to open /dev/mapper/vg_voinet01-lv_log
The superblock could not be read or does not describe a correct ext2
. . .
Значения суперблока после 90304 всегда давали ошибку недопустимого аргумента в дополнение к ошибке суперблока. Как мне продолжить?