DSM-G600, DNS-3xx and NSA-220 Hack Forum

The unit's accessible but it shows no files, no folders, nothing. I can't create anything on it either, getting the dreaded -50 error (unexpected failure message, from memory) if I try. I can't get to the files through the command line either - once I go /Volumes/drivename/ I see that it's empty.

I'll give it another try tomorrow (using telnet), but I'm tempted to junk the unit once I've salvaged my files. I might keep it for interest's sake, but I know it's not possible to use it as a backup drive. I'd be happier if a drive had failed catastrophically inside the case - that's unfortunate, but still more reasonable than the unit failing to read or write completely. I require a backup that... well, backs up.

After you sort things out with your data, why don't you try upgrading the firmware to 1.05 and resetting it up?  I've been using 2 of these things since for over a year now and have gone through F/W 1.03 - 1.05 and have never lost a thing.  The only time I lost any data was using an NTFS module to try to connect up a USB drive with NTFS -- and that was my fault.  If you have not made any changes, I suppose it's possible to have a corrupted F/W, since it has failed 2 times.  Try reflashing it.

@fordem: The unit's not a bad unit - it worked fine for a long time once I set it up correctly and got past the first screw-up (which was most likely my fault, early days and all that), although I had it sitting in the corner powered off for the last few months. It's well past warranty though.

@bq041: I'm not willing to use this unit to store data. It fails in a manner that I won't allow. I might reflash to 1.05 and play with it, but it's proven to be strictly something to toy with, not a reliable backup unit.

@mig: I never quite got the script working to start afpd automatically, so when I power the drive up I telnet in, start etch and then start afpd manually. I tried killing it and starting again, rebooting the unit, powering down overnight but the result is the same - nothing shows at all on the mounted drive even though the space available reports correctly (123GB of 457 free).

I realised last night that if I could telnet in then something must be there, and I've now located my files in /mnt/HD_a2/etch/home/patterson/ (which is the folder presented as the mount point). Today I'll pick up an external FireWire case, plug the drives in and clean them up. I'll lose RAID-1, which was a big part of the reason to get this unit, and network attachment, which was the other big reason to get this unit, but I'll gain a drive that actually works and is reliable.

Thanks for replying everyone, but I'm done with the 323 now.

Last edited by Gary Patterson (2008-05-31 04:41:01)

Let me just make sure I've got this right. 

You are blaming the device for being unreliable because it does not meet your expectations when running a custom OS the manufacturer never intended to run on it, in order to run a custom compiled program, that comunicates in a protcol that was also not intended by the manufacturer?

Gary, depending on the type of backup application your are using,
perhaps something like Apple's Time Capsule would suit your needs better?