Am I too late to get NSA320 not booting help?

Marvell Kirkwood based
fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Am I too late to get NSA320 not booting help?

Post by fromutah » Wed Jun 27, 2018 7:18 am

I know this device is past it's prime. I have a bricked NSA320. I can't get it to boot to a USB, or to get far enough along to gain tftp access. nand bad returns six bad locations. And, I'm not a wizard at linux, shells, etc. I mostly just follow instructions. I have a serial cable and can see and use uboot. I've extracted what I believe are the needed files from a firmware (4.7 rev 3). I can't seem to get any connection through Ethernet to use tftp to transfer the files back

What can I try?

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Thu Jun 28, 2018 7:00 am

Do you have a serial log of your attempt?

Are you aware the tftp should have a fixed address, known by the 320?

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 5:47 am

This with a USB drive inserted, no HDD. The USB has


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

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) 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 CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
//--- stateButtonBit = 3, recovery ---//
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0

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

Reading data from 0x503f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.22.18
Created: 2010-08-19 13:31:09 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5683352 Bytes = 5.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (root@Neo) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.70.0501961 2005-12-18)) #12 Thu Aug 19 21:30:49 CST 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 511360KB available (4844K code, 404K data, 3092K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB

Marvell Development Board (LSP Version KW_LSP_4.2.7)-- RD-88F6281A Soc: MV88F6281 Rev 3 LE

Detected Tclk 200000000 and SysClk 400000000
Marvell USB EHCI Host controller #0: c0cbe600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
o RAID 5 Xor calculation
o kernel memcpy
o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c0011f88)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
gpio_dev = fd00000
LED_SET_CTL_IOC_NUM= 6702
High gpio polarity = 50
High gpio polarity = 70
Enable Interrupt
mv88f6281_wdt: Watchdog Timer timeout = 8 sec.
mv88f6281_wdt: HW Watchdog timeout = 15 sec.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.8)
SGI XFS with large block numbers, no debug enabled
SGI XFS Quota Management subsystem
yaffs Jun 18 2010 22:04:25 Installing.
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload enabled
o Receive checksum offload enabled
o Transmit checksum offload enabled
o Network Fast Processing (Routing) supported
o Proc tool API enabled
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o eth0, ifindex = 1, GbE port = 0
eth_get_config: Unexpected port number 1
EthPort #1: Bad initialization parameters
eth port=1: load failed
eth_init_module: can't init eth_hal driver
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
EnablePowerSaving
PowerSavingTime = 15
No found HD
/////////////////////////////////// init sd
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x00000000
Bad eraseblock 1 at 0x00020000
Bad eraseblock 2 at 0x00040000
...
Bad eraseblock 1022 at 0x07fc0000
Bad eraseblock 1023 at 0x07fe0000
9 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 9 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "uboot"
0x00100000-0x00180000 : "uboot_env"
0x00180000-0x00200000 : "key_store"
0x00200000-0x00280000 : "info"
0x00280000-0x00c80000 : "etc"
0x00c80000-0x01680000 : "kernel_1"
0x01680000-0x04640000 : "rootfs1"
0x04640000-0x05040000 : "kernel_2"
0x05040000-0x08000000 : "rootfs2"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
In hub_port_init, and number is 0, retry 0, port 1 .....
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 94 MB/s
raid6: int32x2 136 MB/s
raid6: int32x4 123 MB/s
raid6: int32x8 109 MB/s
raid6: using algorithm int32x2 (136 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1090.800 MB/sec
8regs : 653.600 MB/sec
32regs : 884.400 MB/sec
raid5: using function: arm4regs (1090.800 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: setting the system clock to 2000-04-30 00:21:32 (957054092)
Freeing init memory: 3092K
Cannot read bad block mark: Invalid argument
*** Stage 1: Setup system and device drivers ***
Cannot read bad block mark: Invalid argument
BusyBox v1.1.1 (2010.06.18-13:49+0000) multi-call binary

Usage: ifconfig [-a] <interface> [<address>]

egiga0: link down
egiga0: started
Cannot set device generic segmentation offload settings: Operatipcf8563 0-0051: low voltage detected, date/time is not reliable.
on not supported
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
*** Stage 2: Prepare the root file system ***
Mount system partition...
mount: special device /dev/mtdblock does not exist
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
Starting Pure-FTPd ...
1 second...
usb 1-1.2: new high speed USB device using ehci_marvell and address 3
In hub_port_init, and number is 1, retry 0, port 2 .....
usb 1-1.2: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
2 second...
egiga0: link up, full duplex, speed 1 Gbps
3 second...
egiga0: link down
4 second...
5 second...
egiga0: link up, full duplex, speed 1 Gbps
6 second...
scsi 2:0:0:0: Direct-Access Verbatim STORE N GO 8.07 PQ: 0 ANSI: 4
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
7 second...
egiga0: link down
8 second...
9 second...
egiga0: link up, full duplex, speed 1 Gbps
10 second...
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok
usb 1-1.2: reset high speed USB device using ehci_marvell and address 3
In hub_port_init, and number is 1, retry 0, port 2 .....

Please press Enter to activate this console. egiga0: link down
egiga0: link up, full duplex, speed 100 Mbps


=======================================
I have also stopped the boot process and extracted DATA_0001 files from the ras.bin file, but can't get them to the NSA320 in U-boot mode.

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 5:58 am

Also, upon hitting a key while "Hit any key to stop autoboot:" is displayed, I can see this using the nand commands:


NSA320>> nand info

Device 0: NAND 128MB 3,3V 8-bit, sector size 128 KB

NSA320>> nand bad

Device 0 bad blocks:
003a0000
00780000
02500000
03ba0000
07ae0000
07dc0000
NSA320>> <INTERRUPT>
NSA320>>



From this prompt, can I connect/start an FTP client, setup a network connections, and connect to a computer on the network, or use a crossover LAN connection to be able to transfer DATA_0001?

These are the instructions I'm trying to follow:


How to generate related files from binary ras.bin
1. Connect RS-232 serial port to NSA320
2. Open Tera Term terminal software or other terminal software
3. Copy firmware to USB and insert into NSA320 (if it was not mounted automatically, please mount it manually)
mkdir e-data/1234/
mount /dev/sda1 /e-data/1234/
4. Run command to extract flash images, and make sure the return value ($?) is 4:
bin2ram little /e-data/1234/400AFM4C0.bin /e-data/1234/tlv.bin; echo $?
5. Run command to unpack flash images, and make sure the return value ($?) is 0:
fw_unpack -C /e-data/1234 -i /e-data/1234/tlv.bin; echo $?
6. You’ll see all extracted files in USB: DATA_0000: header version
DATA_0001: firmware version
DATA_0002: firmware revision
DATA_0101: model number
DATA_0200: core checksum
DATA_0201: ZLD checksum
DATA_0202: ROM checksum
DATA_0203: Not used in NSA320
DATA_0204: Image checksum
DATA_1000: kernel file, uImage
DATA_1004: fs.tar.gz, for NAND flash
DATA_a000: executable, for some jobs before firmware upgrade
DATA_a002: executable, for some jobs after firmware upgrade

How to recover firmware corrupted NSA320 via RS-232 serial port
1. Connect RS-232 serial port to NSA320
2. Remove All SATA and USB Disks
3. Open Tera Term terminal software or other terminal software
4. Get free TFTP server from http://kin.klever.net/dist/pumpkin-2.7.2.exe
5. Change TFTP filesystem root to the driver letter of the USB
6. Copy DATA_1000 to the directory accessible by TFTP server
7. Setup PC IP address :192.168.1.1
• in network adapter TCPIP properties
8. Connect Ethernet cable to NSA320
9. Power on NSA320, and it will show boot prompt “Hit any key to stop autoboot: 0”, and press “ESC” to enter into U-Boot command mode.
10. In U-Boot
 Update kernel
=> setenv ipaddr 192.168.1.3 board IP
setenv ipaddr 1.0.0.32

=> setenv serverip 192.168.1.1 TFTP server IP
setenv serverip 1.0.0.80
=> tftp 0x2000000 DATA_1000
=> protect off all
=> nand erase 0x00C80000 0xa00000 erase first uImage
=> nand write 0x2000000 0x00C80000 0xa00000 write first uImage
=> nand erase 0x04640000 0xa00000 erase second uImage
=> nand write 0x2000000 0x04640000 0xa00000 write second uImage
=> reset
11. After bootup, Press “Enter” after you see this message “Please press Enter to activate this console.”
12. In BusyBox shell, plug the USB with firmware files DATA_xxxx inside and mount it Ex.
If the USB is /dev/sdb1(can be got from command “fdisk -l”), you can mount it to:
 mkdir /mnt/USB
 mount /dev/sdb1 /mnt/USB
13. Copy the root fs to NAND flash and verify it’s checksum
 umount /zyxel/mnt/nand
 flash_eraseall /dev/mtd6 erase partition 1 for root fs
 mkdir /mnt/rootfs1
 mount -t yaffs2 -o rw /dev/mtdblock6 /mnt/rootfs1
 flash_eraseall /dev/mtd8 erase partition 2 for root fs
 mkdir /mnt/rootfs2
 mount -t yaffs2 -o rw /dev/mtdblock8 /mnt/rootfs2
 cp /mnt/USB/DATA_1004 /mnt/rootfs1/sysdisk.img.gz copy root fs 1
 cp /mnt/USB/DATA_1004 /mnt/rootfs2/sysdisk.img.gz copy root fs 2
 md5sum /mnt/rootfs1/sysdisk.img.gz /mnt/rootfs2/sysdisk.img.gz
 cat /mnt/USB/DATA_0201 these two lines must get the same checkeum result
13. Update the FW information
 /zyxel/sbin/info_setenv fwversion_1 `cat /mnt/USB/DATA_0001`
 /zyxel/sbin/info_setenv fwversion_2 `cat /mnt/USB/DATA_0001`
 /zyxel/sbin/info_setenv revision_1 `cat /mnt/USB/DATA_0002`
 /zyxel/sbin/info_setenv revision_2 `cat /mnt/USB/DATA_0002`
 /zyxel/sbin/info_setenv modelid_1 `cat /mnt/USB/DATA_0101`
 /zyxel/sbin/info_setenv modelid_2 `cat /mnt/USB/DATA_0101`
 /zyxel/sbin/info_setenv core_checksum_1 `cat /mnt/USB/DATA_0200`
 /zyxel/sbin/info_setenv core_checksum_2 `cat /mnt/USB/DATA_0200`
 /zyxel/sbin/info_setenv zld_checksum_1 `cat /mnt/USB/DATA_0201`

 /zyxel/sbin/info_setenv zld_checksum_2 `cat /mnt/USB/DATA_0201`
 /zyxel/sbin/info_setenv romfile_checksum_1 `cat /mnt/USB/DATA_0202`
 /zyxel/sbin/info_setenv romfile_checksum_2 `cat /mnt/USB/DATA_0202`
 /zyxel/sbin/info_setenv img_checksum_1 `cat /mnt/USB/DATA_0204`
 /zyxel/sbin/info_setenv img_checksum_2 `cat /mnt/USB/DATA_0204`
 umount /mnt/rootfs1
 umount /mnt/rootfs2
 umount /mnt/USB
 reboot
14. Finished


Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Fri Jun 29, 2018 8:49 am

Seeing your bootlog, the firmware is still mainly present. The kernel and ramfs are OK, only the flash partition is damaged. A Force flash stick should work for you.

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 3:01 pm

I have tried this. I repeated fresh for completeness. The log looks like the one that I sent in the first post. I think what is happening is that the USB stick is never seen (light on USB drive doesn't light until after this process), so boot starts from the NAS rather than the USB stick. It doesn't seem to matter if the HDD is in or out. For completeness, here is the new log:


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

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) 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 CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
//--- stateButtonBit = 3, recovery ---//
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0 -- I ignore this and let it continue

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

Reading data from 0x503f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.22.18
Created: 2010-08-19 13:31:09 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5683352 Bytes = 5.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (root@Neo) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.70.0501961 2005-12-18)) #12 Thu Aug 19 21:30:49 CST 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 511360KB available (4844K code, 404K data, 3092K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB

Marvell Development Board (LSP Version KW_LSP_4.2.7)-- RD-88F6281A Soc: MV88F6281 Rev 3 LE

Detected Tclk 200000000 and SysClk 400000000
Marvell USB EHCI Host controller #0: c0cbe600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
o RAID 5 Xor calculation
o kernel memcpy
o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c0011f88)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
gpio_dev = fd00000
LED_SET_CTL_IOC_NUM= 6702
High gpio polarity = 50
High gpio polarity = 70
Enable Interrupt
mv88f6281_wdt: Watchdog Timer timeout = 8 sec.
mv88f6281_wdt: HW Watchdog timeout = 15 sec.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.8)
SGI XFS with large block numbers, no debug enabled
SGI XFS Quota Management subsystem
yaffs Jun 18 2010 22:04:25 Installing.
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload enabled
o Receive checksum offload enabled
o Transmit checksum offload enabled
o Network Fast Processing (Routing) supported
o Proc tool API enabled
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o eth0, ifindex = 1, GbE port = 0
eth_get_config: Unexpected port number 1
EthPort #1: Bad initialization parameters
eth port=1: load failed
eth_init_module: can't init eth_hal driver
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
EnablePowerSaving
PowerSavingTime = 15
No found HD
/////////////////////////////////// init sd
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1 at 0x00020000
Bad eraseblock 2 at 0x00040000
Bad eraseblock 3 at 0x00060000

...

Bad eraseblock 1021 at 0x07fa0000
Bad eraseblock 1022 at 0x07fc0000
Bad eraseblock 1023 at 0x07fe0000
9 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 9 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "uboot"
0x00100000-0x00180000 : "uboot_env"
0x00180000-0x00200000 : "key_store"
0x00200000-0x00280000 : "info"
0x00280000-0x00c80000 : "etc"
0x00c80000-0x01680000 : "kernel_1"
0x01680000-0x04640000 : "rootfs1"
0x04640000-0x05040000 : "kernel_2"
0x05040000-0x08000000 : "rootfs2"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
In hub_port_init, and number is 0, retry 0, port 1 .....
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 94 MB/s
raid6: int32x2 136 MB/s
raid6: int32x4 123 MB/s
raid6: int32x8 109 MB/s
raid6: using algorithm int32x2 (136 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1090.800 MB/sec
8regs : 653.600 MB/sec
32regs : 884.400 MB/sec
raid5: using function: arm4regs (1090.800 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: setting the system clock to 2000-04-30 09:16:35 (957086195)
Freeing init memory: 3092K
Cannot read bad block mark: Invalid argument
*** Stage 1: Setup system and device drivers ***
Cannot read bad block mark: Invalid argument
BusyBox v1.1.1 (2010.06.18-13:49+0000) multi-call binary

Usage: ifconfig [-a] <interface> [<address>]

egiga0: link down
egiga0: started
Cannot set device generic segmentation offload settings: Operatipcf8563 0-0051: low voltage detected, date/time is not reliable.
on not supported
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
*** Stage 2: Prepare the root file system ***
Mount system partition...
mount: special device /dev/mtdblock does not exist
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
Starting Pure-FTPd ...
1 second...
2 second...
usb 1-1.2: new high speed USB device using ehci_marvell and address 3
In hub_port_init, and number is 1, retry 0, port 2 .....
usb 1-1.2: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
3 second...
4 second...
5 second...
egiga0: link up, full duplex, speed 1 Gbps
6 second...
egiga0: link down
7 second...
scsi 2:0:0:0: Direct-Access Verbatim STORE N GO 8.07 PQ: 0 ANSI: 4
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
8 second...
egiga0: link up, full duplex, speed 1 Gbps
9 second...
egiga0: link down
10 second...
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok

Please press Enter to activate this console.

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Fri Jun 29, 2018 3:29 pm

Actually, this is the usb stick kicking in:

Code: Select all

sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok
Here is the corresponding /etc/init.d/rcS scriptlet. The line 'md5 check ok' is the output of /sbin/check_key, which means that it will execute /mnt/parnerkey/usb_key_func.sh.

The line 'Please press Enter to activate this console.' is (I think) the shell which remains after the exit 0, which means /mnt/parnerkey/usb_key_func.sh returned an error. The stick might contain a file exec.log, which tells why.

This is strange:

Code: Select all

5 second...
egiga0: link up, full duplex, speed 1 Gbps
6 second...
egiga0: link down
8 second...
egiga0: link up, full duplex, speed 1 Gbps
9 second...
egiga0: link down
Why is it blinking? Have you checked cable & other side?

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 4:22 pm

It doesn't look like it's mounting. There is no /mnt/parnerkey/ when I see it in the console. Does it umount after it returns the exec.log?

with fat32 stick: (I removed HDD so now USB is sda)
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok


exec.log:
Cannot read bad block mark: Invalid argument
[: 1: unknown operand
[: 2: unknown operand
ERROR!!! Invalid INFO value 'curr_bootfrom'!
led_state_map_addr = 49
led_state_map_addr = 9
led_state_map_addr = 19

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 4:27 pm

This is strange:
Is that simply the LAN cable being detected? Should I unplug that? Without LAN, the console shows this:
...
Mount system partition...
mount: special device /dev/mtdblock does not exist
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
Starting Pure-FTPd ...
1 second...
usb 1-1.2: new high speed USB device using ehci_marvell and address 3
In hub_port_init, and number is 1, retry 0, port 2 .....
usb 1-1.2: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
2 second...
3 second...
4 second...
5 second...
6 second...
scsi 2:0:0:0: Direct-Access Verbatim STORE N GO 8.07 PQ: 0 ANSI: 4
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 30535680 512-byte hardware sectors (15634 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
7 second...
8 second...
9 second...
10 second...
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok

Please press Enter to activate this console.

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Fri Jun 29, 2018 7:02 pm

fromutah wrote:
Fri Jun 29, 2018 4:27 pm
This is strange:
Is that simply the LAN cable being detected? Should I unplug that?
It is the network link being detected. For the current problem it shouldn't matter, but it's, well, strange.
In combination with

Code: Select all

Cannot set device generic segmentation offload settings: Operatipcf8563 0-0051: low voltage detected, date/time is not reliable.
makes me wonder if the power supply is sufficient. (Although the 'low voltage detected' also could point to the RTC battery).

Anyway.

Code: Select all

Cannot read bad block mark: Invalid argument
[: 1: unknown operand
[: 2: unknown operand
ERROR!!! Invalid INFO value 'curr_bootfrom'!
led_state_map_addr = 49
led_state_map_addr = 9
led_state_map_addr = 19
is bad news. It corresponds to this lines of usb_key_func.sh.2:

Code: Select all

# which kernel and system image partitions
CURR_BOOTFROM=`/zyxel/sbin/info_printenv curr_bootfrom | awk -F"=" '{print $2}'`
if [ ${CURR_BOOTFROM} -eq 1 ]; then
	NEXT_BOOTFROM=2
elif [ ${CURR_BOOTFROM} -eq 2 ]; then
	NEXT_BOOTFROM=1
else
	echo "ERROR!!! Invalid INFO value 'curr_bootfrom'!"
	# All leds show red
	setLED SYS RED BLINK
	setLED HD RED BLINK
	setLED COPY RED BLINK
	exit 1
fi
The box has double flash memory. When flashing, it flashes the part which is not in use, and only when that succeeds it sets the other half active. This way it's protected against a bad flash.

What this part of the script does is reading which part is currently active. /zyxel/sbin/info_printenv read the u-boot environment (u-boot has to know which of the 2 kernels has to be used), and according to the log the u-boot environment is bad too.

I suggest you to first check your powersupply. If that is OK, you can edit the script to simply set CURR_BOOTFROM to 2, and hope the best.

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Fri Jun 29, 2018 8:58 pm

I'll give that a try when I'm back with it tonight. I assume there is nothing in the first part of the console log that would tell me whether 1 or 2 is safer? What am I looking for with the power supply? it's the same one that came with it. Just check to see if voltage is close to that states as output voltage?

Thank you so much for your help.

Is a Zyxel NAS540 a good 4-bay replacement, or what would be another good cheap home/small business NAS? I've got the healthy drives and salvaged the data from this NSA320.

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Sat Jun 30, 2018 5:49 am

This was the console output from the attempt:


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

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) 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 CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
//--- stateButtonBit = 3, recovery ---//
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0

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

Reading data from 0x503f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.22.18
Created: 2010-08-19 13:31:09 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5683352 Bytes = 5.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (root@Neo) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.70.0501961 2005-12-18)) #12 Thu Aug 19 21:30:49 CST 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 511360KB available (4844K code, 404K data, 3092K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB

Marvell Development Board (LSP Version KW_LSP_4.2.7)-- RD-88F6281A Soc: MV88F6281 Rev 3 LE

Detected Tclk 200000000 and SysClk 400000000
Marvell USB EHCI Host controller #0: c0cbe600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
o RAID 5 Xor calculation
o kernel memcpy
o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c0011f88)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
gpio_dev = fd00000
LED_SET_CTL_IOC_NUM= 6702
High gpio polarity = 50
High gpio polarity = 70
Enable Interrupt
mv88f6281_wdt: Watchdog Timer timeout = 8 sec.
mv88f6281_wdt: HW Watchdog timeout = 15 sec.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.8)
SGI XFS with large block numbers, no debug enabled
SGI XFS Quota Management subsystem
yaffs Jun 18 2010 22:04:25 Installing.
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload enabled
o Receive checksum offload enabled
o Transmit checksum offload enabled
o Network Fast Processing (Routing) supported
o Proc tool API enabled
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o eth0, ifindex = 1, GbE port = 0
eth_get_config: Unexpected port number 1
EthPort #1: Bad initialization parameters
eth port=1: load failed
eth_init_module: can't init eth_hal driver
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
EnablePowerSaving
PowerSavingTime = 15
No found HD
/////////////////////////////////// init sd
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1 at 0x00020000
Bad eraseblock 2 at 0x00040000
Bad eraseblock 3 at 0x00060000

...

Bad eraseblock 1021 at 0x07fa0000
Bad eraseblock 1022 at 0x07fc0000
Bad eraseblock 1023 at 0x07fe0000
9 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 9 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "uboot"
0x00100000-0x00180000 : "uboot_env"
0x00180000-0x00200000 : "key_store"
0x00200000-0x00280000 : "info"
0x00280000-0x00c80000 : "etc"
0x00c80000-0x01680000 : "kernel_1"
0x01680000-0x04640000 : "rootfs1"
0x04640000-0x05040000 : "kernel_2"
0x05040000-0x08000000 : "rootfs2"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
In hub_port_init, and number is 0, retry 0, port 1 .....
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 94 MB/s
raid6: int32x2 136 MB/s
raid6: int32x4 123 MB/s
raid6: int32x8 109 MB/s
raid6: using algorithm int32x2 (136 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1090.800 MB/sec
8regs : 653.600 MB/sec
32regs : 884.400 MB/sec
raid5: using function: arm4regs (1090.800 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: setting the system clock to 2000-05-01 00:04:55 (957139495)
Freeing init memory: 3092K
Cannot read bad block mark: Invalid argument
*** Stage 1: Setup system and device drivers ***
Cannot read bad block mark: Invalid argument
BusyBox v1.1.1 (2010.06.18-13:49+0000) multi-call binary

Usage: ifconfig [-a] <interface> [<address>]

egiga0: started
Cannot set device generic segmentation offload settings: Operatipcf8563 0-0051: low voltage detected, date/time is not reliable.
on not supported
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
*** Stage 2: Prepare the root file system ***
Mount system partition...
mount: special device /dev/mtdblock does not exist
ls: /zyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
Starting Pure-FTPd ...
usb 1-1.2: new high speed USB device using ehci_marvell and address 3
In hub_port_init, and number is 1, retry 0, port 2 .....
usb 1-1.2: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
1 second...
2 second...
3 second...
4 second...
5 second...
scsi 2:0:0:0: Direct-Access Memorex Mini TravelDrive 6.50 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sda] 985087 512-byte hardware sectors (504 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] 985087 512-byte hardware sectors (504 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
6 second...
7 second...
8 second...
9 second...
10 second...
sda
checking sda
Trying to mount /dev/sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
cp: `/mnt/parnerkey/usb_key_func.sh' and `/mnt/parnerkey/usb_key_func.sh' are the same file
md5 check ok
Doing pre-install ...
... pre-install finishes!

Please press Enter to activate this console.


Now it has lights from top to bottom:
Blue
Amber blinking
Red Blinking
Off
Free
Red blinking

How long should I wait, maybe twenty minutes?

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Sat Jun 30, 2018 6:04 am

fromutah wrote:
Fri Jun 29, 2018 8:58 pm
I'll give that a try when I'm back with it tonight. I assume there is nothing in the first part of the console log that would tell me whether 1 or 2 is safer?
No. I can only tell you that it's now using kernel 2:

Code: Select all

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

Code: Select all

Creating 9 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "uboot"
0x00100000-0x00180000 : "uboot_env"
0x00180000-0x00200000 : "key_store"
0x00200000-0x00280000 : "info"
0x00280000-0x00c80000 : "etc"
0x00c80000-0x01680000 : "kernel_1"
0x01680000-0x04640000 : "rootfs1"
0x04640000-0x05040000 : "kernel_2"
0x05040000-0x08000000 : "rootfs2"
Maybe you can simply set the u-boot environment variable curr_bootfrom to 1, to get the other half. But first check your power supply. If that is causing the problem attempting to write the nand could just make things worse.
What am I looking for with the power supply? it's the same one that came with it. Just check to see if voltage is close to that states as output voltage?
Yes. And if you can, measure it while the disks are spinning up.
Is a Zyxel NAS540 a good 4-bay replacement, or what would be another good cheap home/small business NAS? I've got the healthy drives and salvaged the data from this NSA320.
The 540 is deprecated. It's replacer NAS542 is technically identical. (Only has another color drive bracket. Sigh).

I don't know if that is a good choice. The hardware is good, but ZyXEL is not very good in keeping the firmware up to date. The last firmware is more than a year old. (It contains a fix for sambacry). The same is true for the packages.
On the other hand, it just works. If your NAS isn't exposed to the internet, and you don't care about fanciness, a 542 could be a good choice. (And fancy it is. The webinterface is totally changed, compared to a 320.) A comparable choice of a more active competitor is significantly more expensive.
Be aware that you can't plug in the 320 disks and expect it to accept them as is. They will need to be reformatted.

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Am I too late to get NSA320 not booting help?

Post by Mijzelf » Sat Jun 30, 2018 6:07 am

How long should I wait, maybe twenty minutes?
The box should reboot if it's ready. But if you see the 'press key to enter console', the script is already ready. Check the log.

fromutah
Posts: 10
Joined: Wed Jun 27, 2018 7:08 am

Re: Am I too late to get NSA320 not booting help?

Post by fromutah » Mon Jul 02, 2018 4:51 am

The log. I'll go through the script and remove some of the safety measures in homes of forcing a write. What have I got to loose?

Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
Cannot read bad block mark: Invalid argument
led_state_map_addr = 4b
Cannot read bad block mark: Invalid argument
board_model=(), file_model=(DD01) ... NOT equal!
led_state_map_addr = 4a
led_state_map_addr = 5
led_state_map_addr = 15
led_state_map_addr = 4b
led_state_map_addr = 0
led_state_map_addr = 10
*** current revision:
*** montavista last revision: 34713
[: 34713: unknown operand
*** it's already new firmware, do nothing here. ***
Kernel checksum pass!
System image checksum pass!
/sbin/flash_eraseall: /dev/mtd: No such file or directory
/sbin/flash_eraseall: /dev/mtd: No such file or directory
/sbin/flash_eraseall: /dev/mtd: No such file or directory
open flash: No such file or directory
/sbin/flash_eraseall: /dev/mtd: No such file or directory
open flash: No such file or directory
/sbin/flash_eraseall: /dev/mtd: No such file or directory
open flash: No such file or directory
/sbin/flash_eraseall: /dev/mtd: No such file or directory
open flash: No such file or directory
Fail to write kernel to nand
led_state_map_addr = 49
led_state_map_addr = 9
led_state_map_addr = 19

Post Reply