ReadyNas 104 RAID 0 Failure - Can I re-establish RAID 0 between drives?

[sunsparc]

Good Morning - Ive had this readynas unit for about 3 years now and never any issues.  This weekend it started acting strange and the windows computers using the shares started to have long wait times.  I attempted to reboot the device but it just hung so I powered it down by pulling the plug.  It booted back up to FS check and then just sat at booting for a long time and it failed and would never boot.

I took the advice from another post and pulled the two drives.  I put in a new clean drive and the readynas unit booted and wanted to install new firmware twice so I did that to 6.6.1.  The nas booted up fine and then I shut it down and put the two RAID 0 drives back in and it boots up, but says the two volumes are inactive.

Is there a way I can re-establish the RAID 0 between these drives either through the GUI or SSH etc?  

Also, if I subscribe to the Phone Support, is this something they could re-establish or is advanced support required for something like this?  Or is the data pretty much gone?  I did backup the critical data on the drive to Amazon Glacier every night at least, but there are some LUNs Id like to recover etc if at all possible.  

From my recent logs, it does show the two drives as being ok, so shouldnt I be able to re-establish it ok?

Disk /dev/sdb: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 63AEC502-0A8C-4A49-8580-F710A48272AE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 64-sector boundaries
Total free space is 45 sectors (22.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
3 9437248 5860533119 2.7 TiB FD00

Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0F08DF93-D0BD-46CC-9E86-34623B45A90C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 64-sector boundaries
Total free space is 45 sectors (22.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
3 9437248 5860533119 2.7 TiB FD00

[sunsparc]

To add additional information, I SSH'd into the device and checked the dmesg..md127 is the raid mount point...Does this mean this can't be repaired??

[ 17.989481] BTRFS critical (device md127): corrupt leaf, slot offset bad: block=73203712,root=1, slot=232
[ 17.990383] BTRFS critical (device md127): corrupt leaf, slot offset bad: block=73203712,root=1, slot=232
[ 17.991115] BTRFS: Failed to read block groups: -5
[ 18.020868] BTRFS: open_ctree failed

[mdgm-ntgr]

Updating the firmware in a situation like this is not recommended unless you get professional advice from us that determines that it is.

Using RAID-0 is inherently risky. If a disk fails all RAID-0 volumes using that disk are lost.

Data recovery is much more likely to be successful if a redundant RAID level is used.

What are the SMART stats of your disks like?

[sunsparc]

Both disks in the array look good.  When i do a btrfs check /mnt/md127 thats when I see the bad block.  When trying to mount thats when the message in dmesg is generated..

[FramerV]

Hi sunsparc,

Let me see if I can get some inputs from mdgm about this.

Regards,

[sunsparc]

Thanks for your help!  I ended up expanding my drives to 4 and doing a RAID5..losing everything in process, but had it all backed up to amazon glacier...