Rozpadlé pole RAID 5

[Benda]

Co se mi to dnes nestalo :-(
raid 5   --- >   [8/6] [__UUUUUU]
vypadá to na chybu řadiče
oba dva disky jsou pripojeny na axago PCIS-60
pujde to jeste dat do kupy
mas s timto problemem nekdo zkusenosti

Kód: [Vybrat]

Nov 11 06:40:42 shrek kernel: [737292.844507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:40:47 shrek kernel: [737297.828507] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:40:47 shrek kernel: [737297.828513] ata7: soft resetting link
Nov 11 06:40:53 shrek kernel: [737303.404126] ata7.00: qc timeout (cmd 0xec)
Nov 11 06:40:53 shrek kernel: [737303.404132] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Nov 11 06:40:58 shrek kernel: [737308.440007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:41:03 shrek kernel: [737313.424009] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:41:03 shrek kernel: [737313.424016] ata7: soft resetting link
Nov 11 06:41:08 shrek kernel: [737318.620007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:41:13 shrek kernel: [737323.436014] ata7: soft resetting link
Nov 11 06:41:18 shrek kernel: [737328.632007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:41:23 shrek kernel: [737333.448013] ata7: soft resetting link
Nov 11 06:41:28 shrek kernel: [737338.644507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:41:30 shrek kernel: [737340.768672] ata7.00: configured for UDMA/133
Nov 11 06:41:30 shrek kernel: [737340.777492] ata7.01: configured for UDMA/133
Nov 11 06:41:30 shrek kernel: [737340.777501] ata7: EH complete
Nov 11 06:47:07 shrek kernel: [737677.804512] ata7: lost interrupt (Status 0x50)
Nov 11 06:47:07 shrek kernel: [737677.804554] ata7: soft resetting link
Nov 11 06:47:08 shrek kernel: [737678.425174] ata7.00: configured for UDMA/133
Nov 11 06:47:08 shrek kernel: [737678.440910] ata7.01: configured for UDMA/133
Nov 11 06:47:08 shrek kernel: [737678.440917] ata7: EH complete
Nov 11 06:49:07 shrek kernel: [737797.856510] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:49:12 shrek kernel: [737802.840507] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:49:12 shrek kernel: [737802.840513] ata7: soft resetting link
Nov 11 06:49:17 shrek kernel: [737808.036506] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:49:22 shrek kernel: [737812.852514] ata7: soft resetting link
Nov 11 06:49:27 shrek kernel: [737818.048507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:49:32 shrek kernel: [737822.864513] ata7: soft resetting link
Nov 11 06:49:37 shrek kernel: [737828.060507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:49:38 shrek kernel: [737828.884651] ata7.00: configured for UDMA/133
Nov 11 06:49:38 shrek kernel: [737828.893334] ata7.01: configured for UDMA/133
Nov 11 06:49:38 shrek kernel: [737828.893370] ata7: EH complete
Nov 11 06:51:48 shrek kernel: [737958.856006] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:51:53 shrek kernel: [737963.840007] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:51:53 shrek kernel: [737963.840013] ata7: soft resetting link
Nov 11 06:51:58 shrek kernel: [737969.036006] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:52:03 shrek kernel: [737973.852514] ata7: soft resetting link
Nov 11 06:52:08 shrek kernel: [737979.048007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:52:13 shrek kernel: [737983.864514] ata7: soft resetting link
Nov 11 06:52:18 shrek kernel: [737989.060506] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:52:27 shrek kernel: [737997.477176] ata7.00: configured for UDMA/133
Nov 11 06:52:27 shrek kernel: [737997.488772] ata7.01: configured for UDMA/133
Nov 11 06:52:27 shrek kernel: [737997.488781] ata7: EH complete
Nov 11 06:53:20 shrek kernel: [738050.820023] ata7.00: limiting speed to UDMA/100:PIO4
Nov 11 06:53:25 shrek kernel: [738055.856507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:53:30 shrek kernel: [738060.840507] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:53:30 shrek kernel: [738060.840513] ata7: soft resetting link
Nov 11 06:53:35 shrek kernel: [738066.036506] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:53:40 shrek kernel: [738070.852014] ata7: soft resetting link
Nov 11 06:53:45 shrek kernel: [738076.048054] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:53:49 shrek kernel: [738079.521152] ata7.00: configured for UDMA/100
Nov 11 06:53:49 shrek kernel: [738079.537282] ata7.01: configured for UDMA/133
Nov 11 06:53:49 shrek kernel: [738079.537290] ata7: EH complete
Nov 11 06:54:33 shrek kernel: [738123.844006] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:54:38 shrek kernel: [738128.828006] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:54:38 shrek kernel: [738128.828012] ata7: soft resetting link
Nov 11 06:54:43 shrek kernel: [738134.024007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:54:48 shrek kernel: [738138.840014] ata7: soft resetting link
Nov 11 06:54:53 shrek kernel: [738144.036007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:54:58 shrek kernel: [738148.852014] ata7: soft resetting link
Nov 11 06:55:03 shrek kernel: [738154.048012] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:55:32 shrek kernel: [738182.656668] ata7.00: configured for UDMA/100
Nov 11 06:55:32 shrek kernel: [738182.665678] ata7.01: configured for UDMA/133
Nov 11 06:55:32 shrek kernel: [738182.665687] ata7: EH complete
Nov 11 06:56:23 shrek kernel: [738233.804519] ata7: lost interrupt (Status 0x50)
Nov 11 06:56:23 shrek kernel: [738233.804560] ata7: soft resetting link
Nov 11 06:56:24 shrek kernel: [738234.432639] ata7.00: configured for UDMA/100
Nov 11 06:56:24 shrek kernel: [738234.449124] ata7.01: configured for UDMA/133
Nov 11 06:56:24 shrek kernel: [738234.449133] ata7: EH complete
Nov 11 06:58:50 shrek kernel: [738380.844506] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:58:55 shrek kernel: [738385.828507] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 06:58:55 shrek kernel: [738385.828513] ata7: soft resetting link
Nov 11 06:59:00 shrek kernel: [738391.024507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:59:05 shrek kernel: [738395.840515] ata7: soft resetting link
Nov 11 06:59:10 shrek kernel: [738401.036507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:59:15 shrek kernel: [738405.852514] ata7: soft resetting link
Nov 11 06:59:20 shrek kernel: [738411.048507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 06:59:32 shrek kernel: [738422.500645] ata7.00: configured for UDMA/100
Nov 11 06:59:32 shrek kernel: [738422.512896] ata7.01: configured for UDMA/133
Nov 11 06:59:32 shrek kernel: [738422.512905] ata7: EH complete
Nov 11 07:03:22 shrek kernel: [738652.804027] ata7.00: limiting speed to UDMA/33:PIO4
Nov 11 07:03:27 shrek kernel: [738657.844007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:03:32 shrek kernel: [738662.828007] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 07:03:32 shrek kernel: [738662.828013] ata7: soft resetting link
Nov 11 07:03:35 shrek kernel: [738665.248652] ata7.00: configured for UDMA/33
Nov 11 07:03:35 shrek kernel: [738665.256999] ata7.01: configured for UDMA/133
Nov 11 07:03:35 shrek kernel: [738665.257006] ata7: EH complete
Nov 11 07:08:01 shrek kernel: [738931.856007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:08:06 shrek kernel: [738936.840007] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 07:08:06 shrek kernel: [738936.840014] ata7: soft resetting link
Nov 11 07:08:11 shrek kernel: [738942.036506] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:08:16 shrek kernel: [738946.852015] ata7: soft resetting link
Nov 11 07:08:21 shrek kernel: [738952.048007] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:08:26 shrek kernel: [738956.864014] ata7: soft resetting link
Nov 11 07:08:30 shrek kernel: [738960.788654] ata7.00: configured for UDMA/33
Nov 11 07:08:30 shrek kernel: [738960.797577] ata7.01: configured for UDMA/133
Nov 11 07:08:30 shrek kernel: [738960.797617] ata7: EH complete
Nov 11 07:14:48 shrek kernel: [739338.844507] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:14:53 shrek kernel: [739343.828508] ata7: device not ready (errno=-16), forcing hardreset
Nov 11 07:14:53 shrek kernel: [739343.828514] ata7: soft resetting link
Nov 11 07:14:58 shrek kernel: [739349.024508] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:15:03 shrek kernel: [739353.840516] ata7: soft resetting link
Nov 11 07:15:08 shrek kernel: [739359.036508] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:15:13 shrek kernel: [739363.852513] ata7: soft resetting link
Nov 11 07:15:18 shrek kernel: [739369.048509] ata7: link is slow to respond, please be patient (ready=0)
Nov 11 07:15:48 shrek kernel: [739398.896014] ata7: soft resetting link
Nov 11 07:15:53 shrek kernel: [739403.924014] ata7.00: disabled
Nov 11 07:15:53 shrek kernel: [739403.924016] ata7.01: disabled
Nov 11 07:15:53 shrek kernel: [739403.924024] ata7: EH complete
Nov 11 07:15:53 shrek kernel: [739403.924039] sd 6:0:0:0: [sde] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.924041] sd 6:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.924045] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 31 21 77 3f 00 00 80 00
Nov 11 07:15:53 shrek kernel: [739403.924073] sd 6:0:1:0: [sdf] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.924075] sd 6:0:1:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.924078] sd 6:0:1:0: [sdf] CDB: Read(10): 28 00 31 21 76 f7 00 00 48 00
Nov 11 07:15:53 shrek kernel: [739403.924093] sd 6:0:0:0: [sde] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.924095] sd 6:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.924098] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 31 21 78 3f 00 01 00 00
Nov 11 07:15:53 shrek kernel: [739403.924113] sd 6:0:1:0: [sdf] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.924114] sd 6:0:1:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.924117] sd 6:0:1:0: [sdf] CDB: Read(10): 28 00 31 21 77 bf 00 01 80 00
Nov 11 07:15:53 shrek kernel: [739403.928608] sd 6:0:1:0: [sdf] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.928610] sd 6:0:1:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.928614] sd 6:0:1:0: [sdf] CDB: Read(10): 28 00 31 21 77 3f 00 00 80 00
Nov 11 07:15:53 shrek kernel: [739403.928625] raid5:md0: read error not correctable (sector 824276736 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928628] raid5:md0: read error not correctable (sector 824276744 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928631] raid5:md0: read error not correctable (sector 824276752 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928634] raid5:md0: read error not correctable (sector 824276760 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928637] raid5:md0: read error not correctable (sector 824276768 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928639] raid5:md0: read error not correctable (sector 824276776 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928642] raid5:md0: read error not correctable (sector 824276784 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928645] raid5:md0: read error not correctable (sector 824276792 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928648] raid5:md0: read error not correctable (sector 824276800 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928651] raid5:md0: read error not correctable (sector 824276808 on sdf1).
Nov 11 07:15:53 shrek kernel: [739403.928662] sd 6:0:0:0: [sde] Unhandled error code
Nov 11 07:15:53 shrek kernel: [739403.928663] sd 6:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov 11 07:15:53 shrek kernel: [739403.928666] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 31 21 77 bf 00 01 80 00
Nov 11 07:15:54 shrek kernel: [739405.028040] RAID5 conf printout:
Nov 11 07:15:54 shrek kernel: [739405.028043]  --- rd:8 wd:6
Nov 11 07:15:54 shrek kernel: [739405.028046]  disk 0, o:0, dev:sde1
Nov 11 07:15:54 shrek kernel: [739405.028048]  disk 1, o:0, dev:sdf1
Nov 11 07:15:54 shrek kernel: [739405.028050]  disk 2, o:1, dev:sdg1
Nov 11 07:15:54 shrek kernel: [739405.028052]  disk 3, o:1, dev:sdh1
Nov 11 07:15:54 shrek kernel: [739405.028054]  disk 4, o:1, dev:sda1
Nov 11 07:15:54 shrek kernel: [739405.028055]  disk 5, o:1, dev:sdb1
Nov 11 07:15:54 shrek kernel: [739405.028057]  disk 6, o:1, dev:sdc1
Nov 11 07:15:54 shrek kernel: [739405.028059]  disk 7, o:1, dev:sdj1
Nov 11 07:15:54 shrek kernel: [739405.036006] RAID5 conf printout:
Nov 11 07:15:54 shrek kernel: [739405.036008]  --- rd:8 wd:6
Nov 11 07:15:54 shrek kernel: [739405.036010]  disk 1, o:0, dev:sdf1
Nov 11 07:15:54 shrek kernel: [739405.036012]  disk 2, o:1, dev:sdg1
Nov 11 07:15:54 shrek kernel: [739405.036014]  disk 3, o:1, dev:sdh1
Nov 11 07:15:54 shrek kernel: [739405.036016]  disk 4, o:1, dev:sda1
Nov 11 07:15:54 shrek kernel: [739405.036018]  disk 5, o:1, dev:sdb1
Nov 11 07:15:54 shrek kernel: [739405.036020]  disk 6, o:1, dev:sdc1
Nov 11 07:15:54 shrek kernel: [739405.036022]  disk 7, o:1, dev:sdj1
Nov 11 07:15:54 shrek kernel: [739405.036030] RAID5 conf printout:
Nov 11 07:15:54 shrek kernel: [739405.036032]  --- rd:8 wd:6
Nov 11 07:15:54 shrek kernel: [739405.036034]  disk 1, o:0, dev:sdf1
Nov 11 07:15:54 shrek kernel: [739405.036035]  disk 2, o:1, dev:sdg1
Nov 11 07:15:54 shrek kernel: [739405.036037]  disk 3, o:1, dev:sdh1
Nov 11 07:15:54 shrek kernel: [739405.036039]  disk 4, o:1, dev:sda1
Nov 11 07:15:54 shrek kernel: [739405.036041]  disk 5, o:1, dev:sdb1
Nov 11 07:15:54 shrek kernel: [739405.036043]  disk 6, o:1, dev:sdc1
Nov 11 07:15:54 shrek kernel: [739405.036045]  disk 7, o:1, dev:sdj1
Nov 11 07:15:54 shrek kernel: [739405.052005] RAID5 conf printout:
Nov 11 07:15:54 shrek kernel: [739405.052007]  --- rd:8 wd:6
Nov 11 07:15:54 shrek kernel: [739405.052009]  disk 2, o:1, dev:sdg1
Nov 11 07:15:54 shrek kernel: [739405.052011]  disk 3, o:1, dev:sdh1
Nov 11 07:15:54 shrek kernel: [739405.052013]  disk 4, o:1, dev:sda1
Nov 11 07:15:54 shrek kernel: [739405.052015]  disk 5, o:1, dev:sdb1
Nov 11 07:15:54 shrek kernel: [739405.052017]  disk 6, o:1, dev:sdc1
Nov 11 07:15:54 shrek kernel: [739405.052019]  disk 7, o:1, dev:sdj1
Nov 11 07:18:23 shrek kernel: [739553.392103] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:18:23 shrek kernel: [739553.406022] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:18:23 shrek kernel: [739553.406054] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:18:23 shrek kernel: [739553.410344] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:18:23 shrek kernel: [739553.410368] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:18:23 shrek kernel: [739553.410395] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.298309] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.298334] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.298362] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.302636] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.302660] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:23:33 shrek kernel: [739863.302687] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.613101] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.613126] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.613154] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.617568] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.617593] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:28:43 shrek kernel: [740173.617620] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.012204] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.012229] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.012257] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.016761] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.016786] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:33:53 shrek kernel: [740484.016814] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.600410] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.600435] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.600463] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.604860] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.604885] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 11 07:38:54 shrek kernel: [740784.604911] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

[Reklama]

[Jenda]

Tohle by fakt mohl být řadič nebo kabel. Když se ti je podaří zase zpřístupnit, mělo by to jít.

[Jakub Váňa]

S prominutím, ale ..... co je to pane bože za kravinu udělat osmidiskový RAID 5 ?

[citanus]

Treba jeste nebyl raid6 v kernelu kdyz to vytvarel a raid 10 (1+0) se mu nezdal jako vhodna volba. Btw nevite nekdo jestli se pro linux chysta neco jako raid Z resp raid DP.

[raidak]

Proč kravina? Setkal jsem se i s většími. Nestavěl jsem je, ale nepřišlo mi to až tak divné. Je tam s něčím problém?

[Reklama]

[citanus]

Proč kravina? Setkal jsem se i s většími. Nestavěl jsem je, ale nepřišlo mi to až tak divné. Je tam s něčím problém?

Toleruje jen vypadek jen jednoho disku ne?

[Trupik]

Najprv spojazdni tie disky, potom by mohlo to pole normálne rozpoznať pri štarte. Ak nie, na opätovné zostavenie poľa je potrebné použiť mdadm --assemble...

[Benda]

RAID 5 + spear disk .
Na moje domací použití stačí, problém je ,že jsem nečekal selhaní řadiče.

[RDa]

Ja mel taky 8x disk v raid5, bez spare.. proste nekdy je dulezitejsi kapacita a 2 disky opravdu neodejtou uplne naraz. Navic pro osobni (single-user) velkokapacitni uloziste to je idealni.

Co se tyce zprovozneni - musite oddelit ty funkcni disky [ U ] a nefunkcni [ _ ]. Na nefunkcnich pres mdadm zjistete verzi (events) - muze byt, ze jedna ma vetsi a druha mensi (vypadli z pole v nestejnou dobu) - v tom pripade pripojte ten s vice eventama (pozdejsi verzi, vypadl jako posledni) a pole by se mohlo chytnout.

V pripade, ze je pocet eventu stejny, slo opravdu o chybu radice - a muzete zkusit pripojit kterykoliv z te dvojice.

A kdyz se to nechytne automaticky - lze pouzit mdadm assemble s force parametrem, pak se ignoruje verzovani (eventy) a pole se sestavi. Je ale mozne, ze na poli budete mit poskozeny filesystem - takze prvni krok by mela byt zaloha dat (ktere precist jdou) a druhy fsck a pak se podivat zda se nejake soubory opravili a zalohovat je oddelene... pokud fsck nenajde zadny problem, pole muzete pouzivat, ale pokud tam neco bylo, radeji bych to zformatoval a vratil data ze zalohy.


Jeste dulezita poznamka k radici - prosim nekupujte tyto "silicon image" radice. Investujte radeji do (second hand) SAS HBA... da to sice trocha namahy vybrat takovy ktery umi SMART ze sata disku do linuxu, ale spolehlivosti je to uplne jinde.

[jar]

Zdravím, nechci zakládat nové téma, tak jestli se můžu zeptat. Chci si udělat RAID1 na fotky a data.
Dělal jsem to pomocí nástroje mdadm podle návodů co jsem sehnal po netu.
fdiskem jsem si rozdělil sdb na sdb1 (pro swap) a sdb2 pro data ext4
pomocí
sfdisk -d /dev/sdb | /dev/sdc
mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb2 /dev/sdc2
začala rekonstrukce.
tady byl trochu zásek při pokusu o mount hlásilo neznámý filesystem, ale další hledání mi pomohlo
mkfs -t ext4 -j /dev/md0
mount /dev/md0 /data
raid připojen, data se krásně kopírují na nové disky. Jenže, večer vypnu komp a ráno disk nikde. Hledal jsem různě v návodech ale všechny jsou přibližne stejné, nemusí se to ještě někam zapsat aby si to systém (fedora, jádro 2.6.30) pamatoval?

[pocestny]

Zdravím, nechci zakládat nové téma, tak jestli se můžu zeptat. Chci si udělat RAID1 na fotky a data.
Dělal jsem to pomocí nástroje mdadm podle návodů co jsem sehnal po netu.
fdiskem jsem si rozdělil sdb na sdb1 (pro swap) a sdb2 pro data ext4
pomocí
sfdisk -d /dev/sdb | /dev/sdc
mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb2 /dev/sdc2
začala rekonstrukce.
tady byl trochu zásek při pokusu o mount hlásilo neznámý filesystem, ale další hledání mi pomohlo
mkfs -t ext4 -j /dev/md0
mount /dev/md0 /data
raid připojen, data se krásně kopírují na nové disky. Jenže, večer vypnu komp a ráno disk nikde. Hledal jsem různě v návodech ale všechny jsou přibližne stejné, nemusí se to ještě někam zapsat aby si to systém (fedora, jádro 2.6.30) pamatoval?

mdadm --examine --scan /dev/sdb2 >> /etc/mdadm/mdadm.conf

[jar]

aha díky :-)

mdadm --examine --scan /dev/sdb2 >> /etc/mdadm/mdadm.conf
nemělo by být místo sdb2 md0 ? nebo proč zapisovat sdb2 do mdadm.conf

[Benda]

musis si ulozit konfiguraci do /etc/mdadm.conf

pouzij tento prikaz mdadm --detail --scan >> /etc/mdadm.conf
a taky nezapomen na editaci /etc/fstab
melo vy tam neco jako
/dev/md0     /mnt         ext4     defaults     0  2(2 - znamna ze se pri startu bude kontrolovat jako 2 v poradi)

a to je vse

[Rhinox]

musis si ulozit konfiguraci do /etc/mdadm.conf

Jestli se nemylim, u raid1 by mela fungovat autodetekce. Tudiz konfiguraci nikam ukladat nemusi...

[jar]

Vyzkouším. Co vlastně zapisuje ten mdadm do configu, nedalo by se nějak zrestaurovat to stávající "neviditelné" pole? Nechce se mi znovu kopírovat skoro půl tera dat. :-/
S tím souvisí ještě taková maličkost, když se mi podaří to pole vytvořit a dejme tomu odejde deska. Dá se to pole na jiném stroji zrestaurovat, nebo alespoň budou soubory přístupné když disk připojím jako /dev/sdb2 ? Na widlích se dali připojit a přečíst.