first I deleted libgcc_s.so.1, after that I cut and pasted another file from the same version of firmware, MBWE booted and work. I connected disks to my PC and made images by command dd. But when I returned disks back to MBWE, device hasn't already started. Because I didn't know what happenned, I tried some rescue procedures from this forum.
No succes. I tried image, that has damaged one of archive (I think it is SDA1-disk B). I don't understand, which image can I use instead of that damaged archive. It is the reason, why I am working with my images, but I am not sure, whether images are good. I know about create RAID on the sda4 and sdb4 to the md4, about modification of mdadm.conf. All of partitions have type fd (Linux raid autodetect). I don't have any ideas.
Behaviour of MBWE: When I switch on, LEDs blinks once, disks works…but that's all. LEDs don't light, fan don't spin, no connect to LAN. If I look at inittab, first records mounts other partitions. In my opinion, it is problem…when this procedure failed, it can't be written to logs and all is freeze.
Today, I appeared interesting thing-I opened fstab on disk A and there was strange content, later I found out that was content of smbd.conf. I didn't understand what happened. I repaired fstab from the disk B and I connected disks back to MBWE, no works. I connected disk to PC, fstab on both disks was good, but mdadm.conf on disk A contain only . (dots). On disk B was right content. Both of files had same sizes.
Do you know any rescue procedure, which works for two-disks devices? I don't need understand, what happened with my MBWE, but I want functional device. I spent with repairing about 40 hours…:-( and I have no ideas.
Thanks a lot for your advice