Dotaz: Druhý HW RAID fedora 3

[latis]

Zdravím,

mám takový neskutečný problém, na fedore 3 bezi jeden raid pro ATA disky (md0, md1, md2)

včera jsem poridil SATA disky (raid edition) s HW RAIDEM do PCI. V Raid configuration tools jsem nastavil mirroring a nabootoval do fedory.

Jenze zaboha nevim jak vytvorit /mountnout onen druhy RAID  set (md3,md4,md5?)

Bohuzel jsem ten prvni raid netvořil, tak ani nevim kde a jak se to da konfigurovat. Jedinné co jsem našel je konfigurák raidtab, ve kterém je právě ten první raid.

Může prosím někdo poradit? Předem díky

Odpovědi

[Mti.]

nepises podrobnosti, ale ....

• fedora 3 je dost stara - podporuje tu kartu vubec?
• ta karta ... neni to jen siditko? (s cenou do 2000 bych necekal nic "HW")
• moc HW raid radicu neznam (pouze adaptecy a mylexy), ale ty  urcite nepouzivaji md zarizeni. (osone preferuji sw raid, pokud opravdu neni potreba  "specialnich" vlastnosti hw raidu)

Jestli trpis 2. bodem, tak to je obycenjny sata radic...a v tom pripade se vykasli na to siditko a pouzij softwarovy raid, co umi linux sam i bez "polochytreho" radice. Usetris si nervy. Nastroje, ktere budes potrebovat jsou fdisk a mdadm.

[gtz]

Zdravím , bez výpisu z dmesg těžko něco radit , kolik disků jste přidal ? a md3-md4-md5 to jste tvořil kde ? Pokud jde  o hw raid pak by se pole mělo tvořit přímo řadičem  - rozdělit , u některych  řadičů Intel , je problém s aktivací pole.Pokud na HW layeru vytvořím 3 svazky (virtuální disk jakoby ) pak v systému ho vidím jako standardní disk SCSI. Kouknul bych se do výpisu dmesg , popř, do lspci zda vůbec poznal kartu ... ? zaváděl jste nějaké moduly ? Pro mountnutí nic netřeba , ale pro vytváření musíte říct systému co a jak je na raidu - na FC3 raidtab. Raid se vytvářel pokud si dobře pamatuju přes mkraid.

Chtělo by to více informací

[latis]

Zdravím, tak abych upřesnil, připojil jsem 2 sata disky do noveho pci radice (ted nevim koli presne stal - ale typuju tak do tech 2000) a najel do te utility co nabizi radic po probehnuti posttestu, tam jsem vytvoril raid1 - mirroring a vypl utilitu. pak jsem najel a badal na servru v raidtabu.. jenze tam uz jeden raid je vytvoreny (na servru jiz bezi raid z ata disku cca 20gb -> ty tam chci zatim nechat).

Ted kdyz se divam do lspci tak mi ten raid hlasi jako unknown device

00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02)
01:04.0 RAID bus controller: CMD Technology Inc: Unknown device 3114 (rev 02)
01:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:09.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
 

takze jsem asi v pasti ,tu je jeste vypis z dmesg:

usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 08:42:20 Dec  1 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1d.0
PCI: Sharing IRQ 11 with 00:02.0
PCI: Sharing IRQ 11 with 00:1d.3
PCI: Sharing IRQ 11 with 01:04.0
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0xc000, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.1
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0xc400, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 9 for device 00:1d.2
PCI: Sharing IRQ 9 with 00:1f.1
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0xc800, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.3
PCI: Sharing IRQ 11 with 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
PCI: Sharing IRQ 11 with 01:04.0
PCI: Setting latency timer of device 00:1d.3 to 64
usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Found IRQ 5 for device 00:1d.7
PCI: Setting latency timer of device 00:1d.7 to 64
ehci_hcd 00:1d.7: Intel Corp. 82801EB USB2
ehci_hcd 00:1d.7: irq 5, pci mem d0058000
usb.c: new USB bus registered, assigned bus number 5
ehci_hcd 00:1d.7: enabled 64bit PCI DMA
PCI: cache line size of 128 is not supported by device 00:1d.7
ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 8 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,0), internal journal
Adding Swap: 522040k swap-space (priority -1)
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.

 

Pokud mate nekdo nervy, zkuste napsat strucny postup jak byste to resili.. predpokladam ze jedine pres ten mkraid jelikoz se mi nedari stahnout mdadm pro FC.
 

 

[Zdenek]

Hmm, ten dmesg je hlavne o USB, co takhle sem pastnout cio to vypise o diskach?

[latis]

PCI: PCI BIOS revision 2.10 entry at 0xfb9f0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge
PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0
PCI: Found IRQ 9 for device 00:1f.1
PCI: Sharing IRQ 9 with 00:1d.2
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Detected PS/2 Mouse Port.
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 00:1f.1
PCI: Found IRQ 9 for device 00:1f.1
PCI: Sharing IRQ 9 with 00:1d.2
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
hda: C/H/S=30/1/0 from BIOS ignored
hda: ST340014A, ATA DISK drive
blk: queue c0400f40, I/O limit 4095Mb (mask 0xffffffff)
hdc: ST340014A, ATA DISK drive
blk: queue c040139c, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
Partition check:
 hda: hda1 hda2 hda3
 hdc: hdc1 hdc2 hdc3
ide: late registration of driver.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
md: autorun ...
md: considering hdc3 ...
md:  adding hdc3 ...
md:  adding hda3 ...
md: created md2
md: bind<hda3,1>
md: bind<hdc3,2>
md: running: <hdc3><hda3>
md: hdc3's event counter: 0000008e
md: hda3's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md2 stopped.
md: unbind<hdc3,1>
md: export_rdev(hdc3)
md: unbind<hda3,0>
md: export_rdev(hda3)
md: considering hdc2 ...
md:  adding hdc2 ...
md:  adding hda2 ...
md: created md1
md: bind<hda2,1>
md: bind<hdc2,2>
md: running: <hdc2><hda2>
md: hdc2's event counter: 0000008e
md: hda2's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md1 stopped.
md: unbind<hdc2,1>
md: export_rdev(hdc2)
md: unbind<hda2,0>
md: export_rdev(hda2)
md: considering hdc1 ...
md:  adding hdc1 ...
md:  adding hda1 ...
md: created md0
md: bind<hda1,1>
md: bind<hdc1,2>
md: running: <hdc1><hda1>
md: hdc1's event counter: 0000008e
md: hda1's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
md: personality 3 is not loaded!
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<hdc1,1>
md: export_rdev(hdc1)
md: unbind<hda1,0>
md: export_rdev(hda1)
md: ... autorun DONE.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 169k freed
VFS: Mounted root (ext2 filesystem).
md: raid1 personality registered as nr 3
Journalled Block Device driver loaded
md: Autodetecting RAID arrays.
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
 [events: 0000008e]
md: autorun ...
md: considering hda1 ...
md:  adding hda1 ...
md:  adding hdc1 ...
md: created md0
md: bind<hdc1,1>
md: bind<hda1,2>
md: running: <hda1><hdc1>
md: hda1's event counter: 0000008e
md: hdc1's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
md0: max total readahead window set to 124k
md0: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda1 operational as mirror 0
raid1: device hdc1 operational as mirror 1
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
md: hda1 [events: 0000008f]<6>(write) hda1's sb offset: 7164864
md: hdc1 [events: 0000008f]<6>(write) hdc1's sb offset: 7164864
md: considering hda2 ...
md:  adding hda2 ...
md:  adding hdc2 ...
md: created md1
md: bind<hdc2,1>
md: bind<hda2,2>
md: running: <hda2><hdc2>
md: hda2's event counter: 0000008e
md: hdc2's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
md1: max total readahead window set to 124k
md1: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda2 operational as mirror 0
raid1: device hdc2 operational as mirror 1
raid1: raid set md1 active with 2 out of 2 mirrors
md: updating md1 RAID superblock on device
md: hda2 [events: 0000008f]<6>(write) hda2's sb offset: 522048
md: hdc2 [events: 0000008f]<6>(write) hdc2's sb offset: 522048
md: considering hda3 ...
md:  adding hda3 ...
md:  adding hdc3 ...
md: created md2
md: bind<hdc3,1>
md: bind<hda3,2>
md: running: <hda3><hdc3>
md: hda3's event counter: 0000008e
md: hdc3's event counter: 0000008e
md: RAID level 1 does not need chunksize! Continuing anyway.
md2: max total readahead window set to 124k
md2: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda3 operational as mirror 0
raid1: device hdc3 operational as mirror 1
raid1: raid set md2 active with 2 out of 2 mirrors
md: updating md2 RAID superblock on device
md: hda3 [events: 0000008f]<6>(write) hda3's sb offset: 31390912
md: hdc3 [events: 0000008f]<6>(write) hdc3's sb offset: 31390912
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 136k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 08:42:20 Dec  1 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1d.0
PCI: Sharing IRQ 11 with 00:02.0
PCI: Sharing IRQ 11 with 00:1d.3
PCI: Sharing IRQ 11 with 01:04.0
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0xc000, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.1
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0xc400, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 9 for device 00:1d.2
PCI: Sharing IRQ 9 with 00:1f.1
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0xc800, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:1d.3
PCI: Sharing IRQ 11 with 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
PCI: Sharing IRQ 11 with 01:04.0
PCI: Setting latency timer of device 00:1d.3 to 64
usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Found IRQ 5 for device 00:1d.7
PCI: Setting latency timer of device 00:1d.7 to 64
ehci_hcd 00:1d.7: Intel Corp. 82801EB USB2
ehci_hcd 00:1d.7: irq 5, pci mem d0058000
usb.c: new USB bus registered, assigned bus number 5
ehci_hcd 00:1d.7: enabled 64bit PCI DMA
PCI: cache line size of 128 is not supported by device 00:1d.7
ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 8 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,0), internal journal
Adding Swap: 522040k swap-space (priority -1)
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
 

[Zdenek]

Podle tohoto vypisu, zrejme jadro ten radic nezna. Jadro mate distribucni? FC3 je opravdu stara distribuce, takze bych to resil upgradem na Centos 5.2 vzhledem k tomu, ze to hodlate pouzivat dele nez je zivotnost jednotlivych vydani Fedory.

[latis]

Heh.. takhle. jedna se o server v jedne firme, pokud by se jednalo o upgrade, pak by to byl luxus..pokud to budu muset nainstalovat znovu, tak to bude blbe, ale mate pravdu ze ta fc3 je hrozne stara. Cili se chci zeptat zda je mozne nejakym zpusobem upgradovat cely system na jiny (treba centos)?

[Zdenek]

U FC3 mam pocit, ze nejde ani bezproblemove upgradovat na vyssi verzi natoz na jinou distribuci Muzete zkusit nove jadro, ale asi bude potreba i par dalsich veci jako binutils a pak si pohrat s udev.

[latis]

Tak jeste VELKÁ OMLUVA. jedná se o FC 1 ... neni co resit.. pomuze pouze uplne nova distribuce... i tak diky za rady..

[houska]

a priste davej konfiguraky a logy do <pre> </pre>

[Mti.]

par poznamek:

Zkus zase v biosu toho radice zrusit to jakozepole (pokud na nem nemas uz data) a podivat se, jestli system neuvidi aspon samotne disky. (pak postupovat za pouziti mkraid a spol) Vetsinou radic "samotny" funguje temer vzdy, narozdil od tech jejich polo-(urcite-ne-hw)-raidu.

Kernel se k tomu radici zjevne nezna. ... na netu casto odkazuji driver sata_sil ... opravdu netusim, ktera verze jadra ho "uz" podporuje. (zkus zadat    modprobe sata_sil   a podivat se co pribude v logu... teda, pokud ten driver mas aspon jako modul )

kdyz nabootujes nejake cerstvejsi (staci live) distro, uvidi ten radic "lepe" ?

mdadm je vicemene prijemne zapouzdreny balik starsich nastroju, mkraid je jednim z nich, nebal bych se toho.

V nejnuznejsim pripade opatrit nejaky laciny sata radic a neresit to. (to v pripade, ze tam MUSI zustat tak stara verze systemu).

kompilace kernelu by chybejici driver aspi poresila, ale to je psychicky narocne a rozhodne bych to doporucoval nacvicit mimo ostry stroj. (to zakladani/ruseni sw raidu taky)

[latis]

Jeste prikladam raidtab:

raiddev             /dev/md0
raid-level                  1
nr-raid-disks               2
chunk-size                  64
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda1
    raid-disk     0
    device          /dev/hdc1
    raid-disk     1
raiddev             /dev/md2
raid-level                  1
nr-raid-disks               2
chunk-size                  64
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda3
    raid-disk     0
    device          /dev/hdc3
    raid-disk     1
raiddev             /dev/md1
raid-level                  1
nr-raid-disks               2
chunk-size                  64
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda2
    raid-disk     0
    device          /dev/hdc2
    raid-disk     1
 

[Zdenek]

Pokud to ma byt HW raid, tak nejde o zadne /dev/md*, ale normalne se vam vytvori dalsi device /dev/sd*.

[houska]

.. s HW RAIDEM do PCI...

co to je zac? znacka, typ? bez toho se nehnem

Bohuzel jsem ten prvni raid netvořil

prvni = to jsou ty "stare" softwarove raidy? proc byste je znovu vytvarel?
predtim totiz pisete :

fedore 3 bezi jeden raid pro ATA disky (md0, md1, md2)

[Josef Navrátil]

Toto mluvi za vse...

     01:04.0 RAID bus controller: CMD Technology Inc: Unknown device 3114 (rev 02)

 

Zadny HW RAID, ale softwarove siditko - PCI SATA radic Sil 3114. Pokud jste vytvarel raidove pole v BIOSu teto karty, urcite jej pod linuxem neuvidite (nehlede na to, ze FC1 nezna ani tento SATA radic). Myslim ze stanovisko vyvojaru je jasne - jedna se o Fake RAID - unsupported, pouzijte linuxovy softwarovy RAID.

 

Jedinou cestou ven tak je upgradnout jadro na verzi ktera radic pozna, raidove pole v BIOSu rozbit a linux nechat nadetekovat jednotlive pripojene disky a nad nimi pak vytvorit softwarovy raid pomoci mdadm.

[Josef Navrátil]

Za predpokladu ze pridavate dva disky, ktere system nadetekuje jako sda a sdb, rozdelite je na 3 oddily (1-3) a nove vytvarena raidove pole maji mit stejne parametry jako ta stavajici (level 1, chunk size 64k),  vse co potrebujete vedet je ...

mdadm --create /dev/md3 --level=1 --chunk=64 --spare-devices=0 --raid-devices=2 /dev/sd[ab]1
mdadm --create /dev/md4 --level=1 --chunk=64 --spare-devices=0 --raid-devices=2 /dev/sd[ab]2
mdadm --create /dev/md5 --level=1 --chunk=64 --spare-devices=0 --raid-devices=2 /dev/sd[ab]3

 

a do souboru /etc/mdadm.conf doplnte

DEVICE /dev/sd[ab]
ARRAY /dev/md3 devices=/dev/sd[ab]1
ARRAY /dev/md4 devices=/dev/sd[ab]2
ARRAY /dev/md5 devices=/dev/sd[ab]3

 

[houska]

jestli ma /etc/raidtab tak mdadm to distro jeste asi nezna ... mkraid