Zyxel Nsa325 brick

Its my first NAS repair

at first I replaced U38 (DDR3 Vcc) and two DDR ICs.
NAS began to turn on but reboot every 35sec
I have no idea how to fix it

_ _
        |  \/  |  _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  / | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   |  )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| | 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: DB-88F6282A-BP LE 

U-Boot 1.1.4 (Nov 23 2012 - 14:38:22) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz 

DRAM (DDR3) CAS Latency = 7 tRP = 8 tRAS = 24 tRCD=8
DRAM CS[0] base 0x00000000   size 512MB 
DRAM Total size 512MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0x4640000.

Streaming disabled 
Write allocate disabled


USB 0: host mode
  [BlueDBG] reseting SoC Pex[0]  0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
  [BlueDBG] reseting SoC Pex[1]  0 ...
  [BlueDBG] reseting SoC Pex[1]  1 ...
  [BlueDBG] reseting SoC Pex[1]  2 ...
  [BlueDBG] reseting SoC Pex[1]  3 ...
  [BlueDBG] reseting SoC Pex[1]  4 ...
  [BlueDBG] reseting SoC Pex[1]  5 ...
  [BlueDBG] reseting SoC Pex[1]  6 ...
  [BlueDBG] reseting SoC Pex[1]  7 ...
  [BlueDBG] reseting SoC Pex[1]  8 ...
  [BlueDBG] reseting SoC Pex[1]  9 ...
  [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0x4640000, size 0xa00000


Reading data from 0x4640000 --   0% complete.
Reading data from 0x4659800 --   1% complete.
Reading data from 0x4673000 --   2% complete.
Reading data from 0x468c800 --   3% complete.
Reading data from 0x46a6000 --   4% complete.
Reading data from 0x46bf800 --   5% complete.
Reading data from 0x46d9800 --   6% complete.
Reading data from 0x46f3000 --   7% complete.
Reading data from 0x470c800 --   8% complete.
Reading data from 0x4726000 --   9% complete.
Reading data from 0x473f800 --  10% complete.
Reading data from 0x4759800 --  11% complete.
Reading data from 0x4773000 --  12% complete.
Reading data from 0x478c800 --  13% complete.
Reading data from 0x47a6000 --  14% complete.
Reading data from 0x47bf800 --  15% complete.
Reading data from 0x47d9800 --  16% complete.
Reading data from 0x47f3000 --  17% complete.
Reading data from 0x480c800 --  18% complete.
Reading data from 0x4826000 --  19% complete.
Reading data from 0x483f800 --  20% complete.
Reading data from 0x4859800 --  21% complete.
Reading data from 0x4873000 --  22% complete.
Reading data from 0x488c800 --  23% complete.
Reading data from 0x48a6000 --  24% complete.
Reading data from 0x48bf800 --  25% complete.
Reading data from 0x48d9800 --  26% complete.
Reading data from 0x48f3000 --  27% complete.
Reading data from 0x490c800 --  28% complete.
Reading data from 0x4926000 --  29% complete.
Reading data from 0x493f800 --  30% complete.
Reading data from 0x4959800 --  31% complete.
Reading data from 0x4973000 --  32% complete.
Reading data from 0x498c800 --  33% complete.
Reading data from 0x49a6000 --  34% complete.
Reading data from 0x49bf800 --  35% complete.
Reading data from 0x49d9800 --  36% complete.
Reading data from 0x49f3000 --  37% complete.
Reading data from 0x4a0c800 --  38% complete.
Reading data from 0x4a26000 --  39% complete.
Reading data from 0x4a3f800 --  40% complete.
Reading data from 0x4a59800 --  41% complete.
Reading data from 0x4a73000 --  42% complete.
Reading data from 0x4a8c800 --  43% complete.
Reading data from 0x4aa6000 --  44% complete.
Reading data from 0x4abf800 --  45% complete.
Reading data from 0x4ad9800 --  46% complete.
Reading data from 0x4af3000 --  47% complete.
Reading data from 0x4b0c800 --  48% complete.
Reading data from 0x4b26000 --  49% complete.
Reading data from 0x4b3f800 --  50% complete.
Reading data from 0x4b59800 --  51% complete.
Reading data from 0x4b73000 --  52% complete.
Reading data from 0x4b8c800 --  53% complete.
Reading data from 0x4ba6000 --  54% complete.
Reading data from 0x4bbf800 --  55% complete.
Reading data from 0x4bd9800 --  56% complete.
Reading data from 0x4bf3000 --  57% complete.
Reading data from 0x4c0c800 --  58% complete.
Reading data from 0x4c26000 --  59% complete.
Reading data from 0x4c3f800 --  60% complete.
Reading data from 0x4c59800 --  61% complete.
Reading data from 0x4c73000 --  62% complete.
Reading data from 0x4c8c800 --  63% complete.
Reading data from 0x4ca6000 --  64% complete.
Reading data from 0x4cbf800 --  65% complete.
Reading data from 0x4cd9800 --  66% complete.
Reading data from 0x4cf3000 --  67% complete.
Reading data from 0x4d0c800 --  68% complete.
Reading data from 0x4d26000 --  69% complete.
Reading data from 0x4d3f800 --  70% complete.
Reading data from 0x4d59800 --  71% complete.
Reading data from 0x4d73000 --  72% complete.
Reading data from 0x4d8c800 --  73% complete.
Reading data from 0x4da6000 --  74% complete.
Reading data from 0x4dbf800 --  75% complete.
Reading data from 0x4dd9800 --  76% complete.
Reading data from 0x4df3000 --  77% complete.
Reading data from 0x4e0c800 --  78% complete.
Reading data from 0x4e26000 --  79% complete.
Reading data from 0x4e3f800 --  80% complete.
Reading data from 0x4e59800 --  81% complete.
Reading data from 0x4e73000 --  82% complete.
Reading data from 0x4e8c800 --  83% complete.
Reading data from 0x4ea6000 --  84% complete.
Reading data from 0x4ebf800 --  85% complete.
Reading data from 0x4ed9800 --  86% complete.
Reading data from 0x4ef3000 --  87% complete.
Reading data from 0x4f0c800 --  88% complete.
Reading data from 0x4f26000 --  89% complete.
Reading data from 0x4f3f800 --  90% complete.
Reading data from 0x4f59800 --  91% complete.
Reading data from 0x4f73000 --  92% complete.
Reading data from 0x4f8c800 --  93% complete.
Reading data from 0x4fa6000 --  94% complete.
Reading data from 0x4fbf800 --  95% complete.
Reading data from 0x4fd9800 --  96% complete.
Reading data from 0x4ff3000 --  97% complete.
Reading data from 0x500c800 --  98% complete.
Reading data from 0x5026000 --  99% complete.
Reading data from 0x503f800 -- 100% complete.
 10485760 bytes read: OK
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2017-06-21   8:44:30 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5796368 Bytes =  5.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.........

invalid compressed format (err=2)

 -- System halted

Wladislaw,

We have moved on to the new u-boot and rootfs/kernel for this box a long time ago.

For this NSA325 box, the reboot every 35 seconds is the HW watchdog in action. When the system is stalling for a while, the watchdog kicks in and restart the box.

In the new u-boot, I've turned off the watchdog so it will not interfere with the system booting.

My suggestion: boot the box using UART booting using my u-boot image uboot.2017.07-tld-1.nsa325.mtd0.kwb to see if you can.

An example of UART booting with kwboot:

https://forum.doozan.com/read.php?3,51739,51919#msg-51919

And perhaps create the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB, and from the kwboot session, boot into Debian (no need to adjust any envs).

If you can do the above, then you'll know your hardware is OK. And then consider running Debian permanently (forget about stock).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)