NSA325v2 - Issue with installation

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

NSA325v2 - Issue with installation

Postby arunnu » Tue Oct 04, 2016 9:24 am

Hello Arch forums,

Following the instructions found here, I inserted a 1 TB drive in the left slot, USB in a rear port and turned on the NSA.

After rebooting, the HD spins, the blue LED on the front is on, the fan is active and the ethernet port is blinking. The rest of the LEDs are inactive. I at first assumed that this is because of the Arch autoinstaller being busy configuring things, after giving it 30 minutes to finish this task it appears that something has gone wrong. Looking up my router's IP table suggests that the NSA was never assigned an IP, ruling out a net-based checkup.

Having searched the forums I am aware of the existence of this thread. However:
1) The first solution offered refers to MBR issues. Best I know, these do not happen when the drive is under 2 TB. I could be completely wrong, however.
2) Restoring the default environmental variables and restarting the installation either causes the USB to not be read or results in the situation described above.
3) The v2's hard disk bay is attached in such a way that I don't think I can safely attach a serial cable to the pins while the disk is in place, unless I support the HD creatively. This is a problem as to the best of my understanding the bootloader is configured to read from the disk.

The version of the original firmware is V4.81(AAAJ.0)C0. FFP has been installed previously and uninstalled prior to originally attempting to install Arch. I possess a working serial TTL cable.

Given the above, in what way can I find information on where the problem lies and how to fix it?
arunnu
 
Posts: 2
Joined: Tue Oct 04, 2016 8:28 am

Re: NSA325v2 - Issue with installation

Postby WarheadsSE » Tue Oct 04, 2016 1:03 pm

Hmm, I have never really had a problem fitting the TTL cable in under the HDD cage, but then I don't have a v2.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: NSA325v2 - Issue with installation

Postby Kabbone » Tue Oct 04, 2016 8:50 pm

I have a v2 and it still fits for me. I pluged a female-female in one time and just left it connected to the NSA325 with the other end behind the front cover.
Kabbone
 
Posts: 153
Joined: Thu Jul 25, 2013 9:20 am

Re: NSA325v2 - Issue with installation

Postby Socaltom » Tue Oct 04, 2016 11:40 pm

Most likely the drive you used had a partition on it, so the install choked. You need to put the drive in a linux PC and create the 2 partitions, format and extract the filesystem per the script on the USB stick. Then you can put in the drive.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: NSA325v2 - Issue with installation

Postby arunnu » Wed Oct 05, 2016 8:07 am

Thanks for the quick replies, everyone.

The reason I deemed connecting the TTL unsafe is because of how tight the fit between the serial cable and the hard disk bay is. Really wary of putting any undue pressure on the pins, you see. However, it appears to be working just fine. This makes everything a lot easier.

So: I attached the TTL cable and returned the NSA to how it was when I was installing Arch, minus the USB. Here's the uboot printout:

$this->bbcode_second_pass_code('', '
__ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9

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

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 8 tRAS = 24 tRCD=8
DRAM CS[0] base 0x00000000 size 512MB
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)
Kernel address is 0x4640000.

Streaming disabled
Write allocate disabled


USB 0: host mode
[BlueDBG] reseting SoC Pex[0] 0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
[BlueDBG] reseting SoC Pex[1] 0 ...
[BlueDBG] reseting SoC Pex[1] 1 ...
[BlueDBG] reseting SoC Pex[1] 2 ...
[BlueDBG] reseting SoC Pex[1] 3 ...
[BlueDBG] reseting SoC Pex[1] 4 ...
[BlueDBG] reseting SoC Pex[1] 5 ...
[BlueDBG] reseting SoC Pex[1] 6 ...
[BlueDBG] reseting SoC Pex[1] 7 ...
[BlueDBG] reseting SoC Pex[1] 8 ...
[BlueDBG] reseting SoC Pex[1] 9 ...
[BlueDBG] reseting SoC Pex[1] 10 ...
PEX 1: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: ST1000DM003-1CH162 Firm: CC47 Ser#: Z1D68PGC
Type: Hard Disk
Supports 48-bit addressing
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)


** Unable to read "/uImage" from ide 0:1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>
')

As the NSA is the only device on hand which both runs Linux and can easily have HDDs attached to it (I happen to be in a laptop-only office environment and can't take the NSA home to work on it - asked if that was a possibility already) I proceeded to return to the original firmware.

The boot process outputs this interesting bit:

$this->bbcode_second_pass_code('', '
Trying to mount /dev/sda1
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
')

However, after full bootup fdisk -l outputs:

$this->bbcode_second_pass_code('', '
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1b5502d6

Device Boot Start End Blocks Id System
/dev/sda1 1 3 24066 83 Linux
/dev/sda2 4 121601 976735935 83 Linux
')

In regards to the drive: While it wasn't fresh from the factory when I started installing, I ensured that there are no partitions on it before getting to it.

At this point I looked into usb_key_func.sh.2 and found that the partitions seem to be working as designed, the bootloader was set up properly and the issue was with the uImage. After mounting the partitions, I found that the uImage was not present. In fact, on both partitions nothing but the lost+found directory was present.
...this is around where I add the USB drive to the mix and notice while the partition seems okay (it mounts as /mnt/sdb1/ as compared to the /mnt/parnerkey/ the script expects) all the files are gone. Which explains why there are no files on the partitions. Still, very strange.

At this point I followed the commands in usb_key_func.sh.2 - had to wget a new kirkwood rootfs, then unpack the files where they're needed and finally set up the bootloader before syncing and resetting. Could've sworn I messed with this on and off for a week, and here we are.

Thanks for the help.
arunnu
 
Posts: 2
Joined: Tue Oct 04, 2016 8:28 am


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 8 guests