Hey, just wanted to post my feedback and experience with 2TB ADF drives and the DLINK DNS-343 after one of my drives bit the dust last week.
Originally, I had four 2TB Seagate Barracuda LP drives (ST32000542AS) which were configured as a JBOD array; Now that one of them has failed, I decided it best to reconfigure the unit using a RAID-5 array with the new replacement.
Originally, I tried replacing and building the array using a new 2TB Seagate Desktop HDD (ST2000DM001) since it was the closest available drive to me, but after re-configuring the drives into a RAID-5 array, and having the format saying it was successful, the DNS-343 would state that the RAID-5 array was degraded after the initial reboot following the re-configuration, and after spending days trying to rebuild the array.
Then I realized that this replacement drive was running at 7200rpm vs 5900rpm of 3 remaining original drives I had in the array as well, so I returned this drive and picked up a 2TB Seagate NAS HDD (ST2000VN000), which runs at 5900rpm and should do the trick, right? Negative. Same issue, formats successfully but always reports that the RAID is degraded.
Finally I stumbled across this thread and read about the issues with ADF and the DNS-343. Even though firmware 1.05 states there is support for ADF, apparently it is dependant on the drive being used, as the Seagate ST2000VN000 should technically be supported but did not work in my DNS-343 running 1.05.
So, I took this drive back and picked up a 2TB WD RED NAS HDD (WD20EFRX) as recommended by Schtuperman, and opted to fully reset the DNS-343 configuration back to default/factory settings before rebooting the unit and re-configuring the array.
The format completed successfully (although the web interface got stuck on "Initializing 0%") but the OLED display was showing the formatting progress up until it read "100% done", and then I had to physically hold down the power button to power off and reboot the DNS-343 since I could not access the web interface at all as it was literally frozen on the "Initializing 0%" screen so I closed the browser window and kept getting connection timeout errors when trying to access it again via the IP).
However, I'm happy to report that once it booted up again, the RAID-5 array no longer reported back as 'Degraded' and had completed the configuration/format/sync successfully, and no more errors running the S.M.A.R.T. test on any of the drives! Again, note that I am now running three older Seagate ST32000542AS drives with one WD RED WD20EFRX in a RAID-5 configuration without any issues!
Thanks to Schtuperman for his comments which greatly helped me get my unit back up and functional with a working RAID-5 configuration!
