|
Guten Tag, mir ist ein Raid10 Verbund, bestehend aus 6 Partitionen, auseinander geflogen. Die beiden weiteren Raid10 auf den gleichen Harddisks funktionieren noch!? Hardware: 6 1TB HD's von Samsung jede Platte mit einer primären 10GB und einer primären 6GB Partition versehen. Diese sind jeweils in einem Raid10 verbunden. Der Rest der jeweiligen Platten ist als eine erweiterte Partition mit ~984GB eingerichtet und diese sind ebenfalls in einem Raid10 zusammengefasst. Dieser große Raid10 Verbund ist auseinandergefallen. In den Logdateien finde ich folgendes: messages: Feb 16 19:33:53 HAM-XEN1 kernel: [158397.781663] ata2: hard resetting link Feb 16 19:33:53 HAM-XEN1 kernel: [158397.781762] ata3: hard resetting link Feb 16 19:33:54 HAM-XEN1 kernel: [158398.264077] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:33:54 HAM-XEN1 kernel: [158398.265581] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306561] sd 5:0:0:0: [sdf] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306566] sd 5:0:0:0: [sdf] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306570] sd 5:0:0:0: [sdf] CDB: Write(10): 2a 00 50 2a 23 50 00 00 18 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306962] sd 0:0:0:0: [sda] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306965] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306971] sd 4:0:0:0: [sde] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306974] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 50 14 4d d8 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.306999] sd 0:0:0:0: [sda] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307001] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307004] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 50 2a 23 50 00 00 20 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307030] sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307037] sd 4:0:0:0: [sde] CDB: Write(10): 2a 00 50 2a 23 50 00 00 18 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307362] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307365] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307368] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 2d 64 fe 38 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307457] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307460] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307463] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 4f 87 ad 40 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307525] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307527] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307543] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 4f 87 ad 58 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307575] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307577] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307598] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 4f 87 ad 98 00 00 10 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307657] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307671] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.307675] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 4f 87 ad b8 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308080] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308083] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308087] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 4f 87 ad f0 00 00 08 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308159] sd 3:0:0:0: [sdd] Unhandled error code Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308161] sd 3:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Feb 16 19:33:56 HAM-XEN1 kernel: [158400.308165] sd 3:0:0:0: [sdd] CDB: Write(10): 2a 00 50 2a 23 50 00 00 20 00 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.313519] ata3.00: configured for UDMA/133 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.313544] ata3: EH complete Feb 16 19:33:56 HAM-XEN1 kernel: [158400.314031] ata2.00: configured for UDMA/133 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.314036] ata2.00: device reported invalid CHS sector 0 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.314080] ata2: EH complete Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646358] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646370] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646381] disk 0, wo:1, o:0, dev:sda5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646390] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646398] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646405] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646413] disk 4, wo:1, o:0, dev:sde5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.646421] disk 5, wo:1, o:0, dev:sdf5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661117] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661137] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661151] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661160] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661167] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661175] disk 4, wo:1, o:0, dev:sde5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661182] disk 5, wo:1, o:0, dev:sdf5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661208] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661215] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661221] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661228] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661235] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661242] disk 4, wo:1, o:0, dev:sde5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.661249] disk 5, wo:1, o:0, dev:sdf5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693127] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693139] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693151] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693160] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693167] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693175] disk 4, wo:1, o:0, dev:sde5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693200] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693206] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693213] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693220] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693227] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.693234] disk 4, wo:1, o:0, dev:sde5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725101] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725112] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725126] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725133] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725141] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725166] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725172] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725179] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725186] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.725193] disk 3, wo:1, o:0, dev:sdd5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.757123] RAID10 conf printout: Feb 16 19:33:56 HAM-XEN1 kernel: [158400.757134] --- wd:2 rd:6 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.757145] disk 1, wo:0, o:1, dev:sdb5 Feb 16 19:33:56 HAM-XEN1 kernel: [158400.757154] disk 2, wo:0, o:1, dev:sdc5 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.070881] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.070958] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071019] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071089] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071150] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071235] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071307] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071374] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071453] lost page write due to I/O error on dm-0 Feb 16 19:34:12 HAM-XEN1 kernel: [158416.071527] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084271] __ratelimit: 74 callbacks suppressed Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084296] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084332] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084367] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084400] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084441] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084474] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084507] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084541] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084574] lost page write due to I/O error on dm-0 Feb 16 19:34:47 HAM-XEN1 kernel: [158451.084610] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098325] __ratelimit: 85 callbacks suppressed Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098373] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098468] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098540] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098610] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098678] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098758] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098826] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098898] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.098967] lost page write due to I/O error on dm-0 Feb 16 19:35:22 HAM-XEN1 kernel: [158486.099035] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118622] __ratelimit: 138 callbacks suppressed Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118648] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118684] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118717] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118751] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118790] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118823] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118860] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118894] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118923] lost page write due to I/O error on dm-0 Feb 16 19:35:57 HAM-XEN1 kernel: [158521.118973] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134222] __ratelimit: 73 callbacks suppressed Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134276] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134363] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134431] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134500] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134582] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134651] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134721] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134803] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134880] lost page write due to I/O error on dm-0 Feb 16 19:36:32 HAM-XEN1 kernel: [158556.134948] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148086] __ratelimit: 90 callbacks suppressed Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148135] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148200] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148285] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148355] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148423] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148481] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148550] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148598] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148690] lost page write due to I/O error on dm-0 Feb 16 19:37:07 HAM-XEN1 kernel: [158591.148758] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.161848] __ratelimit: 64 callbacks suppressed Feb 16 19:37:42 HAM-XEN1 kernel: [158626.161895] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.161968] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162035] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162109] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162203] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162274] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162341] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162410] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162479] lost page write due to I/O error on dm-0 Feb 16 19:37:42 HAM-XEN1 kernel: [158626.162561] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.178961] __ratelimit: 85 callbacks suppressed Feb 16 19:38:17 HAM-XEN1 kernel: [158661.178982] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179016] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179052] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179078] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179107] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179128] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179153] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179178] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179203] lost page write due to I/O error on dm-0 Feb 16 19:38:17 HAM-XEN1 kernel: [158661.179230] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192235] __ratelimit: 103 callbacks suppressed Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192283] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192357] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192425] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192492] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192559] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192643] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192711] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192778] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192861] lost page write due to I/O error on dm-0 Feb 16 19:38:52 HAM-XEN1 kernel: [158696.192950] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211397] __ratelimit: 159 callbacks suppressed Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211419] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211450] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211476] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211500] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211525] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211550] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211576] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211601] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211626] lost page write due to I/O error on dm-0 Feb 16 19:39:27 HAM-XEN1 kernel: [158731.211656] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226481] __ratelimit: 99 callbacks suppressed Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226528] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226601] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226693] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226762] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.226829] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.229795] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.229961] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.230039] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.230131] lost page write due to I/O error on dm-0 Feb 16 19:40:02 HAM-XEN1 kernel: [158766.230209] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.247751] __ratelimit: 185 callbacks suppressed Feb 16 19:40:37 HAM-XEN1 kernel: [158801.247799] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.247876] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.247969] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248047] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248130] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248202] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248305] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248384] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248434] lost page write due to I/O error on dm-0 Feb 16 19:40:37 HAM-XEN1 kernel: [158801.248506] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261144] __ratelimit: 116 callbacks suppressed Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261192] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261288] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261360] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261484] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261553] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261612] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261681] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261750] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261828] lost page write due to I/O error on dm-0 Feb 16 19:41:12 HAM-XEN1 kernel: [158836.261895] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275002] __ratelimit: 81 callbacks suppressed Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275051] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275125] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275215] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275283] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275355] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275424] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275491] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275558] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275628] lost page write due to I/O error on dm-0 Feb 16 19:41:47 HAM-XEN1 kernel: [158871.275718] lost page write due to I/O error on dm-0 Nach dem nächsten booten findet sich folgendes: Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996100] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996124] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996143] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996161] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996179] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 0.996197] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.001828] ata4.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.001833] ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.001863] ata3.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.001866] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002627] ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002630] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002634] ata6.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002638] ata6.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002664] ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01118, max UDMA7 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002667] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002688] ata5.00: ATA-7: SAMSUNG HD103UJ, 1AA01118, max UDMA7 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.002691] ata5.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.007654] ata3.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.007677] ata4.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.009221] ata2.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.009250] ata1.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.009261] ata5.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.009272] ata6.00: configured for UDMA/133 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.024226] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.024517] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.024751] scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.024965] scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.025122] scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.025360] scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035212] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035302] sd 0:0:0:0: [sda] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035344] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035472] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035579] sd 1:0:0:0: [sdb] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035605] sda: Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035625] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.035823] sdb: Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036017] sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036097] sd 2:0:0:0: [sdc] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036132] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036298] sdc: Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036439] sd 3:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036531] sd 3:0:0:0: [sdd] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036566] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036742] sdd: Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.036934] sd 4:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037022] sd 4:0:0:0: [sde] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037061] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037207] sd 5:0:0:0: [sdf] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037302] sd 5:0:0:0: [sdf] Write Protect is off Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037347] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037615] sdf: Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.037646] sde: sdb1 sdb2 sdb3 < sdc1 sdc2 sdc3 < sde1 sde2 sde3 < sdf1 sdf2 sdf3 < sdd1 sdd2 sdd3 < sda1 sda2 sda3 < sdf5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.053938] sdb5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.054355] sd 5:0:0:0: [sdf] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.054383] sd 1:0:0:0: [sdb] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.054666] sdd5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.055068] sd 3:0:0:0: [sdd] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.055314] sda5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.055689] sd 0:0:0:0: [sda] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.056188] sde5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.056579] sd 4:0:0:0: [sde] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.075324] sdc5 > Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.075747] sd 2:0:0:0: [sdc] Attached SCSI disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.481011] md: raid10 personality registered for level 10 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.535096] md: md0 stopped. Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.540582] md: bind<sdb1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.540738] md: bind<sdc1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.542921] md: bind<sdd1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.543139] md: bind<sde1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.543352] md: bind<sdf1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.543877] md: bind<sda1> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.546943] raid10: raid set md0 active with 6 out of 6 devices Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.546989] md0: detected capacity change from 0 to 30005526528 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.549208] md0: unknown partition table Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.602546] md: md1 stopped. Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.605855] md: bind<sdb2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.606911] md: bind<sdc2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.607089] md: bind<sdd2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.607393] md: bind<sde2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.608725] md: bind<sdf2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.608990] md: bind<sda2> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.611563] raid10: raid set md1 active with 6 out of 6 devices Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.611597] md1: detected capacity change from 0 to 17999659008 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.614316] md1: unknown partition table Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.651508] md: md2 stopped. Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.675260] md: bind<sda5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.675789] md: bind<sdc5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.675927] md: bind<sdd5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.676087] md: bind<sde5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.678580] md: bind<sdf5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.678782] md: bind<sdb5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.678804] md: kicking non-fresh sdf5 from array! Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.678811] md: unbind<sdf5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.692116] md: export_rdev(sdf5) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.692181] md: kicking non-fresh sde5 from array! Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.692192] md: unbind<sde5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.704067] md: export_rdev(sde5) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.704080] md: kicking non-fresh sdd5 from array! Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.704089] md: unbind<sdd5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.716058] md: export_rdev(sdd5) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.716120] md: kicking non-fresh sda5 from array! Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.716128] md: unbind<sda5> Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.744058] md: export_rdev(sda5) Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.760915] device-mapper: uevent: version 1.0.3 Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.761665] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com Feb 16 19:57:48 HAM-XEN1 kernel: [ 1.970788] PM: Starting manual resume from disk Feb 16 19:57:48 HAM-XEN1 kernel: [ 2.011324] EXT4-fs (md0): mounted filesystem with ordered data mode Feb 16 19:57:48 HAM-XEN1 kernel: [ 2.905863] udev[481]: starting version 166 Feb 16 19:57:48 HAM-XEN1 kernel: [ 3.045260] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 Feb 16 19:57:48 HAM-XEN1 kernel: [ 3.045268] ACPI: Power Button [PWRB] So weit, so schlecht. Der Versuch, den Verbund mittels mdadm --assemble /dev/sd[a-f]5 wieder zusammenzufügen scheitert. Ein mdadm --examine /dev/sd[a-f]5 ergibt folgendes: root@Microknoppix:/var/log# mdadm --examine /dev/sd[a-f]5 /dev/sda5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 212b9662:bffaa01c:222b200e:e5abe2ba Update Time : Wed Feb 16 18:55:43 2011 Checksum : 48567961 - correct Events : 0 Layout : near=2 Chunk Size : 4K Device Role : spare Array State : .AA... ('A' == active, '.' == missing) /dev/sdb5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 9c2d3357:15074540:5ab7d82b:4571851b Update Time : Wed Feb 16 18:55:43 2011 Checksum : def2da66 - correct Events : 162 Layout : near=2 Chunk Size : 4K Device Role : Active device 1 Array State : .AA... ('A' == active, '.' == missing) /dev/sdc5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : e76a68e6:972c6d46:43e4796e:3d6617e6 Update Time : Wed Feb 16 18:55:43 2011 Checksum : 81835f17 - correct Events : 162 Layout : near=2 Chunk Size : 4K Device Role : Active device 2 Array State : .AA... ('A' == active, '.' == missing) /dev/sdd5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : 5cb4c654:687a72eb:13327150:6eea6365 Update Time : Wed Feb 16 18:55:43 2011 Checksum : f62ac7bf - correct Events : 0 Layout : near=2 Chunk Size : 4K Device Role : spare Array State : .AA... ('A' == active, '.' == missing) /dev/sde5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : ed7703a0:68cb9773:bc4fd223:ad6f15a4 Update Time : Wed Feb 16 18:55:43 2011 Checksum : db9f7f38 - correct Events : 0 Layout : near=2 Chunk Size : 4K Device Role : spare Array State : .AA... ('A' == active, '.' == missing) /dev/sdf5: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 9326853a:28cc0a17:261d22f3:6258fc33 Name : HAM-XEN1:2 Creation Time : Wed Jan 5 23:56:04 2011 Raid Level : raid10 Raid Devices : 6 Avail Dev Size : 1922265088 (916.61 GiB 984.20 GB) Array Size : 5766794448 (2749.82 GiB 2952.60 GB) Used Dev Size : 1922264816 (916.61 GiB 984.20 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : bcf87c99:a95c7413:c2750aba:39b63c21 Update Time : Wed Feb 16 18:55:43 2011 Checksum : 8854fdda - correct Events : 0 Layout : near=2 Chunk Size : 4K Device Role : spare Array State : .AA... ('A' == active, '.' == missing) Gibt es noch eine Chance, die Daten zu retten oder muss ich das ganze vollständig neu aufsetzen? Jede Hilfe ist willkomen. Vielen Dank und beste Grüße Oliver |