Welcome! Log In Create A New Profile

Advanced

2023.04 U-Boot Kirkwood - ZyXEL NSA325

Posted by bodhi 
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 20, 2024 05:45PM
AleXSR700 Wrote:
-------------------------------------------------------
> Quick question: is this only for NSA325 or also
> the NSA325v2?

Yes, it is for both. The NSA325 and NSA325v2 are basically identical. Only the form factor is different.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 22, 2024 09:40PM
Hi bodhi - My NSA325 returns the following for the command "cat /etc/fw_env.config"

# MTD device name Device offset Env. size Flash sector size Number of sectors
# NAND example
/dev/mtd1 0x0000 0x20000 0x20000 4


cat /proc/mtd returns

mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"


dmesg | grep -i 'bad' returns nothing

Can I move forward with the flashing? Thank you for your help!
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 12:18AM
n325,

> Hi bodhi - My NSA325 returns the following for the
> command "cat /etc/fw_env.config"
>
> # MTD device name Device offset Env.
> size Flash sector size Number of
> sectors
> # NAND example
> /dev/mtd1 0x0000 0x20000 0x20000 4

>
> cat /proc/mtd returns
>
> mtd0: 00100000 00020000 "uboot"
> mtd1: 00080000 00020000 "uboot_env"
> mtd2: 00080000 00020000 "key_store"
> mtd3: 00080000 00020000 "info"
> mtd4: 00a00000 00020000 "etc"
> mtd5: 00a00000 00020000 "kernel_1"
> mtd6: 02fc0000 00020000 "rootfs1"
> mtd7: 00a00000 00020000 "kernel_2"
> mtd8: 02fc0000 00020000 "rootfs2"

>
> dmesg | grep -i 'bad' returns nothing

Are you running stock u-boot? and running Debian on USB or HDD rootfs?

Please post output of
dmesg
So I can see the complete picture, before I can advise further.

If you have serial console, then post the serial entire boot log (no need to post dmesg if you do this).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 08:52AM
I believe it's the stock u-boot. Here is the output from dmesg.

,0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 2048 (order: 11, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 506752KB available (5360K code, 302K data, 2872K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1599.07 BogoMIPS (lpj=7995392)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
invoking softwareStaggeredSpinUp()..., it will delay 5 seconds to spin up the second harddisk
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 02:04PM
So your system is all stock.

Yes you can install new u-boot and Debian rootfs.

But I would recommend to connect serial console during installation to make sure you can have a recovery path, in case something goes wrong.

Quote
Installation Steps
A. Preparation

A.1. UART booting

It is strongly recommmended that you try to run kwboot to test this boot image with UART booting before flashing to NAND. This is the rescue path when and if the flashing goes wrong for some reason. See example here. And to download latest ARM kwboot binary for UART booting see here.

Of course, you can do it blind, but prepare to connect serial console if you cannot boot after installation. And remember to keep the log of the entire session (on the terminal) when you flash u-boot and prepare the rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 03:09PM
Thank you. I do have access to a serial console so will follow that approach.
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 26, 2024 07:53PM
I successfully competed the process and the device now booted into Debian. Thank you bodhi for your help!
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 27, 2024 01:56PM
Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 02:39PM
I found the following services failed. How can I fix these services?

root@debian:/# systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
* cockpit.service loaded failed failed Cockpit Web Service
* systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage
* systemd-journald.service loaded failed failed Journal Service
* systemd-logind.service loaded failed failed User Login Management
* systemd-udevd.service loaded failed failed Rule-based Manager for Device Events and Files
* systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
* systemd-journald.socket loaded failed failed Journal Socket
* systemd-udevd-control.socket loaded failed failed udev Control Socket
* systemd-udevd-kernel.socket loaded failed failed udev Kernel Socket

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
9 loaded units listed.
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 03:45PM
> I found the following services failed. How can I
> fix these services?

This basic rootfs init system is sysvinit.

Are you running systemd? If you have not set up for systemd then you can use uEnv.txt to run it

It was mentioned in the installation instruction.

Quote
https://forum.doozan.com/read.php?2,12096

Note 5 (Optional):

Note 5.1. To boot with systemd

After loged into Debian, run:

apt-get install systemd
And then add parameter init=/usr/bin/systemd to your u-boot env bootargs.

- For example,
fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/usr/bin/systemd'

- Or, if you are booting with my latest u-boot images you can also use the uEnv.txt capability to do this. In the default envs, custom_params is a variable that allows you to add extra bootargs. So add the following line to uEnv.txt:
custom_params=earlyprintk=serial init=/usr/bin/systemd

While in Debian,
cd /boot
echo "custom_params=earlyprintk=serial init=/usr/bin/systemd" > uEnv.txt
sync

And reboot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 04:41PM
bodhi Wrote:
-------------------------------------------------------
> > I found the following services failed. How can
> I
> > fix these services?
>
> This basic rootfs init system is sysvinit.
>
> Are you running systemd? If you have not set up
> for systemd then you can use uEnv.txt to run it
>
> It was mentioned in the installation instruction.
>
>
Quote
https://forum.doozan.com/read.php?2,12096
>
> Note 5 (Optional):
>
> Note 5.1. To boot with systemd
>
> After loged into Debian, run:
>
> apt-get install systemd
> And then add parameter init=/usr/bin/systemd to
> your u-boot env bootargs.
>
> - For example,
> fw_setenv set_bootargs 'setenv bootargs
> console=ttyS0,115200 root=LABEL=rootfs
> rootdelay=10 $mtdparts init=/usr/bin/systemd'
>
> - Or, if you are booting with my latest u-boot
> images you can also use the uEnv.txt capability to
> do this. In the default envs, custom_params is a
> variable that allows you to add extra bootargs. So
> add the following line to uEnv.txt:
> custom_params=earlyprintk=serial
> init=/usr/bin/systemd
>
>
> While in Debian,
>
> cd /boot
> echo "custom_params=earlyprintk=serial
> init=/usr/bin/systemd" > uEnv.txt
> sync
>
>
> And reboot.


Yes, I was running systemd. I actually upgraded to Debian 6.8.7 now and I don't see any failed services now. Thank you!
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 02:36PM
Hello. It's my first post on this forum. I have old NSA325 v2 and I would like to change software with new one from bodhi.
I am not totally newbie and know what is terminal, basic Linux commands, etc., but I need someone who can support me.

For instance, while I am trying to install U-Boot from this topic, after I sent command:
nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd

I got answer:

nanddump: unrecognized option '--noecc'
Usage: nanddump [OPTIONS] MTD-device
Dumps the contents of a nand mtd partition

and I have no idea, how to solve it.

bodhi, could you please support me?

Greetings from Poland ;)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 02:48PM
MireQ,

> I am not totally newbie and know what is terminal,
> basic Linux commands, etc., but I need someone who
> can support me.

Ask questions whenever you need!

>
> For instance, while I am trying to install U-Boot
> from this topic, after I sent command:
> nanddump --noecc --omitoob -l 0x80000 -f
> mtd0.nsa325 /dev/mtd
>
> I got answer:
>
> nanddump: unrecognized option '--noecc'
> Usage: nanddump [OPTIONS] MTD-device
> Dumps the contents of a nand mtd partition
>
> and I have no idea, how to solve it.

- Are you inside stock OS?
- The nanddump command has many old and new versions, so syntax or options might be different. You can try and see what the options are

nanddump --help

Or you can use nanddump from my uploaded tools tarball.

https://forum.doozan.com/read.php?3,27280

Quote

While in stock OS, you can download the following binpack so that the normal tools for use in nand installation will be available in the system. Since Dropbox use https, you can download it to an USB stick on another Linux box and copy this tarball to the stock OS (I'll upload this to my available storage here so stock wget can be used, when I can).

Dowload at Dropbox
linux-tools-installation-bodhi.tar.gz
md5:
e58f442411eb35e641d40ea0577e00ff linux-tools-installation-bodhi.tar.gz
sha256:
88dfa8eadb319e2e286320643a654bf89bff0b0d450562fce09938e7f3b0007d linux-tools-installation-bodhi.tar.gz
Date: May 18 00:31 PST

This binpack contains these files:
tools/
tools/busybox
tools/e2fsck
tools/nanddump
tools/fw_printenv
tools/flash_erase
tools/nandwrite
tools/fw_env.config

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 03:18PM
bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > I am not totally newbie and know what is
> terminal,
> > basic Linux commands, etc., but I need someone
> who
> > can support me.
>
> Ask questions whenever you need!
>
> >
> > For instance, while I am trying to install
> U-Boot
> > from this topic, after I sent command:
> > nanddump --noecc --omitoob -l 0x80000 -f
> > mtd0.nsa325 /dev/mtd
> >
> > I got answer:
> >
> > nanddump: unrecognized option '--noecc'
> > Usage: nanddump [OPTIONS] MTD-device
> > Dumps the contents of a nand mtd partition
> >
> > and I have no idea, how to solve it.
>
> - Are you inside stock OS?
> - The nanddump command has many old and new
> versions, so syntax or options might be different.
> You can try and see what the options are
>
>
> nanddump --help
>
>
> Or you can use nanddump from my uploaded tools
> tarball.
>
> https://forum.doozan.com/read.php?3,27280
>
>
Quote

While in stock OS, you can download the
> following binpack so that the normal tools for use
> in nand installation will be available in the
> system. Since Dropbox use https, you can download
> it to an USB stick on another Linux box and copy
> this tarball to the stock OS (I'll upload this to
> my available storage here so stock wget can be
> used, when I can).
>
> Dowload at Dropbox
> linux-tools-installation-bodhi.tar.gz
> md5:
> e58f442411eb35e641d40ea0577e00ff
> linux-tools-installation-bodhi.tar.gz
> sha256:
> 88dfa8eadb319e2e286320643a654bf89bff0b0d450562fce09938e7f3b0007d
> linux-tools-installation-bodhi.tar.gz
> Date: May 18 00:31 PST
>
> This binpack contains these files:
> tools/
> tools/busybox
> tools/e2fsck
> tools/nanddump
> tools/fw_printenv
> tools/flash_erase
> tools/nandwrite
> tools/fw_env.config

Thanks bodhi,
Yes, I am inside stock.
I can say that I have read few topics (about Debian/Rootfs, U-boot, also your binpack) and the initially tried to make few steps in these areas, but I have met problems:
1. I cannot copy tools to /usr/local/bin or /usr/sbin in stock OS because I receive info like this:
cp: can't create '/usr/local/bin/busybox': Read-only file system
and I don't know what I can do, so then I tried:
2. to change U-boot even I have not tools installed. I get info like I wrote above in my first post.
3. In the meantime I prepared, I hope correctly, an USB flash drive for booting from Stock U-boot, but didn't decide to follow this way and tried to install your U-boot.
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 03:44PM
MireQ,

> Yes, I am inside stock.
> I can say that I have read few topics (about
> Debian/Rootfs, U-boot, also your binpack) and the
> initially tried to make few steps in these areas,
> but I have met problems:
> 1. I cannot copy tools to /usr/local/bin or
> /usr/sbin in stock OS because I receive info like
> this:
> cp: can't create '/usr/local/bin/busybox':
> Read-only file system
> and I don't know what I can do, so then I tried:

The binaries can be run directly, there is no need to copy them to /usr/local/bin or /usr/sbin. So extract it to /tmp (in RAM), or some folder like /locadisk. If the root / is also read only then use the /tmp folder.

mkdir /localdisk
cd /localdisk
tar -xf linux-tools-installation-bodhi.tar.gz


And execute it like this

cd /localdisk/tools
./nanddump > nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd0

It's been a long time so I forgot what the syntax of this nanddump. If the above does not work, try this to see the options

./nanddump --help

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 04:02PM
bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > Yes, I am inside stock.
> > I can say that I have read few topics (about
> > Debian/Rootfs, U-boot, also your binpack) and
> the
> > initially tried to make few steps in these
> areas,
> > but I have met problems:
> > 1. I cannot copy tools to /usr/local/bin or
> > /usr/sbin in stock OS because I receive info
> like
> > this:
> > cp: can't create '/usr/local/bin/busybox':
> > Read-only file system
> > and I don't know what I can do, so then I
> tried:
>
> The binaries can be run directly, there is no need
> to copy them to /usr/local/bin or /usr/sbin. So
> extract it to /tmp (in RAM), or some folder like
> /locadisk. If the root / is also read only then
> use the /tmp folder.
>
>
> mkdir /localdisk
> cd /localdisk
> tar -xf linux-tools-installation-bodhi.tar.gz
>
>
>
> And execute it like this
>
>
> cd /localdisk/tools
> ./nanddump > nanddump --noecc --omitoob -l 0x80000
> -f mtd0.nsa325 /dev/mtd0
>
>
Here I have answer: sh: ./nanddump: Text file busy

> It's been a long time so I forgot what the syntax
> of this nanddump. If the above does not work, try
> this to see the options
>
>
> ./nanddump --help
>
Here is the same: sh: ./nanddump: Text file busy
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 04:34PM
While in stock OS,

dmesg
cat /proc/mtd
cat /etc/fw_env.config
cd /localdisk/tools
ls -larth
And post the entire log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 21, 2025 10:02AM
bodhi Wrote:
-------------------------------------------------------
> While in stock OS,
>
>
> dmesg
> cat /proc/mtd
> cat /etc/fw_env.config
> cd /localdisk/tools
> ls -larth
>
> And post the entire log here.


/localdisk/tools # dmesg
Access     Pretec   08GB REX100      1.00 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 15917056 512-byte logical blocks: (8.14 GB/7.58 GiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
svc: failed to register lockdv1 RPC service (errno 97).
GbE port 0: TxEnable WA - Enabled, deep=1, tx_en_bk=1


***************************************
*            HD1 stand by now!        *
***************************************

***************************************
*            HD0 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by zyfw_downloader !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************
In usb_disconnect, and number is 1 .....
usb 2-1: USB disconnect, address 2

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink
FAT: bread failed in fat_clusters_flush
FAT: Directory bread(block 32768) failed
FAT: Directory bread(block 32769) failed
FAT: Directory bread(block 32770) failed
FAT: Directory bread(block 32771) failed
FAT: Directory bread(block 32772) failed
FAT: Directory bread(block 32773) failed
FAT: Directory bread(block 32774) failed
FAT: Directory bread(block 32775) failed

#######################################
#              HD1 awaked by sh !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink
FAT: bread failed in fat_clusters_flush
FAT: bread failed in fat_clusters_flush
FAT: bread failed in fat_clusters_flush
xhci_hcd 0000:00:01.0: remove, state 1
In usb_disconnect, and number is 0 .....
usb usb2: USB disconnect, address 1
xhci_hcd 0000:00:01.0: Host controller not halted, aborting reset.
xhci_hcd 0000:00:01.0: USB bus 2 deregistered
xhci_hcd 0000:00:01.0: xHCI Host Controller
xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:00:01.0: irq 9, io mem 0xe0000000
usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor
usb usb2: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
usb 2-1: new SuperSpeed USB device using xhci_hcd and address 2
In hub_port_init, and number is 2, retry 0, port 1 .....
usb 2-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: Direct-Access     Pretec   08GB REX100      1.00 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdc] 15917056 512-byte logical blocks: (8.14 GB/7.58 GiB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 3:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Attached SCSI removable disk
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

***************************************
*            HD1 stand by now!        *
***************************************

***************************************
*            HD0 stand by now!        *
***************************************


/localdisk/tools # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"


/localdisk/tools # cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
# NAND example
/dev/mtd1               0x0000          0x20000         0x20000                 4


/localdisk/tools # cd /localdisk/tools
/localdisk/tools # ls -larth
-rwxr-xr-x    1 root     root        1.5M Nov 15  2010 busybox
-rwxr-xr-x    1 root     root      768.6K Jun 20  2011 e2fsck
-rwxr-xr-x    1 root     root       28.9K Jun 30  2014 nandwrite
-rwxr-xr-x    1 root     root       25.0K Jun 30  2014 flash_erase
-rwxr-xr-x    1 root     root      652.8K May 17  2016 fw_printenv
-rw-r--r--    1 root     root         329 May 17  2016 fw_env.config
drwxrwxrwx    3 root     root           0 Jan 21 16:45 ..
drwxr-xr-x    2 root     root           0 Jan 21 16:45 .
-rwxr-xr-x    1 root     root           0 Jan 21 16:46 nanddump


Regarding to ls -larth command I can say that directly after executing binaries the nanddump size is 25.9K, but after I run the command nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd0 its size becomes to 0 KB

===
moderator edit: please use code tags (formatted code button) to post log.



Edited 2 time(s). Last edit at 01/21/2025 01:34PM by bodhi.
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 21, 2025 01:36PM
MireQ,

Extract the tools tarball again. And
./nanddump --help

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 23, 2025 04:44PM
bodhi, thanks,

Finally I got it, I installed both your u-boot and Debian on a usb drive.
Now my goal is to install OMV, but I have met new problems. How can I configure it to have DNS support in OMV and in the terminal?
I have 2 disks in NSA325 and would like to configure them as RAID1 preferably in OMV interface, but it can be in console. But for that I need DNS translation....
Now for the 3rd time I lost access to the box and I need to prepare the USB tomorrow again.
Could you please help me?
I know I am writing in wrong topic, but I don't want to start a new one.
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 23, 2025 06:43PM
MireQ,

> Finally I got it, I installed both your u-boot and
> Debian on a usb drive.

Cool!

> Now my goal is to install OMV, but I have met new
> problems. How can I configure it to have DNS
> support in OMV and in the terminal?
> I have 2 disks in NSA325 and would like to
> configure them as RAID1 preferably in OMV
> interface, but it can be in console. But for that
> I need DNS translation....

You can look at the Wiki thread fo topic about OMV

https://forum.doozan.com/read.php?2,23630

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 27, 2025 12:36PM
bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > Finally I got it, I installed both your u-boot
> and
> > Debian on a usb drive.
>
> Cool!
>
> > Now my goal is to install OMV, but I have met
> new
> > problems. How can I configure it to have DNS
> > support in OMV and in the terminal?
> > I have 2 disks in NSA325 and would like to
> > configure them as RAID1 preferably in OMV
> > interface, but it can be in console. But for
> that
> > I need DNS translation....
>
> You can look at the Wiki thread fo topic about
> OMV
>
> https://forum.doozan.com/read.php?2,23630

bodhi,

thank you very much. This was very helpful. Now I have installed everything I wanted. But there is one thing I don't understand. After restarting the box is unreachable on my network. It doesn't matter how it is restarted - from the OMV menu or from Terminal. The same is true after a power outage. After several re-installations, I discovered that there is a way around this. If the box is unreachable after a reboot, I unplug the box, remove the flash drive and put it back in, turn on the power, press the power button and everything is OK. Is it normal?
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 27, 2025 03:02PM
MireQ,

> thank you very much. This was very helpful. Now I
> have installed everything I wanted. But there is
> one thing I don't understand. After restarting the
> box is unreachable on my network.

I recall it is a known problem with the later versions of OMV (OMV reset the network file to its own upon reboot)

> It doesn't
> matter how it is restarted - from the OMV menu or
> from Terminal. The same is true after a power
> outage. After several re-installations, I
> discovered that there is a way around this. If the
> box is unreachable after a reboot, I unplug the
> box, remove the flash drive and put it back in,
> turn on the power, press the power button and
> everything is OK. Is it normal?

I can't remember where in this forum some users have discovered and had a work around. Too bad I did not save the link.

Try searching the forum for it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 28, 2025 04:57AM
bodhi,
Is not the problem at the boot level?
As I wrote above, the sequence “remove the power plug > remove the USB stick > wait a while > insert the USB stick > plug in the power > press the power button” works.
However, restarting from the console or menu, as well as after a power outage, does not work.

Shutting down the system from the menu and then pressing the power button also doesn’t work.

I know it sounds strange, but it seems that the key step is cutting the power and removing the USB stick.

Maybe you could take a look at my configuration?

For now, I don’t have a serial console, but I can buy a converter.

MireQ
Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 28, 2025 01:29PM
MireQ,

> Is not the problem at the boot level?

At the kernel booting level, yes. Not u-boot. But there should be no problem with the network if you don't install OMV.

> For now, I don’t have a serial console, but I
> can buy a converter.

It's best that you connect serial console.

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

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: