NSA310 how to install debian on fresh HDD

Hi

I used to have Zyxel NSA310 with debian but my hdd failed recently and I am struggling to find documentation on how to install it on fresh HDD ?
Can you point me to such howto ?

Thanks

SirK79,

> I used to have Zyxel NSA310 with debian but my hdd
> failed recently and I am struggling to find
> documentation on how to install it on fresh HDD ?
>
> Can you point me to such howto ?

The same procedure is used whether you use USB or HDD.

http://forum.doozan.com/read.php?2,12096

Use Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016) rootfs in this section:

Quote

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:

- tarball size: 137M
- install size: 398M
- a basic jessie rootfs.
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Follow the instruction closely, to the letter. For example, being root, single Ext3 parttion,... And you can use any other Linux box to do this.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for you help bodhi I believe I followed this document closely {afaik} and hit a problem while booting:

U-Boot 2013.07 (Sep 20 2013 - 15:45:03)
ZyXEL NSA310 1-Bay Power Media Server 


SoC:   Kirkwood 88F6281_A1
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0 
NSA310> usb start
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
NSA310> setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb'
NSA310>  setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
NSA310>  setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
NSA310>  run load_dtb
11897 bytes read in 559 ms (20.5 KiB/s)
NSA310> run load_uimage
3167962 bytes read in 385 ms (7.8 MiB/s)
NSA310>  run load_initrd
7179935 bytes read in 477 ms (14.4 MiB/s)
NSA310>  bootm 0x800000 0x1100000 0x1c00000
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3167898 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 0f465000, end 0fb3de5f ... OK
   Loading Device Tree to 0f45f000, end 0f464e78 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: ZyXEL NSA310
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 250576K/262144K available (6007K kernel code, 573K rwdata, 1992K rodata, 296K init, 312K bss, 11568K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07d7ef4   (8000 kB)
[    0.000000]       .init : 0xc07d8000 - 0xc0822000   ( 296 kB)
[    0.000000]       .data : 0xc0822000 - 0xc08b169c   ( 574 kB)
[    0.000000]        .bss : 0xc08b169c - 0xc08ff9d0   ( 313 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000326] Console: colour dummy device 80x30
[    0.000357] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[    0.090099] pid_max: default: 32768 minimum: 301
[    0.090210] Security Framework initialized
[    0.090287] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090307] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091157] Initializing cgroup subsys io
[    0.091192] Initializing cgroup subsys devices
[    0.091216] Initializing cgroup subsys freezer
[    0.091247] Initializing cgroup subsys net_cls
[    0.091329] CPU: Testing write buffer coherency: ok
[    0.091784] Setting up static identity map for 0x8200 - 0x8258
[    0.092112] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.095764] devtmpfs: initialized
[    0.101186] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.101648] prandom: seed boundary self test passed
[    0.105387] prandom: 100 self tests passed
[    0.105413] pinctrl core: initialized pinctrl subsystem
[    0.106787] NET: Registered protocol family 16
[    0.107149] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.130106] cpuidle: using governor ladder
[    0.160105] cpuidle: using governor menu
[    0.160483] Feroceon L2: Enabling L2
[    0.160529] Feroceon L2: Cache support initialised.
[    0.166181] No ATAGs?
[    0.201603] vgaarb: loaded
[    0.201980] usbcore: registered new interface driver usbfs
[    0.202062] usbcore: registered new interface driver hub
[    0.202125] usbcore: registered new device driver usb
[    0.203163] clocksource: Switched to clocksource orion_clocksource
[    0.258235] NET: Registered protocol family 2
[    0.259042] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.259080] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.259112] TCP: Hash tables configured (established 2048 bind 2048)
[    0.259180] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.259204] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.259399] NET: Registered protocol family 1
[    0.259806] RPC: Registered named UNIX socket transport module.
[    0.259819] RPC: Registered udp transport module.
[    0.259827] RPC: Registered tcp transport module.
[    0.259834] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.260191] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.261226] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.261298] audit: initializing netlink subsys (disabled)
[    0.261348] audit: type=2000 audit(0.250:1): initialized
[    0.261696] Initialise system trusted keyring
[    0.262083] zbud: loaded
[    0.262374] VFS: Disk quotas dquot_6.6.0
[    0.262435] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.262983] NFS: Registering the id_resolver key type
[    0.263022] Key type id_resolver registered
[    0.263032] Key type id_legacy registered
[    0.263058] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.263073] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.263365] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.263902] Key type big_key registered
[    0.275246] Key type asymmetric registered
[    0.275269] Asymmetric key parser 'x509' registered
[    0.275361] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.275384] io scheduler noop registered
[    0.275400] io scheduler deadline registered
[    0.275460] io scheduler cfq registered (default)
[    0.276867] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.277549] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    0.277977] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    0.278821] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.278841] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.278855] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.278869] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.279281] PCI: bus0: Fast back to back transfers disabled
[    0.279307] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.293350] PCI: bus1: Fast back to back transfers disabled
[    0.293537] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    0.293552] pci 0000:00:01.0: BAR 13: assigned [io  0x10000-0x10fff]
[    0.293572] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[    0.293589] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[    0.293613] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[    0.293635] pci 0000:01:00.0: BAR 0: assigned [io  0x10000-0x100ff]
[    0.293650] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.293663] pci 0000:00:01.0:   bridge window [io  0x10000-0x10fff]
[    0.293678] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.293765] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[    0.294064] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.333843] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.334068] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.373842] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.374317] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.375723] console [ttyS0] disabled
[    0.375787] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    1.058784] console [ttyS0] enabled
[    1.063615] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[    1.069999] nand: Samsung NAND 128MiB 3,3V 8-bit
[    1.074670] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.082284] Scanning device for bad blocks
[    1.168283] Bad eraseblock 848 at 0x000006a00000
[    1.192330] libphy: Fixed MDIO Bus: probed
[    1.196902] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.203548] ehci-pci: EHCI PCI platform driver
[    1.208088] ehci-orion: EHCI orion driver
[    1.212300] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.217915] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.225873] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    1.243186] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.249458] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.256307] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.263587] usb usb1: Product: EHCI Host Controller
[    1.268485] usb usb1: Manufacturer: Linux 4.4.0-kirkwood-tld-1 ehci_hcd
[    1.275148] usb usb1: SerialNumber: f1050000.ehci
[    1.280605] hub 1-0:1.0: USB hub found
[    1.284457] hub 1-0:1.0: 1 port detected
[    1.289394] mousedev: PS/2 mouse device common for all mice
[    1.295725] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    1.302799] i2c /dev entries driver
[    1.309617] hidraw: raw HID events driver (C) Jiri Kosina
[    1.315511] drop_monitor: Initializing network drop monitor service
[    1.322061] NET: Registered protocol family 17
[    1.326839] Key type dns_resolver registered
[    1.331936] registered taskstats version 1
[    1.336135] Loading compiled-in X.509 certificates
[    1.341013] zswap: loaded using pool lzo/zbud
[    1.346489] Key type encrypted registered
[    1.351145] rtc-mv f1010300.rtc: setting system clock to 2016-09-10 13:25:48 UTC (1473513948)
[    1.361416] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    1.369016] Please append a correct "root=" boot option; here are the available partitions:
[    1.377516] 1f00          131072 mtdblock0  (driver?)
[    1.382605] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    1.390907] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.0-kirkwood-tld-1 #1
[    1.397896] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    1.404223] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[    1.412006] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[    1.418922] [<c00c2200>] (panic) from [<c07d9280>] (mount_block_root+0x204/0x24c)
[    1.426444] [<c07d9280>] (mount_block_root) from [<c07d93b4>] (mount_root+0xec/0x118)
[    1.434318] [<c07d93b4>] (mount_root) from [<c07d9504>] (prepare_namespace+0x124/0x184)
[    1.442358] [<c07d9504>] (prepare_namespace) from [<c07d8e9c>] (kernel_init_freeable+0x208/0x258)
[    1.451283] [<c07d8e9c>] (kernel_init_freeable) from [<c05b16b4>] (kernel_init+0x8/0xe4)
[    1.459417] [<c05b16b4>] (kernel_init) from [<c000f090>] (ret_from_fork+0x14/0x24)
[    1.467027] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Does anybody know what might be the reason ?

After reading about my problem I discovered that env might be the problem

NSA310> printenv 
CASset=min
CONTRY_TYPE=FF
FEATURE_BIT=00
MALLOC_len=3
MODEL_ID=A203
PRODUCT_NAME=NSA-310
VENDOR_NAME=ZyXEL Communications Corp.
arcNumber=4022
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda3
bootargs_end=:::DB88FXX81:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=ide reset; ext2load ide 0:1 0x800000 /uImage-3.2; bootm 0x800000
bootdelay=2
console=100000
disL2Cache=no
disL2Prefetch=yes
disaMvPnp=no
enaAutoRecovery=yes
enaCpuStream=no
enaDCPref=yes
enaICPref=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:19:CB:00:51:82
eth1mtu=1500
ethact=egiga0
ethaddr=50:67:F0:69:55:7D
ethmtu=1500
ethprime=egiga1
hddPowerCtrl=no
image_name=uImage
ipaddr=10.4.50.165
kernel_addr=0x4640000
loadaddr=0x02000000
loads_echo=0
mainlineLinux=yes
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
nandEcc=1bit
nandEnvBase=100000
netbsd_en=no
netmask=255.255.255.0
netretry=no
pcieTune=no
pexMode=RC
rcvrip=169.254.100.100
rootpath=/mnt/ARM_FS/
run_diag=yes
sata_dma_mode=yes
serverip=10.4.50.5
setL2CacheWT=yes
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 1464/131068 bytes

In my nsa I have usb that I am trying to boot but also have stata drive too. Not sure how this will affect root device

NSA310> ide reset

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: ST250LT007-9ZV14C  Firm: 0001DEM1 Ser#: W0Q022GJ
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

 usb start                                                                    
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

SirK79,

There are a few problems:

1. Your envs are still set to boot from USB. And the DTB is the GoflexNet

NSA310> setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb'
NSA310>  setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
NSA310>  setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'

So, they must be

setenv load_dtb 'ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-nsa310.dtb'
setenv load_initrd 'ext2load ide 0:1 0x1100000 /boot/uInitrd'
setenv load_uimage 'ext2load ide 0:1 0x800000 /boot/uImage'

2. You have either not flashed the default envs image that came with the new u-boot, or have accidentally restored the stock envs.

3. Your rootfs has the kirkwood-nsa310.dtb embedded inside uImage. When booting with separate DTB as in the u-boot envs setting above, you need the original uImage. Basically, you don't need to do section 4

Quote

4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
sync

So for the rootfs, reverse this step:

mv uImage uImage.nsa310
mv uImage.orig uImage

For item 1 and 2, if you can boot into this box with USB without changing u-boot envs, then I'd recommend doing that, and then install the latest version of u-boot:
http://forum.doozan.com/read.php?3,12381

If you don't want to install the new u-boot, I'll have to give you a good set of envs so you can use current u-boot 2013.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi

Thanks very much for full explanation of my problems. I have done what you've suggested and it worked perfectly !

I am in debian now :)

SirK79 Wrote:
-------------------------------------------------------
> Hi bodhi
>
> Thanks very much for full explanation of my
> problems. I have done what you've suggested and it
> worked perfectly !
>
> I am in debian now :)

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello Bodhi

I have a question. I wanted to install Debian on my NSA-310, till now I have upgraded UBoot to the newest version.
Before I was on stock firmware. Is there a way or tutorial how to install Debian from the beginning without upgrading
existing installation? It seems tutorial http://forum.doozan.com/read.php?2,12096 is about upgrading existing one?

AdamPL,

You can use create a new basic rootfs: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016)

Updated 20 Feb 2016: 

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. 

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs: 

- tarball size: 137M 
- install size: 398M 
- a basic jessie rootfs. 
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below. 
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils. 
- see LED controls in /etc/rc.local, and /etc/init.d/halt 
- see some useful aliases in /root/.profile 
- root password: root

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Once have Debian working on my NSA310 is there know way to fix front panel light to be working ?

SirK79 Wrote:
-------------------------------------------------------
> Once have Debian working on my NSA310 is there
> know way to fix front panel light to be working ?

Yes. I did not add that to the rootfs, since I released this before some of our members provided the listing of the LED class triggers. If nobody post it, you can get this listing and set it easily in /etc/rc/local:

ll -R /sys/class/leds/

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

krzysiek@NSA310:~$ ls -l  -R /sys/class/leds/
/sys/class/leds/:
total 0
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:green:copy -> ../../devices/platform/gpio-leds/leds/nsa310:green:copy
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:green:esata -> ../../devices/platform/gpio-leds/leds/nsa310:green:esata
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:green:hdd -> ../../devices/platform/gpio-leds/leds/nsa310:green:hdd
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:green:sys -> ../../devices/platform/gpio-leds/leds/nsa310:green:sys
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:green:usb -> ../../devices/platform/gpio-leds/leds/nsa310:green:usb
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:red:copy -> ../../devices/platform/gpio-leds/leds/nsa310:red:copy
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:red:esata -> ../../devices/platform/gpio-leds/leds/nsa310:red:esata
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:red:hdd -> ../../devices/platform/gpio-leds/leds/nsa310:red:hdd
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:red:sys -> ../../devices/platform/gpio-leds/leds/nsa310:red:sys
lrwxrwxrwx 1 root root 0 Sep 12 19:46 nsa310:red:usb -> ../../devices/platform/gpio-leds/leds/nsa310:red:usb

I see how to works :)

root@NSA310:/home/krzysiek# echo 1 > /sys/class/leds/nsa310\:green\:hdd/brightness
root@NSA310:/home/krzysiek# echo 0 > /sys/class/leds/nsa310\:green\:hdd/brightnes

will update /etc/rc.local scripts and post it for other dummies like me :)

SirK79 Wrote:
-------------------------------------------------------
> I see how to works :)
>
>

> root@NSA310:/home/krzysiek# echo 1 >
> /sys/class/leds/nsa310\:green\:hdd/brightness
> root@NSA310:/home/krzysiek# echo 0 >
> /sys/class/leds/nsa310\:green\:hdd/brightnes
>

>
>
> will update /etc/rc.local scripts and post it for
> other dummies like me :)

:)

You want to set the trigger:

echo default-on > /sys/class/leds/nsa310:green:sys/trigger

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hdd and system work with below, only annoying thing is that leds do not work during boot up process

if [ -d /sys/class/leds/nsa310\:green\:sys ]; then
   echo default-on  > /sys/class/leds/nsa310\:green\:sys/trigger
   echo none        > /sys/class/leds/nsa310:orange:sys/trigger
fi

if [ -d /sys/class/leds/nsa310\:green\:hdd ]; then
   echo ide-disk1  > /sys/class/leds/nsa310\:green\:hdd/trigger
fi

if [ -d /sys/class/leds/nsa310\:green\:esata ]; then
   echo ide-disk2  > /sys/class/leds/nsa310\:green\:esata/trigger
fi

if [ -d /sys/class/leds/nsa310\:green\:usb ]; then
   echo usb-host > /sys/class/leds/nsa310\:green\:usb/trigger
fi

SirK79,

> Hdd and system work with below, only annoying
> thing is that leds do not work during boot up
> process

U-Boot 2013.07 (Sep 20 2013 - 15:45:03)
ZyXEL NSA310 1-Bay Power Media Server

Which u-boot is this? your own build or from somewhere? that might be the reason. My latest released u-boot should blink the LED correctly.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks Bodhi will upgrade uboot to your latest one. This was quite old uboot one of the first that I found supporting dft kernels boot.

Is esata working on Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on NSA310?

SirK79 Wrote:
-------------------------------------------------------
> Is esata working on
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> on NSA310?

Yes. It should.

BTW, there are 3 variations of the NSA310. You should use the right one.

/boot/dts/kirkwood-nsa310a.dtb
/boot/dts/kirkwood-nsa310b-lmsensor-redusbled.dtb
/boot/dts/kirkwood-nsa310.dtb

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/14/2016 02:18PM by bodhi.

What is the best way to determine which version I have ?
Console reports:

U-Boot 2013.07 (Sep 20 2013 - 15:45:03)
ZyXEL NSA310 1-Bay Power Media Server 


SoC:   Kirkwood 88F6281_A1
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0

and

root@nsa310:~# lscpu 
Architecture:          armv5tel
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Model name:            Feroceon 88FR131 rev 1 (v5l)

Looks like this was human error as I have satap cable where nsa310 do not have power so has just esata without P(ower)