Questions for adding debian on NSA320

My NSA320 has been acting odd lately and before I give up and get new hardware Id like to update it to newer uboot/kernel.
(issue is that drives seem to drop and the nsa iteself seems unresponsive. Light for hd1 turns orange, but reboot clears it. Disk checks and SMART info dont point out any issues. Nothing in logs. After reboot things work ok and then after a while the process has to be repeated.)

I plan to use a usb drive for the filesystem. 16 GB would be more than enough?

I also prefer a web based setup and it seems OMV fits the bill. Any other suggestions I check out?

If something is wrong I expect I will have more power to diagnosing the problem with a custom debian setup with ssh.

Pickle,

> My NSA320 has been acting odd lately and before I
> give up and get new hardware Id like to update it
> to newer uboot/kernel.

What is currently installed on this box?

> (issue is that drives seem to drop and the nsa
> iteself seems unresponsive. Light for hd1 turns
> orange, but reboot clears it. Disk checks and
> SMART info dont point out any issues. Nothing in
> logs. After reboot things work ok and then after a
> while the process has to be repeated.)
>

I will need to see the kernel log to help troubleshooting the problem. So before reboot, you should take the disk out, mount it on another Linux box and get the system logs from /var/log/messages.


> I plan to use a usb drive for the filesystem. 16
> GB would be more than enough?

Yes.

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

Its still running Zyxel's default firmware 4.70

Thats probably a good thing to try. I will hook both of my drives through my usb sata adapter tonight and post any output.

I didnt have /var/log/messages but have the systemd journal messages.
Is that what you are looking for?

Seagate drive

Aug 27 19:36:07 seashell kernel: scsi 4:0:0:0: Direct-Access     ST3000DM 001-1CH166       0041 PQ: 0 ANSI: 0
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] 1565565872 512-byte logical blocks: (802 GB/747 GiB)
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] Write Protect is off
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] No Caching mode page found                                                                                                                   
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through                                                                                                          
Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: [sdb] Attached SCSI disk

WD Drive

Aug 27 20:00:57 seashell kernel: scsi 4:0:0:0: Direct-Access     WDC WD40 EFRX-68WT0N0     0041 PQ: 0 ANSI: 0
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: [sdb] 3519069872 512-byte logical blocks: (1.80 TB/1.64 TiB)
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: [sdb] Write Protect is off
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Aug 27 20:00:57 seashell kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Aug 27 20:00:58 seashell kernel: sd 4:0:0:0: [sdb] Attached SCSI disk

same info from dmesg

[  473.000066] usb 5-1: new high-speed USB device number 3 using ehci-pci
[  473.138349] usb 5-1: New USB device found, idVendor=05e3, idProduct=0718
[  473.138368] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[  473.138373] usb 5-1: Product: USB Storage
[  473.138378] usb 5-1: SerialNumber: 000000000033
[  473.343556] usb-storage 5-1:1.0: USB Mass Storage device detected
[  473.346029] scsi host4: usb-storage 5-1:1.0
[  473.346545] usbcore: registered new interface driver usb-storage
[  473.374508] usbcore: registered new interface driver uas
[  474.356092] scsi 4:0:0:0: Direct-Access     ST3000DM 001-1CH166       0041 PQ: 0 ANSI: 0
[  474.357329] sd 4:0:0:0: Attached scsi generic sg1 type 0
[  474.359585] sd 4:0:0:0: [sdb] 1565565872 512-byte logical blocks: (802 GB/747 GiB)
[  474.360756] sd 4:0:0:0: [sdb] Write Protect is off
[  474.360771] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[  474.364372] sd 4:0:0:0: [sdb] No Caching mode page found
[  474.364383] sd 4:0:0:0: [sdb] Assuming drive cache: write through                                                                                                                            
[  474.391140] sd 4:0:0:0: [sdb] Attached SCSI disk
[  772.601088] usb 5-1: USB disconnect, device number 3
[  776.264081] usb 5-1: new high-speed USB device number 4 using ehci-pci
[  776.397945] usb 5-1: New USB device found, idVendor=05e3, idProduct=0718
[  776.397956] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[  776.397961] usb 5-1: Product: USB Storage
[  776.397967] usb 5-1: SerialNumber: 000000000033
[  776.398804] usb-storage 5-1:1.0: USB Mass Storage device detected
[  776.399925] scsi host4: usb-storage 5-1:1.0
[  777.405092] scsi 4:0:0:0: Direct-Access     USB TO I DE/SATA Device   0041 PQ: 0 ANSI: 0
[  777.406320] sd 4:0:0:0: Attached scsi generic sg1 type 0
[  777.411005] sd 4:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[  777.411019] sd 4:0:0:0: [sdb] 0-byte physical blocks
[  777.412617] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  777.413722] sd 4:0:0:0: [sdb] Asking for cache data failed
[  777.413736] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  777.425996] sd 4:0:0:0: [sdb] Attached SCSI disk
[  835.914467] usb 5-1: USB disconnect, device number 4
[  843.592080] usb 5-1: new high-speed USB device number 5 using ehci-pci
[  843.726269] usb 5-1: New USB device found, idVendor=05e3, idProduct=0718
[  843.726287] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[  843.726291] usb 5-1: Product: USB Storage
[  843.726295] usb 5-1: SerialNumber: 000000000033
[  843.727247] usb-storage 5-1:1.0: USB Mass Storage device detected
[  843.740143] scsi host4: usb-storage 5-1:1.0
[  844.741135] scsi 4:0:0:0: Direct-Access     USB TO I DE/SATA Device   0041 PQ: 0 ANSI: 0
[  844.742501] sd 4:0:0:0: Attached scsi generic sg1 type 0
[  844.743798] sd 4:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[  844.743810] sd 4:0:0:0: [sdb] 0-byte physical blocks
[  844.744923] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  844.749782] sd 4:0:0:0: [sdb] Asking for cache data failed
[  844.749792] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  844.762648] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 1098.803389] usb 5-1: USB disconnect, device number 5
[ 1103.792111] usb 5-1: new high-speed USB device number 7 using ehci-pci
[ 1103.926872] usb 5-1: New USB device found, idVendor=05e3, idProduct=0718
[ 1103.926886] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[ 1103.926891] usb 5-1: Product: USB Storage
[ 1103.926894] usb 5-1: SerialNumber: 000000000033
[ 1103.929287] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 1103.932373] scsi host4: usb-storage 5-1:1.0
[ 1104.934278] scsi 4:0:0:0: Direct-Access     WDC WD40 EFRX-68WT0N0     0041 PQ: 0 ANSI: 0
[ 1104.935519] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 1104.939257] sd 4:0:0:0: [sdb] 3519069872 512-byte logical blocks: (1.80 TB/1.64 TiB)
[ 1104.940374] sd 4:0:0:0: [sdb] Write Protect is off
[ 1104.940388] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 1104.941497] sd 4:0:0:0: [sdb] No Caching mode page found
[ 1104.941510] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 1104.970564] sd 4:0:0:0: [sdb] Attached SCSI disk

Pickle,

Is this the last line in the log?

[ 1104.970564] sd 4:0:0:0: [sdb] Attached SCSI disk

I was hoping to see some errors in the log before

Quote

(issue is that drives seem to drop and the nsa iteself seems unresponsive. Light for hd1 turns orange

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

Yes that is basically the last line. In the dmesg output i actually disconnected and reconnected.

Actually i think might have misunderstood your request. Did you want me to get the logs from NAS? These were logs from attaching the drives to my laptop.
If you wanted to see logs from the NAS I think ill have to do it from a terminal connected to the NAS since the partition type (jbod) wasnt recognized by my linux pc.

Pickle Wrote:
-------------------------------------------------------
> Yes that is basically the last line. In the dmesg
> output i actually disconnected and reconnected.
>
> Actually i think might have misunderstood your
> request. Did you want me to get the logs from NAS?

Yes.

> These were logs from attaching the drives to my
> laptop.

If you mount the drive on your laptop, and assuming it is mounted at /media/sdb1. The kernel log should be in ./var/log

cd /media/sdb1/var/log
ls -l messages

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

bodhi Wrote:
>
> If you mount the drive on your laptop
>

How to mount a JBOD partition?
When i looked at the drives in gparted it couldnt tell what it was.

Edit:

Telnet on the NSA320 worked and I pulled this from dmesg

https://pastebin.com/EkfEJyGz

there are no logs in /var/og



Edited 1 time(s). Last edit at 08/28/2018 07:28PM by Pickle.

i suspect maybe the first drive is starting to die.

This pulled from dmesg over telnet on the nsa320

sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 80 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177917056
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 80 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177917056
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
        0a 9a cc 20 
sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sda, sector 177916960

Edited 1 time(s). Last edit at 08/29/2018 06:29PM by Pickle.

Pickle,

I would recommend going ahead and create a new rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB:
https://forum.doozan.com/read.php?2,12096

You need serial console to make sure you can recover if the system crashes while you install new u-boot. But if it is running long enough for you to complete u-boot installation then you can run with USB rootfs. And then come back to the HDD failing issue.

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

I had another video stop while playing looking at the dmesg log the nas reboot itself

https://pastebin.com/t71SCex9

I have a TTL cable on the way so I can get the serial terminal, ill have to wait until then.

So ive got the TTL serial cable today and I can see the output but i cant get a key press to register to break the boot cycle. Pretty sure I have the right pins connected. Any suggestions for this?

Im using this cable
https://www.amazon.com/gp/product/B014GZTCC6/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

I connected the black gnd to the pin on the right
going left theres a blank space
next i connected the green for TX
next is white for RX



Edited 1 time(s). Last edit at 09/01/2018 02:32PM by Pickle.

Pickle,

          +----+----+           
          |    |    |
+----+----+----+----+----+
|3.3V| TX | RX |    | GND|
+----+----+----+    +----+

Try reverse TX and RX, if seeing no output.

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

Bodhi, seeing output is not the issue. im having issues transmitting to break the boot to get the uboot terminal.



Edited 1 time(s). Last edit at 09/01/2018 04:25PM by Pickle.

Pickle Wrote:
-------------------------------------------------------
> Bodhi, seeing output is not the issue. im having
> issues transmitting to break the boot to get the
> uboot terminal.

Seeing or not seeing output is a confirmation that the pins connection is correct or incorrect.

So now the issue is the connection from your converter TX to the plug RX.

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

Turns out the cable was bad, ive hooked up a bypass and everything worked as expected.

Im not sure if this an issue:

/ # cat /etc/fw_env.config
# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
# NAND example
/dev/mtd1               0x0000          0x20000         0x20000                 4

step 1 i think i saying this ok for nsa3XX, but step 8 is saying it has to match. Can I continue with this setting?

Pickle Wrote:
-------------------------------------------------------
> Turns out the cable was bad, ive hooked up a
> bypass and everything worked as expected.
>
> Im not sure if this an issue:
>
>

> / # cat /etc/fw_env.config
> # MTD device name       Device offset   Env. size 
>      Flash sector size       Number of sectors
> # NAND example
> /dev/mtd1               0x0000          0x20000   
>      0x20000                 4
>

>
> step 1 i think i saying this ok for nsa3XX, but
> step 8 is saying it has to match. Can I continue
> with this setting?

Yes. It is not relevant during u-boot installation.

However, that definition become obsolete after u-boot image is flashed. So in the new rootfs, it should match what the new u-boot expects.

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

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

just rebooted and was greeted by the uboot output:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700)
ZyXEL NSA320 2-Bay Power Media Server

Setting up my usb with the debian rootfs now.

Update:

Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~#

It worked :-)



Edited 1 time(s). Last edit at 09/01/2018 09:28PM by Pickle.

Looks like im not quite there. Eth0 isnt being setup

[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"
Failed to get interface index: No such device

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.
ifup: failed to bring up eth0
failed.

am i missing a firmware?

[    0.018326] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.022792] No ATAGs?

the mac address is set in the env's

Full log:
https://pastebin.com/0qxtLixs


UPDATE:
i had the wrong dtb file (loading pogo instead of nsa320). Now eth0 is there and getting an ip



Edited 1 time(s). Last edit at 09/01/2018 10:24PM by Pickle.

> UPDATE:
> i had the wrong dtb file (loading pogo instead of
> nsa320). Now eth0 is there and getting an ip

Cool! I was going to post that oservation, but you've already figured it out :)

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

and i also upgraded to the latest kernel 4.18.4 and its working

thinking about if i should update the debian to a newer dist. (edit. whoops looks like stretch is the latest)

is there really much benefit to enabling systemd?



Edited 1 time(s). Last edit at 09/01/2018 11:03PM by Pickle.

bodhi thanks for the work and effort you put into providing the binaries and instructions. It really is incredible.

Im running OMV now and just about have everything setup. I need get my backups back onto the new hard drive to replace the one that went bad. I have more power with ssh and omv that i didnt have before.

Only thing I dont think is the same is the LEDS on the front of the box. But i might be ok without that given the email logging options omv has. My NAS is already sending me mails :-)

Regarding LED.

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

Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- 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

# turn on LED

if [ -d /sys/class/leds/status:green:health ]; then
   echo default-on > /sys/class/leds/status:green:health/trigger
   if [ -d /sys/class/leds/status:orange:fault ]; then
      echo none > /sys/class/leds/status:orange:fault/trigger
   fi
   if [ -d /sys/class/leds/status:blue:health ]; then
      echo none > /sys/class/leds/status:blue:health/trigger
   fi
fi
if [ -d /sys/class/leds/dockstar:green:health ]; then
   echo default-on > /sys/class/leds/dockstar:green:health/trigger
   echo none > /sys/class/leds/dockstar:orange:misc/trigger
fi

if [ -d /sys/class/leds/plug:green:health ]; then
   echo default-on > /sys/class/leds/plug:green:health/trigger
   if [ -d /sys/class/leds/plug:red:misc ]; then
      echo none  > /sys/class/leds/plug:red:misc/trigger
   fi
fi

if [ -d /sys/class/leds/power:blue ]; then
   echo default-on  > /sys/class/leds/power:blue/trigger
   ### echo default-on  > /sys/class/leds/otb:blue/trigger
   echo none        > /sys/class/leds/power:red/trigger
fi

if [ -d /sys/class/leds/usb1:blue ]; then
   echo usb-host > /sys/class/leds/usb1\:blue/trigger
fi
if [ -d /sys/class/leds/usb2:blue ]; then
   echo usb-host > /sys/class/leds/usb2\:blue/trigger
fi
if [ -d /sys/class/leds/usb3:blue ]; then
   echo usb-host > /sys/class/leds/usb3\:blue/trigger
fi
if [ -d /sys/class/leds/usb4:blue ]; then
   echo usb-host > /sys/class/leds/usb4\:blue/trigger
fi

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

if [ -d /sys/class/leds/nsa325:green:sata1 ]; then
   echo ide-disk1  > /sys/class/leds/nsa325:green:sata1/trigger
fi

if [ -d /sys/class/leds/nsa325:green:sata2 ]; then
   echo ide-disk2  > /sys/class/leds/nsa325:green:sata2/trigger
fi

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

exit 0

It does not have your box in there. But you can replicate the NSA325 part. See what's in the /sys/class/leds for NSA320:

ls -l /sys/class/leds/

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

thanks that worked replacing 325 with 320.