D-Link Forums
The Graveyard - Products No Longer Supported => DNS-343 => D-Link Storage => beta code! => Topic started by: drick on April 30, 2010, 07:04:29 AM
-
the other string is getting very loaded down with a lot of back and forth bickering, so I'm going to start this thread in the hopes (probably futile) that we can stay focused on documenting and working the issues with the new code.
here goes...
1st thanks to D-Link for sending me the BETA patch within 15m of requesting, that was appreciated.
2nd i installed on all 3 of my units, so far so good
3rd I've noticed that the email function for system logs which did not used to work now works, which is an added benefit to the patch which i didn't expect
4th the interaction with ffp after fw upgrade has been changed. usually after doing a fw upgrade you have to reload ffp altogether. not so anymore, it's now in a weird hybrid state that sort of recognizes the config, but not really. the net result is that is has to be reloaded, but the behavior is different.
5th error messages in the syslog (Dlink syslog) are interesting, but not clear what they mean?
2010/04/28 08:59:14 fan can't rotate
2010/04/28 09:06:30 fan can't rotate
6th i'm now able to see my units from network and by name instead of having to type in IP address to get to them. this "broke" with the last fw release.
more to follow once i get them re funplugged and get access to the better syslog.
so far so good!!
-
here are a few more new items from proper syslog after getting ffp installed correctly again:
---
Apr 30 14:19:55 DNS343B user.warn kernel: egiga0: Ilegal MTU value 9000, rounding MTU to: 9004
Apr 30 14:19:55 DNS343B user.notice kernel: egiga0: change mtu 1500 (buffer-size 1520) to 9004 (buffer-size 9024)
---
Apr 30 14:19:55 DNS343B user.warn kernel: EXT2-fs warning (device sda4): ext2_fill_super: mounting ext3 filesystem as ext2
Apr 30 14:19:55 DNS343B user.warn kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended
---
-
i also don't remember seeing this before, maybe it's a sign that a RAID6 box is coming (hint hint)! :)
Apr 30 14:19:55 DNS343B user.warn kernel: raid6: int32x4 53 MB/s
Apr 30 14:19:55 DNS343B user.warn kernel: raid6: int32x8 48 MB/s
Apr 30 14:19:55 DNS343B user.warn kernel: raid6: using algorithm int32x4 (53 MB/s)
Apr 30 14:19:55 DNS343B user.info kernel: md: raid6 personality registered for level 6
Apr 30 14:19:55 DNS343B user.info kernel: md: raid5 personality registered for level 5
Apr 30 14:19:55 DNS343B user.info kernel: md: raid4 personality registered for level 4
-
it also appears that the SMART reporting function actually works now, i don't recall this ever working properly before. full disclosure on this one, it may have worked before i don't remember.
sample output below:
Slot 4 S.M.A.R.T INFO
ID Item Now Worst Thres Raw
1 Raw_Read_Error_Rate 118 91 6 177734863
3 Spin_Up_Time 93 93 0 0
4 Start_Stop_Count 99 99 20 1186
5 Reallocated_Sector_Ct 100 100 36 0
7 Seek_Error_Rate 81 60 30 165145824
9 Power_On_Hours 91 91 0 8567
10 Spin_Retry_Count 100 100 97 0
12 Power_Cycle_Count 100 100 20 181
187 Reported_Uncorrect 100 100 0 0
189 High_Fly_Writes 100 100 0 0
190 Airflow_Temperature_Cel 56 51 45 44
194 Temperature_Celsius 44 49 0 44
195 Hardware_ECC_Recovered 65 54 0 58622467
197 Current_Pending_Sector 100 100 0 1
198 Offline_Uncorrectable 100 100 0 1
199 UDMA_CRC_Error_Count 200 200 0 0
200 Multi_Zone_Error_Rate 100 253 0 0
202 TA_Increase_Count 100 253 0 0
-
something seems amiss.
the new fw and logs are really chatty on 1 unit, the other 2 don't have this issue.
2010/04/30 10:04:03 fan can't rotate
2010/04/30 10:10:23 fan can't rotate
2010/04/30 10:25:41 fan can't rotate
2010/04/30 13:14:08 fan can't rotate
2010/04/30 13:35:24 fan can't rotate
2010/04/30 15:50:48 fan can't rotate
2010/04/30 17:13:06 fan can't rotate
2010/04/30 17:19:22 fan can't rotate
2010/04/30 17:26:37 fan can't rotate
2010/04/30 17:34:53 fan can't rotate
2010/04/30 17:43:08 fan can't rotate
2010/04/30 17:52:23 fan can't rotate
2010/04/30 18:01:39 fan can't rotate
2010/04/30 18:09:54 fan can't rotate
2010/04/30 18:19:10 fan can't rotate
2010/04/30 18:28:25 fan can't rotate
2010/04/30 18:37:40 fan can't rotate
2010/04/30 18:46:56 fan can't rotate
2010/04/30 18:56:11 fan can't rotate
2010/04/30 19:05:27 fan can't rotate
2010/04/30 19:14:42 fan can't rotate
2010/04/30 19:23:58 fan can't rotate
2010/04/30 19:34:13 fan can't rotate
2010/04/30 19:43:29 fan can't rotate
2010/04/30 19:52:45 fan can't rotate
2010/04/30 20:03:00 fan can't rotate
2010/04/30 20:12:16 fan can't rotate
2010/04/30 20:22:32 fan can't rotate
2010/04/30 20:32:48 fan can't rotate
2010/04/30 20:42:03 fan can't rotate
2010/04/30 20:51:19 fan can't rotate
2010/04/30 21:00:35 fan can't rotate
2010/04/30 21:10:50 fan can't rotate
2010/04/30 21:20:06 fan can't rotate
2010/04/30 21:29:21 fan can't rotate
2010/04/30 21:39:37 fan can't rotate
2010/04/30 21:48:52 fan can't rotate
2010/04/30 21:59:07 fan can't rotate
2010/04/30 22:08:23 fan can't rotate
2010/04/30 22:17:39 fan can't rotate
2010/04/30 22:26:54 fan can't rotate
2010/04/30 22:37:10 fan can't rotate
2010/04/30 22:46:25 fan can't rotate
2010/04/30 22:55:41 fan can't rotate
2010/04/30 23:05:56 fan can't rotate
2010/04/30 23:15:12 fan can't rotate
2010/04/30 23:24:27 fan can't rotate
2010/04/30 23:33:43 fan can't rotate
2010/04/30 23:42:58 fan can't rotate
2010/04/30 23:52:14 fan can't rotate
-
Are both fan's rotating when they are on? That error leads me to believe one of your fans has physically failed.
-
good question, can i actually see them rotating by looking at the back of the unit?
obviously i haven't looked yet.
-
something seems amiss.
the new fw and logs are really chatty on 1 unit, the other 2 don't have this issue.
2010/04/30 10:04:03 fan can't rotate
2010/04/30 10:10:23 fan can't rotate
2010/04/30 10:25:41 fan can't rotate
2010/04/30 13:14:08 fan can't rotate
2010/04/30 13:35:24 fan can't rotate
2010/04/30 15:50:48 fan can't rotate
2010/04/30 17:13:06 fan can't rotate
2010/04/30 17:19:22 fan can't rotate
2010/04/30 17:26:37 fan can't rotate
2010/04/30 17:34:53 fan can't rotate
2010/04/30 17:43:08 fan can't rotate
2010/04/30 17:52:23 fan can't rotate
2010/04/30 18:01:39 fan can't rotate
2010/04/30 18:09:54 fan can't rotate
2010/04/30 18:19:10 fan can't rotate
2010/04/30 18:28:25 fan can't rotate
2010/04/30 18:37:40 fan can't rotate
2010/04/30 18:46:56 fan can't rotate
2010/04/30 18:56:11 fan can't rotate
2010/04/30 19:05:27 fan can't rotate
2010/04/30 19:14:42 fan can't rotate
2010/04/30 19:23:58 fan can't rotate
2010/04/30 19:34:13 fan can't rotate
2010/04/30 19:43:29 fan can't rotate
2010/04/30 19:52:45 fan can't rotate
2010/04/30 20:03:00 fan can't rotate
2010/04/30 20:12:16 fan can't rotate
2010/04/30 20:22:32 fan can't rotate
2010/04/30 20:32:48 fan can't rotate
2010/04/30 20:42:03 fan can't rotate
2010/04/30 20:51:19 fan can't rotate
2010/04/30 21:00:35 fan can't rotate
2010/04/30 21:10:50 fan can't rotate
2010/04/30 21:20:06 fan can't rotate
2010/04/30 21:29:21 fan can't rotate
2010/04/30 21:39:37 fan can't rotate
2010/04/30 21:48:52 fan can't rotate
2010/04/30 21:59:07 fan can't rotate
2010/04/30 22:08:23 fan can't rotate
2010/04/30 22:17:39 fan can't rotate
2010/04/30 22:26:54 fan can't rotate
2010/04/30 22:37:10 fan can't rotate
2010/04/30 22:46:25 fan can't rotate
2010/04/30 22:55:41 fan can't rotate
2010/04/30 23:05:56 fan can't rotate
2010/04/30 23:15:12 fan can't rotate
2010/04/30 23:24:27 fan can't rotate
2010/04/30 23:33:43 fan can't rotate
2010/04/30 23:42:58 fan can't rotate
2010/04/30 23:52:14 fan can't rotate
another observation, this is only in the D-Link syslog, not the linux log (which apparently are different).
said differently, these messages are not in /var/log/messages at all
-
Yeah you should be able to see it not spinning pretty easily if one isn't.
-
I've installed the 1.04b firmware successfully. No such errors in the system log.
I'll give it a week or so to verify the problem is gone as it happened once every few days.
-
Guys,
I have 2 questions:
1. Is there list of new features in 1.04Beta?
2. Where to download this FW?
Regards,
-
Currently there is no list of fixes, it is basically just to fix the Fan/lockup issue. To obtain this firmware you must send D-Link Multimedia (MOD) a private massage requesting the firmware.
-
Are both fan's rotating when they are on? That error leads me to believe one of your fans has physically failed.
looks like 1 fan is running and the other isn't. do i have to RMA the entire unit for this?
-
looks like 1 fan is running and the other isn't. do i have to RMA the entire unit for this?
Yes. We don't send out parts =P.
As to eLGremlin's questions,
1. Right now it is the fan lockup issue and ADS fix.
2. The firmware is currently not publicly downloadable. If you want to use the beta you can send me a PM with your email address and serial # of your device.
-
Ever since 1.03 came out, my DNS-343 UPnP Media Server no longer recognizes or streams MP4's. I have almost 1.2TB of them on my server, and haven't been able to access them since "upgrading".
Does 1.04a fix this? If so, I'll PM you for the Firmware, if it's ok.
If not, when can I expect to get this functionality back? The docs and advertising clearly say the UPnP Media Server supports MPEG4, and this support was key to me buying the unit in the first place.
I can't go back to 1.02 because I populated the server with 2TB drives after 1.03 added support for them (that's why I upgraded - there was no notice that MP4 support had been Sony'd).
I phoned support but all they could suggest was to wait for 1.04... :\
-
Yes. We don't send out parts =P.
that is what i figured, will they cross ship me a new unit if i provide CC up front?
-
here is another weird one.
one one of my units, i have 3 directories mapped to a Win7 X64 machine that is in a workgroup. i can not any of the directories via their mapped names. i also cannot mount the unit by ip address to the root folder
i can see directory 2 from other machines on my network
this changed after upgrading to 1.04 fw.
-
1.04beta is working for me, thank you.
I believe this is a known issue, but browsing the Upnp directories, %20 is used instead of a space on all files and directories.
Dice
-
that is what i figured, will they cross ship me a new unit if i provide CC up front?
Yes they will. I have done it twice now, trying to trouble shoot this fan issue.
Dice
-
1.04beta is working for me, thank you.
I believe this is a known issue, but browsing the Upnp directories, %20 is used instead of a space on all files and directories.
Dice
Yeah I am aware of this issue. We did do some minor upnp changes in this beta so it must have caused this.
-
I have also posted this in the "Requires frequent manual refreshes" thread:
Also, with the 1.04beta.
Another issue I have noticed (i haven't played around with it however), is that some folders are not located in their proper directories when accessing via my Upnp device.
Folders that should be located in Volume1 - Media - Pictures are located in Volume1. These folders are located in the correct location when browsing via windows on the PC.
The device is a Samsung Blu-Ray Player: BD-C5500
I do have two other Upnp devices, an Asus O!Play HD, and two PS3's a old style and a new slim. i will try and recreate this on the other devices when I get a chance.
Dice
-
here is another weird one.
one one of my units, i have 3 directories mapped to a Win7 X64 machine that is in a workgroup. i can not any of the directories via their mapped names. i also cannot mount the unit by ip address to the root folder
i can see directory 2 from other machines on my network
this changed after upgrading to 1.04 fw.
never mind, this is not a DLink problem, it's a NetGear problem. I also added another switch to my environment at the same time.
That's what i get for making multiple changes at once. :-[
-
I have also posted this in the "Requires frequent manual refreshes" thread:
Also, with the 1.04beta.
Another issue I have noticed (i haven't played around with it however), is that some folders are not located in their proper directories when accessing via my Upnp device.
Folders that should be located in Volume1 - Media - Pictures are located in Volume1. These folders are located in the correct location when browsing via windows on the PC.
The device is a Samsung Blu-Ray Player: BD-C5500
I do have two other Upnp devices, an Asus O!Play HD, and two PS3's a old style and a new slim. i will try and recreate this on the other devices when I get a chance.
Dice
This is actually occurring on the other devices as well. When I go to the Pictures folder where these folders should be, they are not there.
I am doing a manual refresh of the Upnp and will see if this has an effect.
Dice
-
After getting the lockup/loud fan issue repeatedly on my relatively new unit, I got the new beta firmware. I attempted to install it through the web interface and it appeared to go through the update process (progress bar went to the end), ending with the fan running at full blast. After about 30 minutes, the web page hadn't refreshed and I couldn't ping the device, so I pulled the power. Now it's stuck in a reboot loop that I can't get it out of, even if I hold down the reset button on the back. Is there any way out of this?
The current sequence is "DLink", "System is booting..." (animated), "System Restart!", "DLink", etc.
My searches for a "dead device" restore are coming up empty.
Thanks,
Rob
-
After getting the lockup/loud fan issue repeatedly on my relatively new unit, I got the new beta firmware. I attempted to install it through the web interface and it appeared to go through the update process (progress bar went to the end), ending with the fan running at full blast. After about 30 minutes, the web page hadn't refreshed and I couldn't ping the device, so I pulled the power. Now it's stuck in a reboot loop that I can't get it out of, even if I hold down the reset button on the back. Is there any way out of this?
The current sequence is "DLink", "System is booting..." (animated), "System Restart!", "DLink", etc.
My searches for a "dead device" restore are coming up empty.
Thanks,
Rob
I have seen something similar before. Are you running a Raid 5 with 4 drives? Try popping out the last drive in the array before booting. You may need to wipe the partitions on that drive and put it back in the DNS-343 to let it rebuild correctly.
-
I have seen something similar before. Are you running a Raid 5 with 4 drives? Try popping out the last drive in the array before booting. You may need to wipe the partitions on that drive and put it back in the DNS-343 to let it rebuild correctly.
I'm actually running in JBOD mode (it's a backup of my other two NASs, which are running a RAID configuration). I tried popping out all of the disks and I get the same behavior, but I can try other combinations. If the DLink works like other brands, I'm afraid that I've hosed up something in on-board flash.
-
Well, I'm officially out of ideas. No amount of playing around with the device is bringing it back to life, and I've contacted support. Just in case, I'll ask again: Is there any sort of "emergency recovery" procedure? Maybe via USB?
Thanks,
Rob
-
This is actually occurring on the other devices as well. When I go to the Pictures folder where these folders should be, they are not there.
I am doing a manual refresh of the Upnp and will see if this has an effect.
Dice
Manual refresh worked.
Any word on a release date for an official firmware update of 1.04?
-
I sent an email with my sn# and other info and have not received the new firmware. Can someone send it to me? Dlink has no support and cannot support me.
-
I sent an email with my sn# and other info and have not received the new firmware. Can someone send it to me? Dlink has no support and cannot support me.
There is a link at the top of this forum in the firmware release sticky. Read it and download it.
-
Not to nitpick, but for the sake of clarity there's a typo on the NS-343 beta beta download thread:
Click the link below to access the DNS-323 Beta firmware
ftp://ftp.dlink.com/Multimedia/dns343/Beta/
-
Not to nitpick, but for the sake of clarity there's a typo on the NS-343 beta beta download thread:
Click the link below to access the DNS-323 Beta firmware
ftp://ftp.dlink.com/Multimedia/dns343/Beta/
Looks like the page was updated today for the correct model number.
- Thanks
-
Finally got off my backside and loaded the new firmware...unfortunately, after about 30 seconds, the fans came on high speed and the system locked up. Running Raid 5 with 4x1.5 TB disks...just rebooted and getting the 'System is booting' message.
About to pull the plug again and pull that 4th disk as mentioned earlier in the thread....SO MUCH FUN!!
Kind of sad that all this effort has to go into getting these setups nice and reliable.
-
OK...so...system rebooted with 3 out of 4 disks, still showing 1.03 as the firmware. Should I repartition that 4th drive and reinstert...or try to do the firmware upgrade to 1.04a FIRST...then pop the 4th drive in??
I have my config backed up so reapplying all that once this drama is over should not be a problem.
Let me know if you can. In the meantime, I run 'degraded' with 3 drives in.
-
The new firmware worked great after a manual refresh. Without the manual refresh, the folder structure changed to something erroneous and still showed the %20 as the space placeholder.
It should be part of the firmware upgrade to force a manual refresh so users.
Just my opinions :)
-
OK...so...system rebooted with 3 out of 4 disks, still showing 1.03 as the firmware. Should I repartition that 4th drive and reinstert...or try to do the firmware upgrade to 1.04a FIRST...then pop the 4th drive in??
I have my config backed up so reapplying all that once this drama is over should not be a problem.
Let me know if you can. In the meantime, I run 'degraded' with 3 drives in.
Any assistance would be GREATLY appreciated....
-
Any assistance would be GREATLY appreciated....
Try reflashing the firmware again. Once it is successful you can try re-inserting the 4th drive. If it keeps locking up on bootup, wipe the partitions on that drive and re-insert it.
-
Ok, I spoke too soon...
Folders that contain spaces are still showing %20 on the PS3, however, this only appears after the folder is selected.
Sorry to say, there is still a problem with the firmware...
-
Ok, I spoke too soon...
Folders that contain spaces are still showing %20 on the PS3, however, this only appears after the folder is selected.
Sorry to say, there is still a problem with the firmware...
Try resetting to defaults and refreshing.
-
Try reflashing the firmware again. Once it is successful you can try re-inserting the 4th drive. If it keeps locking up on bootup, wipe the partitions on that drive and re-insert it.
OK...1.04beta is on with the 3 drives, gonna power down and reinstert drive 4 and bring it back up...wish me luck!!
-
Try resetting to defaults and refreshing.
I did as instructed, yet remain with the same error. %20
-
OK...1.04beta is on with the 3 drives, gonna power down and reinstert drive 4 and bring it back up...wish me luck!!
FYI...system is running in Raid 5 with 4 good disks again showing FW 1.04Beta...
So far no high speed fans or lock ups....will put her through her paces and see what happens.
Thanks!
-
Is there an update to the 1.04Beta firmware recently? Is there a tentative release date? This is getting crazy that it is taking so long. It's been months with all these known and supposedly resolved issues.
Dice
-
Is there an update to the 1.04Beta firmware recently? Is there a tentative release date? This is getting crazy that it is taking so long. It's been months with all these known and supposedly resolved issues.
Dice
Yeah theres another update coming. Wont be posted today but probably early next week pending no major issues on my units after loading it.
-
Yeah theres another update coming. Wont be posted today but probably early next week pending no major issues on my units after loading it.
Cool. Thank you for the quick reply!
-
hmm...just uploaded the 1.04beta firmware...but my 343 seems to have to response...network is no long accessiblezzzzz
-
I downloaded and applied the 1.04b firmware yesterday. My system is RAID 5 on 4 Seagate 1.5TB drives. So far, no problem, BUT I thought this was supposed to include settable fan speed according to temperature. I have not found any evidence of this. Did I misunderstand - is this a feature for some new version of the firmware?
So far, everything seems to be fine. My previous data is still available, which is nice to see. Will include more as testing continues.
-
One thing I noticed. I no longer have the ability to mount the DNS-343 directories from my Linux box. ??? It still works on my 1.02b server, but will not work with the 1.04b one. I can still access the directories, but only in read only mode which is set for ALL.
Does anyone have any info about this problem?
-
Loaded beta firmware, Unit working without any issues so far. Not getting the lockups like I used too. So far so good. Had no issues after installing new firmware, unit came up all data on drives and accessing without issues.
:D
-
Well just had the first issue. System was working great, went to copy over to it and the unit froze. Had to pull the plug.
The system would not reboot just kept getting system is booting.........
Pulled the 4th hard drive and the system fired up.
Had to delete the partition on the 4th hard drive and then got it up with the 4th drive blank
just redoing the 4th drive - format and then rebuild the data.
I hope it goes well
-
just upgrade all 3 of my units to 1.04b03, no issues on upgrade process.
all 3 took just fine.
-
Data rebuilt - everything working again
Really can't say what happened other then my unit has the 1.04 beta bios in it. Just coping over to the unit from windows 7 and lost all connection to it. The Fans were not on full rev like 1.03 but the same type of lock up.
The wierd thing is having to erase the 4th hard drive like I have read in other posts.
Other then that one time the unit seems to be running just fine.
Will report if anything else happens.
Did notice that the e-mail reporting from the unit worked and reported everything which is really nice.
-
Yeah theres another update coming. Wont be posted today but probably early next week pending no major issues on my units after loading it.
This was posted over a month ago, what is the time line looking like these days?
-
Just keeping this alive. Any word on an official release date for 1.04? Things have finally been running well for me for quite a while with the 1.04b03.
I would feel more comfortable with an official release. Do we even have a time frame yet?
Thank you.
Dice
-
i cannot believe they're not fixing the 'formatting the wrong drive' problem... isnt that a fundamental problem to begin with?!
-
What I find difficult to swallow is that I started this thread:
http://forums.dlink.com/index.php?topic=7955.0 (http://forums.dlink.com/index.php?topic=7955.0)
Almost a year ago and D-Link still has not released an official firmware update that addresses the underlying issue. What is going on there?
-
ya and they can't find a better reason and simply locked the thread and thinks they people will just forget your issue
What I find difficult to swallow is that I started this thread:
http://forums.dlink.com/index.php?topic=7955.0 (http://forums.dlink.com/index.php?topic=7955.0)
Almost a year ago and D-Link still has not released an official firmware update that addresses the underlying issue. What is going on there?
-
Was this because your RAID5 was EXT3 file format and you didn't reformat the drives after the upgrade?
If you read the BIOS update thread it states that you should backup your data, update the FW, format, and then restore the RAID5 and data.
It seems that with the "wipe the fourth drive" and letting the unit rebuild the RAID, it is basically doing what was suggested in the thread.
[quote auth, or=redtheman link=topic=12841.msg81995#msg81995 date=1278734106]
Data rebuilt - everything working again
Really can't say what happened other then my unit has the 1.04 beta BIOS in it. Just coping over to the unit from windows 7 and lost all connection to it. The Fans were not on full rev like 1.03 but the same type of lock up.
The wierd thing is having to erase the 4th hard drive like I have read in other posts.
Other then that one time the unit seems to be running just fine.
Will report if anything else happens.
Did notice that the e-mail reporting from the unit worked and reported everything which is really nice.
[/quote]
-
No my Drives are setup in RAID 5 NTFS, I know what the instuctions said but I didn't have another 2 TB kicking around for backup.
I have not had a single issue with my Dlink since that one time, I was coping over a fairly large 4GIG file when it happened.
Was this because your RAID5 was EXT3 file format and you didn't reformat the drives after the upgrade?
If you read the BIOS update thread it states that you should backup your data, update the FW, format, and then restore the RAID5 and data.
It seems that with the "wipe the fourth drive" and letting the unit rebuild the RAID, it is basically doing what was suggested in the thread.
-
1.04 has been in Beta since April? I really dont think they are shipping it.
-
Why there is no update on this firmware in such a long time?
Has this product become discontinued?
Is D-link dead or something?
I've been waiting for the final 1.04 firmware for a year and when it was about to be released... total silence.
This is disgusting. They are quick to take customers' money but slow in properly fixing issues.
Shame on you D-link!