JBOD Linux RAW file system recovery

[heatmizer]

Hello. I am hoping that I can get some advice here and if this software will do what I need. What I did to put myself in this situation was completely STUPID and my fault and desperately seeking resolution.

Current situation:
2 Maxtor SATA 300GB disks put into a D-Link DNS 321 NAS, formatted for JBOD. Converting current environment from PC to MAC. The d-link accessible from the new Airport Extreme network so this is where my stupidity comes in to play.

I take the disks out of the dlink and put them back into my Vista Ultimate machine. Of course it can't read the disk and I start to panic. Remember something about Dynamic disk and convert the disk to Dynamic disk. Tells me I must format in order to read, NO CAN DO. So the lights start to brighten up and I rebuild the PC network and hook up the dlink DNS NAS again. It now can not read disk. Actually it is asking me to pick a disk state (JBOD, Raid 1 etc.). This I process again wants to format the disk.

So my delima is that I have two disk set into a linux Raw file system in a JBOD state that have been converted to dynamic disk.

How screwed am I?

Will this program recover the data I need?

Thank you in advance for any help and suggestions that come my way.

Shannon

[Alexey V. Gubin]

Unfortunately, ZAR cannot recover what was originally a JBOD.
I'm actually not aware of any software that can do this in automatic mode.
We're investigating if we can implement that, but it not going to be ready anytime soon (say we need at least a month).
For now, the only option I see is a data recovery lab. (however, we do not provide this sort of service).

[gamez]

DiskInternal's RAID Recovery claims to be able to recover JBOD, but at a price of 250$.

I was wondering if ZAR meanwhile has been complemented with this feature, or if you are considering it.

Regards,

g.

[Alexey V. Gubin]

ZAR will NOT work for a hardware JBOD, nor a Linux-based JBOD.
If you have a damaged Windows Dynamic Disk ("Spanned volume"), it is then worth a try with an eval version (I recall something was massively fixed since 8.4).