Differences

This shows you the differences between the selected revision and the current version of the page.

information:known_issues 2009/03/17 01:48 information:known_issues 2022/03/11 12:02 current
Line 1: Line 1:
-====== Known Issues ====== +====== Known Issues ====== 
-Unfortunately, the DNS-323 isn't the perfect piece of equipment and it contains a bunch of [[wp>Software_bug|bugs]] and some compatibility issues.  +Unfortunately, the DNS-323 isn't a perfect piece of equipment
- +It contains a bunch of [[wp>Software_bug|bugs]] and some compatibility issues. 
-Some of the bugs documented on this page may have been addressed in the newer firmware revision, FW 1.0.6, released 2008-12-29, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes_106.txt|here]] and available [[http://support.dlink.com/products/view.asp?productid=DNS-323#apps|here]]. +Some of these bugs may cause the DNS-323 to 
- +//format or erase one or both of your hard drives//, especially when inserting 
- +or removing hard drives from the enclosure. 
- +Do not insert any disks with valuable information into the DNS-323
 +and make sure you back-up your data before inserting or removing hard drives.
 +Some of the bugs documented on this page may have been addressed in the
 +newer firmware revisions:
 +  * FW 1.10.0, provide some fix and Advanced Disk architecture which is mandatory for new large disks
 +  * FW 1.0.9, dated 06/16/2010, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes.txt|here]] and located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_fw_109.zip|here]]
 +  * FW 1.0.8, dated 02/17/2010, located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_firmware_108.zip|here]]
 +  * FW 1.0.7, dated 03/27/2009 and 2009-04-16, located [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/|here]]
 +  * FW 1.0.6, released 2008-12-29, described [[ftp://ftp.dlink.com/Multimedia/dns323/Firmware/dns323_release_notes_106.txt|here]] and available [[http://support.dlink.com/products/view.asp?productid=DNS-323#apps|here]].
 +Note that the web screens for the DNS-323 may show the firmware as "1.07"
 +not "1.0.7".
Line 15: Line 24:
===== Adding an extra disc can wipe both! ===== ===== Adding an extra disc can wipe both! =====
 +//Firmware//: 1.09\\ Appears to have resolved this issue.  Starting with a single disk in the LEFT bay, I was able to add a second matched blank disk to the right bay.  After rebooting I selected RAID1 with manual rebuild and then manual rebuild.  (Sorry didn't keep the exact procedure, but I did a couple of disk changes and it seemed to work correctly every time.)
 +
//Firmware//: 1.05\\ //Firmware//: 1.05\\
//Severity//: High\\ //Severity//: High\\
Line 20: Line 31:
//Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives.\\ //Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives.\\
 +//Note for FW 1.0.4//:\\
 +This issue does not appear to exist under firmware 1.04, if one uses the
 +RAID menu to format the disc (assuming you have inserted a new disc to
 +fix a broken RAID 1).  I have just rebuilt a Raid-1 array by inserting
 +a blank disc while powered off, however, I did skip the first 'format'
 +prompt, and instead used the RAID configuration to format and introduce
 +the new drive *per manual instructions*.  Perhaps this 'bug' is related
 +only to the first format option offered by the drive firmware, and not
 +the one listed in the RAID menu.
 +Perhaps this 'bug' is due to not following directions in the manual?
===== Adding an extra disc can wipe data on existing drive! ===== ===== Adding an extra disc can wipe data on existing drive! =====
-//Firmware//: 1.03, 1.05, 1.06 are all confirmed\\+//Firmware//: 1.03, 1.05, 1.06, 1.07, 1.08 are all confirmed\\
//Severity//: High\\ //Severity//: High\\
//Description//: Consider you have one disk installed in the right hand bay, when looking at the front cover of the DNS-323. Now insert a second drive in the left bay while the device is powered off. After powering up the web interface will prompt "Your new, second hard drive will now be formatted. The existing harddrive will not lose any data." It will display the vendor/model/serial number and size of the second drive. However if you press "next" it will format the first disk in the right bay.\\ //Description//: Consider you have one disk installed in the right hand bay, when looking at the front cover of the DNS-323. Now insert a second drive in the left bay while the device is powered off. After powering up the web interface will prompt "Your new, second hard drive will now be formatted. The existing harddrive will not lose any data." It will display the vendor/model/serial number and size of the second drive. However if you press "next" it will format the first disk in the right bay.\\
//Remarks//: Slight variations to this procedure might not result in this bug. For example starting with the first drive being installed in another bay or hot adding (= while being powered on) drives.\\ //Remarks//: Slight variations to this procedure might not result in this bug. For example starting with the first drive being installed in another bay or hot adding (= while being powered on) drives.\\
//Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives\\ //Workaround//: Don't have other disks installed when formating a new drive. Boot bay with just the new drive installed, format, power off, reinstall first disk afterwards. If volume numbering and network shares mess up, you can still swap drives. Or search forum for manually formating drives\\
-//Links//:http://forum.dsmg600.info/t3113-Arghhh.-Drive-wiped.html\\ +//Links//:http://dns323.kood.org/forum/t3113-Arghhh.-Drive-wiped.html\\ 
-http://forum.dsmg600.info/t885-OMFG%2C-Lost-data!-D-link-terrible!.html+http://dns323.kood.org/forum/t885-OMFG%2C-Lost-data!-D-link-terrible!.html
 +//Note for FW 1.0.4//:\\
 +This issue does not appear to exist under firmware 1.04, if one uses the
 +RAID menu to format the disc (assuming you have inserted a new disc to
 +fix a broken RAID 1).  I have just rebuilt a Raid-1 array by inserting
 +a blank disc while powered off, however, I did skip the first 'format'
 +prompt, and instead used the RAID configuration to format and introduce
 +the new drive *per manual instructions*.  Perhaps this 'bug' is related
 +only to the first format option offered by the drive firmware, and not
 +the one listed in the RAID menu.
 +Perhaps this 'bug' is due to not following directions in the manual?
 +//How to avoid this//:\\
 +Remember to insert the first HDD into the left handside bay (what is said in the manual). The left one is always the first one, the right one (if exists) is always the second one. If it were to format "the second drive", it is the one on the right handside.
 +===== Adding a disk causes FFP to stop working =====
 +//Firmware//: 1.07\\
 +//Severity//: Medium\\
 +//Description//:
 +I set up the unit with one 1.5 TB drive in the left bay.  No RAID.
 +I installed the FFP 0.5 release and enabled sshd and httpd. When I shut
 +down and added a second 400GB drive with data on it (ext3) into the
 +right bay and rebooted, the unit first ran a massive recursive "chmod -R a+w"
 +on every file and directory in the new 400GB drive
 +(many tens of minutes of blue blinking lights) before it even started
 +the network interface, then on login to the web interface it told me
 +I had to reformat the "new" drive.  I told it to "Skip" the reformat.
 +The scripts in /etc/hotplug/{sata,usb}mount contain recursive "chmod -R
 +a+w" lines that trigger if the root directory of your partition is not
 +"drwxrwxrwx".  Make sure you "chmod 777" all your partitions before
 +you install a disk with existing data.  Make sure you never alter the
 +permissions of the root directory on any installed disk, or you'll trigger
 +the huge recursive chmod.
 +With the second drive present, the FFP configuration that I had set
 +up on the previous drive never started working - no sshd, no httpd.
 +The old disk was still labelled Volume_1 and the new disk (ext3) was
 +listed as Volume_2 and I could browse the data on both disks.  In the
 +web "Status" page under "Physical Disk Info", the numbers were reversed,
 +with the new disk (right) being labelled first as disk "Slot 1" and the
 +old one (left) as disk "Slot 2".
-===== Windows Vista Can't Access Shares After A While ===== +I shut down and removed the ext3 disk I had just added and rebooted. 
-//Firmware//: 1.05\\+The FFP configuration re-appeared; sshd was available again. 
 + 
 +I shut down and swapped the two drives in the two slots.  The system came 
 +up with FFP working this time, but now the new ext3 drive (sdb, left) 
 +was Volume_1 and the old drive (sda, right) was Volume_2.  In the "Status" 
 +page under "Physical Disk Info", the right drive (old, sda) was listed as 
 +"Slot 1" and the left drive (new, sdb, ext3) was listed as "Slot 2". 
 +At least the Volume numbers match the Physical Slot numbers now. 
 + 
 +It appears to me that the fun_plug might have to reside on the "rightmost" disk. 
 +If you only have one disk in the left slot, that's fine until you put a disk in 
 +the right slot and fun_plug stops working until you swap the disks. 
 + 
 + 
 +===== Windows Vista and Windows 7 Can't Access Shares After A While ===== 
 +//Firmware//: 1.05,1.09,1.10\\
//Severity//: High\\ //Severity//: High\\
-//Description//: After some period of normal usage, shares on the DNS-323 can no longer be accessed by Windows Vista.\\+//Description//: After some period of normal usage, shares on the DNS-323 can no longer be accessed by Windows Vista or Windows 7.\\
//Workaround//: Files can be recovered by connecting via FTP, or from a non-Vista computer.\\ //Workaround//: Files can be recovered by connecting via FTP, or from a non-Vista computer.\\
-//Fix//: Disable Flow Control, IP Checksum Offload, Priority & VLAN, TCP and UDP Checksum Offloads if your network adapter has these options and you should be able to access the DNS-323. This is based off a Nvidia based chipset. Options will differ per board or card.\\+ 
 +//Fix//: Disable Flow Control, IP Checksum Offload, Priority & VLAN, TCP and UDP Checksum Offloads if your network adapter has these options and you should be able to access the DNS-323. This is based off a Nvidia based chipset. Options will differ per board or card. \\ 
 +Also make sure the following entry exists in the C:\Windows\System32\drivers\etc\hosts file (and remember to reboot both the device and the Windows machine after making the changes). For eg. if your DNS-323 device IP is 194.164.92.101\\ 
 +194.164.92.101 dns-323\\ 
//Fix//:If you still can connect to the DNS-323 configuration through web browser go to "Advanced/Network Access Settings" and try to give all accounts access to the shared folder //Fix//:If you still can connect to the DNS-323 configuration through web browser go to "Advanced/Network Access Settings" and try to give all accounts access to the shared folder
 +
 +//Fix//:Install vista driver from [[ftp://ftp.dlink.com/Multimedia/dns323/Drivers/dns323_driver_PNPX_102.zip]]
 +
//Fix//: Still investigating. The actual root cause for this problem is still elusive. I have suspected that it may have been caused by installing Vista Service Pack 1, but I'm not sure, because even removing SP1 doesn't fix it, and I'm not about to reinstall Vista, at least not yet. Workarounds attempted so far: //Fix//: Still investigating. The actual root cause for this problem is still elusive. I have suspected that it may have been caused by installing Vista Service Pack 1, but I'm not sure, because even removing SP1 doesn't fix it, and I'm not about to reinstall Vista, at least not yet. Workarounds attempted so far:
  * Uninstall Service Pack 1.   * Uninstall Service Pack 1.
Line 56: Line 136:
I have Windows Vista Home + SP1, I tryed everything described here but nothing worked. //Fix//: Enable UPnP in the Router, and it worked. I have Windows Vista Home + SP1, I tryed everything described here but nothing worked. //Fix//: Enable UPnP in the Router, and it worked.
-//Note//: Virnave: This is definately a network card issue. I have tried booting my PC into Ubuntu with the same network card and it doesnt work. I tried using a usb wireless adapter and it worked in both Vista and Ubuntu. 
//Note//: mbutler2575: Seems to related to Sync Centre in my case. I can access the DNS-323 via \\DLINK-1A9F9C$NoCsc$ which bypasses the local offline files cache but not through \\DLINK-1A9F9C. I can access all the rest of the network from the Vista machine and I can access the DNS-323 from Win 98SE & XP Pro machines. //Note//: mbutler2575: Seems to related to Sync Centre in my case. I can access the DNS-323 via \\DLINK-1A9F9C$NoCsc$ which bypasses the local offline files cache but not through \\DLINK-1A9F9C. I can access all the rest of the network from the Vista machine and I can access the DNS-323 from Win 98SE & XP Pro machines.
 +
 +//Note//: mbutler2575: Seems to related to Sync Centre in my case. I can access the DNS-323 via \\DLINK-1A9F9C$NoCsc$ which bypasses the local offline files cache but not through \\DLINK-1A9F9C. I can access all the rest of the network from the Vista machine and I can access the DNS-323 from Win 98SE & XP Pro machines.
 +
 +//Note//: Random Vista SP2 32bit user here with 1.05 firmware, never experienced this issue at all. Not even with Vista SP1. Something to check with Vista and network problems in general is to check for autotuning. See [[http://support.microsoft.com/kb/934430|Microsoft KB article about it.]]
===== Shares seem to lock from smb mounts ===== ===== Shares seem to lock from smb mounts =====
Line 110: Line 193:
Spin-ups have been reported even after the workaround has been performed. If this happens, print one succesful page and it should then be fixed.\\ Spin-ups have been reported even after the workaround has been performed. If this happens, print one succesful page and it should then be fixed.\\
- 
===== Broken iTunes Interface ===== ===== Broken iTunes Interface =====
-//Firmware//: 1.01, 1.01b23?, 1.02? and 1.05\\+//Firmware//: 1.01, 1.01b23?, 1.02?, 1.05, 1.07, 1.08\\
//Severity//: Low\\ //Severity//: Low\\
//D-Link correction//: 1.03, again broken in 1.05\\ //D-Link correction//: 1.03, again broken in 1.05\\
Line 180: Line 262:
//Description//: Users with Windows 2003 and Windows Vista has reported that they fail to transfer 'large' files to the unit. Some reports indicates that this is not an issue with Windows XP. Apparently files in the range 2-4Gb, 6-8Gb and 10-12Gb fails to transfer while 0-2Gb, 4-6Gb, 8-10Gb and 12-14Gb transfers ok. //Description//: Users with Windows 2003 and Windows Vista has reported that they fail to transfer 'large' files to the unit. Some reports indicates that this is not an issue with Windows XP. Apparently files in the range 2-4Gb, 6-8Gb and 10-12Gb fails to transfer while 0-2Gb, 4-6Gb, 8-10Gb and 12-14Gb transfers ok.
-According to findings by [[http://forum.dsmg600.info/profile.php?id=209|tobyg]], as [[http://forum.dsmg600.info/p1419-Yesterday-095533.html#p1419|posted]] on our forum, the problem is a signing issue in the 2.x.x branch of Samba. Or to put it as [[http://forum.dsmg600.info/profile.php?id=209|tobyg]] says:+According to findings by [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]], as [[http://dns323.kood.org/forum/p1419-Yesterday-095533.html#p1419|posted]] on our forum, the problem is a signing issue in the 2.x.x branch of Samba. Or to put it as [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]] says:
>So go into byteorder.h and change this line: >So go into byteorder.h and change this line:
Line 188: Line 270:
>''#define CVAL(buf,pos) ( (unsigned)( ( (const unsigned char *)(buf))[pos]))'' >''#define CVAL(buf,pos) ( (unsigned)( ( (const unsigned char *)(buf))[pos]))''
\\ \\
-//Workaround//: The Samba daemon needs to be replaced. [[http://forum.dsmg600.info/profile.php?id=209|tobyg]] has submitted patched files and a script, which can be used at **own risk**. Instructions and the files needed can be found in this [[http://forum.dsmg600.info/p1419-Yesterday-095533.html#p1419|thread]].+//Workaround//: The Samba daemon needs to be replaced. [[http://dns323.kood.org/forum/profile.php?id=209|tobyg]] has submitted patched files and a script, which can be used at **own risk**. Instructions and the files needed can be found in this [[http://dns323.kood.org/forum/p1419-Yesterday-095533.html#p1419|thread]].
//Mounting from Linux//:  Many linux distros will not mount smb default with Large file support. Use the mount -o lfs option to get Large file support. //Mounting from Linux//:  Many linux distros will not mount smb default with Large file support. Use the mount -o lfs option to get Large file support.
-[[http://forum.dsmg600.info/t491-Large-files.html|thread]]+[[http://dns323.kood.org/forum/t491-Large-files.html|thread]] 
 + 
Line 204: Line 288:
//Description//: After the DNS was booted it is not possible to access any network shares. You need first to log on to the DNS, go to the NETWORK ACCESS section and "touch" at least one rule. Still not corrected in FW 1.03...\\ //Description//: After the DNS was booted it is not possible to access any network shares. You need first to log on to the DNS, go to the NETWORK ACCESS section and "touch" at least one rule. Still not corrected in FW 1.03...\\
//Workaround//: [[howto:telnet]] to the device and issue ''smb restart''\\ //Workaround//: [[howto:telnet]] to the device and issue ''smb restart''\\
- 
*** can anyone actually confirm this issue?  My DNS-323 runs firmware 1.03 and if I reboot the machine, I can access network shares via SMB without logging in to the machine...\\ *** can anyone actually confirm this issue?  My DNS-323 runs firmware 1.03 and if I reboot the machine, I can access network shares via SMB without logging in to the machine...\\
Line 213: Line 296:
*** I have firmware 1.03 and after a "normal" reboot I can access network shares without logging into the machine, but after a power blackout I have to go to the NETWORK ACCESS section as described above. *** *** I have firmware 1.03 and after a "normal" reboot I can access network shares without logging into the machine, but after a power blackout I have to go to the NETWORK ACCESS section as described above. ***
\\ \\
-\\ 
- 
**__Update: 25-Aug-07;__ **** from D-Link tech support in Australia helped resolve this issue by doing the following:** **__Update: 25-Aug-07;__ **** from D-Link tech support in Australia helped resolve this issue by doing the following:**
Line 244: Line 325:
**__Update: 05-Sept-07;__ **__Update: 05-Sept-07;__
Same problem for my network (cannot accès the DNS, no disk mapped). I fix one static IP for my DNS-323 (192.168.1.99) and all works fine !!!!!! Same problem for my network (cannot accès the DNS, no disk mapped). I fix one static IP for my DNS-323 (192.168.1.99) and all works fine !!!!!!
 +\\
 +**__Update: 11-Jun-10;__
 +After the DNS was booted it is not possible to access any network shares by using device name(dns323) but ip address can, to slove this i need to telnet the device
 +and >smb restart
 +my environment : DNS-323, FW1.08, RAID 1, 1.5TB, smb.conf modify manually. windows 7, win xp, windows server 2003.
 +question : any better solution?
 +\\
 +**__Update: 15-Sep-2011;__**
 +With firmware 1.09 I still have occasionally come across this bug. Before reading about this issue here I was unable to find the real reason, but fiddling with the access right in the NETWORK ACCESS section did it. It would be helpful to clean this bug description from workarounds that deal with other machines (e.g. dns323 alias in the /etc/hosts-file).
 +\\
 +**__Update: 01-Aug-2012;__**
 +Bug was still there after the last swapping of drives, so when trying to mount I got:\\
 +//
 +prompt:~$ sudo mount -a\\
 +retrying with upper case share name\\
 +mount error(6): No such device or address\\
 +Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)\\
 +//
 +
 +This time fiddling with the NETWORK ACCESS LIST did not work. I was only able to re-establish access if I deleted the network access list completely (i.e. pressed the button "Reset Network Access List"). This is a pain because then I had to redo all the shares.
 +\\
 +
Thx for this issue. Thx for this issue.
 +
 +
 +
 +
Line 263: Line 370:
UPnPAV: all of the data wasn't sent, so queue this up.(ILibAyincSocket_Send)\\ UPnPAV: all of the data wasn't sent, so queue this up.(ILibAyincSocket_Send)\\
//Workaround//: Disable onboard upnpav and install Twonkyvision?\\ //Workaround//: Disable onboard upnpav and install Twonkyvision?\\
- 
- 
- 
- 
===== Email Alerts ===== ===== Email Alerts =====
Line 279: Line 382:
 +**Email account passwords cannot contain certain characters (e.g. semi-colon):** When the email application is invoked, your email account password is **not** properly escaped for [[http://en.wikipedia.org/wiki/Almquist_shell|ash]], causing certain characters of your password to be interpreted (e.g. a semi-colon is interpreted as the end of the current command execution). Thus, having a password of ";poweroff" could prove quite frustrating. LOL 
 +Bug reported to D-Link on Aug 31, 2010 under case #ALR401034497 (unresolved as of firmware 1.09).
===== Zone Alarm ===== ===== Zone Alarm =====
Line 328: Line 432:
//D-Link correction//: N/A\\ //D-Link correction//: N/A\\
//Description//: The Dynamic DNS (DDNS) feature used to update your dynamic IP and host a server, doesn't behave correctly. After a few hours, you will get blocked from www.dyndns.org and get a notice: Hostname Blocked Due To Abuse.\\ //Description//: The Dynamic DNS (DDNS) feature used to update your dynamic IP and host a server, doesn't behave correctly. After a few hours, you will get blocked from www.dyndns.org and get a notice: Hostname Blocked Due To Abuse.\\
-//Workaround//: Look at this thread: http://forum.dsmg600.info/p15441-2008-05-23-06:16:22.html+//Workaround//: Look at this thread: http://dns323.kood.org/forum/p15441-2008-05-23-06:16:22.html 
 + 
 +===== Problem loading Libraries and Executables Issue ===== 
 +//Hardware//: Acer Aspire easyStore\\ 
 +//Firmware//: Unknown works with 2.6.x Kernel\\ 
 +/Severity//: Critical\\ 
 +//Description//: It needs several attempts to run an executable. Libraries are not loaded or partially loaded. Program crashes directly after execution. Library loading error messages in this timeframe. No clean booting. Sometimes telnet starts and sometimes not.\\ 
 +//Workaround//: Setting // /proc/sys/vm/vfs_cache_pressure// to more than 100 seems to be safer instead of using //swappiness// and //min_free_kbyte//.\\ 
 +//vfs_cache_pressure//: Controls the tendency of the kernel to reclaim the memory which is used for caching of directory and inode objects.\\ 
 +At the default value of vfs_cache_pressure = 100 the kernel will attempt to reclaim dentries and inodes at a "fair" rate with respect to pagecache and swapcache reclaim. Decreasing vfs_cache_pressure causes the kernel to prefer to retain dentry and inode caches. Increasing vfs_cache_pressure beyond 100 causes the kernel to prefer to reclaim dentries and inodes.

Navigation

Personal Tools