General NAS-Central Forums

Welcome to the NAS community
It is currently Sun Nov 19, 2017 1:17 am

All times are UTC




Post new topic Reply to topic  [ 17 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: NSA210 problems
PostPosted: Fri Nov 30, 2012 10:59 pm 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
Hey all,

My NSA210 has come to a point where it was unable to remount the drive or boot (not sure which, webadmin didn't work). It's already a second unit which I had to manually restore data from with mdadm (for those who seek help with this:
Code:
mdadm --assemble --run /dev/md0 /dev/{partition from your drive from NSA}
- obviously that's when you took out your drive and attached it to a linux box )

I would like to see the boot process of the thingy to see what's wrong (not sure it boots atm). Does anybody have an idea if the board has any sort of serial console port? What about that JP2 ? any pinout ?

thanks


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 10:11 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
I have no experience with the '210, but I have two ZyXEL NASses here, the '220 and the '325, and a ZyXEL modem which all have the same pinning and baudrate:
Code:
+----+----+----+    +----+
|3.3V| TX | RX |    | GND|
+----+----+----+    +----+
115200 baud, no parity, 8 data bits, 1 stop bit, no handshake.

So I suppose this is some sort of 'ZyXEL universal' serial port.

BTW, this is TTL level, not RS232! You'll need a RS232 to TTL level converter, or an USB to TTL converter. I used a FTDI TTL-232R-3V3, but on ebay you can find cheaper equivalents.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 10:22 am 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
thanks a lot. Gonna have to get the unit to my friend, I don't have TTL converter at hand atm.
the pins on the IC+ IP 1001 chip seemed a bit oxidized, but the network seems to be working (I cleaned it a bit with alcohol)
weirdly FTP works (it gets connected).
I tried the telnet 6s reset, but unfortunately I have already 4.40 FW, which doesn't seem to support that option. And it doesn't load usbkeyfunc.sh with telnet aswell, which sucks bigtime :(
NSU stucks at "Initializing", sigh.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 10:43 am 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
hm actually NSU is able to set the IP properly and it pings, so it doesn't seem to be totally bricked. Gonna have to try serial console
Actually it has two rows :

did I understand it correctly?

I tried the NSU with initialization (without HDD - that could be some problem), it did set the network during the process, but after the reboot the config was lost - could it be it stores the config on the drive ?


You do not have the required permissions to view the files attached to this post.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 11:46 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
Only an FTP server? At IP 192.168.1.3? Did you do a portscan? This is a part of the bootscript of fw 3.20:
Code:
no_disk_handler()
{
        # Try to umount ${DISKPATH}; we don't need a non-NSA210 system disk.
        /bin/umount ${DISKPATH} > /dev/null 2>&1

        # Create a tmpfs for sysinit
        /bin/mkdir -p ${SYSINIT_PATH}
        /bin/mount -t tmpfs none ${SYSINIT_PATH} -o size=30m > /dev/null 2>&1

        # Allow a user 'sysinit' to login FTP server
        /bin/sed -i -e "s/^sysinit:\!\!:/sysinit:${SYSINIT_PASSWD}:/g" /etc/shadow
        echo "Starting Pure-FTPd ..."
        /bin/pure-ftpd.official `/bin/cat /etc/pure-ftpd.arg`

        echo "Starting NDU agent for initialization ..."
        /sbin/init_nduagent

        echo 70 > /proc/led

        sleep 5

        # Scan USB disk for HW test.
<snip>

/sbin/ifconfig egiga0 192.168.1.3
/bin/ip route append default via 192.168.1.1 dev egiga0
/sbin/ifconfig lo add 127.0.0.1 netmask 255.0.0.0
/sbin/ifconfig lo up

<snip>

# Check if there is a sysdisk partition in HD
sysdevsdx=`ls "/sys/devices/platform/oxnassata.0/host0/target0:0:0/0:0:0:0"|grep "block:sd"|cut -d ":" -f 2`
echo "${sysdevsdx}"
if [ "${sysdevsdx}" == "" ]; then
        sleep 2
        sysdevsdx=`ls "/sys/devices/platform/oxnassata.0/host0/target0:0:0/0:0:0:0"|grep "block:sd"|cut -d ":" -f 2`
        echo "/dev/${sysdevsdx}"
        if [ "${sysdevsdx}" == "" ]; then
                no_disk_handler
                exit 0
        fi
fi
As you can read in case of 'no_disk_handler' the IP address is 192.168.1.3, and an FTP server and the NDU agent is started. The no_disk_handler is invoked when either no disk is present, or the disk doesn't have a valid (valid for a ZyXEL NAS) system partition. So if this is the behavior with the disk inserted, something happened to the system partition, or the disk died, of course.

Quote:
And it doesn't load usbkeyfunc.sh with telnet aswell
What *exactly* did you do? It should work, but it's very easy to do it wrong.
Quote:
Actually it has two rows
That doesn't look like a 'ZyXEL standard serial port®'. Is there nowhere a 3pin-space-1pin on the board?
Quote:
after the reboot the config was lost - could it be it stores the config on the drive ?
Maybe. Most ZyXEL NASses store it in flash, but the 210 (and the 221) are quite different.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 12:24 pm 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
this is the board - notice the JP2 connector in the bottom left. Other side of the board has only some smd's and drive connector, nothing special. So I need to somehow figure it out by myself :S

Attachment:
fotka.JPG


but firstly I'll try to get it running with some drive, maybe it'll fix things


You do not have the required permissions to view the files attached to this post.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 12:55 pm 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
Code:
root@ubuntu:/home/ubuntu# nmap -PN 192.168.2.5

Starting Nmap 6.00 ( http://nmap.org ) at 2012-12-01 12:55 UTC
Nmap scan report for 192.168.2.5
Host is up (0.00069s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
21/tcp open  ftp
MAC Address: 00:23:F8:73:5D:B3 (ZyXEL Communications)

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 1:14 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
That 3 pin connector top right is the fan, I suppose?

Well, in that case the serial port must be on jp2, as you suggested.
Quote:
So I need to somehow figure it out by myself :S
Actually it's less difficult and risky as it sounds. You have a multimeter? First measure (with unpowered board) the resistance between ground (from the power connector) and the pins. You'll find at least 1 zero ohm. That's the ground. (duh). It is perfectly possible that you'll find 5 grounds, or something like that. Then power up the board, and measure the voltage between a ground pin, and the remaining pins. You'll probably find one or more 3.3V, and several zero V pins, maybe a 'in between', and maybe also a +5V or +12V pin.

All 'zero V' pins (not the ground pins), 'in between' and 3.3V pins are suspect of being RX or TX. But the 'zero V' pins are more suspect of being RX, while the others are more suspect of being TX.

All 5V and higher pins are suspect of being dangerous for your TTL port, so don't touch these.

Now you can start your serial terminal, set the baudrate to 115200-n-8-1. Short the RX and TX of your TTL cable, and type something. It should be echoed. If you break the short, the echoing should stop. Then the cable is OK.

Connect the ground to one of the ground pins, and probe with the TTL-RX line the TX suspects. Connect the pin, and power up the board. If you don't see anything in 10 seconds, repeat with next suspect, until you find the boot log. Then you've found the TX.
The RX is found basically the same, but it is possible you won't find it, as you'll need feedback of the NAS, and possibly the NAS never actually listens to it's RX.

BTW, you only need ground,RX and TX.
3.3V is only needed in the rare cases the TTL level port of your converter needs a reference voltage, or even power from that line.

About your nmap log, did you change ip address using NDU? It's not the default 'panic' address.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Sat Dec 01, 2012 1:44 pm 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
Exactly, top right is fan.

In the bottom line of JP2 I found following (I measured GND's from the spots where the screws are)

3.32V | 3.32V | 3.09V | GND | GND
which would correspond to:
VNC | TX | RX | GND | GND

top line (as in the pic) was following:
0V | 0V | 0V | 3.32V | 0.01V - though all of these had some resistance value

I didn't find anything higher than 5V on any pin

I need now to get some TTL converter

Am under linux atm (backing up 500GB of data /sigh), so couldn't run NDU. Though even when I ran NDU, the board booted up with DHCP address. Gonna try to switch a notebook of mine to 192.168.1.0 network and shall see wether it'll respond to telnet calls


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Mon Dec 03, 2012 7:23 pm 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
So, managed to confirm:

bottom row:
VCC, TX, RX, GND, GND

used serial with 115200 + standard setup, boot log follows:

Code:
1.00 U-Boot 1.1.2 (Apr 10 2009 - 16:43:58)

U-Boot code: 48D00000 -> 48D17270  BSS: -> 48D1AF20
RAM Configuration:
        Bank #0: 48000000 128 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:    1771216 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 T                                                                                                                                                             hu Jul 19 16:51:18 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: 32512
Kernel command line: console=ttyS0,115200n8 root=/dev/ram0 rw init=/sbin/init in                                                                                                                                                             itrd=0x4a000000,4M elevator=cfq mtdparts=physmap-flash.0:128k(uboot),1792k(kerne                                                                                                                                                             l),1664k(initrd),448k(etc),48k(empty),8k(env1),8k(env2) mem=128M poweroutage=yes
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 122240KB available (3188K 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 0x0acb15eaacc0 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: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
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 ICPlus 1001
phy init done
eth0: GMAC ver = 51, vendor ver = 17 at 0xe8000000, IRQ 8
eth0: Found PHY at address 1, type 0x02430d90 -> 10/100/1000
eth0: Ethernet addr: 00:30:e0:00:00:00
Init phy sucessfully
thermAndFan: initializing - ox810
Init led blk
Enable Interrupt
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
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
usbcore: registered new interface driver usblp
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
OXNAS bit-bash I2C driver initialisation OK
md: linear personality registered for level -1
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 ICPlus 1001
Resetting GMAC
GMAC reset complete
ifconfig: bad address 'add'
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: retrieved date/time is not valid.
Starting udhcpc ...
udhcpc (v1.17.2) started
ls: /sys/devices/platform/oxnassata.0/host0/target0:0:0/0:0:0:0: No such file or directory
Sending discover...

egiga0: PHY is ICPlus 1001
egiga0: link down
ls: /sys/devices/platform/oxnassata.0/host0/target0:0:0/0:0:0:0: No such file or directory
/dev/
Starting Pure-FTPd ...
Starting NDU agent for initialization ...
MTD_open
MTD_ioctl
MTD_read
MTD_close
MTD_open
MTD_ioctl
MTD_read
MTD_close
Sending discover...
Sending discover...


Please press Enter to activate this console. No lease, forking to background



BusyBox v1.17.2 (2012-07-19 21:36:49 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Tue Dec 04, 2012 11:56 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
That could be a normal log, provided there is no disk inside. Here you can find a 'normal' bootlog, and as far as I can see (without using diff tools) the difference is in harddisk detection.

BTW, do you mind if I use your photo in the wiki?


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Wed Dec 05, 2012 7:31 am 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
Mijzelf wrote:
That could be a normal log, provided there is no disk inside. Here you can find a 'normal' bootlog, and as far as I can see (without using diff tools) the difference is in harddisk detection.

BTW, do you mind if I use your photo in the wiki?


thanks - sure you can use the photos np

Anyway, there's one difference which I see:
mine:
Code:
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: retrieved date/time is not valid.


vs default:
Code:
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0


might be that there's some capacitor hickup somewhere on the board resulting in lower voltages eventually in other areas aswell? I checked the battery, it's at ~3.112V

Didn't really come up yet to some proper testing (had a lot of work to do lately), maybe on weekend I get back to the board


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Wed Dec 05, 2012 3:54 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
neosk wrote:
might be that there's some capacitor hickup somewhere on the board resulting in lower voltages eventually in other areas aswell? I checked the battery, it's at ~3.112V
Who knows? Your 3.3V reference voltage was OK, I suppose? But of course it could be another circuit.
What is the battery supposed to deliver?


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Thu Dec 06, 2012 9:29 am 
Offline

Joined: Fri Nov 30, 2012 10:52 pm
Posts: 10
Mijzelf wrote:
neosk wrote:
might be that there's some capacitor hickup somewhere on the board resulting in lower voltages eventually in other areas aswell? I checked the battery, it's at ~3.112V
Who knows? Your 3.3V reference voltage was OK, I suppose? But of course it could be another circuit.
What is the battery supposed to deliver?

battery probbably helps keep the clock being remembered and running. That means the low voltage report means the voltage being supplied to the RTC chip is below normal.
Other thing - after booting, ping works, though name resolving does not, even for example when /etc/resolv.conf was set to use 8.8.8.8 (google dns - which I find reliable). Even nslookup didn't help. Which would maybe mean that some lib is corrupt. On weekend I'll try to boot some busybox all-in-one kernel with high hopes of having the drivers. A friend of mine suggested to build a new kernel, the question is - are there some drivers available at least for 2.6.24-4 (one would guess for sure - hence it's GPL).


Top
 Profile  
 
 Post subject: Re: NSA210 problems
PostPosted: Thu Dec 06, 2012 12:04 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6072
The major part of the firmware is loaded from harddisk, normally. So it's not surprising when not everything works without disk. Without harddisk the box must be able to start NDU agent, and an FTP server, and be able to partition/format the disk, so the NDU client is able to upload the disk-part of the firmware.

BTW, about name resolving, did you check the default gateway?

Quote:
On weekend I'll try to boot some busybox all-in-one kernel with high hopes of having the drivers. A friend of mine suggested to build a new kernel, the question is - are there some drivers available at least for 2.6.24-4 (one would guess for sure - hence it's GPL).
I'm not sure what you mean with drivers here. The box runs an Oxnas 810 SoC, and the *only* available Linux kernel (the Oxfort supplied 2.6.24.4) of course supports all devices in this SoC, sata, usb, fancontrol, nic and gpio.
There are some more Oxnas 810 based NASses, but they basically all use the same kernel. Well, some minor changes in gpio.
ZyXEL NSA221, Iomega Home Media, Sitecom MD-253/254 and Western Digital Mybook World Edition (white light).

You might be interested in this.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 17 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group