[solved] Install problem on Zyxel NSA 310

[dietgert]

Hello,

i tried to install arch to this device but it is not possible for me.
The serial console tells me:

.....
Trying to mount /dev/sdb1
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
cmd = cat /etc/Zy_Private /mnt/parnerkey/usb_key_func.sh | md5sum -c /mnt/parnerkey/salted_md5sum_3x0
md5sum: WARNING: 1 of 1 computed checksum did NOT match
md5 check error

Any suggestions ?

BR
didi

[WarheadsSE]

Sounds like it needs an updated checksum. From that device, run the md5sum program on the file as mentioned.

[dietgert]

Hello,

Why does a 2 years old file need an updated checksum?
What changed here? I dont get the point.
Did no other user have the same problem until now ?
Also, im not able to calculate a new checksum on the nsa310.
On my linux-desktop this worked well, on the nsa i dont even get an output.

BR
Didi

[WarheadsSE]

The fact that you got no output from md5sum on the 310 would lead to why the comparison didn't work.

No one I know has had this issue, correct. However, like I said, this is symptomatic to you, and I can't use the force to fix it.

[dietgert]

Ok, this brings me a little step further.
My NSA 310 is a TDC-rebranded one.
It contains however the normal zyxel firmware - i thought until now...

BR
didi

[dietgert]

Probably the behaviour has nothing to do with the rebrand.
I tried however a (successful) forced install of the stock zyxel firmware.
http://zyxel.nas-central.org/wiki/Flashing_firmware
And look, this usb_key_func.sh was accepted ..
I used it, added manually the correct usb_key_func.sh.2 for the installer,
with it then the installer began its work, formatted the hdd.
Then however i received an error, extracting of the rootfs.tgz failed.
many outputted:
tar: warning: skipping header `x`
The rootfs.tgz was not extracted. Probably because of an outdated or limited tar from the buysbox.
How can i fix that ? Any suggestion ?

Thanks,
Didi

[dietgert]

The installer is now finishing the installation.
To achieve this i had to unpack the ArchLinuxARM-kirkwood-latest.tar.gz file on my linux desktop
and recompressed it there.
Then the installer went through without any problem.
After a reboot the nsa 310 gives the following output:


...

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (5)
Device 0 @ 0 0:
Model: FUJITSU MHV2120BH PL Firm: 00000029 Ser#: NWADT6A27R03
Type: Hard Disk
Supports 48-bit addressing
Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)


4078520 bytes read
## Booting image at 02000000 ...
Image Name: Linux-4.2.0-1-ARCH
Created: 2015-09-02 13:00:35 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4078456 Bytes = 3.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Then nothing happens.
I suspect a false kernel here now, because all problems experienced until now were related to
the installer-file and scripts and not the rebranded tdc-device.

didi

[moonman]

Notice the warnings, they are not errors.

Did you recompress as root (NOT sudo)?

Since you have U-Boot installed, just take the drive out, connect it to your PC and extract the tarball on the PC (as root, and again, do not use sudo)

[dietgert]

Hello,

i made that. Extracted the original tarball on the PC, not my self-compressed one.
There were some warnings for "Schily-Flags" during the extraction, but no failure messages.
I also made a 2nd. attempt: did the steps as in the script manually on the hdd attached to the PC, hdd was wiped before.
In both cases the behaviour keeps the same as in my last email:
A kernel-image is loaded after reboot - then nothing happens: no boot process, no warnings, no errors ...
But what`s the reason ?

BR
didi

[dietgert]

Next Try..

i took an old kernel for debian arm from:
https://github.com/peeter123/NSA310-320 ... h/arm/boot
copied it to the boot partition (instead of the one supplied with the installer) and then ...

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: WDC WD5000AAKX-001CA0 Firm: 15.01H15 Ser#: WD-WMAYU0428964
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)


2503816 bytes read
## Booting image at 02000000 ...
Image Name: Linux-3.3.6
Created: 2012-05-17 22:47:20 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2503752 Bytes = 2.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.3.6 (peter@Ubuntu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 Fri May 18 00:46:28 CEST 2012
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Zyxel NSA-310

....
....


This kernel booted a least!
So the kernel supplied with the kirkwood-installer is a problem too..
Did someone have had a useful install on a zyxel -nsa-device at all with this tarball from the 3rd of September ?
Where can i find an older (and working) tarball of this installer ?

Best Regards,
didi