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

1.06 with RAID1

Judging from the content of your edit, you appear to have misunderstood the purpose of RAID1 - which as my signature says is about disk redundancy, not data backup.

The idea behind redundancy is to keep things running, on a server with redundant power supplies, if one power supply fails, the server continues to run rather than failing, allowing you to schedule the down time required for the repair - which in most cases would be just the removal and replacement of the failed power supply - they are usually "hot swappable" - servers are now built with redundant disk, redundant power, redundant fans, redundant memory, redundant NICs - pretty much everything that is critical to it's function as a server - except the processor and the system board - but if you need that level of redundancy, you can install redundant servers.

Now - all this redundancy does for you is attempt to make sure your data continues to be available, even in times of component failure - but none of it protects your data itself from being lost - files get deleted - a disgruntled employee, an inexperienced new hire, databses become corrupt - viruses, power & network glitches, without a backup, you'd have all of this expensive redundant hardware - and no useable data on it.

One last thing - D-Link uses the term JBOD - just a bunch of disks - in a different context, on a DNS-323 a JBOD configuration concatenates the two disks to form a single volume, and the failure of either disk WILL result in the loss of all data regardless of which physical disk it was stored on.

For example, if you create a JBOD with your 2 x 1TB disks, you'll get a single 2TB Volume_1 - now, store 250GB of data on it, and whilst doing that observe which disk activity light is flashing (I'm going to guess the left side), so you know which physical disk has the data.  Hot unplug the other disk - you should still be able to access your data - until you reboot the system.

Be very careful with the terminology - make sure you understand how it's implemented - before committing your data, and if you place any value at all on the data, make sure you back it up to a different device or removable media

1.06, Standard.

Won't even consider RAID0 and JBOD. Well actually for that matter, RAID1 either.

1.06, two 400GB Seagate 7200.11 drives, standard (i.e. no RAID or JBOD).

1.05, 2 WD Caviar Green 1TB, Standard (=2 Volumes). TimeMachine Backup Vol1 --> Vol2

I started out with a single Seagate 7200.10 750 GB drive when I first set up my DNS-323. The unit shipped with v1.03 firmware, but I upgraded to v1.04 first thing after installing the drive.

Now I'm running two Seagate 7200.11 1.5TB drives as standard drives under v1.06 firmware.

I cannot comment on firmware v1.03 as I never used it, but v1.04, v1.05, and v1.06 have all been stable for me and each new version has offered increased functionality.

The best thing I ever did was start running the Windows 7 beta as it never forgets my NAS usernames and passwords whereas my old Vista install did all the time.

Innuendo wrote:

The best thing I ever did was start running the Windows 7 beta as it never forgets my NAS usernames and passwords whereas my old Vista install did all the time.

From what I know, the reason windows "forgets" usernames and passwords is just because they try to mount before you get your network up. Therefore it will always try - but fail to reach the IP address.

There is a possibility that the time it takes to receive a DHCP address for your desktop is the reason behind it. If you tried a static - it might just work. Alternatively, I wonder if there are ways to delay the mounting procedure until after the network.

I just have to live with that annoying popup.