Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[oliveirahalisson]

Hello friends, I searched a lot about this information and it was not a solution.
I'm from Brazil, I'm a DNS323, it always worked very well.
The power supplies from the OK source were running fine, until the moment I saw the blue front led flashing and were no search results by Easy Search - Dlink Utility.
I made the serial cable, but when doing the process http://dns323.kood.org/howto:reflash_from_windows I have a step of I have a DNS-323 that I can not update the firmware, I can upload the images via TerraTerm using kermit (according to the Wiki), however, once it is loaded, it immediately drops with the error message in the title repeated several times.
Is there any way to fix this DNS323?
What is a remote access feature to my equipment, donate some value through paypal so that I can help the subject resolver.
Thank you very much
Regards,
Halisson

[oliveirahalisson]

This is log :


 ** LOADER **
 ** MARVELL BOARD: RD-88F5182-NAS-2 LE

U-Boot 1.1.1 (Feb 26 2009 - 11:33:03) Marvell version: 1.7.3.003

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB
Detect phy 1118
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5182 Rev 2
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Hit any key to stop autoboot:  0
Marvell>> loadb k
## Ready for binary (kermit) download to 0x00100000 at 115200 bps...
## Total Size      = 0x0016bd5c = 1490268 Bytes
## Start Addr      = 0x00100000
Un-Protect Flash Bank # 1
Erase Kernel from 0xff820000 to 0xff99ffff Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Kernel Size = 1490268
Copy to Flash... done
Protect Flash Bank # 1
Marvell>> loadb r
## Ready for binary (kermit) download to 0x00100000 at 115200 bps...
## Total Size      = 0x00540a6b = 5507691 Bytes
## Start Addr      = 0x00100000
Un-Protect Flash Bank # 1
Erase Ramdisk from 0xff9a0000 to 0xfff7ffff Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Ramdisk Size = 5507691
Copy to Flash... done
Protect Flash Bank # 1
Marvell>>

[ivan]

I have to ask why you decided on such drastic measures? 

1) did you check the +12v and +5v output from the power supply under load?
2) did you try the reset?
3) if you removed the drives did you mark them with which slot they came from?
4) do you have a backup of your data on the unit?
5) have you checked the c-mos battery voltage and if low did you replace it.

The usual cause of the power LED flashing is a problem with the external power supply. One voltage may not be working or be too low when under load which could also be the cause of failure in the log.

If it is the power supply that is faulty you had better hope you haven't killed the unit and I returns to normal operation without more radical work.

[oliveirahalisson]

I have to ask why you decided to take such drastic measures?

Tks to answer and help me.



1) Have you checked the + 12v and + 5v output of the power supply under load? Yes, 11.9vdc and 5.01 vdc.
2) Have you tried resetting it? Yes, not the response at system startup, after startup or before troubleshooting and serial testing.
3) If you removed the drives, did you mark them with which slot they came from? Yes, I write "writing" HDD 0 and HDD 1.
4) Do you have a backup of your data on the drive? Yes.
5) Have you checked the battery voltage c-mos and, if low, did you replace it? I have the test without battery, change the battery, but no problem of change.

The usual cause of power LED blinking is a problem with the external power supply. A voltage may not be working or be very low when under load, which could also be the cause of log failure. Ok, but if with the NAS connected it shows the tensions that I measured, I believe it is not a problem, what do you think?

If it is the power supply that is defective, it is better to expect that you have not killed the unit and I return to normal operation without more radical work.

I appreciate all the help. I even tested one of the disks: I got another NAS (DNS 320) and I put one of the disks, it started normally, I see a space used on disk, but I can not mount the file share (\\ 192.168 .xx \ NAS \ Data, for example), when trying to create a share and permissions, I can evolve to conclude it does not show error but also does not create the share. I do not know if the disk is in Read Only or it can be permissions, I really am noob in Linux.

Tks to help me!

Halisson

[ivan]

A few points.  The unit uses the Linux Ext2/3 file system when it formats the drives and it uses a Software RAID.  both of which can lead to losing all your data if not handled correctly.

Now, before I can do much to help you I need to know the answers to some questions.

1) what are the voltages, under load, at the output plug of the power supply?  You may need to get an electronics technician to do the measurements for you (should be 12v @ 3A load and 5x @ 3A load, if not a replacement is required)
2) how were the disks setup, RAID 0, RAID 1 JBOD or Standard?
3) do you have a recent tested backup of your data?
4) since you have removed the disks did you mark then indicating which slot they came from?

Questions 2 & 3 are to determine how to deal with the data on the disks and 4 determines if you have broken the RAID array.

[oliveirahalisson]

hi Ivam,

Some points. The drive uses the Linux Ext2 / 3 file system when it formats the drives and uses a software RAID. both can lead to the loss of all your data if they are not handled correctly.
I took care of this, it is written HDD0 and HDD1 with a card / sticker.

Now, before I can do much to help you, I need to know the answers to some questions.

1) What are the voltages, under load, in the power supply output plug? You may need an electronics technician to make measurements (12v @ 3A load and 5x @ 3A load if no replacement is required)
I refit all welds and recap of the capacitors, the power supply voltage were measured with a fluke 108 11.9vdc and 5.01 vdc were measured with the NAS connected and with the disks in the test case with load.

2) how were the disks, RAID 0, RAID 1 JBOD or Standard configured? RAID 1.
3) Do you have a recent tested backup of your data? Yes I have.
4) Since you removed the disks you then marked indicating which slot they came from? Yes, I marked with the sticker and did not reverse at any time.

Questions 2 and 3 are to determine how to handle the data on the disks and 4 determines whether you have broken the RAID array.

The big problem is to make the NAS go back and not just be a paper weight box, as for the data I have another NAS that did an "online" Rsync so I have the NAS to NAS data backup mirror.
I appreciate your help, thank you for your patience and goodwill.

[ivan]

Sorry for the delay but I needed to get some information, when I retired and passed the company on I left all my notes there.

My old head technician asked one question that I should have asked.  When you tried to flash the unit did you use a serial down converter (in other words a circuit that converts the 5v output of the serial, or USB, down to the necessary 3.3v required by the CMOS memory)?

The following is from the instructions we supplied with each NAS we were contracted to maintain.

Hard reset instructions for D-Link DNS-323  NAS

If your DNS-323 NAS is not working as it should, dropping connections or not being responsive, you should first do a reset of the NAS to see if the problems persist.
Other scenarios where you might want to reset your NAS is if you've forgotten the password or misconfigured it and can't get access anymore.
Your can reset your D-Link DNS-323 in the following way(s):

With the reset button

    Locate the reset button on the back off the NAS
    While the unit is powered on, press the reset button with a thin object (e.g. paperclip)
    Hold the button pressed for 10 seconds,  or  until the power LED on the front  panel start flashing then release.
    The unit will reboot by itself. Allow a minute for the device to reset.
    You can now setup your NAS again through the user interface
   

The last resort 30-30-30 reset

If the above instructions don't work you can always try the 30-30-30 reset as follows:

    When NAS is powered on, press the reset button and hold for 30 seconds. (Use a paper clip or something thin)
    While holding the reset button pressed, unplug the power of the NAS and hold the reset button for 30 seconds
    While still holding the reset button down, turn on the power to the unit again and hold for another 30 seconds.

This process usually works for resetting any NAS to it's factory setting.

Note:  THIS IS THE LAST RESORT RESET  If it doesn't work call our technician.



Default factory settings for D-Link DNS-323

If you have performed a reset of your DNS-323 device or not changed the defaults, you should be able to access it with the following settings:
Default Gateway IP: 192.168.0.32 D-Link login instructions
Default username: admin
Default password: blank
Default subnet mask: 255.255.255.0
Default DNS server: 192.168.0.32
Note: If you are using the default settings you should change them to increase security and prevent unauthorised access to your network.

How to login to the DNS-323

To login to the DNS-323 NAS and change the settings, you can follow these steps:

    Make sure you are connected to the NAS's network by ethernet cable.
    Open your browser and visit http://192.168.0.32
    You should be prompted with a login dialogue.
    Enter the username: admin and the password blank
    Note: If you have already changed the password use that instead.
    You will now be logged in. If you haven't yet changed the defaul password, we recommend that you change it first thing you do after logging in.

If these instructions don't work for your NAS, you should call our technician on:                                                  and quote your service contract number.

I offer this in the hope that it might help - sometimes the simple things are those we forget.

One of the techs is going to go digging in the records because she thinks she remembers seeing something like your log.  If there is something there it will say what we did to fix it or why it couldn't be fixed.

[oliveirahalisson]

Again I appreciate all your help.


My old chief technician asked a question I should have asked. When you tried to flash the drive, did you use a serial down converter (in other words, a circuit that converts the 5v output from serial, or USB, to the required 3.3v required by CMOS memory)?
It is a PL2303 adapter, 5vdc, and remembering that I can do typing text, upload files, etc.
The reset does not work at any time, nor with the 30-30-30, does not change the led and does not change the post of the prompt line command.

I offer this in the hope that it might help - sometimes the simple things are those we forget.

One of the techs is going to go digging in the records because she thinks she remembers seeing something like your log.  If there is something there it will say what we did to fix it or why it couldn't be fixed.


I really appreciate all the tips, I hope I have clarified your doubts.
I appreciate your help and I can make you a gift of appreciation, for you to take a wine a beautiful lunch. 

[ivan]

OK your PL2303 USB to Serial adapter isn't enough for flashing the unit. For that you also need a Serial to TTL/Cmos voltage unit because anything exceeding 3.3v will kill the flash memory.

An example of such a converter is: https://www.petervis.com/modules/max3232-rs232-serial-port-to-ttl-converter-module-db9/max3232-rs232-serial-port-to-ttl-converter-module-db9.html   

As I said, if you didn't use one of the serial to ttl/Cmos converters then I am afraid your unit is dead as far as flashing the firmware is concerned.  Sorry.

[oliveirahalisson]

Hi Ivan
Sorry for all this time to answer, I had health problems in the family and I was far from all this.
Understood about the adapter, however the PL2303HK also provides 3.3vdc, in tests it had not connected the 3.3vdc or 5vdc, but from its suggestion it is connected to power from 3.3vdc - RX - TX - GND.
 ( http://www.prolific.com.tw/UserFiles/files/ds_pl2303HXD_v1_4_4.pdf )
however nothing has changed. Do you think it could be the cable? it's a TTL cable if so, if I can indicate another cable, because my notebook does not have a serial port.
Thank you very much

[ivan]

OK, I think I need to try and explain some c-mos basics.

In almost all cases c-mos semi conductors operate at 3.3v or less for any write, or read signal.  If you write to them with a signal greater than 3.5v you kill the, hence the need for the level converter between the RS232 serial port and the device.  on average the signal level of the RS232 serial port is -13v to +13v.

It appears the first time you tried writing to the DNS-323 you did so without using a level converter and the log shows the results - burnt out sections of the flash memory of the SOC.  The only way to recover from that is to replace the SOC which requires specialist equipment.

Below are a few URLs that might help you to get a better idea but I doubt that they will help restore your NAS.

http://dns323.kood.org/start
http://dns323.kood.org/hardware:serial
http://dns323.kood.org/howto:serial_level_adapter

[oliveirahalisson]

Hi, thanks for all your help. The technician who made the electronic connection made sure that the cable 5v was not connected at any time, only RX-TX-GND. either the 5v or 3.3 was not connected because it showed the success of the connection (did not have to say) when I said to be connected to 5v power I was wrong. After his tip, what only was done would be the feeding with 3.3vdc which did not change, according to the report.
Sorry for the inconvenience, it was my mistake. What do you think?

[oliveirahalisson]

Hi Ivan,

I bought the cable http://www.nskelectronics.in/index.php?route=product/product&product_id=904 but still without success and news.

Could you share a way to erase the memory, maybe it was all there, something like that?

I'm with less hope than before.

[ivan]

I am sorry but having talked with my old employees W think you have killed the flash programmable memory.

You say that all that was connected between the RE232 serial port and the NAS was Rx, Tx and Gnd. Now unless you had a level shifter on the Rx and Tx lines you supplied much more than the maximum 3.3v to the Flash memory and that is what kills it.

I started working with Cmos chips  in the early 1980s, in that time the operating voltage dropped from 5v, as in TTL chips, to the current 3.3v of SOC units of today.  In that time I have never seen anyone recover a device that has had an over voltage applied to it.  In fact we had special workspaces - anti static bench tops and anti static floor covering and we wore anti static wrist straps because a static charge could easily kill the devices.

Sorry but I don't think I can be of any more help at the moment.

[oliveirahalisson]

Hi Ivam,

Thank you for your help,
I have a friend who was able to evaluate a problem on another 320 DNS and believed to be the problem of my NAS. I made the purchase of IC En29lv640b (flash memory), however our device is DNS323 rev C (different from the other) and despite getting the new part, we do not have the file to write, when trying to back up the information, several pins presented errors and badblocks while reading.
I have the new part but I do not know the file to put in, do you have any tips?
Could it be just this defective IC?
Could it be the .bin file of the firmware recorded inside?