2017.07 U-Boot Kirkwood - NSA325

Hello yo the whole forum for my first post.

I'm waking my old NAS - Zixel and I have found all this nice job that I would like to apply.
I'm not very familiar with all this stuff and I do not have time to apply for the UART emergency serial interface (I have one it in any case if needed).
So I would like to do everything right at the first time.

I am startin with a stock uboot (at least this is my guess because I got this second hand)

1st Question: For this NSA325 I have to follow the The Marvell Dreamplug box installation procedure Right ?
At Step 1a the root password is my password.
At Step 1b I needed to change /dev/sdc1 with /dev/sdb1 (this is where my USB is mounted)
At Step 1c I'm stuck ... mount: according to mtab, /dev/sda1 is mounted on /zyxel/mnt/sysdisk
What shall I do ?

Thanks



Edited 1 time(s). Last edit at 04/02/2022 05:29AM by miazza.

miazza Wrote:
- 1st Question: For this NSA325 I have to follow the
> The Marvell Dreamplug box installation procedure
> Right ?

Nope. From the thread 2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug :
"The Marvell Dreamplug box installation procedure is different from other Kirkwood u-boots,"

So you have to follow the main procedure in that thread.

Thanks for the answer. Now .... I do not know what I have done but now I have an issue:
When I switch on the NAS it power up for few seconds, I can SSH but immediately after it power shut down.

This happened immediately after that I formatted the rootfs USB but this was not active because I never arrived to the step 1b.

Now it is useless and I do not know what to do ...

any suggestion ?

miazza,

> When I switch on the NAS it power up for few
> seconds, I can SSH but immediately after it power
> shut down.
>
> This happened immediately after that I formatted
> the rootfs USB but this was not active because I
> never arrived to the step 1b.

You were using the wrong instruction. And probably wrong commands.

> Now it is useless and I do not know what to do
> ...
>
> any suggestion ?

Connect serial console, and use picocom/minicom/screen on a another Linux box, or putty on Windows, to monitor the boot progress.

Let it boot without interruption, log into stock OS. Wait until it shutdown like you mentioned above. And then copy and post the entire boot log here.

-bodhi
===========================
Forum Wiki
bodhi's corner

Thanks, yhis is the time to set-up a serial console ... this is what happens when you try :(

Ok I will apply but it will take some time.

Thanks

I made some progress: NAS is now stable (i did nothing may be it was to hot yeterday and built in protection was shutting down)
I am following now the A. Flashing Instruction: Flashing Instruction

- Damping Nand OK

nanddump -o -l 0x80000 -f mtd0 /dev/mtd0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00100000...

- BAD Block Scan

/ # dmesg | grep -i 'bad'
Scanning device for bad blocks
Bad eraseblock 226 at 0x000001c40000
Bad eraseblock 460 at 0x000003980000
Bad eraseblock 783 at 0x0000061e0000
Bad eraseblock 833 at 0x000006820000

Can I go on ?

> - BAD Block Scan
>

> / # dmesg | grep -i 'bad'
> Scanning device for bad blocks
> Bad eraseblock 226 at 0x000001c40000
> Bad eraseblock 460 at 0x000003980000
> Bad eraseblock 783 at 0x0000061e0000
> Bad eraseblock 833 at 0x000006820000
>

>
> Can I go on ?

Yes (these bad blocks are not in the first 1 MB).

-bodhi
===========================
Forum Wiki
bodhi's corner