NAS box is not detected

[OldSag]

Hi, All
I have a NAS box (Zyxel NSA221) with 2 x Seagate Barracuda 1Tb drives, set up as Raid 1. My router is a Thomson TG585. The NAS is now about 60% full (approx 580Gb data).

Problem is now none of the computers on the network can see the NAS. The software that came with it has a 'Discover' applet that is supposed to show it on the network (but doesn't). The router is aware of it and shows its IP address, which when pinged does not respond. I've tried doing a 'factory reset', (which doesn't effect the data or partitions), and reading one of the drives with an external reader (in Windows), with no luck.

I really don't want to lose the data, so if anyone can come up with a way of getting it working long enough to copy the data off, or any other way to get the data off, that would be great!
Thanks in advance

 

[Nothinman]

What happened when you plugged it into Windows? Chances are it runs Linux so the drives are using a Linux filesystem that Windows can't read. Can you try booting from a Linux Live CD with the drives plugged in externally and see if it reads them?

 

[OldSag]

Windows didnt see the drive, it could tell a drive was there under disc management but thats about as far as it went.

I just tried getting a spare computer and plugging the drives into that and then booting from a linux live cd, but linux wasnt able to read the drives either.

I thought it could be as the raid wasnt setup so i set up the drives as a raid 1 array through the bios making sure not to select to wipe the drives, now through the bios it comes up as a mirror array with a status as healthy, but when i boot into linux its a no go, it can see the drives but if i go to disk utility it can see that the drives are part of a raid component but thats it, i try to enable the raid but it says an error about missing components of the raid

It does seem to be a dilly of a pickle ive got myself into here with this box

 

[Nothinman]

If you run 'fdisk -l' it should print the partitions on all disks it sees. From there you can run 'file -s /dev/blah' to see what's on there. That should give you some idea about in which direction you need to go.