Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I've had my DNS323 for over a year and it has been running faultlessly 24x7 in Raid 1 with 2 x 250GB drives. Cron jobs backup to it every night and it is mounted by an XP Pro box and two Fedora boxes (using NFS and fun-plug).
The 250GB is now not enough, so I've got a 1GB drive that I can mirror after a bit of a shuffle.
The new drive is a WD Caviar Green WD10EADS
Stage 1 was copy all the Raid 1 structure to a 1GB disc on a QNAP 209.
Step 2 was replace the 2 x 250 with a new 1GB and copy back the file structure.
Step 3 would have been move the 1GB from the QNAP into the 323 to restore the Raid 1 feature, then put the 2 x 250 in the QNAP as JBOD for fast general network use.
To do this, I upgraded the firmware to 1.07 (from 1.03, I think) at the same time as Step 2. Bad move: two changes at once. Should have known better.
Since the upgrade/disc change and file restore, I've been having total lockups on the 323. Symptoms:
* 323 will not respond to telnet or ssh from Linux. Locks the user terminal requiring a kill to free it.
* File sharing by CIFS and NFS lost.
- XP says the device has become unavailable.
- Linux ls (or any other access) of the mount point causes a freeze requiring a kill of the frozen shell from another session.
* But 323 responds to ping ok! (Fixed IP allocated from modem/router DHCP)
* Front panel network light is flashing like crazy; disc light is on - disc in LH bay.
* 323 ignores the off switch. Requires scary power unplug to shut it down (ignores the reset button too)
I have managed to umount the CIFS and NFS with a rather brutal -fl when in this state. Naturally, they will not remount as the 323 is dead apart from ping (CIFS says "no directory", NFS just times out).
So at long last, the question:
Has anyone else had problems after a 1.07 upgrade? I really doubt the new 1 x 1GB disc (not Hitachi) is at fault as it comes up again ok with everthing as before--but it is not 24x7 backup usable as it is now. Presumably, I can backout the 1.07 upgrade--not gone looking for how yet.
Last edited by modeng (2009-08-06 03:56:38)
Offline
Additional data: despite the crazy flickering of the network activity light, packet sniffing shows only light, innocuous traffic to/from it. Sample:
12:40:10.386974 IP dlink-1.microsoft-ds > modeng2.58185: . ack 664971781 win 4428 <nop,nop,timestamp 5020252 34398113>
12:40:10.387002 IP modeng2.58185 > dlink-1.microsoft-ds: R 664971781:664971781(0) win 0
12:40:15.386241 arp who-has dlink-1 tell modeng2
12:40:15.386365 arp reply dlink-1 is-at 00:1c:f0:1a:9f:e2 (oui Unknown)
12:40:31.589221 IP modeng2.1023 > dlink-1.nfs: . ack 1 win 501 <nop,nop,timestamp 36195908 5010330>
12:40:31.589379 IP dlink-1.nfs > modeng2.1023: . ack 1 win 0 <nop,nop,timestamp 5022380 33981689>
12:40:36.562186 arp who-has modeng2 tell dlink-1
12:40:36.562213 arp reply modeng2 is-at 00:00:e2:78:b9:c0 (oui Unknown)
12:42:31.611025 IP modeng2.1023 > dlink-1.nfs: . ack 1 win 501 <nop,nop,timestamp 36225908 5022380>
12:42:31.611227 IP dlink-1.nfs > modeng2.1023: . ack 1 win 0 <nop,nop,timestamp 5034430 33981689>
12:42:36.581774 arp who-has modeng2 tell dlink-1
12:42:36.581800 arp reply modeng2 is-at 00:00:e2:78:b9:c0 (oui Unknown)
So at a low level, the OS is alive and well (modeng2 is the Linux box which had the 323 CIFS and NFS mounted, but has had it umounted with -fl, so I don't know why it is still asking questions...)
Offline
hi,
have you been able to resolve the issue ? I have the same problem and it just started few weeks ago. I am running 1.09 and have not changed anything since a long time but it just freezes exactly the way you are mentionning. I can ping it but can't access it or reboot it unless I unplug it.
Offline
I've also notice that the fan turned off when the device freezes... I did a scan disk and they seem to be fine.
Offline
HAve you tried a reset and manual reconfiguration? Enable services one at a time to isolate the issue.
Offline
I have noticed that although I had the Fan set to Auto, it was not turning on. I also had the unit close to a heat source so I think it was overheating. I moved it away and forced to fan to be high all the time and it has been working for the last 8 hours. Will update in a couple of days to see if that was the issue. It was at about 45-46 degree, I've set it up to shut down at 60 and now it is running at about 33.
Offline
A reset and manual reconfigure is still suggested as this often fixes the fan issue.
Offline