Can't start NSA-221

Oxnas 810 based
Post Reply
bb00197
Posts: 2
Joined: Wed May 22, 2013 3:39 am

Can't start NSA-221

Post by bb00197 » Wed May 22, 2013 3:48 am

I have NSA221 with 440AFM0C0 firmware and I try to recover firmware corrupted NSA221...But my NSA221 can't boot now...
Can you help me?

This is my Log File:

1.00 U-Boot 1.1.2 (Apr 11 2010 - 20:23:49)

U-Boot code: 48D00000 -> 48D172F4 BSS: -> 48D1AFA4
RAM Configuration:
Bank #0: 48000000 256 MB
SRAM Configuration:
128KB at 0x58000000
Flash: 4 MB
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
## Booting image at 41020000 ...
Image Name: Linux-2.6.24.4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1774952 Bytes = 1.7 MB
Load Address: 48008000
Entry Point: 48008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................... done, booting the kernel.
Linux version 2.6.24.4 (root@Neo) (gcc version 4.3.2 (sdk3.3-ct-ng-1.4.1) ) #1 Thu Aug 16 14:34:54 CST 2012
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Oxsemi NAS
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: console=ttyS0,115200n8 root=/dev/ram0 rw init=/sbin/init initrd=0x4a000000,4M elevator=cfq mtdparts=physmap-flash.0:128k(uboot),1792k(kernel),1664k(initrd),448k(etc),48k(empty),8k(env1),8k(env2) mem=256M poweroutage=yes
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 252160KB available (3196K code, 198K data, 116K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
Number of DMA channels = 5, version = 4
Allocating 891 SRAM generic DMA descriptors
Chip Id: die-id 0x0b6512347140 read back 0xbeefcafe
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
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
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 4096K
Probing for Synopsis GMAC, unit 0
eth0: PHY is Realtek RTL8211BGR
phy init done
eth0: GMAC ver = 51, vendor ver = 17 at 0xe8000000, IRQ 8
eth0: Found PHY at address 1, type 0x001cc912 -> 10/100/1000
eth0: Ethernet addr: 00:30:e0:00:00:00
Init phy sucessfully
thermAndFan: initializing - ox810
Init led blk
Enable Interrupt
Copy button
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.9)
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ÿserial8250: ttyS0 at MMIO 0x44900000 (irq = 29) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: module loaded
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ox810sata: OX810 sata core.
scsi0 : oxnassata
ata1: SATA max UDMA/133 irq 18
ata_eh_reset(2207):Sleep 1 sec before any error happens
Copy button release
ata1: SATA link down (SStatus 0 SControl 300)
ox810sata: OX810 sata core.
scsi1 : oxnassata
ata2: SATA max UDMA/133 irq 18
ata_eh_reset(2207):Sleep 1 sec before any error happens
ata2: SATA link down (SStatus 0 SControl 300)
physmap platform flash device: 00400000 at 41000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
7 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 7 MTD partitions on "physmap-flash.0":
0x00000000-0x00020000 : "uboot"
mtd: Giving out device 0 to uboot
0x00020000-0x001e0000 : "kernel"
mtd: Giving out device 1 to kernel
0x001e0000-0x00380000 : "initrd"
mtd: Giving out device 2 to initrd
0x00380000-0x003f0000 : "etc"
mtd: Giving out device 3 to etc
0x003f0000-0x003fc000 : "empty"
mtd: Giving out device 4 to empty
0x003fc000-0x003fe000 : "env1"
mtd: Giving out device 5 to env1
0x003fe000-0x00400000 : "env2"
mtd: Giving out device 6 to env2
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver@e7000000 Device ID register 42fa05
oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
oxnas-ehci oxnas-ehci.0: irq 7, io mem 0x00000000
oxnas-ehci oxnas-ehci.0: USB 0.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: 3 ports detected
USB Universal Host Controller Interface driver v3.0
sl811: driver sl811-hcd, 19 May 2005
usb 1-1: new high speed USB device using oxnas-ehci 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
usb 1-1.2: new high speed USB device using oxnas-ehci 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
usb 1-1.3: new high speed USB device using oxnas-ehci and address 4
In hub_port_init, and number is 2, retry 0, port 3 .....
usb 1-1.3: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
scsi3 : SCSI emulation for USB Mass Storage devices
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
OXNAS bit-bash I2C driver initialisation OK
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc)
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 116K
MTD_open
MTD_ioctl
MTD_read
MTD_close
MTD_open
MTD_ioctl
MTD_read
MTD_close
Mounting file systems...
MTD_open
MTD_ioctl
MTD_read
MTD_close
MTD_open
MTD_ioctl
MTD_read
MTD_close
egiga0: PHY is Realtek RTL8211BGR
Resetting GMAC
GMAC reset complete
ifconfig: bad address 'add'
Starting udhcpc ...
INITRD: Trying to mount NAND flash as Root FS.egiga0: PHY is Realtek RTL8211BGR
egiga0: link down
...scsi 2:0:0:0: Direct-Access ZyXEL USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sda] 247808 512-byte hardware sectors (127 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
scsi 3:0:0:0: Direct-Access ADATA USB Flash Drive 1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: [sda] 247808 512-byte hardware sectors (127 MB)
sd 3:0:0:0: [sdb] 30869504 512-byte hardware sectors (15805 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda:<5>sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sda1
sd 2:0:0:0: [sda] Attached SCSI removable disk
sd 3:0:0:0: [sdb] 30869504 512-byte hardware sectors (15805 MB)
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 3:0:0:0: [sdb] Attached SCSI removable disk
sd 3:0:0:0: Attached scsi generic sg1 type 0
/dev/sdb
mount upgrade key
umount: can't umount /zyxel/mnt/NAND: Invalid argument
bsname}: no internal disk available
Flag_HD_Exists = 1
WARNING: No valid partition on HDD or no HDD plugged!
WARNING: No valid partition on HDD or no HDD plugged
Booting from ramdisk
gzip: /zyxel/mnt/NAND/sysdisk.img.gz: No such file or directory
mount: mounting /dev/loop0 on /ram_bin failed: Invalid argument
*** ERROR: Can not mount system image, file is invalid
killall: udhcpc: no process killed
mount: mounting /ram_bin/usr on /usr failed: No such file or directory
mount: mounting /ram_bin/sbin on /sbin failed: No such file or directory
mount: mounting /ram_bin/bin on /bin failed: No such file or directory
mount: mounting /ram_bin/lib on /lib failed: No such file or directory
tar: can't open '/ram_bin/tmp.tar.gz': No such file or directory
cp: can't stat '/ram_bin/var/*': No such file or directory
cp: can't stat '/ram_bin/home/*': No such file or directory
cp: can't stat '/ram_bin/mnt/*': No such file or directory
cp: can't stat '/ram_bin/etc/*': No such file or directory
cp: can't stat '/bin/makedev.sh': No such file or directory
/etc/init.d/rcS.221: line 307: ./makedev.sh: not found
/etc/init.d/rcS.221: line 309: /etc/init.d/rcS2: not found

Please press Enter to activate this console.

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

Re: Can't start NSA-221

Post by Mijzelf » Wed May 22, 2013 7:49 am

Can you give some history? When I compare your bootlog to this one, the most striking difference is a large block of (s)ata messages. I suppose due to you are running without disks.

Can you enter a shell? What is the output of:

Code: Select all

cat /proc/partitions
cat /proc/mounts

bb00197
Posts: 2
Joined: Wed May 22, 2013 3:39 am

Re: Can't start NSA-221

Post by bb00197 » Wed May 22, 2013 4:41 pm

Mijzelf wrote:Can you give some history? When I compare your bootlog to this one, the most striking difference is a large block of (s)ata messages. I suppose due to you are running without disks.

Can you enter a shell? What is the output of:

Code: Select all

cat /proc/partitions
cat /proc/mounts
My NSA221 can boot, thank you for reply.

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

Re: Can't start NSA-221

Post by Mijzelf » Wed May 22, 2013 5:59 pm

What did you do to get it booting again?

Post Reply