Welcome! Log In Create A New Profile

Advanced

NSA310 stopped working after release upgrade

Posted by Fred Fartwind 
Fred Fartwind
NSA310 stopped working after release upgrade
December 28, 2018 06:54AM
Hi,

yesterday, I digged out my ole NSA310 running Debian Wheezy fine for a long time and thought it is a good idea to upgrade to Stretch (via Jessie, of course). It wasn´t a good idea, maybe due to some beer and the late evening...one should read here before upgrading...this is what happened when I changed everything in /etc/apt/sources.list from wheezy to jessie, did apt-get update && apt-get upgrade, then apt-get dist-upgrade and reboot...


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

U-Boot 1.1.4 (Jun  8 2011 - 18:48:37) Marvell version: 3.4.19

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

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

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

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

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0, egiga1 [PRIME]
Hit any key to stop autoboot:  0

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

Reading▒|,_▒f▒▒x4a35800 --  99% complete.ete.
               ▒▒▒▒&▒▒▒▒▒00% complete.
 4194304 bytes read: OK
## Booting image at 02000000 ...
   Ima▒e ▒ث▒   Linux-3.2.0
   Created:      2012-03-3▒ 16:31:31 UTC
   Image type:   A^}▒▒in_▒K▒rnel Image (uncompres▒ed)
   Data Size:    2668776 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Poont▒▒▒▒00▒
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0 (peter@Ubuntu) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 Sat Mar 31 18:31:28 CEST 2▒j
                                      CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Zyxel NSA-310
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS0,115200 roo]O▒▒ٽsda2
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 b▒tg▒▒HX▒▒▒▒▒▒ 256MB = 256MB total
Memory: 254468k/254468k availab ▒▒6k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xd0800000 - 0xfe800000   ( 736 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc04cc000   (4880 kB)
      .init : 0xc04cc000 - 0xc04f7000   ( 172 kB)
      .data : 0xc04f8000 - 0xc0522660   ( 170 kB)
       .bss : 0xc0522684 - 0xc0543668   ( 132 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Kirkwood: MV▒▒▒�j▒, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
Power resume enabled
Power-off GPIO enabled
Kirkwood PCIe port 0:
link up
PCI: bus0 uses PCIe port 0
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
pci 0000:00:01.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
pci 0000:00:01.0: BAR 4: set to [mem 0xe0010000-0xe0013fff 64bit pref] (PCI address [0xe0010000-0xe0013fff])
pci 0000:00:01.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
pci 0000:00:01.0: BAR 2: set to [mem 0xe0014000-0xe0014fff 64bit pref] (PCI address [0xe0014000-0xe0014fff])
pci 0000:00:01.0: BAR 0: assigned [io  0x1000-0x10ff]
pci 0000:00:01.0: BAR 0: set to [io  0x1000-0x10ff] (PCI address [0x1000-0x10ff])
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
NTFS driver 2.1.30 [Flags: R/W].
fuse init (API version 7.17)
msgmni has been set to 497
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 840 at 0x000006900000
Creating 9 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "uboot_env"
0x000000180000-0x000000200000 : "key_store"
0x000000200000-0x000000280000 : "info"
0x000000280000-0x000000c80000 : "etc"
0x000000c80000-0x000001680000 : "kernel_1"
0x000001680000-0x000004640000 : "rootfs1"
0x000004640000-0x000005040000 : "kernel_2"
0x000005040000-0x000008000000 : "rootfs2"
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:00:01.0: eth0: RTL8168d/8111d at 0xd0806000, 00:00:00:00:00:30, XID 083000c0 IRQ 9
r8169 0000:00:01.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
hwmon_vid: Unknown VRM version of your CPU
lm85 0-002e: Starting monitoring
Orion Watchdog Timer: Initial timeout 21 sec
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
cpuidle: using governor ladder
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
ALSA device list:
  No soundcards found.
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3976 buckets, 15904 max)
ctnetlink v0.93: registering with nfnetlink.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
L2TP core driver, V2.0
8021q: 802.1Q VLAN Support v1.8
Registering the dns_resolver key type
input: gpio-keys as /devices/platform/gpio-keys/input/input0
rtc-mv rtc-mv: setting system clock to 2018-12-28 12:30:49 UTC (1546000249)
usb 1-1: new high-speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata1.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133
ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST3000DM001-9YN1 CC4B PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
sd 0:0:0:0: [sda] 4096-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link down (SStatus 0 SControl F300)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (244)
EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda2): recovery complete
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 8:2.
devtmpfs: mounted
Freeing init memory: 172K
systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
USB power enabled

No more input possible, system just standing...I guess its kinda kernel stuff with systemd...but I don´t know how to fix this. Can anyone guide me to the right direction? Meanwhile, I will setup a linux VM, think we need it. Sorry for my lack of knowledge, long time ago since I worked with this stuff...

Thanks in advance
Fred


Uh, almost forgot:
NSA310>> printenv
bootdelay=2
baudrate=115200
loads_echo=0
eth1addr=00:19:CB:00:51:82
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=A203
PRODUCT_NAME=NSA-310
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
ethaddr=FC:F5:28:76:B4:88
console=100000
=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
CASset=min
ethprime=egiga1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
arcNumber=4022
MALLOC_len=3
filesize=28B928
bootargs=console=ttyS0,115200 root=/dev/sda2
bootcmd=nand read.e 0x2000000 0x04640000 0x400000; bootm 0x2000000
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=100000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
hddPowerCtrl=no
enaAutoRecovery=yes
kernel_addr=0xc80000
pcieTune=no
ethact=egiga1

Environment size: 1428/131068 bytes

Re: NSA310 stopped working after release upgrade
December 28, 2018 05:35PM
Please remind me in a day or 2 about this, if I have not answered.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA310 stopped working after release upgrade
December 30, 2018 11:23PM
Hi Fred,

I've looked at your log but sorry I can't help you. You are running a Ubuntu kernel, with systemd.

> Linux version 3.2.0 (peter@Ubuntu) (gcc version
> 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 Sat Mar

My released kernel and Debian rootfs is here:

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

-bodhi
===========================
Forum Wiki
bodhi's corner
Fred Fartwind
Re: NSA310 stopped working after release upgrade
December 31, 2018 07:52AM
bodhi Wrote:
-------------------------------------------------------
> Hi Fred,
>
> I've looked at your log but sorry I can't help
> you. You are running a Ubuntu kernel, with
> systemd.
>
> > Linux version 3.2.0 (peter@Ubuntu) (gcc version
> > 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 Sat
> Mar
>
> My released kernel and Debian rootfs is here:
>
> https://forum.doozan.com/read.php?2,12096

Hi bodhi,

thanks for your quick answer.

I am not married with the Ubuntu kernel :)
My only goal is to bring back the 310 to live...

Thanks for your link. I am not understanding anything in detail, sorry.
What to do if there is no access to the 310? I can´t enter /boot or anything...
I guess: I have to create uInitrd and uImage as described (on my linux VM), copy both files to the USB-Stick and plug it in the 310.
Questions for that:

1) How to make the 310 start from USB?
2) If this succeeded, how to make this permanent (without the stick)?

Again, sorry for the dumb questions, its been a while...Maybe its written somewhere more detailed, but I didn´t found...

Happy new year for you and yours (and, of course, the other users)

Tia
Fred
Re: NSA310 stopped working after release upgrade
January 01, 2019 05:30AM
Fred,

> I am not married with the Ubuntu kernel :)
> My only goal is to bring back the 310 to live...

Since your box has stock u-boot, and Ubuntu kernel, several steps are needed to get to run Debian and new u-boot.

1. Booting with UART. You can run kwboot to load the new uboot to start the box using serial console. See this post:

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

The uboot image that you need to use is in this tarball:

Quote

uboot.2017.07-tld-1.nsa310.bodhi.tar
md5
b2d04eafe402bb356c8dc8e42dc21f8f
sha256
4a5e1e730607b8d8f42544de0bd6c476e0af0e70cc1d201405ae6d4843047d21

2. After you can run kwboot and load the uboot.2017.07-tld-1.nsa310 image to start the box, you can proceed to create a new Debian rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and a USB thumb drive:

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

Scroll down to:


Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
bf3d29569943875df348fb5ca03b348c
sha256:
4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb

.......


-bodhi
===========================
Forum Wiki
bodhi's corner
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: