mdadm raid 5 no superblocks anymore

i am german, so sorry for my english ;)

just had zero-superblock my mdadm raid 5 on 4 devices. then i tried to create new array to restore my bad raid 5 (read this on article, but i am not allowed to post this link)
now i have this

one hdd got superblock back, but i think it is not the original one
three still got none

Code:

---

debian:/# tune2fs -l /dev/sdb
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name:  <none>
Last mounted on:          <not available>
Filesystem UUID:          319ae1ff-5c87-4d2f-b1bd-4152e2bf1fbe
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:        signed_directory_hash
Default mount options:    (none)
Filesystem state:        clean with errors
Errors behavior:          Continue
Filesystem OS type:      Linux
Inode count:              183148544
Block count:              732571872
Reserved block count:    36628593
Free blocks:              61263574
Free inodes:              183002300
First block:              0
Block size:              4096
Fragment size:            4096
Reserved GDT blocks:      849
Blocks per group:        32768
Fragments per group:      32768
Inodes per group:        8192
Inode blocks per group:  512
Filesystem created:      Thu Mar 12 16:37:19 2009
Last mount time:          Thu Jan  7 17:28:51 2010
Last write time:          Sat Jan  9 10:03:02 2010
Mount count:              184
Maximum mount count:      25
Last checked:            Thu Mar 12 16:37:19 2009
Check interval:          15552000 (6 months)
Next check after:        Tue Sep  8 17:37:19 2009
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:    28
Desired extra isize:      28
Journal inode:            8
Default directory hash:  half_md4
Directory Hash Seed:      65279f15-a0ab-433c-90f6-97ba97f48aae
Journal backup:          inode blocks

---

RAID when it was correct:

Code:

---

debian:/dev# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90
  Creation Time : Thu Mar 12 16:35:56 2009
    Raid Level : raid5
    Array Size : 2930287488 (2794.54 GiB 3000.61 GB)
  Used Dev Size : 976762496 (931.51 GiB 1000.20 GB)
  Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Dec 31 20:48:40 2009
          State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
  Spare Devices : 0

        Layout : left-symmetric
    Chunk Size : 64K

          UUID : 8f8d9f47:15d5e353:030e4bb8:1b229647
        Events : 0.430

    Number  Major  Minor  RaidDevice State
      0      8        0        0      active sync  /dev/sda
      1      8      16        1      active sync  /dev/sdb
      2      8      32        2      active sync  /dev/sdc
      3      8      48        3      active sync  /dev/sdd

---

raid now: it showed up an existring file system, but cannot be mounted, cuz it could not be recognized.

Code:

---

debian:/share# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90
  Creation Time : Sat Jan  9 11:44:55 2010
    Raid Level : raid5
    Array Size : 2930287488 (2794.54 GiB 3000.61 GB)
  Used Dev Size : 976762496 (931.51 GiB 1000.20 GB)
  Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sat Jan  9 11:44:55 2010
          State : clean, degraded
Active Devices : 3
Working Devices : 4
Failed Devices : 0
  Spare Devices : 1

        Layout : left-symmetric
    Chunk Size : 64K

          UUID : 68bd0dfd:29169258:71a8b18e:84df83c0
        Events : 0.1

    Number  Major  Minor  RaidDevice State
      0      8        0        0      active sync  /dev/sda
      1      8      16        1      active sync  /dev/sdb
      2      8      32        2      active sync  /dev/sdc
      3      0        0        3      removed

      4      8      48        -      spare  /dev/sdd

---

any chance of getting my old raid back?