2008/12/7 Per Jessen :
Per Jessen wrote:
PaPa NoeL wrote:
I had no /etc/mdadm.conf so I wrote it myself from the example in
/usr/share/doc/package/mdadm.
No success.
I tried the assemble option: no success.
Uh, you tried 'mdadm --assemble' and it didnt work?? Which errors
messages did you get?
It says something weird about the file system on md0 and md1 such as
it's formated in ext2.
I've just checked the mdadm man page, and it seems the procedure for
creating a RAID10 is not what I thought - it looks you can do with a
single "mdadm --create -n4 -l10" - you probably need to try that.
Sorry about confusing the issue, I was certain a RAID10 was created in
two rounds.
/Per
--
/Per Jessen, Zürich
Here are the logs:
DMESG:
Adding 2104472k swap on /dev/sda1. Priority:-1 extents:1 across:2104472k
md: md0 stopped.
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
md: bind<sdc>
md: bind<sdb>
md: raid1 personality registered for level 1
raid1: raid set md0 active with 2 out of 2 mirrors
md: md1 stopped.
md: bind<sde>
md: bind<sdd>
raid1: raid set md1 active with 2 out of 2 mirrors
md: md3 stopped.
bootsplash: status on console 0 changed to on
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
IA-32 Microcode Update Driver: v1.14a
powernow: This module only works with AMD K7 CPUs
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:02.0 to 64
[drm] Initialized i915 1.6.0 20060119 on minor 0
warning: `ntpd' uses deprecated v2 capabilities in a way that may be insecure.
atl1 0000:02:00.0: eth0 link is up 1000 Mbps full duplex
NET: Registered protocol family 17
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
Before mounting md3:
(none):/ # more /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdd[0] sde[1]
732574464 blocks [2/2] [UU]
md0 : active raid1 sdb[0] sdc[1]
732574464 blocks [2/2] [UU]
unused devices: <none>
Assemble commande:
(none):/ # mdadm --assemble /dev/md0 /dev/md1
mdadm: device /dev/md0 already active - cannot assemble it
Creating my way!
(none):/ # mdadm --create /dev/md3 --chunk=64 --level=0
--raid-devices=2 /dev/md0 /dev/md1
mdadm: /dev/md0 appears to contain an ext2fs file system
size=1465148800K mtime=Sun Dec 7 16:08:08 2008
mdadm: /dev/md0 appears to be part of a raid array:
level=raid0 devices=2 ctime=Sun Dec 7 16:34:04 2008
mdadm: /dev/md1 appears to be part of a raid array:
level=raid0 devices=2 ctime=Sun Dec 7 16:34:04 2008
Continue creating array? y
mdadm: array /dev/md3 started.
(none):/ # cat /proc/mdstat
Personalities : [raid1] [raid0]
md3 : active raid0 md1[1] md0[0]
1465148800 blocks 64k chunks
md1 : active raid1 sdd[0] sde[1]
732574464 blocks [2/2] [UU]
md0 : active raid1 sdb[0] sdc[1]
732574464 blocks [2/2] [UU]
unused devices: <none>
The mdadm --examin command: No output. but changes the conf file.
(none):/ # mdadm --examine --scan >/etc/mdadm.conf
(none):/ # more /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=f8046dc0:05c37635:7fcbf47e:4ac21441
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=c36ae49b:699da7bc:a4f43e27:6aca9070
ARRAY /dev/md3 level=raid0 num-devices=2
UUID=132f9525:5eea8007:9884fa3f:17c9560b
I have rebooted and it works fine now, I think it's the mdadm
--examine --scan >/etc/mdadm.conf that sort it out!
Will the 'mdadm --create -n4 -l10' make any difference from this configuration?
best Regards,
El PaPa NoeL
N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�Z+i�b�*'jW(�f�vǦj)h���Ǿ��i�������