Всем добрый день! Oc Ubuntu server 10.04. Создан JBOD рейд из 4 Sata дисков по 160 ГБ. Отформатирован в ext4. Но есть две проблемы:
1)Вывод команды mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.
2)И fdisk ругается на таблицу раздела md0
Показать
255 heads, 63 sectors/track, 14593 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: 0x000b0215
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4377 35154944 83 Linux
/dev/sda2 4377 14346 80077824 83 Linux
/dev/sda4 14346 14594 1986560 82 Linux swap / Solaris
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 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: 0xda45406c
Device Boot Start End Blocks Id System
/dev/sdb1 1 19457 156287328+ fd Linux raid autodetect
Disk /dev/sdd: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 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: 0x0008bc28
Device Boot Start End Blocks Id System
/dev/sdd1 1 19457 156288321 fd Linux raid autodetect
Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 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: 0x000b750f
Device Boot Start End Blocks Id System
/dev/sdc1 1 19457 156288321 fd Linux raid autodetect
Disk /dev/sde: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 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: 0x000cc169
Device Boot Start End Blocks Id System
/dev/sde1 1 19457 156288321 fd Linux raid autodetect
Disk /dev/md0: 640.2 GB, 640155648000 bytes
2 heads, 4 sectors/track, 156288000 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Хотя в cat /proc/mdstat написано что рейд активен
Показать
md0 : active linear sdd1[2] sdb1[0] sde1[3] sdc1[1]
625152000 blocks 64k rounding
unused devices: <none>
Если проверить каждый из дисков входящий в рейд, то все вроде бы ок!
Например mdadm --examine /dev/sde1Показать
Magic : a92b4efc
Version : 00.90.00
UUID : d44b8049:a1a29d83:858fc05d:7d43c95e (local to host teoserver)
Creation Time : Tue May 22 16:21:39 2012
Raid Level : linear
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Tue May 22 16:21:39 2012
State : active
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : c1651df4 - correct
Events : 1
Rounding : 64K
Number Major Minor RaidDevice State
this 3 8 65 3 active sync /dev/sde1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 33 1 active sync /dev/sdc1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 65 3 active sync /dev/sde1
Информацию о рейде занес в /etc/mdadm/mdadm.conf командой mdadm --examine --scan >> /etc/mdadm/mdadm.conf
Показать
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This file was auto-generated on Tue, 08 May 2012 13:48:05 +0300
# by mkconf $Id$
ARRAY /dev/md0 level=linear num-devices=4 UUID=d44b8049:a1a29d83:858fc05d:7d43c95e
Как можно решить данные проблемы?