D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: salmiakx on October 18, 2009, 02:48:57 AM
-
Hello
As i have seen some report i have/Had the same problem.
About every 3-4 day my dns-343 froze and the fans started speeding up. No repons from gui or ping.
I read here that the new version 1.03 Had help some people whit this problem so i downloaded it and upgraded the nas.
And the problem got worse.
First it took about 5 min for the nas to start then i i looged in to the gui and then the nas froze up and the fans started spinning fast.
The Nas froze up after about 3 min use.
Then i just suddenly said in the start of the gui that there was a upgrade for the oled-firmware and there only one button to push "start". It upgraded the oled-firmware and it said that i should unplug the cord, wait 5 sec and the plug it in again.
I did that and now it just says "system booting..." for about 10 sec and then i says "system restarts...." then "system booting..." and so on...
SO now i have a NAS that reboots itself every 20 sec. and i cant access it at all.
I have also tryed to hold in the reset-button when starting up to reset the config but this doesn't help ether...
I live in Sweden and the v1.03 hasn't been release for the European market yet.. i downloaded it from the us-site. Does this matter?
-
i can confirm a similar problem happens to me, sans the restarting. every couple of days (depends on how much writing i'm doing to the NAS) it will become non-accessible. usually restarting the router by cycling the power will fix the problem for a little while.
if i try shutting down the NAS via holding down the POWER button, the OLED just says 'system is halting.......' for ever. if i power down the NAS while that message is on, the raid gets completely rebuilt once i power it back on. that process takes about 12 hours.
i have 4 seagate 1tb drives in r5 array. do you have seagate drives too? i've read about some issues with seagates and the 343.
i'm in australia and we dont have the latest firmware either, but i've flashed 1.03 from the US site without any problems.
This problem was happening before i flashed the firmware, by the way.
-
Iīm using 4 1TB samsung F1 HDD in a R5.
I hade exactly the same problem whit v 1.02
The update to 1.03 f***ed it up totaly... Now it just try to boot up and then restart itself... i have 1,6 TB data laying on the drives... 15 years of work... thank god that i alwas has a backup of all data to a usb-hdd..
Iīm gone report it to Dlink support... and get it replace whit a new one...
-
I got my unit like 1.5 weeks ago. I wish I'd read this forum first.
Now I suffer from the same problem (newest firmware). Froze once a day or two after I got it, and froze again tonight. It takes like 24 hours to synchronize the RAID (4X1.5 TB), during which time transferring anything to it is impossibly slow.
It would be nice if an official could tell us whether or not they're aware of the problem, or working on it.
It seems widespread enough to warrant a hot-fix. I'd love the unit if it wasn't for this, so I'm really hoping I don't have to return it.
-
@ViviOrunitia - when it freezes, just unplug it and plug it back in - dont shut it down via the power button. it wont re-sync then.
however .. i've been doign this over the last few days and it will only stay up for half a day now - instead of at least a week or so. must be the raid getting out of sync or something?? dlink! little help please!
-
I did that last night; simply unplugged it without using the power button.
It still had to re-sync the RAID unfortunately. Quite frustrating.
-
Try resetting the unit to factory defaults and allow it time to sync once more time.
-
resetting the unit wont wipe the raid array?
-
@ben
When you click reset it will tell you that it doesn't effect data on the drives.
I just did it, will be done re-syncing tomorrow. Will come back if the problem persists.
Would be interesting to know if anyone else solved it this way.
-
Interesting...I am no expert, but about the only thing I would be cautious of is what drives you have in the machine. If it came from the factory with say version 1.01 which only supported 1TB drives, and you upgraded to version 1.03 to give you support for larger drives, if you have the large drives in there, how would it handle a factory reset to a firmware that won't handle the drive size??
I don't think that is the issue in this case as the user has only 1TB drives in it, but I know for my unit I had to do a firmware upgrade just to get it to work with my 1.5TB drive array.
Just a cautious word to the wise, remember what you started with and where you are at now.
FWIW
Neill
-
@BatMobile i would assume (and hope) that the firmware would stay the same and not retrograde... @ViviOrunitia let us know how you get on!
-
It doesn't reset the firmware. Just resets the configuration of the unit.
-
i am using the latest firmware 1.03
and i am also experiencing the same problem,
especially often when there is a lot of activities going on at the same time,
e.g. torrent, rsync
-
It doesn't reset the firmware. Just resets the configuration of the unit.
OK...that is interesting...may have to keep that in mind if my unit does not sort itself out in the next few days.
Thanks for clarifying that.
:)
-
Try resetting the unit to factory defaults and allow it time to sync once more time.
I have been having the same problem (fan stay on and NAS freeze up) for the past six months, this seems to get worse with this official 1.30 FW. The symptoms I have observed so far is as the temperature increases and at the same time some large set of data are being written, the fan will will kick starts and system will freeze up in about 10 seconds time. And connection to NAS will be lost, access the the web GUI is not possible but NAS LED is still working normally. Tried power down the NAS by holding on to the power button, the 'Shutting down ...' message will appear like forever while the fan is still blasting away (tried left it in that state for 24hrs before and it is still blasting away, always ended up unplugging the power cable).
A few days ago, I tried reset to factory default and reconfigure the setup to my own settings. Then encountered another freeze last night, it is re-syncing now. D-Link should be looking into this. This seems to affect people using Raid 5. I have 4x1T WD HD configured under Raid 5. I had also encountered a fan-blasting-freeze when doing a scandisk through the webgui.
I also recalled that using one of the beta fw version (cannot remember which one as I tried out every one just hoping to solve this big issue), this freeze never did happen for that beta version, the fan will kick start when getting too hot while writing data to the NAS, the NAS became not responsive for a few seconds then became normal and continue with the writing.
-
sounds like i'm currently doing a factory reset for nothing then. great.
DLC that is *exactly* what is happening with mine. i have 4 x 1tb seagates though. raid 5. by just posting in this forum, does that make dlink look at the problem and respond???
-
Hmmm. Guess I shouldn't expect much improvement from the factory reset after it finishes syncing tonight.
Just throwing it out there that I'm using a similar setup. 4 X 1.5TB WD drives in RAID5.
DLC where did you get access to the beta firmwares? I might have to give that a shot.
-
I have been having the same problem (fan stay on and NAS freeze up) for the past six months, this seems to get worse with this official 1.30 FW. The symptoms I have observed so far is as the temperature increases and at the same time some large set of data are being written, the fan will will kick starts and system will freeze up in about 10 seconds time. And connection to NAS will be lost, access the the web GUI is not possible but NAS LED is still working normally. Tried power down the NAS by holding on to the power button, the 'Shutting down ...' message will appear like forever while the fan is still blasting away (tried left it in that state for 24hrs before and it is still blasting away, always ended up unplugging the power cable).
A few days ago, I tried reset to factory default and reconfigure the setup to my own settings. Then encountered another freeze last night, it is re-syncing now. D-Link should be looking into this. This seems to affect people using Raid 5. I have 4x1T WD HD configured under Raid 5. I had also encountered a fan-blasting-freeze when doing a scandisk through the webgui.
I also recalled that using one of the beta fw version (cannot remember which one as I tried out every one just hoping to solve this big issue), this freeze never did happen for that beta version, the fan will kick start when getting too hot while writing data to the NAS, the NAS became not responsive for a few seconds then became normal and continue with the writing.
So your saying you were having this issue and it went away using one of the betas then the issue came back with the official 1.03?
-
So your saying you were having this issue and it went away using one of the betas then the issue came back with the official 1.03?
Yes, using one of the past beta fw version, the fan started blasting and the freeze occurred only momentary and after the system cooled down, the fan slow down also (at least I don't hear it). Intially I suspected that it may be due to Western Digital HDD Time-Limited Error Recovery (TLER) with RAID, but it seems more like the activation of the fan interrupted some internal process causing a freeze that does not affect the LED display. Also with or without funplug, the freeze still happen with official fw 1.03.
So now I added a external fan to blow against the NAS to lower the temp + breaking up data copy over to the NAS in smaller chunks to reduce the likelihood of another freeze. I removed this external fan hoping a factory default may resolve this by it did not. Hope my findings can help D-Link in making this product more stable.
-
I tried 1.01 (the box came with this), 1.02, 1.03 beta (b60 i think?) and 1.03 proper and had the same problem regardless..
-
I just wanted to tell you peolpe what happend to this case...
I contacted DLINK support in sweden.. And they sent me a replace of the NAS i had.
I talked to a guy there who sayid that they ran a dns-343 on in there test-net and hade run a Beta-driver for about 6 month that had been really stabel. He email me a link to download the same firmware they used.
I got the new NAS and upgraded the firware to that beta. It is beta 1.03 but i dont now if it is the same that dlink has on it support site.
<-- thats the link that they gave me.
If that link is broken you can get it from my own site at:
I have run this firware for over a week now an pushed it whit big heavy files and it works great.
Happy to say that whit the new NAS i didnīt lost any data. It just sync for about 20 hours. Most of the setting in the config was there to. But i reloaded my from my config-backup and everything works great.
Also the NAS runs cooler and the fan doesnīt work that much anymore.
-
Anyone else try this beta and have the problem fixed ?
I just bought the NAS, upgraded to 1.03 right away, put in 4x 1.5 WD Green drives, changed HD settings to prevent the head parking thing and also enable TLER.
I was copying data from my DNS323 to the 343 but after 500gigs out of 1TB transferred, exact same thing happened, 343 froze, I tried to shut down, but it just sat there... after I pulled the plug and reset it took 24hrs to resync...
-
be careful with the above, I tried to downgrade to v1.03b60 and my 343 hung after uploading the fw and now its bricked...
-
Do not post links to OLD betas on these forums from non-dlink sites. On top of that B60 was riddled with critical bugs including data corruption. Links have been removed.
-
Do not post links to OLD betas on these forums from non-dlink sites. On top of that B60 was riddled with critical bugs including data corruption. Links have been removed.
Thats good - some reaction. Solution please.
-
This problem is related to the upnp server on the dns343. I have 4x1tb seagates in mine - was running raid5. With the upnp server enabled under fw 1.02, it would reliably hang on me (couldn't see it any more from XP or vista & the fans just turn on & stay on) every couple of days. Front panel didn't work after that - only solution is to pull the power plug and reboot it cold. Erk.
As soon as I disable the upnp server, the problem goes away. Upgraded to fw 1.03 a while back and re-enabled the upnp server to see what it would do - the problem was worse - usually hangs and the fans turn permanently on within an hour or two rather than within a day or two of the server being up, regardless of whether or not the 343 was being accessed or not. Reformatted it to JBOD to see what it'd do, which gave me more space I needed anyway. Same problem happens under JBOD when I re-enabled the upnp server, so it's not a upnp/raid linked issue - it's just related to the upnp server somehow.
Now I run tversity on a spare pc and that acts as my media server with upnp on the 343 permanently off. That's a pity as it means I have a pc on I don't need and I can't use the upnp function of the 343 which is the main reason I purchased it, but everything works without a hitch at least in this config.
If someone CAN fix the dns343's upnp server with a fw upgrade - that'd be brilliant - it's definately broken. Oh and while you're at it, can you PLEASE give us better config options than "Root yes or no". Really - ignoring the fact that it hangs the box - it's about as basic as it gets and could really use some work.
-
This problem is related to the upnp server on the dns343.
I don't think so. I have the upnp server disabled on mine and I still experience the problem.
-
Well ... it was a good theory!!!
In any case, I don't get the problem with the server off, so there's some commonality there that I'm sure the dlink techs will love to get their teeth into, so we'll see a fw upgrade rsn ... :-)
-
FYI: salmiakx the OP was having trouble because his DNS-343 bricked after he updated his firmware. I have just done the same thing.
All it does is restart over and over. It had locked up I guess after loading firmware. It even got to 100% as well... >:(
I will be calling DLink for another unit.
Dice
-
FYI: salmiakx the OP was having trouble because his DNS-343 bricked after he updated his firmware. I have just done the same thing.
All it does is restart over and over. It had locked up I guess after loading firmware. It even got to 100% as well... >:(
I will be calling DLink for another unit.
Dice
Are you running Raid 5? Try popping out the 4th disk and restarting and let me know how it goes.
-
I have had my DNS-343 for a little over a year. It has supported every request technically that I have made of it. That is until I upgraded one of my 2 home computers to Windows 7. This should have nothing to do with the DNS-343 suddenly going to high speed fan and the loss of the network connectivity for the device, but that is what happened.
The firmware version on the device is 1.03, it has 4 hard drives of varying sizes, 1 - 1TB Wester Digital, 1 - 500 MB Wester Digitital and 2 - 2TB Seagates. All these drives had been working in perfect harmony until the event listed above.
I began to work with the device and to try transferring files of various sizes from outside the device as well as between drives inside the device to determine if there was anything that could be discovered that was consistent. All to no avail. But one thing I did begin to do was reinstall the firmware. At first I got the same result of going to the fans high speed. One time I received @@@@@@@@@@@ along the bottom row on the LCD after a re-installation of the firmware. That was cleared up by rebooting the device a couple of times, but the same issue of the getting the high speed fan result appreared again. Then I reinstalled the firmware again (this was the 5th time since the problem began), which was 6 weeks ago, and then everything began to operate normally which included transferring mass amounts of data of up 39 GB in size without issue. All I can glean from this is that you need to persistent, and continue to work with the device, and continue working with 1.03 firmware.