Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[deca66]

If it is mission critical data you shouldn't run beta code anyways. You should always have a backup somewhere.

Is it the same for official release ?

[ttmcmurry]

Is it the same for official release ?

Of course!  Just because you may have a RAID-1 configured on your DNS-323, it doesn't mean you're completely protected.

For example:  What if lightening struck your DNS-323?  No RAID will protect you from that.  Where is your backup?  How will you get that data back?  How about if a fire occurred?  What if both drives failed simultaneously due to defect?

There are many many more reasons why RAID isn't a replacement for a backup.  RAID-1 is only purposed to create resiliency in the case of a single drive failure.  RAID also doesn't protect against accidental deletion by a user.

Realistically, however the odds of both drives failing simultaneously or being destroyed by natural disaster are amazingly low.  But like anything in life, if you take a moment to prepare for the worst -- IF it ever happens, you'll at least have a place to pick up the pieces and start over without losing everything.

[gasman]

I've managed to stuff my NAS the same way.

Thanks for the post, it fixed my problem.
------------------------------------------------
Update
I'm really grateful someone found out about this, as I would have been well stuffed otherwise.

It is a shame that people who can write such decent software end up causing such grief.

Hi,

I did the same configuration, and had the same problem.
The admin page works fine, but the drive cannot be mounted by the DNS software once Twonky is started.
The red light are blinking for the HDD

I fixed it by desactivating the TwonkyMedia server, using the following preocedure :
 - connect to the DNS using telnet
 - edit the fun_plug file (using VI for ex.)
 - find the line that "starts" the Twonkymedia server (/mnt/HD_a2/starttwonky.sh), and comment (placing a # sign at the beginning of the line.)
 - restart the DNS using the http Admin interface
... then you can connect again to your drive (but twonky is deactivated...)

... hope this helps