Welcome! Log In Create A New Profile

Advanced

NSA 320 possible messedup Env

Posted by Th3l0lb0y 
NSA 320 possible messedup Env
February 25, 2024 07:05AM
Hi i'm Robert "th3l0lb0y" from germany
i hope my english isn´t to bad

So to my Question
i installed the latest uBoot + latest debian by @bodhi on my nsa320 an i think i ether messed up my Env´s
or the debian install, because i cant get an network connection in debian and at the boot it say´s eth0 failed......
and at uboot in my Env´s there is the machID 2x present :-S

To the system i can connect to the nsa320 via Serial Connection
and my debian is installed on an brand new 120gb USB stick
My plan was to install OMV at the end

You guy´s are my Last hope
(im fideling on that think for the past 4 day´s because i´m not an linux guy)

Greetings From Germany
Re: NSA 320 possible messedup Env
February 25, 2024 08:49AM
So the log say´s thise

All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"
Failed to get interface index: No such device

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging.

exiting.
ifup: failed to bring up eth0
failed.
Starting RPC port mapper daemon: rpcbind.
Starting NFS common utilities: statd idmapd.
Cleaning up temporary files....
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Not starting NFS kernel daemon: no exports ... (warning).
Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
989 (syslogd)


My original env´s and the envs befor the mods are here



Edited 1 time(s). Last edit at 02/25/2024 11:12AM by Th3l0lb0y.
Attachments:
open | download - Orig Env´s.txt (1.6 KB)
open | download - Current Envs.txt (4.5 KB)
Re: NSA 320 possible messedup Env
February 25, 2024 12:07PM
i did some mor testing but im completly los at this point hope someone can help me

Greetings from germany
Re: NSA 320 possible messedup Env
February 25, 2024 02:06PM
Hi Robert,

Quote

Hi i'm Robert "th3l0lb0y" from germany
i hope my english isn´t to bad

Your English is quite good!

The problem is most likely just one u-boot env. And it explained why you don't have Ethernet. You 've picked the wrong DTB (these 2 names are almost identical :-)

Currently:
dtb_file=/boot/dts/kirkwood-dns320.dtb

It should be
dtb_file=/boot/dts/kirkwood-nsa320.dtb

So at u-boot prompt correct it and boot

setenv dtb_file '/boot/dts/kirkwood-nsa320.dtb'
boot
After booted into Debian, you can set it permanently using fw_setenv:
fw_setenv dtb_file '/boot/dts/kirkwood-nsa320.dtb'

EDITED: see Robert's correction in the next post.

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



Edited 2 time(s). Last edit at 02/25/2024 02:31PM by bodhi.
Re: NSA 320 possible messedup Env
February 25, 2024 02:24PM
That works like a Charm i'm so incredibly thankful
only thing i needet to change was

( setenv dtb_file '/boot/dts/kirkwood-kirkwood-nsa320.dtb' )
to
(setenv dtb_file '/boot/dts/kirkwood-nsa320.dtb' )

Next install OMV (hopefully^^)
and then Internal Usb mod for my usb stick ^^

Thank you bodhi

-Th3l0lb0y



Edited 1 time(s). Last edit at 02/25/2024 02:26PM by Th3l0lb0y.
Re: NSA 320 possible messedup Env
February 25, 2024 02:29PM
> That works like a Charm i'm so incredibly
> thankful
> only thing i needet to change was
>
> ( setenv dtb_file
> '/boot/dts/kirkwood-kirkwood-nsa320.dtb' )
> to
> (setenv dtb_file '/boot/dts/kirkwood-nsa320.dtb'
> )
>

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 25, 2024 02:50PM
i have another question is it possible to get the buttons to work for like (power off )
And the LED´s for hdd activity
and do you have another debian build (older like debian 11) or an hint were i can find it ? ^^

hope i can help someday , someone like you help´d me ^^

thank you bodhi for that and your incredible work



Edited 1 time(s). Last edit at 02/25/2024 03:05PM by Th3l0lb0y.
Re: NSA 320 possible messedup Env
February 25, 2024 03:51PM
Th3l0lb0y,

Quote

i have another question is it possible to get the buttons to work for like (power off )

We have a Wiki thread.

Quote

Key daemon (button control)

Multimedia keyboard daemon for Linux
How to use set up button to reboot or shutdown with Key Daemon (esekeyd)
Shutdown with Power button with regret option by esekeyd

Read the "Multimedia keyboard daemon for Linux" post for a primer how buttons work in Debian with esekeysd. It also points to the other 2 posts below.

Quote

And the LED´s for hdd activity

Yeah, it has been posted from time to time, but I forgot to add this topic to the Wiki thread.

Here is how to set the HDD LED triggers for this box NSA320 box:

You can run these at command line, or add these commands to /etc/rc.local to set the triggers during boot.
echo ide-disk1  > /sys/class/leds/nsa320:green:hdd1/trigger 
echo ide-disk2  > /sys/class/leds/nsa320:green:hdd2/trigger


Quote

and do you have another debian build (older like debian 11) or an hint were i can find it ? ^^

It is in the rootfs/kernel release thread. Scroll down for previous rootfs such as Debian 11.

Quote

Updated 26 Sept 2021:

Basic Debian bullseye Kirkwood rootfs for most Kirwood plugs:

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 26, 2024 03:42AM
thank you

one more question is it normal that in my current env´s were is 2x arcNumber= with two different numbers behind ?

-Th3l0lb0y
Re: NSA 320 possible messedup Env
February 26, 2024 01:42PM
> one more question is it normal that in my current
> env´s were is 2x arcNumber= with two different
> numbers behind ?

No, it is not normal. Probably one of the two has some hidden char in the name that we cannot see.


Also, these 2 are not needed.
boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts; ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
boot_sata2=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sdb1 rootdelay=10 $mtdparts; ide reset; ext2load ide 1:1 0x800000 /boot/uImage; ext2load ide 1:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000

You could try to clean it up by removing both arcNumber (arcNumber is no longer relevant). And remove boot_sata1, boot_sata2, too.

But before doing that, you should run kwboot to make sure you have a recovery path in case something goes wrong.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 26, 2024 06:26PM
if edited the led trigger like you wanted but until now it only blicks´the USB led :-S
Re: NSA 320 possible messedup Env
February 26, 2024 08:20PM
Please post output of

uname -a
mount
df -h
ls -l /sys/class/leds/
cat /sys/class/leds/nsa320:green:hdd1/trigger
cat /sys/class/leds/nsa320:green:hdd2/trigger

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



Edited 1 time(s). Last edit at 02/26/2024 08:21PM by bodhi.
Re: NSA 320 possible messedup Env
February 27, 2024 05:30AM
Linux debian 6.5.7-kirkwood-tld-1 #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023 armv5tel GNU/Linux
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=245992k,nr_inodes=61498,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=49868k,mode=755)
/dev/sdc1 on / type ext3 (rw,noatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
Filesystem      Size  Used Avail Use% Mounted on
udev            241M     0  241M   0% /dev
tmpfs            49M  1.3M   48M   3% /run
/dev/sdc1        11G  1.6G  8.1G  17% /
tmpfs           244M     0  244M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           244M     0  244M   0% /tmp
total 0
drwxr-xr-x  2 root root 0 Jan  1  1970 .
drwxr-xr-x 48 root root 0 Jan  1  1970 ..
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:green:copy -> ../../devices/platform/gpio-leds/leds/nsa320:green:copy
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:green:hdd1 -> ../../devices/platform/gpio-leds/leds/nsa320:green:hdd1
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:green:hdd2 -> ../../devices/platform/gpio-leds/leds/nsa320:green:hdd2
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:green:sys -> ../../devices/platform/gpio-leds/leds/nsa320:green:sys
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:green:usb -> ../../devices/platform/gpio-leds/leds/nsa320:green:usb
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:orange:sys -> ../../devices/platform/gpio-leds/leds/nsa320:orange:sys
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:red:copy -> ../../devices/platform/gpio-leds/leds/nsa320:red:copy
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:red:hdd1 -> ../../devices/platform/gpio-leds/leds/nsa320:red:hdd1
lrwxrwxrwx  1 root root 0 Jan  1  1970 nsa320:red:hdd2 -> ../../devices/platform/gpio-leds/leds/nsa320:red:hdd2
[none] usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock f1072004.mdio-bus-mii:01:link f1072004.mdio-bus-mii:01:1Gbps f1072004.mdio-bus-mii:01:100Mbps f1072004.mdio-bus-mii:01:10Mbps usbport timer oneshot disk-activity disk-read disk-write ide-disk1 ide-disk2 mtd nand-disk heartbeat gpio cpu cpu0 default-on panic
[none] usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock f1072004.mdio-bus-mii:01:link f1072004.mdio-bus-mii:01:1Gbps f1072004.mdio-bus-mii:01:100Mbps f1072004.mdio-bus-mii:01:10Mbps usbport timer oneshot disk-activity disk-read disk-write ide-disk1 ide-disk2 mtd nand-disk heartbeat gpio cpu cpu0 default-on panic

Re: NSA 320 possible messedup Env
February 27, 2024 02:19PM
Th3l0lb0y,

Filesystem      Size  Used Avail Use% Mounted on
udev            241M     0  241M   0% /dev
tmpfs            49M  1.3M   48M   3% /run
/dev/sdc1        11G  1.6G  8.1G  17% /
tmpfs           244M     0  244M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           244M     0  244M   0% /tmp
total 0

I don't see any HDD mounted. You must mount the HDDs and then do something (access the disk) to see its LED flashing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 27, 2024 02:43PM
I did try id but rhe problem for me is that im not so good at linux stuff yesterday i installd webmin an tryd to format my hdd but after the format the drives didnt show up
My hope at first was that i can install omv on debian 10 but that didnt work because some packages don't install right

Now im searching for an simple fast webui that installs on debian arm :(
I only want to link thise drives to my omv box :(
Re: NSA 320 possible messedup Env
February 28, 2024 12:02PM
Little update i did get everything to work
only thing now is the extremly slow transfer speed of only 20kb/s on an gigabite connection
is there anything i can do about ?

-Th3l0lb0y
Re: NSA 320 possible messedup Env
February 28, 2024 01:49PM
> only thing now is the extremly slow transfer speed
> of only 20kb/s on an gigabite connection
> is there anything i can do about ?

Definitely something is wrong there. This box could get up to 800-900mb/s if the other end is capable.

First thing you'd do is to run pure network benchmark while connect to another host that is Gbs capable. See the Wiki thread:

Quote

Perfornance Tuning & Benchmarks

Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)

Samba Tuning
Mount NTFS with big_writes
Increase NFSD max_block_size
Reduce NFSD threads

And then knowing that your system has no problem with network (if it reach ~800 Mbs), you would run NFS or SAMBA benchmark on an HDD (don't use USB storage)....

If you cannot see what was the reason for getting such a low performance, post the test you did and describe in details (what's the protocol? disk drive, file size....) here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 28, 2024 03:42PM
ok i do as you say ^^

do i need to create the bigfile in this test on the nas itself ?
(Network performance - SAMBA - NFS (various protocols)


sry for this old windows user ( also on servers ) its pretty hard to unterstand sometimes :-S

when i test ethtool -A
it say´s  ethtool: bad command line argument(s)
For more information run ethtool -h

an with  ethtool -A eth0 rx off tx off

Cannot get device pause settings: Operation not supported



Edited 2 time(s). Last edit at 03/01/2024 09:46AM by Th3l0lb0y.
Re: NSA 320 possible messedup Env
February 28, 2024 04:35PM
if got a new problem right before i wanted to test the speed´s
my serial output starts to push out this endless
what do i do next :-S
 1183.731484][ T7311] __nand_correct_data: uncorrectable ECC error
[ 1183.753539][ T7311] __nand_correct_data: uncorrectable ECC error
[ 1183.759599][ T7311] print_req_error: I/O error, dev mtdblock8, sector 0 flags 0
[ 1183.783533][ T7311] Buffer I/O error on dev mtdblock8, logical block 0, async page read

Re: NSA 320 possible messedup Env
February 28, 2024 06:15PM
>
>  1183.731484][ T7311] __nand_correct_data:
> uncorrectable ECC error
> [ 1183.753539][ T7311] __nand_correct_data:
> uncorrectable ECC error
> [ 1183.759599][ T7311] print_req_error: I/O error,
> dev mtdblock8, sector 0 flags 0
> [ 1183.783533][ T7311] Buffer I/O error on dev
> mtdblock8, logical block 0, async page read
> 
>

This problem typically occurs after you installed some software that is continously scanning for block devices (OMV is probably one of them). And your stock FW in NAND has been corrpupted (mtd8 is part of the stock FW).

List the mtds in Debian
fw_printenv mtdparts
It should show
mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
and
cat /proc/mtd
It should show:
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"

So, there is nothing you need to do to fix this stock FW mtd8. We are not using it.

In Debian, redefine the mtds to ignore stock FW as followed, so avoid any attempt to scan or read it:
fw_setenv mtdparts 'mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env_stock)'
Note that we are using only mtd0 for both new u-boot and u-boot envs. So we don't really need mtd1 (uboot_env_stock), but I included it for future convenience when I need to look at it.

And reboot. Log into Debian and verify. There should be 2 mtds: mtd0 and mtd1.
cat /proc/mtd

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
February 28, 2024 06:40PM
Thank you
so
fw_printenv mtdparts show´s
mtdparts=nand_mtd

and cat /proc/mtd

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"

thank you its working :-)
next on the list test wie speed´s :-)
Re: NSA 320 possible messedup Env
March 01, 2024 05:29AM
Hi out of curryosity if testet an SMB transfer with an
USB Network adapter and there i get about 10mb/s witch is about USB2.0 speed
with the same file on the internal adapter i get about 30-100kb/s

so its the internal Network adapter with the problem
is it possible that my env´s are the problem ?
or an linux problem ?
no i need to find out how to do your test´s with an live linux

-Th3l0lb0y



Edited 1 time(s). Last edit at 03/01/2024 05:31AM by Th3l0lb0y.
Re: NSA 320 possible messedup Env
March 01, 2024 01:38PM
> Hi out of curryosity if testet an SMB transfer
> with an
> USB Network adapter and there i get about 10mb/s
> witch is about USB2.0 speed
> with the same file on the internal adapter i get
> about 30-100kb/s
>
> so its the internal Network adapter with the
> problem
> is it possible that my env´s are the problem ?
> or an linux problem ?

Not u-boot envs problem. It's Linux.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
March 01, 2024 03:34PM
is there a way to diagnose the problem with the help of an windows PC or can you find somethin out with the Log from the boot of debian ?

-Th3l0lb0y
Re: NSA 320 possible messedup Env
March 01, 2024 03:43PM
i Hope thise helps i realy don´t know linux is for me just pretty new :-S

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700)
ZyXEL NSA320 2-Bay Power Media Server

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Using egiga0 device
host 192.168.178.82 is alive
Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Zyxel NSA320
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env_stock) init=/bin/systemd
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000][    T0] Memory: 494676K/524288K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 29612K reserved, 0K cma-reserved)
[    0.000000][    T0] random: get_random_u32 called from cache_alloc_refill+0x38c/0x928 with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0]  Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000048][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.000800][    T0] Console: colour dummy device 80x30
[    0.000851][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000877][    T0] pid_max: default: 32768 minimum: 301
[    0.001250][    T0] LSM: Security Framework initializing
[    0.001433][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001461][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002312][    T0] *** VALIDATE proc ***
[    0.002571][    T0] *** VALIDATE cgroup1 ***
[    0.002596][    T0] *** VALIDATE cgroup2 ***
[    0.002693][    T0] CPU: Testing write buffer coherency: ok
[    0.004379][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.004701][    T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.004984][    T1] rcu: Hierarchical SRCU implementation.
[    0.008302][    T1] devtmpfs: initialized
[    0.014621][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.014653][    T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.014895][    T1] xor: measuring software checksum speed
[    0.110117][    T1]    arm4regs  :  1084.400 MB/sec
[    0.210078][    T1]    8regs     :   654.000 MB/sec
[    0.310070][    T1]    32regs    :   950.800 MB/sec
[    0.310089][    T1] xor: using function: arm4regs (1084.400 MB/sec)
[    0.310110][    T1] prandom: seed boundary self test passed
[    0.314287][    T1] prandom: 100 self tests passed
[    0.314299][    T1] pinctrl core: initialized pinctrl subsystem
[    0.315719][    T1] NET: Registered protocol family 16
[    0.316299][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.317096][    T1] audit: initializing netlink subsys (disabled)
[    0.318336][   T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
[    0.318455][    T1] cpuidle: using governor ladder
[    0.318531][    T1] cpuidle: using governor menu
[    0.319114][    T1] Feroceon L2: Enabling L2
[    0.319165][    T1] Feroceon L2: Cache support initialised.
[    0.325485][    T1] No ATAGs?
[    2.560055][    C0] random: fast init done
[    6.252264][   T71] alg: No test for lzo-rle (lzo-rle-generic)
[    6.252621][   T73] alg: No test for lzo-rle (lzo-rle-scomp)
[    6.430666][    T1] raid6: int32x8  gen()   128 MB/s
[    6.600322][    T1] raid6: int32x8  xor()    86 MB/s
[    6.770129][    T1] raid6: int32x4  gen()   130 MB/s
[    6.940240][    T1] raid6: int32x4  xor()    84 MB/s
[    7.110416][    T1] raid6: int32x2  gen()   133 MB/s
[    7.280194][    T1] raid6: int32x2  xor()    94 MB/s
[    7.450400][    T1] raid6: int32x1  gen()   100 MB/s
[    7.620406][    T1] raid6: int32x1  xor()    69 MB/s
[    7.620417][    T1] raid6: using algorithm int32x2 gen() 133 MB/s
[    7.620426][    T1] raid6: .... xor() 94 MB/s, rmw enabled
[    7.620435][    T1] raid6: using intx1 recovery algorithm
[    7.620688][    T1] vgaarb: loaded
[    7.621194][    T1] SCSI subsystem initialized
[    7.621694][    T1] usbcore: registered new interface driver usbfs
[    7.621763][    T1] usbcore: registered new interface driver hub
[    7.621849][    T1] usbcore: registered new device driver usb
[    7.622030][    T1] pps_core: LinuxPPS API ver. 1 registered
[    7.622042][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    7.622070][    T1] PTP clock support registered
[    7.623411][    T1] clocksource: Switched to clocksource orion_clocksource
[    8.654582][    T1] VFS: Disk quotas dquot_6.6.0
[    8.654679][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.664517][    T1] NET: Registered protocol family 2
[    8.665332][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[    8.665369][    T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    8.665427][    T1] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    8.665480][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    8.665577][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    8.665604][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    8.665835][    T1] NET: Registered protocol family 1
[    8.666477][    T1] RPC: Registered named UNIX socket transport module.
[    8.666491][    T1] RPC: Registered udp transport module.
[    8.666499][    T1] RPC: Registered tcp transport module.
[    8.666507][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    8.666522][    T1] PCI: CLS 0 bytes, default 32
[    8.666764][    T1] Trying to unpack rootfs image as initramfs...
[    9.508568][    T1] Freeing initrd memory: 9488K
[    9.508777][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    9.509992][    T1] Initialise system trusted keyrings
[    9.510043][    T1] Key type blacklist registered
[    9.510258][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    9.510368][    T1] zbud: loaded
[    9.511472][    T1] NFS: Registering the id_resolver key type
[    9.511504][    T1] Key type id_resolver registered
[    9.511514][    T1] Key type id_legacy registered
[    9.511534][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    9.511551][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    9.511845][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    9.512082][    T1] fuse: init (API version 7.31)
[    9.512468][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    9.512656][    T1] orangefs_init: module version upstream loaded
[    9.512668][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[    9.529858][    T1] async_tx: api initialized (async)
[    9.529883][    T1] Key type asymmetric registered
[    9.529893][    T1] Asymmetric key parser 'x509' registered
[    9.529965][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    9.531412][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    9.533374][    T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    9.533396][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    9.533525][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    9.533542][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    9.533672][    T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[    9.533712][    T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    9.535252][    T1] PCI: bus0: Fast back to back transfers disabled
[    9.535279][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    9.536756][    T1] PCI: bus1: Fast back to back transfers enabled
[    9.536782][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    9.536985][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[    9.537003][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    9.537645][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    9.594221][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    9.596205][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    9.654225][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    9.656489][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    9.657775][    T1] printk: console [ttyS0] disabled
[    9.657847][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[   10.499387][    T1] printk: console [ttyS0] enabled
[   10.511857][    T1] loop: module loaded
[   10.516354][    T1] sata_mv f1080000.sata: slots 32 ports 2
[   10.524757][    T1] scsi host0: sata_mv
[   10.529211][    T1] scsi host1: sata_mv
[   10.533375][    T1] ata1: SATA max UDMA/133 irq 33
[   10.538256][    T1] ata2: SATA max UDMA/133 irq 33
[   10.544108][    T1] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[   10.551288][    T1] nand: Samsung NAND 128MiB 3,3V 8-bit
[   10.556655][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[   10.564989][    T1] Scanning device for bad blocks
[   10.589564][    T1] Bad eraseblock 205 at 0x0000019a0000
[   10.596700][    T1] Bad eraseblock 224 at 0x000001c00000
[   10.602756][    T1] Bad eraseblock 232 at 0x000001d00000
[   10.622160][    T1] Bad eraseblock 379 at 0x000002f60000
[   10.632171][    T1] Bad eraseblock 428 at 0x000003580000
[   10.646885][    T1] Bad eraseblock 526 at 0x0000041c0000
[   10.658133][    T1] Bad eraseblock 588 at 0x000004980000
[   10.696845][    T1] Bad eraseblock 936 at 0x000007500000
[   10.710549][    T1] 2 cmdlinepart partitions found on MTD device orion_nand
[   10.717563][    T1] Creating 2 MTD partitions on "orion_nand":
[   10.723446][    T1] 0x000000000000-0x000000100000 : "uboot"
[   10.730357][    T1] 0x000000100000-0x000000180000 : "uboot_env_stock"
[   10.739298][    T1] libphy: Fixed MDIO Bus: probed
[   10.744942][    T1] libphy: orion_mdio_bus: probed
[   10.763782][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   10.771830][    T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[   10.779273][    T1] mv643xx_eth: Set the PHY to fix link down
[   10.780079][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address c8:6c:87:9b:2f:78
[   10.795582][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   10.802900][    T1] ehci-pci: EHCI PCI platform driver
[   10.808187][    T1] ehci-orion: EHCI orion driver
[   10.813106][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
[   10.819418][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[   10.828047][    T1] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[   10.863437][    T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[   10.870476][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
[   10.879577][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.887555][    T1] usb usb1: Product: EHCI Host Controller
[   10.893158][    T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-1 ehci_hcd
[   10.900520][    T1] usb usb1: SerialNumber: f1050000.ehci
[   10.906582][    T1] hub 1-0:1.0: USB hub found
[   10.911088][    T1] hub 1-0:1.0: 1 port detected
[   10.916494][    T1] usbcore: registered new interface driver usb-storage
[   10.923655][    T1] mousedev: PS/2 mouse device common for all mice
[   10.930505][    T1] rtc-mv f1010300.rtc: registered as rtc0
[   10.936316][    T1] i2c /dev entries driver
[   10.943277][    T1] rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable.
[   10.951631][    T1] rtc-pcf8563 0-0051: registered as rtc1
[   10.958853][    T1] device-mapper: uevent: version 1.0.3
[   10.964515][    T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
[   10.974125][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[   10.981384][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[   10.988795][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[   10.996247][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[   11.003072][    T1] device-mapper: raid: Loading target version 1.14.0
[   11.011684][    T1] hidraw: raw HID events driver (C) Jiri Kosina
[   11.018180][    T1] drop_monitor: Initializing network drop monitor service
[   11.025634][    T1] NET: Registered protocol family 17
[   11.031042][    T1] Key type dns_resolver registered
[   11.036920][    T1] registered taskstats version 1
[   11.041735][    T1] Loading compiled-in X.509 certificates
[   11.047315][  T112] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   11.054417][    T1] zswap: loaded using pool lzo/zbud
[   11.083832][  T112] ata1.00: HPA detected: current 1953523055, native 1953525168
[   11.091286][  T112] ata1.00: ATA-7: SAMSUNG HD103SI, 1AG01113, max UDMA7
[   11.100882][  T112] ata1.00: 1953523055 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   11.151969][  T112] ata1.00: configured for UDMA/133
[   11.174110][    T7] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD103SI  1113 PQ: 0 ANSI: 5
[   11.189013][    T1] Key type big_key registered
[   11.194675][  T116] sd 0:0:0:0: [sda] 1953523055 512-byte logical blocks: (1.00 TB/932 GiB)
[   11.213726][  T116] sd 0:0:0:0: [sda] Write Protect is off
[   11.219424][  T116] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   11.262948][  T116] sd 0:0:0:0: [sda] Attached SCSI disk
[   11.270583][    T1] Key type encrypted registered
[   11.277403][    T1] rtc-mv f1010300.rtc: setting system clock to 2024-03-01T22:36:55 UTC (1709332615)
[   11.286746][   T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   11.495182][   T15] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63
[   11.504152][   T15] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   11.512066][   T15] usb 1-1: Product: USB2.0 Hub
[   11.517580][   T15] hub 1-1:1.0: USB hub found
[   11.522425][   T15] hub 1-1:1.0: 4 ports detected
[   11.703449][  T114] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   11.733680][  T114] ata2.00: ATA-7: SAMSUNG HD103SI, 1AG01118, max UDMA7
[   11.740432][  T114] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   11.773704][  T114] ata2.00: configured for UDMA/133
[   11.789253][   T23] scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD103SI  1118 PQ: 0 ANSI: 5
[   11.799111][  T116] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[   11.807948][  T116] sd 1:0:0:0: [sdb] Write Protect is off
[   11.813627][  T116] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   11.829126][  T116] sd 1:0:0:0: [sdb] Attached SCSI disk
[   11.837430][    T1] Freeing unused kernel memory: 1024K
[   11.843463][   T15] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[   11.854060][    T1] Checked W+X mappings: passed, no W+X pages found
[   11.860448][    T1] Run /init as init process
Loading, please wait...
Starting version 241
[   12.015578][   T15] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
[   12.033491][   T15] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   12.041540][   T15] usb 1-1.1: Product: Ultra Fit
[   12.063521][   T15] usb 1-1.1: Manufacturer: SanDisk
[   12.068519][   T15] usb 1-1.1: SerialNumber: 4C530001240106114145
[   12.091463][   T15] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[   12.117970][   T15] scsi host2: usb-storage 1-1.1:1.0
[   12.125519][  T161] usbcore: registered new interface driver uas
[   13.205051][  T116] scsi 2:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[   13.223569][   T23] sd 2:0:0:0: [sdc] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
[   13.239522][   T23] sd 2:0:0:0: [sdc] Write Protect is off
[   13.250744][   T23] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   13.278364][   T23]  sdc: sdc1 sdc2
[   13.295866][   T23] sd 2:0:0:0: [sdc] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext3 (1) -- /dev/sdc1] fsck.ext3 -a -C0 /dev/sdc1
rootfs: clean, 49210/677280 files, 433864/2704128 blocks
done.
[   23.879613][  T194] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem
[   23.929030][  T194] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[   25.046127][    T1] systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
[   25.175222][    T1] systemd[1]: Inserted module 'autofs4'
[   25.230081][    T1] NET: Registered protocol family 10
[   25.236565][    T1] Segment Routing with IPv6
[   25.318191][    T1] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[   25.341083][    T1] systemd[1]: Detected architecture arm.

Welcome to Debian GNU/Linux 10 (buster)!

[   25.385578][    T1] systemd[1]: Set hostname to <Vault-111>.
[   26.375772][    C0] random: crng init done
[   27.535810][    T1] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   27.553825][    T1] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[   27.975934][    T1] systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
[   28.043879][    T1] systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
[   28.189010][    T1] systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingly.
[   28.324363][    T1] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[   28.364708][    T1] systemd[1]: Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
         Mounting NFSD configuration filesystem...
         Starting Load Kernel Modules...
         Starting Availability of block devices...
[  OK  ] Reached target Slices.
         Mounting POSIX Message Queue File System...
[  OK  ] Listening on Device-mapper event daemon FIFOs.
         Starting Monitoring of LVM…meventd or progress polling...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Set up automount Arbitrary…s File System Automount Point.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on Journal Audit Socket.
         Starting Journal Service...
[  OK  ] Listening on Network Service Netlink Socket.
         Starting Create list of re…odes for the current kernel...
[  OK  ] Reached target Swap.
         Mounting Kernel Debug File System...
[  OK  ] Listening on fsck to fsckd communication Socket.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on udev Control Socket.
         Starting udev Coldplug all Devices...
         Mounting RPC Pipe File System...
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Listening on LVM2 poll daemon socket.
[  OK  ] Mounted NFSD configuration filesystem.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Availability of block devices.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Monitoring of LVM2… dmeventd or progress p[   29.467957][  T240] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro
olling.
[  OK  ] Started Create list of req… nodes for the current kernel.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Journal Service.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted RPC Pipe File System.
         Starting pNFS block layout mapping daemon...
         Starting Load/Save Random Seed...
         Starting Create System Users...
         Starting Flush Journal to Persistent Storage...
         Mounting FUSE Control File System...
         Starting Apply Kernel Variables...
[  OK  ] Started pNFS block layout mapping daemon.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create System Users.
[   30.355493][  T234] systemd-journald[234]: Received request to flush runtime journal from PID 1
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting Mount /tmp as tmp…e access to the root device...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted Mount /tmp as tmpf…ite access to the root device.
[  OK  ] Reached target Local File Systems.
         Starting Raise network interfaces...
         Starting Create Volatile Files and Directories...
         Starting Cleanup monit state file...
         Starting Preprocess NFS configuration...
         Starting Cleanup PHP session files...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Cleanup monit state file.
[  OK  ] Started Preprocess NFS configuration.
         Starting NFSv4 ID-name mapping service...
[  OK  ] Reached target NFS client services.
         Starting Network Service...
[  OK  ] Started Cleanup PHP session files.
[  OK  ] Started NFSv4 ID-name mapping service.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
         Starting RPC bind portmap service...
[  OK  ] Started RPC bind portmap service.
[  OK  ] Reached target RPC Port Mapper.
[  OK  ] Started Network Service.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Login Service...
[  OK  ] Started Self Monitoring an…ing Technology (SMART) Daemon.
         Starting System Logging Service...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
         Starting WPA supplicant...
[  OK  ] Started Trigger anacron every hour.
[  OK  ] Started Run anacron jobs.
[  OK  ] Started Clean PHP session files every 30 mins.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Reached target Timers.
         Starting Network Name Resolution...
         Starting Wait for Network to be Configured...
[  OK  ] Started System Logging Service.
[[   32.234056][  T283] mv643xx_eth: Set the PHY back to auto-negotiation mode
[   33.518840][  T263] input: gpio_keys as /devices/platform/gpio_keys/input/input0
  OK  ] Started Raise network interfaces.
[  OK  ] Started Login Service.
[   34.774601][  T280] watchdog: f1020300.watchdog-timer: driver supplied timeout (4294967295) out of range
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Network Name Resolution.
[  OK  ] Started WPA supplica[   35.157505][  T280] watchdog: f1020300.watchdog-timer: falling back to default timeout (21)
nt.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target Network.
         Starting NFS Mount Daemon...
         Starting A high performanc… and a reverse proxy server...
         Starting The PHP 7.3 FastCGI Process Manager...
[   35.518730][  T280] orion_wdt: Initial timeout 21 sec
         Starting OpenBSD Secure Shell server...
         Starting The OpenMediaVaul…t processes the RPC request...
[   35.841865][  T263] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   36.017231][    C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   36.028082][   T15] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   36.200473][  T281] marvell-cesa f1030000.crypto: CESA device successfully registered
[  OK  ] Started Wait for Network to be Configured.
[  OK  ] Reached target Network is Online.
         [   36.374710][  T263] sd 1:0:0:0: Attached scsi generic sg1 type 0
Starting /etc/rc.local Compatibility...
[  OK  ] Started Web Services Dynamic Discovery host daemon.
         Starting Generate the prelogin message...
         Starting Samba NMB Daemon...
[   36.753909][  T263] sd 2:0:0:0: Attached scsi generic sg2 type 0
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started NFS Mount Daemon.
         Starting NFS server and services...
[   37.806273][  T385] md0: detected capacity change from 0 to 2000137748480
[   39.098181][  T391] NFSD: Using UMH upcall client tracking operations.
[   39.132898][  T391] NFSD: starting 90-second grace period (net f000001c)
[  OK  ] Started NFS server and services.
[  OK  ] Started The OpenMediaVault…hat processes the RPC request.
[  OK  ] Started A high performance…er and a reverse proxy server.
[  OK  ] Started The PHP 7.3 FastCGI Process Manager.
[  OK  ] Found device /dev/disk/by-…4-bf27-43f1-bcfc-07ce1e578062.
[  OK  ] Started Samba NMB Daemon.
         Starting Samba SMB Daemon...
         Starting File System Check…bf27-43f1-bcfc-07ce1e578062...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Started File System Check Daemon to report status.
[  OK  ] Started File System Check …4-bf27-43f1-bcfc-07ce1e578062.
         Mounting /srv/dev-disk-by-…bf27-43f1-bcfc-07ce1e578062...
[   46.644783][  T448] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  OK  ] Started Samba SMB Daemon.
[   49.438723][  T448] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[  OK  ] Mounted /srv/dev-disk-by-u…4-bf27-43f1-bcfc-07ce1e578062.
         Starting File System Quota Check...
[  OK  ] Started File System Quota Check.
         Starting Enable File System Quotas...
[  OK  ] Started Enable File System Quotas.
[  OK  ] Reached target Remote File Systems.
         Starting LSB: Load kernel …d to enable cpufreq scaling...
         Starting LSB: Starts syslogd...
         Starting LSB: start or stop rrdcached...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: service and resource monitoring daemon...
         Starting Permit User Sessions...
[  OK  ] Started LSB: Starts syslogd.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
         Starting LSB: Starts klogd...
[  OK  ] Started LSB: Starts klogd.
[  OK  ] Started LSB: service and resource monitoring daemon.
[  OK  ] Started LSB: start or stop rrdcached.
         Starting Statistics collection and monitoring daemon...
[  OK  ] Started Statistics collection and monitoring daemon.
[  OK  ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started LSB: set CPUFreq kernel parameters.

openmediavault 5.6.26-1 (Usul) Vault-111 ttyS0
Copyright (C) 2009-2022 by Volker Theile. All rights reserved.

To manage the system visit the openmediavault web control panel:

enxa0cec8fc2a08: 192.168.178.138
eth0: 192.168.178.137

By default the web control panel administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the web control panel or using the 'omv-firstaid' CLI
command.

For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org

Vault-111 login:
openmediavault 5.6.26-1 (Usul) Vault-111 ttyS0
Copyright (C) 2009-2022 by Volker Theile. All rights reserved.

To manage the system visit the openmediavault web control panel:

eth0: 192.168.178.137

By default the web control panel administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the web control panel or using the 'omv-firstaid' CLI
command.

For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org

Vault-111 login: [  110.673869][  T658] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)


Re: NSA 320 possible messedup Env
March 01, 2024 05:01PM
im realy lost at this point
i cant make the test´s because i dont know how i mount the share of my other nas and so on

:-(

-th3l0lb0y
Re: NSA 320 possible messedup Env
March 01, 2024 05:20PM
> im realy lost at this point
> i cant make the test´s because i dont know how i
> mount the share of my other nas and so on

When it comes to OMV, I will let others help you. Or you could Google whatever problems you see.

To me, looks like it booted OK into OMV

Quote

Vault-111 login:
openmediavault 5.6.26-1 (Usul) Vault-111 ttyS0
Copyright (C) 2009-2022 by Volker Theile. All rights reserved.

To manage the system visit the openmediavault web control panel:

eth0: 192.168.178.137

Now you just need to learn how to use OMV.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
March 01, 2024 06:18PM
yes omv boots right but
ive still got that problem with the extreme slow transferrates in omv and in debian
30-100kb/s
also on wget downloads (updates and so on )
i cant get more then 100kb/s but i dont know ho to solve that problem if its linux related
its the same without OMV on your rootfs (debian 10)
i think its an driver problem or something because with an usb network adapter plugt in the nsa320 it runs fine

testdownload with an my my internet connektion is 1Gbit
and my nsa320 plugs into an 1gbit lan connector on my router

500mb testfile from  http://speedtest.wdc01.softlayer.com/downloads/test500.zip
/dev/md0              0%[                    ] 751.98K  23.7KB/s    eta 5h 58m

i mean i dont think its normal that the onboard network connection is that slow

i mean i know how to create and use shares from omv but i dont know how to link 2 linux boxes together to make your test from your link ->
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)



Edited 2 time(s). Last edit at 03/01/2024 06:23PM by Th3l0lb0y.
Re: NSA 320 possible messedup Env
March 01, 2024 06:54PM
> i mean i know how to create and use shares from
> omv but i dont know how to link 2 linux boxes
> together to make your test from your link
> ->
> Network performance - SAMBA - NFS
> (various protocols)
> Pogo Pro V3 Network NFS benchmarks
> Kirkwood vs OXNAS network
> performance (with flow control)
> Kirkwood vs OXNAS network performance (flow
> control turned off )
> OXNAS vs OXNAS network performance (flow control
> turned off)
>

Follow this tutorial in the Wiki to run iperf test:

Kirkwood vs OXNAS network performance (with flow control)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: NSA 320 possible messedup Env
March 01, 2024 07:39PM
the test´s are not the same as my wget and SMB transfer rates
now i'm really Confused

First test 

Server listening on TCP port 5001
TCP window size:  208 KByte (default)
------------------------------------------------------------
[  4] local 192.168.178.70 port 5001 connected with 192.168.178.137 port 37054
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   723 MBytes   606 Mbits/sec
------------------------------------------------------------
Client connecting to 192.168.178.137, TCP port 5001
TCP window size:  867 MByte
------------------------------------------------------------
[  4] local 192.168.178.116 port 59641 connected with 192.168.178.137 port 5001
[  4]  0.0-10.0 sec   870 MBytes   728 Mbits/sec

Second test

------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  208 KByte (default)
------------------------------------------------------------
[  4] local 192.168.178.70 port 5001 connected with 192.168.178.137 port 37070
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   661 MBytes   554 Mbits/sec
------------------------------------------------------------
Client connecting to 192.168.178.137, TCP port 5001
TCP window size:  867 MByte
------------------------------------------------------------
[  4] local 192.168.178.116 port 59672 connected with 192.168.178.137 port 5001
[  4]  0.0-10.1 sec   886 MBytes   735 Mbits/sec

I hope i did that right :-S
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: