DNS-323 serial flash, error "NON GENUINE DEVICE FOUND!!

[petrus_muc]

Hi All,

I have a NAS DNS-323 (CH3SNAS) which worked well for some years but started to hiccup lately. In order to rectify this I have flashed the Alt-F firmware, flashing worked out fine.
NAS is configured as JBOD with 2 identical HDD's.
When starting the NAS it took a long time until the web interface was reachable and the HDD-LED's almost never stooped acting (somtimes blue, sometimes yellow). Access to the files was impossible.
After running for some time web-access wasn't possible any more at all.
So I tried to re-flash the firmware through the serial interface. When starting the NAS and pressing <SPACEBAR> the message "NON GENUINE DEVICE FOUND!" appeared in an endless repetition and no other action was possible any more than to swith the NAS off. I did try this without HDD's attached.

Now my questions:
- where does the error message come from (Marvell ?) and why is it sent ?
- is it possible to erase and reprogram the flash without using the serial interface ?
- do you recommend to bring the NAS to the city dump or is there still hope ?

Thanks in advance for any helpful hint !

Best regards

Peter

[João Cardoso]

On Sunday, 9 August 2015 09:18:48 UTC+1, petrus_muc wrote:

Hi All,

I have a NAS DNS-323 (CH3SNAS) which worked well for some years but started to hiccup lately. In order to rectify this I have flashed the Alt-F firmware,

Which version?

 

flashing worked out fine.
NAS is configured as JBOD with 2 identical HDD's.
When starting the NAS it took a long time until the web interface

The Alt-F web interface?

 

was reachable and the HDD-LED's almost never stooped acting (somtimes blue, sometimes yellow).

If Alt-F was running, than a fsck was being performed. The blue power led should be hearth-beating; in the Status webpage bottom section a Filesystem Operations would appear; in the Login webpage a warning saying that the disks was being checked and not available would appear

 

Access to the files was impossible.

After running for some time web-access wasn't possible any more at all.
So I tried to re-flash the firmware through the serial interface.

Reflashing Alt.-F? Or the vendor (Conceptronic or D-Link) firmware?

 

When starting the NAS and pressing <SPACEBAR>

<space>+<1>

 

the message "NON GENUINE DEVICE FOUND!" appeared in an endless repetition and no other action was possible any more than to swith the NAS off. I did try this without HDD's attached.

I also have a CH3SNAS and never saw that message.

 

Now my questions:
- where does the error message come from (Marvell ?) and why is it sent ?

Probably from the boot loader. It depends at what step in the boot process the message was displayed, the log from the initial powerup screen would help.

- is it possible to erase and reprogram the flash without using the serial interface ?

From linux (on a running system), or through the serial interface or using a JTAG (I never used that)

 

- do you recommend to bring the NAS to the city dump or is there still hope ?

Powerup logs... trying to execute the load and flash commands "in the dark"... is the error message displayed very fast? does the '?' or 'h' commands display anything?

[petrus_muc]

Am Mittwoch, 12. August 2015 19:14:08 UTC+2 schrieb João Cardoso:

On Sunday, 9 August 2015 09:18:48 UTC+1, petrus_muc wrote:

Hi All,

I have a NAS DNS-323 (CH3SNAS) which worked well for some years but started to hiccup lately. In order to rectify this I have flashed the Alt-F firmware,

Which version?

CH3SNAS C05-321

 

flashing worked out fine.
NAS is configured as JBOD with 2 identical HDD's.
When starting the NAS it took a long time until the web interface

The Alt-F web interface?

 

yes

 

was reachable and the HDD-LED's almost never stooped acting (somtimes blue, sometimes yellow).

If Alt-F was running, than a fsck was being performed. The blue power led should be hearth-beating; in the Status webpage bottom section a Filesystem Operations would appear; in the Login webpage a warning saying that the disks was being checked and not available would appear

 

Web Interface wasn't reachable any more, timeout error from Browser

 

Access to the files was impossible.

After running for some time web-access wasn't possible any more at all.
So I tried to re-flash the firmware through the serial interface.

Reflashing Alt.-F? Or the vendor (Conceptronic or D-Link) firmware?

D-Link firmware

 

When starting the NAS and pressing <SPACEBAR>

<space>+<1>

 

Found that out too in  the meantime ! (shame on me !)
 

the message "NON GENUINE DEVICE FOUND!" appeared in an endless repetition and no other action was possible any more than to swith the NAS off. I did try this without HDD's attached.

I also have a CH3SNAS and never saw that message.

One new thing: I tried it again and found out that this ominous message appears as soon as the power connector is plugged in, meaning BEFORE the device is switched on (all LED's are still inactive)

 

Now my questions:
- where does the error message come from (Marvell ?) and why is it sent ?

Probably from the boot loader. It depends at what step in the boot process the message was displayed, the log from the initial powerup screen would help.

No more power-up screen !

- is it possible to erase and reprogram the flash without using the serial interface ?

From linux (on a running system), or through the serial interface or using a JTAG (I never used that)

 

- do you recommend to bring the NAS to the city dump or is there still hope ?

Powerup logs... trying to execute the load and flash commands "in the dark"... is the error message displayed very fast? does the '?' or 'h' commands display anything?

Sorry, acn't access the disks any more where the logfile is stored
nothing stops the weird message, if I send any command the RX text stops for a little while (1-3 sec) and continues then.

 

Thanks in advance for any helpful hint !

Best regards

Peter

Sorry for the delay in answering, I was out of my home !

Thenks and best regards

Peter

[João Cardoso]

That's is very odd...

my box (also a CH3SNAS) u-boot doesn't has the "NON GENUINE DEVICE FOUND!" string in the flash memory.

Have you searched google for for "NON GENUINE DEVICE FOUND"? You will be surprised! Seems that's a MS-Win usb->serial driver issue!

I recently bought a esp8266 12e, with printings on it (AI-Cloud inside) that categorizes it as "fake" according to the descrption of the first message of this thread. And when I hooked it up to my computer, the only things that is sent back via serial is "NON GENUINE DEVICE FOUND!" that appears a few times when I power it up, and then each time I send a command, it just keeps printing the same sentence again and again while the blue led is blinking, only printing the number of letter I sent in the command (if I send "AT" it'll print NO, then if I send "AT" again, it will send "N ", and if I send rubbish like "ATTTTTT" it will just answer by "GENUINE", etc etc....).

I'm afraid I can't help you more.

[petrusmuc28]

Hi João,

Thanks a lot for your finding ! Never in my wildest dreams would I have thought up such a reason !
Anyway I have to sort out my serial2usb interfaces, don't know any more which of the many had that effect !
So again the Chinese fake industry hit ! :-)
I will have to find the right driver (it's somwhere on the NAS) but I have bought a new box (this time a dns-213 rev. B1) and the box works (for the time beeing).
I just have to find out how to set up a directory which I want to access from windows. Until now it doesn't let me in (no permission).
To hell with permissions ! :-D It's mine !

Thanks again for your help to solve a weird problem !!!

Best regards

Peter

[petrusmuc28]

Hi João,

YOUR TIP DID THE TRICK !!!
Just had to find out which serial pin had to be connected to which pin of the usb2serial interface ( in fact TX had to be connected with TX ???) and suddenly I got a readable series of text with various boot messages !
Flashing uboot and uramdisk with TeraTerm was then a piece of cake and completed without error.
Reboot worked without error too.

Thanks to your Tip I have a working NAS again.

Plenty of thanks one more time !!

Peter

[petrusmuc28]

Hi João,

just one information to flashing Alt-f:
after flashing the DNS-323 firmware (and rebooting the device) I flashed the latest version of Alt-f, which worked fine.
After completition however I couldn't reach the web interface of the box.
In one of the how-to's an IP is written "..as a last resort": 192.168.1.230.
I tried it and it didn't work. An IP-Scan showed that the IP is 192.168.1.254 under which the box was reachable and setup worked fine.

Best regards

Peter

[João Cardoso]

On Sunday, 23 August 2015 00:16:25 UTC+1, petrus_muc wrote:

Hi João,

just one information to flashing Alt-f:
after flashing the DNS-323 firmware (and rebooting the device) I flashed the latest version of Alt-f, which worked fine.
After completition however I couldn't reach the web interface of the box.
In one of the how-to's an IP is written "..as a last resort": 192.168.1.230.

Can you identify where that is written? It should say "192.168.1.254, and if it is being used trying to use 192.168.1.253, 252, ... until 192.168.1.230".

Or "trying to find a free IP from the 192.168.1.254 to 192.168.1.230 range, in a decreasing way". Please, Inglish native talkers, suggest a better wording.

In any case, that should only happens when a DHCP server is not available (or the network cable is unplugged). Use Setup->Host

[Arnaldo Barbosa]

Probably the problem is the windows usb2serial driver update. If the usb2serial has a ft232 chip it will not function anymoreunder windows. The updated driver of the FTDI device had idenfied it as a fake device. Try to use linux to communicate whith your hardware or use another usb converter. Take a look at this link: http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/ .

[petrusmuc28]

Hi Arnaldo,
you are totally right !!!
Fortunately I had an older USB-driver for the FT232 converter which doesnt have this check implemented.
Installing this driver caused the USB converter to work as expected and flashing the firmware commenced faultlessly.

Thanks for your help !!

Peter

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/yyAbB-PS-DU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.