D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-327L => Topic started by: TomTM on September 03, 2014, 11:13:04 AM
-
I've tried Firmware 1.02 and 1.03b03 already and whenever (and only) Raid1 is configured my drives are getting accessed by something periodically. The frequency changes when restarting the device between 2sec and 0.5sec. It is so annoying. I'm using the room n which the nas is located and I can hear it all the time. I am using two WDC WD30EFRX it doesn't matter if LAN is connected or not. Even if I take out one HDD the remaining still does the same.
I want to use Raid1 with this device, else I could have bought a simple 1 Bay NAS which would do something like that. Is there ANY solution?
If you don't believe my I can record a video. I have reset the device to factory defaults several times without any change.
Current NAS Firmware Version
1.03
Current Microprocessor Firmware Version
1.04
Firmware Date
07/22/2014
Hardware-Version
A1
-
How is the DNS connected? To any WiFi routers or switches?
Can you connect a wired PC to the DNS directly with out any routers and see if the problem persists?
Does the DNS do this while disconnected from all networking connections?
-
Thank you for your answer. Please have closer look to what I have written:
I've tried Firmware 1.02 and 1.03b03 already and whenever (and only) Raid1 is configured my drives are getting accessed by something periodically. The frequency changes when restarting the device between 2sec and 0.5sec. It is so annoying. I'm using the room n which the nas is located and I can hear it all the time. I am using two WDC WD30EFRX it doesn't matter if LAN is connected or not. Even if I take out one HDD the remaining still does the same.
I want to use Raid1 with this device, else I could have bought a simple 1 Bay NAS which would do something like that. Is there ANY solution?
If you don't believe my I can record a video. I have reset the device to factory defaults several times without any change.
Current NAS Firmware Version
1.03
Current Microprocessor Firmware Version
1.04
Firmware Date
07/22/2014
Hardware-Version
A1
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
-
Ok, I will try to do this. Unfortunately I'm at work at your service-times, so I hoped I could get support by E-Mail or Forum. Now I just want to add some information for other users:
Processes running:
ID Owner Memory CPU Process Name
2408 root 6,10 0.0 /usr/libexec/mysqld
2551 root 4,60 0.0 /usr/bin/php-cgi
2564 root 4,60 0.0 /usr/bin/php-cgi
2565 root 4,60 0.0 /usr/bin/php-cgi
2340 root 4,00 0.0 mmfm
2352 root 4,00 0.0 mmfc
2864 root 3,30 0.0 smbd
2862 root 3,30 0.0 smbd
1582 root 2,90 0.0 mail_daemon
1917 root 2,40 0.0 and
2509 root 2,20 0.0 /usr/bin/afpd
2865 root 2,10 0.0 nmbd
2530 root 2,10 0.0 /usr/sbin/lighttpd
2605 root 1,90 0.0 scheddler
5016 root 1,80 0.0 /var/www/cgi-bin/status_mgr.cgi
1762 root 1,80 0.0 op_server
2923 root 1,70 0.0 /mydlink/signalc
2338 root 1,60 0.0 apkg
1961 root 1,50 0.0 /usr/sbin/lighttpd-angel
1560 root 1,40 0.0 crond
1 root 1,40 0.0 init
2317 root 1,40 0.0 {mysqld_safe}
2776 root 1,40 0.0 /sbin/udhcpc
2924 root 1,40 0.0 {mydlink-watch-d}
2046 root 1,40 0.0 init
2775 root 1,40 0.0 zcip
4933 root 1,40 0.0 sleep
1788 root 1,30 0.0 avahi-daemon:
1785 messageb 1,20 0.0 /usr/bin/dbus-daemon
1994 root 1,20 0.0 system_daemon
2194 root 1,10 0.0 lpd
1354 root 1,10 0.0 xmldb
2922 root 1,10 0.0 /mydlink/dcp
1855 root 1,10 0.0 fan_control
1919 root 1,10 0.0 set_pwm
1998 root 1,10 0.0 chk_io
1357 root 1,10 0.0 xmldb
1577 root 1,10 0.0 mserver
1564 root 1,00 0.0 /usr/sbin/syslogd
1411 root 1,00 0.0 up_read_daemon
1412 root 1,00 0.0 up_send_daemon
2655 root 1,00 0.0 chk_hotplug
Rebuild function can not be stopped and takes a day until completion also with empty hard drives. I started it, after I tried one device only. After 10 hours it has achieved to do 53%. It can not be canceled by resetting the device or restore factory defaults (must have been wirten on the hard drives).
My hard drives never go into sleep mode in Raid1 configuration.
-
Do you happen to have a smaller drive that you can test out, say a 500Gb or 1Tb just to see if the same thing happens?
3Tb is big...it may take some time, however 10 hours is kind extreme...
What region are you located?
-
I am living in beautiful Switzerland :D.
Currently I only have one drive which I could use, but which also contains all my data. If you can ensure me, that by just plugging it the data isn't erased I could test that.
btw. I just tried "Scan Disk(s)" and the frequency can also be changed by that. The phenomenon still exists. (I've erased the drives and reset the DNS, so I was able to restart drive configuration).
-
Ok, I was recommended to have you phone contact your regional D-Link support office. Ask for level 2 or higher support.
Possible this unit could be defective. Ask for an RMA if they can't figure out whats wrong.
Let us know how it goes.
-
Did you try removing all other devices from your LAN to eliminate the possibility that an application or process on another device on your LAN is hitting the DNS-327L? You may also want to try disabling all DNS-327L add-ons for the same reason.
-
Also, do you have a backup of your data? RAID-1 provides redundancy, but is NOT a backup. I would avoid making any changes to your configuration until after you make a full backup.
-
All addons disabled: by default. There is nothing left I could deactivate. Even enabling doesn't change something.
Lan-cable disconnected: no change, still periodic access.
Lan-cable connected directly to computer: no change, still periodic access.
Configuring to raid0: everything is perfect.
Configuring to jbod: everything is perfect.
Configuring independent Devices: everything is perfect.
Plugging hdd to computer: no periodic access.
Plugging usb hdd to DNS: periodic access to DNS internal drives, external device remains silent and is able to enter hibernation mode.
I plan to Backup the critical Data to the external usb hdd, that's what I bought the DNS for. So my Data is stored primarily on my pc/Laptop, backuped at DNS along other Files (that are currently only stored to my external usb hdd) and backuped to external usb Device.
I am aware that raid1 is no Backup and I knew this before I bought the DNS.
-
Hello,
today I got a new device. Of course with the same problem and now I would like to present this video:
http://somevid.com/q9kdp7PAmVsEPazV0yay (http://somevid.com/q9kdp7PAmVsEPazV0yay)
Would you please fix this?
Btw. I just configured it to "standard" and the drives won't enter Hibernation/Standby either! I can't hear them peridically but the LEDs are blinking more often and independently, but there is a visible pattern.
-
As you mentioned I've inserted my WDC WD10JFCX and used re-formating.
When it was not formatted and the LED was orange it went into stand-by.
Now, since it has been formatted (Standard configuration) it is periodically accessed, the LED is blinking and I can hear it being accessed (it is way more silent, though).
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. Ask for level 2 or higher support. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
-
Hi,
in our company, we are experiencing the EXACT same problem (periodic activity with RAID1 config) with every DSN327L. I created a ticket on the D-Link support site more than 3 weeks ago and up to now got no response.
So I came here looking for help:
- Does somebody now how to solve the problem? -or-
- Does the periodic "click" noise of both hard drive do any harm to them (this noise really does not sound healthy)?
TIA
Morkel
-
We find that phone contact has better immediate results over using email.
Let us know how it goes please.
Hi,
in our company, we are experiencing the EXACT same problem (periodic activity with RAID1 config) with every DSN327L. I created a ticket on the D-Link support site more than 3 weeks ago and up to now got no response.
So I came here looking for help:
- Does somebody now how to solve the problem? -or-
- Does the periodic "click" noise of both hard drive do any harm to them (this noise really does not sound healthy)?
TIA
Morkel
-
I re-edited the ticket and told them that I'm now waiting for almost one month for an answer. Promptly, I got a response saying that this periodic activation is "normal operation" and the ticket was closed. I have 4 units and don't know what to do now. Very frustrating. Calling German support again does not make sense to me because they opened the ticket.
Any ideas!?
Morkel
-
We find that phone contact has better immediate results over using email. Ask for level 2 or higher support.
-
Hi guys!
Have you resolved this case?
Thanx!
PS. I found a strange output from mdadm -E /dev/sda2 or /dev/sdb2 in READ1 mode, other RAID levels are ok:
sh-4.1# mdadm -E /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 9293aa8f :De58c6d7:2850313a:85b5a9e2
Name : 1
Creation Time : Fri May 1 06:49:01 2015
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 5855285848 (2792.02 GiB 2997.91 GB)
Array Size : 5855285848 (2792.02 GiB 2997.91 GB)
Super Offset : 5855286104 sectors
State : clean
Device UUID : 815fe282:4c6f5aa4:6aaeb555:4e24f145
Update Time : Fri May 1 06:54:13 2015
Checksum : b1248c39 - correct
Events : 2
Array Slot : 0 (0, 1, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed)
Array State : Uu 382 failed
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
Hi guys!
Have you resolved this case?
Thanx!
PS. I found a strange output from mdadm -E /dev/sda2 or /dev/sdb2 in READ1 mode, other RAID levels are ok:
sh-4.1# mdadm -E /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : 9293aa8f :De58c6d7:2850313a:85b5a9e2
Name : 1
Creation Time : Fri May 1 06:49:01 2015
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 5855285848 (2792.02 GiB 2997.91 GB)
Array Size : 5855285848 (2792.02 GiB 2997.91 GB)
Super Offset : 5855286104 sectors
State : clean
Device UUID : 815fe282:4c6f5aa4:6aaeb555:4e24f145
Update Time : Fri May 1 06:54:13 2015
Checksum : b1248c39 - correct
Events : 2
Array Slot : 0 (0, 1, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed, failed)
Array State : Uu 382 failed
-
Morkel,
Hi did you resolve your case?
Thanks!
-
I was planning of getting a DNS 327L and three identical HDDs. I plan on using two HDDs in Raid1 and occasionally replacing one HDD when I know I'm clear of any infections. I can't find the compatibility list either. I sure would like to see this case resolved, it sounds like I would have the same problem if I proceed.
-
I recommend contacting your regional D-Link support office and ask about the drive compatibility. I believe most drives will work in this unit. Give them the name and model information of your drive and they should be able to let you know...
I was planning of getting a DNS 327L and three identical HDDs. I plan on using two HDDs in Raid1 and occasionally replacing one HDD when I know I'm clear of any infections. I can't find the compatibility list either. I sure would like to see this case resolved, it sounds like I would have the same problem if I proceed.
-
Same problem here. Im using a single harddrive and the drive getting very hot already. Hybernate and suspend settings dont work. I had an USB disk connected but same problem when i disconnect it
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
Same problem here. Im using a single harddrive and the drive getting very hot already. Hybernate and suspend settings dont work. I had an USB disk connected but same problem when i disconnect it
-
Morkel,
Hi did you resolve your case?
Thanks!
Sorry for the late reply. I could NOT resolve the case. German support told me after several mails and a lot of waiting that this behavior has to be considered "normal operation" .
BUT: I installed the new firmware 1.04b8 yesterday and after rebuilding my RAID1 the problem seems to be gone!!!
Best,
Morkel
-
We recommend phone contacting support for more immediate responce. ;)
Morkel,
Hi did you resolve your case?
Thanks!
Sorry for the late reply. I could NOT resolve the case. German support told me after several mails and a lot of waiting that this behavior has to be considered "normal operation" .
BUT: I installed the new firmware 1.04b8 yesterday and after rebuilding my RAID1 the problem seems to be gone!!!
Best,
Morkel