D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: JavaLawyer on September 09, 2011, 11:30:05 AM
-
Post your comments and thoughts on the DNS-320 beta firmware v2.02b01...
-
Hi,
I posted my comments here:
http://forums.dlink.com/index.php?topic=41160.0 (http://forums.dlink.com/index.php?topic=41160.0)
But am reposting them on this thread in case it's more 'visible' to others. Mods feel free to move, remove, whatever.
---
Hi guys,
This new firmware has definitely improved things for me!
For one, it now appears the two main bugs I experienced in my old post here:
http://forums.dlink.com/index.php?topic=38598.0
Appear to be fixed on first glance. I will investigate some more to absolutely confirm, but my PS3 is now displaying the files/folders in alphabetical order, and when P2P is enabled the fan is going off after a period of inactivity.
However I have noticed an annoying bug in this release (this was perhaps in the last release as well, can't remember) relating to P2P. It could be the same as what this post is explaining (http://forums.dlink.com/index.php?topic=40419.0), i'll try to explain in full what I see though:
When you "enable" P2P it by creates a folder called P2P in the root folder of Volume_1 to store the files. However for some reason this folder appears to ONLY be accessible via the Web File Server or the NAS itself. I just do not see it in Windows Explorer when viewing the contents of Volume_1 in Windows.
I have checked the permissions etc, etc, and all is ok. If you rename the P2P folder in the Web File Server it suddenly appears in Windows Explorer. Weird. Also if you try to manually create a 'P2P' folder in Windows Explorer it doesn't let you, but you can create any other folders.
Does anyone else get this? It's quite annoying, but I just can't fathom it out.
One other question:
Does anyone know the interval time the NAS uses when scanning for new media files on the uPnP AV server? I added an album into my music collection earlier this afternoon, and on my PS3 it is displaying only 2 of the 11 files. Perhaps another bug, or do I need to wait for it to rescan? I'm not doing another manual one (this will probably make them show up) as this takes hours!! It should do it itself eventually?
Cheers
-
Does anyone know what 3TB drives are supported?
-
Maybe it is just me, but the link for 202 leads me to the old download for 201. Could you please double check the link. Please and thank you.
-
Maybe it is just me, but the link for 202 leads me to the old download for 201. Could you please double check the link. Please and thank you.
Here's a direct link to the firmware beta directory: ftp://ftp.dlink.com/Multimedia/dns320/Beta/Firmware/
-
JavaLawyer, thanks for the link, the problem was the new file was invisible until I refreshed the page...Anyway comments on 2.02. So far so good, I am using the new beta with 2 3TB Hitachi HDS5C3030ALA630 drives, Raid 1, shows as 2747GB, and the % drive used seems accurate. I have a couple hundred GB of videos and I am optimistic. The media server, which I didn't see in the fixes, appears to be working correctly also, all alphabetical. I am mainly interested in this for storage and streaming media and right now it appears to be usable. I don't know about any of the other security features etc, but hopefully they will get around to everything soon.
PS. You must use Internet Explorer to get this thing working.
-
JavaLawyer, thanks for the link, the problem was the new file was invisible until I refreshed the page...
Some browsers (like Firefox) cache the page until you manually refresh. :)
-
Some browsers (like Firefox) cache the page until you manually refresh. :)
Firmware upgrade process doesn't work using Google Chrome. It just sits forever with the spinning wheel and does nothing. I'm pretty sure I used Chrome to upgrade to 2.01 without issue but I had to revert to IE to do this upgrade.
Before the upgrade, it reported my 3TB Hitachi Deskstar 0S03230 as 2951GB Capacity / XXXX Available and my Samsung Spinpoint 1TB as 982GB Capacity / XXX Available (can't remember exactly what was listed as available before the upgrade). After the upgrade, it reports them as 2748.72GB / 2310.54GB Available and 914.95GB / 886.3GB Available. It doesn't say the word Capacity anymore and doesn't seem to list the correct value. I'm not sure if the second number (which I'd presume to be free space) is correct either. The % listed to the right of these values (15% and 3%, respectively) seem to be what I remember having before the upgrade and also match the ratio of the incorrect numbers listed for capacity and free space.
-
Firmware upgrade process doesn't work using Google Chrome. It just sits forever with the spinning wheel and does nothing.
I just did it, no problem at all.
-
I had the same problem when trying firmware 2.01
Always use internet explorer for firmware updates via web browser.
Btw java, thanks
Everything works fine
P2P Folder has now moved in windows explorer via network drive map
Location is now separate from volume 1
Firmware 2.02 looks to be mighty sexy
(http://img594.imageshack.us/img594/723/unledrw.jpg) (http://img594.imageshack.us/i/unledrw.jpg/)
-
Btw java, thanks
. . . Folder has now moved in windows explorer via network drive map
Location is now separate from volume 1
No problem.
Updated that "Wishlist Item" to Fixed.
-
After upgrading to this beta firmware there is no way to downgrade to earlier version. It simply state firmware upgrade failed, tried on both FF and IE browser.
-
After upgrading to this beta firmware there is no way to downgrade to earlier version. It simply state firmware upgrade failed, tried on both FF and IE browser.
If the firmware is giving you trouble, you can reset the DNS-320 to the factory default firmware and settings:
Press and hold the Reset button on the rear of the unit for more than 6 seconds.
Before you perform this procedure, I suggest you save your configurations settings on your local PC and upload the settings after you revert to the original firmware. This file will save you the trouble of recreating all of your user settings. In the web interface, navigate to: Management > System Management > System Settings > Configuration Settings "Save Configuration Settings".
Resetting the factory default firmware will not impact your HDD configuration or data.
-
If the firmware is giving you trouble, you can reset the DNS-320 to the factory default firmware and settings:
Press and hold the Reset button on the rear of the unit for more than 6 seconds.
Before you perform this procedure, I suggest you save your configurations settings on your local PC and upload the settings after you revert to the original firmware. This file will save you the trouble of recreating all of your user settings. In the web interface, navigate to: Management > System Management > System Settings > Configuration Settings "Save Configuration Settings".
Resetting the factory default firmware will not impact your HDD configuration or data.
It's not the firmware that is giving problem, at least not at the moment, it's just doesn't allow downgrading of firmware which is unlike previous beta firmware I have tried before.
Anyway have not try doing a factory reset and see if work. Will post result later.
-
It's not the firmware that is giving problem, at least not at the moment, it's just doesn't allow downgrading of firmware which is unlike previous beta firmware I have tried before.
Anyway have not try doing a factory reset and see if work. Will post result later.
The firmware drives the user interface and end-user functionality. If the firmware upgrade/downgrade is failing, the likely culprit is some issue with or corruption of the current firmware installation.
-
The firmware drives the user interface and end-user functionality. If the firmware upgrade/downgrade is failing, the likely culprit is some issue with or corruption of the current firmware installation.
AFAIK, I'm not the only one facing this issue, which made me wonder why hasn't D-Link themselves encounter this? Anyway, tried doing the downgrade again after performing a restore to factory default settings (via webUI) with the same result.
Can someone kindly verify this on their NAS?
-
AFAIK, I'm not the only one facing this issue, which made me wonder why hasn't D-Link themselves encounter this? Anyway, tried doing the downgrade again after performing a restore to factory default settings (via webUI) with the same result.
Can someone kindly verify this on their NAS?
I believe the factory default settings option in the web interface only resets the user configurations. This feature does not reset the firmware. The reset button on the rear of the unit should reinstall the factory default firmware stored in ROM memory.
-
I believe the factory default settings option in the web interface only resets the user configurations. This feature does not reset the firmware. The reset button on the rear of the unit should reinstall the factory default firmware stored in ROM memory.
I knew you're going to say that so I proceed and perform the reset using the reset button and sure enough it's still the same result.
-
I don't know if it's just me, but is anybody else having trouble using ddns to ftp with 2.02. My ftp was working fine before the upgrade, re-entered the DDNS info, checked the router settings but I cannot access the dns-320. I can't get to it either locally or outside my home network, via the ddns link. I was going to try and downgrade to 2.00 firmware to see if that clears the issue, but apparently that is problematic. Could it be the user settings? I added one after I upgraded but I didn't test 2.02 before adding the new user. Any feedback or suggestions would be appreciated. Thanks
UPDATE: Tried to downgrade firmware from 2.02. Did factory reset first. It will not downgrade to either 2.00 or 2.01. Oh yes, the logon screen will forever remember your password if you make the mistake of checking that little "remember me" box.
-
I'm having exactly the same problem, I cannot downgrade back to the original 2.0 firmware.
Everytime I try to upload the original firmware, I get an upload failed error.
Could someone at DLink pls look into this as its rather annoying, as I'd liek to go back to the 2.0 firmware due to the beta having a bug where the fan nver turns off, even when the box is completely idle (this was working fine in the 2.0 firmware).
-
I'm having exactly the same problem, I cannot downgrade back to the original 2.0 firmware.
Everytime I try to upload the original firmware, I get an upload failed error.
Could someone at DLink pls look into this as its rather annoying, as I'd liek to go back to the 2.0 firmware due to the beta having a bug where the fan nver turns off, even when the box is completely idle (this was working fine in the 2.0 firmware).
I haven't tried downgrading, but I don't have the fan issue. It turns off normally when the temperature gets low, and of course on idle.
-
I don't know if it's just me, but is anybody else having trouble using ddns to ftp with 2.02. My ftp was working fine before the upgrade, re-entered the DDNS info, checked the router settings but I cannot access the dns-320. I can't get to it either locally or outside my home network, via the ddns link. I was going to try and downgrade to 2.00 firmware to see if that clears the issue, but apparently that is problematic. Could it be the user settings? I added one after I upgraded but I didn't test 2.02 before adding the new user. Any feedback or suggestions would be appreciated. Thanks
Same problem here.
My Router was configured one-DDNS, says "x.dyndns.org" while, DNS-320 was configured another-DDNS says "y.dyndns.org"
DDNS@router still works fine but DDNS@DNS320 acts strangely after firmware upgrade to v2.02b01.
DDNS@DNS-320 updates too often until dyndns.org blocks my access :(. No joys when I switch to dlinkddns.com-DDNS
-
also unable to revert back to 2.00 from 2.02beta.
As well found some issues no one else has mentioned.
I'm new with the product - just bought 2 a few days back.
Upgraded one to 2.02beta and set up 2 1TB drives in a RAID 0 configuration.
Did a fairly substantial file copy (about 900GB) using a program called TeraCopy.
With this program I normally do a CRC validation as well.
Shockingly after the process was done nearly every file failed the CRC validation.
All the failed files were larger A/V media files - 175MB, 220MB, 350MB, 500MB, 550MB & 700MB in size.
The only files that passed were the small nfo's - usually less than 1MB in size.
Did some more experimentation - tried some file copies using the standard configuration rather than RAID (silly me, I thought storing a file in RAID 0 might physically make the file different and as a result change the CRC value.)
As I said earlier, I bought 2 DNS-320's. One is now FW 2.02beta and the other still at FW 2.00
with 2 pairs of drives ( 2 x 2TB & 2 x 1TB) I tried copying (a significantly smaller sample than my initial 900GB) to both sets of drives in each of the 2 DNS-320 units.
In all cases all of the larger media files failed CRC validation on both volumes (and on both pairs of drives) on the FW 2.02beta unit
and in all cases all files passed CRC validation on the FW 2.00 unit.
so beware if you are on 2.02beta - your files are not safe.
z
<<added>>
also having file sequencing issues when accessing the DNS-320 with a networked media player.
<<added 2>>
just to clarify
the CRC validation is not a physical write check but a confirmation that the target file matches the source file. I have also attempted to open the "corrupted" files with application programs such as vlc etc - doesn't play them, but doesn't give any message either - just does nothing.
also another observation - from the graphic display of TeraCopy, during the writing process on the FW 2.02beta unit there is a 10 - 15 sec pause in the processing either at the start or end of each file - this pause does not occur on the FW 2.00 unit.
<<another added>>
just did a simple Windows copy and paste of one of the "corrupted" files rather than TeraCopy to the FW 2.02beta unit and the file is fine. Appears it is the use of TeraCopy and FW 2.02beta together which causes the corruption problem as FW 2.00 & TeraCopy worked fine together.
-
I have upgraded to the beta b01, for me it's faster, the fan is less noisy, until now I'm happy with
-
After upgrading unable to use Sync-Centre on mapped drives.
-
I hope D-Link could gave us the possibility to return to a previous firmware..... :(
-
I upgraded to 2.02 hoping that the P2P folder will not be visible in anonymous FTP as I have read in other forums. But it is still there. I even tried changing the settings in File server but it's still the same.
I can't modify the settings in the Account Management->Network Shares. Is there a work-around on this? I thought it was going to be fixed in this firmware.
Can anybody help, please?
Thanks!!!
-
I upgraded To 2.02 and now my NAS crashes all the time. If I am downloaded a few torrents and try to stream a movie or music it freezes and I have to power down the NAS and the power back up. I cannot even find it on the network when this happens.
This was not happening until i upgraded the firmware!
Is this happening for anyone else?
[EDIT]
This seems to be happening when I approach the "10" torrent download more, and if I stream then it crashes... If I don't have any downloads running it will stream OK, this is only after the 2.02 firmware
-
I find I cannot map to a share created under Volume_1 this firmware is buggy!
-
Hello,
i have upgraded my dns-320 to firmware 2.02b01 and now i get issues with FTP.
before upgrading, i could suspend (abort) a FTP file upload to NAS and resume it later.
i could replace a file by the same file with any issue.
for example, i could resume upload of a large file and now it is not possible any more.
i get an error 553, Users may not upload files.
note :temporary files like .pureftpxxxxxx are not created any more by the NAS.
To success the upload i have to delete uncompleted file/files on the NAS ftp, deconnect and reconnect.
So it is possible to replace the file on the NAS with FTP client but still impossible to resume it.
may be d-link technicien could have a look to this issue.
PS : i discovered too late that it's impossible to downgrade the firmware.. :-\
thanks to D-link for precious help
-
:( nobody get the same issue with FTP upload ?
-
:( nobody get the same issue with FTP upload ?
I have got the same problems. FTP don't upload properly after the upgrade. Need to delete the original files to try again>:( >:( >:(
-
I think I have found a problem with files over 4GB on samba shares (not tried ftp or afp) using 3 different apps ViceVersa, and Create Synchronicity, teracopy fail crc/ file size checks or just fail to copy correctly. So any copies from pc to dns320 over 4GB are worthless.
I'm running windows 7 x64.
-
I have got the same problems. FTP don't upload properly after the upgrade. Need to delete the original files to try again>:( >:( >:(
thanks, know i feel less crazy, it's a firmware bug
-
thanks, know i feel less crazy, it's a firmware bug
I've added this bug to the firmware wishlist.
-
I was able to replicate the issue with resuming an upload to the FTP
However not the issue with files copied to my volume. Running a CRC check against the two files, the original an the copy to my Volume the CRC checks out..Has anyone else had any issues with this other than znoga?
-
I was able to replicate the issue with resuming an upload to the FTP
However not the issue with files copied to my volume. Running a CRC check against the two files, the original an the copy to my Volume the CRC checks out..Has anyone else had any issues with this other than znoga?
Yep I have issues with crc checks on files over 4GB, see my post #32
-
Has anyone managed to downgrade or upgrade from v2.02b01 (the original not the re-released version from today) yet?
Tried puting the re-released version on, but no luck ???