NAS540 Tried to boot Debian from USB and now constant beeping

gsshelton
gsshelton Posts: 21  Freshman Member
First Anniversary Friend Collector First Comment
I've tried reinstalling the firmware (I used the latest from this link: https://mysupport.zyxel.com/hc/en-us/articles/360012549559--NSA-NAS-Disclaimer-about-current-firmware-patch-pertaining-to-CVE-2020-9054), but it doesn't seem to be reading the usb drive. I tried it in all three usb ports and an SD card in the card slot). I've also tried factory reset several times.

I have a serial connection and here is the beginning output.

uloader 2011.06.0 (May 20 2014 - 16:36:41)

Board: Mindspeed C2000
c2k_spi_probe

Copying Barebox from SPI Flash(bootopt=0)
BB Copying Done
## Starting Barebox at 0x01000000 ...

barebox 2011.06.0-svn44305-dirty6 (Aug 28 2014 - 22:25:22)

Board: Mindspeed C2000
c2k_spi_probe
c2k_otp_probe.
cbus_baseaddr: 9c000000, ddr_baseaddr: 03800000, ddr_phys_baseaddr: 03800000
class init complete
tmu init complete
bmu1 init: done
bmu2 init: done
util init complete
GPI1 init complete
GPI2 init complete
HGPI init complete
HIF rx desc: base_va: 03e80000, base_pa: 03e80000
HIF tx desc: base_va: 03e80400, base_pa: 03e80400
HIF init complete
bmu1 enabled
bmu2 enabled
pfe_hw_init: done
pfe_firmware_init
pfe_load_elf
pfe_load_elf no of sections: 10
pfe_firmware_init: class firmware loaded
pfe_load_elf
pfe_load_elf no of sections: 10
pfe_firmware_init: tmu firmware loaded
pfe_load_elf
pfe_load_elf no of sections: 14
pfe_firmware_init: util firmware loaded
eth_port: 0
NAS540_phy_reg_setting[eth_port].phyaddr: 0x4
miidev_restart_aneg for PHY4
eth_port: 1
NAS540_phy_reg_setting[eth_port].phyaddr: 0x6
miidev_restart_aneg for PHY6
cfi_probe: cfi_flash base: 0xc0000000 size: 0x04000000
## Unknown FLASH on Bank at 0xc0000000 - Size = 0x00000000 = 0 MB
bootopt = 0x0
Using ENV from SPI Flash.
nand_probe: comcerto_nand base: 0xc8300000 size: 0x256 MB
NAND device: Manufacturer ID: 0x01, Chip ID: 0xda (AMD NAND 256MiB 3,3V 8-bit), page size: 2048, OOB size: 64
Using default values 
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad block table written to 0x0ffe0000, version 0x01
Bad block table written to 0x0ffc0000, version 0x01
Malloc space: 0x00600000 -> 0x01000000 (size 10 MB)
Stack space : 0x005f8000 -> 0x00600000 (size 32 kB)
running /env/bin/init...
Unknown command 'export' - try 'help'

Hit any key to stop autoboot:  1
booting kernel of type uimage from /dev/nand0.kernel2.bb
   Verifying Checksum ... OK
   Image Name:   Linux-3.2.54
   Created:      2020-06-04   2:17:01 UTC
   Image Type:   <NULL> <NULL> <NULL> (<NULL>)
   Data Size:    7430736 Bytes =  7.1 MB
   Load Address: 0f008000
   Entry Point:  0f008000
OK

Starting kernel ...

commandline: console=ttyS0,115200n8, init=/etc/preinit pcie_gen1_only=yes  mac_addr=,, ip=dhcp root=ubi0:rootfs ubi.mtd=2,2048 rootfstype=ubifs rw noinitrd mtdparts=spi0.0:256k(uloader)ro,512k(barebox)ro,256k(env);comcertonand:10M(config),10M(kernel1),110M(rootfs1),10M(kernel2),110M(rootfs2),-(reserved) usb3_internal_clk=yes
arch_number: 1094
Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Linux version 3.2.54 (root@twsvnnt01652-01) (gcc version 4.8.5 20150209 (prerelease) (crosstool-NG 1.21.0) ) #1 SMP Thu Jun 4 10:16:59 CST 2020
[    0.000000] CPU: ARMv7 Processor [412fc091] revision 1 (ARMv7), cr=50c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Comcerto 2000 EVM
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] Comcerto: zone_dma mapping size=2c00000 type=b
[    0.000000] PERCPU: Embedded 8 pages/cpu @85268000 s9504 r8192 d15072 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 254976
[    0.000000] Kernel command line: console=ttyS0,115200n8, init=/etc/preinit pcie_gen1_only=yes  mac_addr=,, ip=dhcp root=ubi0:rootfs ubi.mtd=2,2048 rootfstype=ubifs rw noinitrd mtdparts=spi0.0:256k(uloader)ro,512k(barebox)ro,256k(env);comcertonand:10M(config),10M(kernel1),110M(rootfs1),10M(kernel2),110M(rootfs2),-(reserved) usb3_internal_clk=yes
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 44MB 960MB = 1004MB total
[    0.000000] Memory: 1008396k/1008396k available, 40180k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff30000 - 0xfffe0000   ( 704 kB)
[    0.000000]     vmalloc : 0xc0800000 - 0xf0000000   ( 760 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
[    0.000000]     modules : 0x83600000 - 0x84000000   (  10 MB)
[    0.000000]       .text : 0x84008000 - 0x8468b460   (6670 kB)
[    0.000000]       .init : 0x8468c000 - 0x849b7520   (3246 kB)
[    0.000000]       .data : 0x849b8000 - 0x84a00bb0   ( 291 kB)
[    0.000000]        .bss : 0x84a00bd4 - 0x84a61218   


  File "<string>", line 1, in <module>
  File "/home/release-build/NAS540/521AATB6B2/sysapps/web_framework/build/models/network_common.py.pre", line 158, in check_and_write_routing
ValueError: need more than 2 values to unpack
[21/Feb/2021:10:17:59]  [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[21/Feb/2021:10:17:59]  [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
2021/02/21 10:17:59 [ipnotify] : rth->rta_type = 1, IFA_ADDRESS=1, IFA_LOCAL=2
2021/02/21 10:17:59 [ipnotify] : detect a delete IP and execute /sbin/ipnotify_exec.sh
[ipnotify_exec.sh]: ******** detect egiga1 delete IP********
2021/02/21 10:17:59 [ipnotify] : rth->rta_type = 1, IFA_ADDRESS=1, IFA_LOCAL=2
2021/02/21 10:17:59 [ipnotify] : detect a delete IP and execute /sbin/ipnotify_exec.sh
[ipnotify_exec.sh]: ******** detect egiga0 delete IP********
killall: httpd: no process killed
loop link has been checked. Do nothing
Feb 21 10:18:00 NAS540 ifplugd(egiga0): started: BusyBox v1.19.4 (2020-06-04 10:09:11 CST)
Feb 21 10:18:00 NAS540 ifplugd(egiga0): using SIOCETHTOOL detection mode
Feb 21 10:18:00 NAS540 ifplugd(egiga0): link is down
Feb 21 10:18:00 NAS540 ifplugd(egiga1): started: BusyBox v1.19.4 (2020-06-04 10:09:11 CST)
Feb 21 10:18:00 NAS540 ifplugd(egiga1): using SIOCETHTOOL detection mode
Feb 21 10:18:00 NAS540 ifplugd(egiga1): link is down
killall: httpd: no process killed
[21/Feb/2021:10:18:01]  [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[21/Feb/2021:10:18:01]  [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
the interface egiga0 is down or unusable
[21/Feb/2021:10:18:01]  [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[21/Feb/2021:10:18:01]  [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/release-build/NAS540/521AATB6B2/sysapps/web_framework/build/models/network_common.py.pre", line 158, in check_and_write_routing
ValueError: need more than 2 values to unpack
[21/Feb/2021:10:18:02]  [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[21/Feb/2021:10:18:02]  [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
the interface egiga0 is down or unusable
[21/Feb/2021:10:18:02]  [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[21/Feb/2021:10:18:02]  [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/release-build/NAS540/521AATB6B2/sysapps/web_framework/build/models/network_common.py.pre", line 158, in check_and_write_routing
ValueError: need more than 2 values to unpack
[   73.743718] bz time = 1f
[   73.746265] bz status = 3
[   73.748890] bz_timer_status = 0
[   73.752066] start buzzer
Feb 21 10:18:02 NAS540 httpd[3680]: [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
Feb 21 10:18:02 NAS540 httpd[3680]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Feb 21 10:18:02 NAS540 httpd[3680]: [warn] RSA server certificate CommonName (CN) `NAS540' does NOT match server name!?
Feb 21 10:18:02 NAS540 httpd[3680]: [error] mod_auth_zyxel: initialized.
===> Stopping crond ...
Feb 21 10:18:04 NAS540 httpd[3681]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Feb 21 10:18:04 NAS540 httpd[3681]: [warn] RSA server certificate CommonName (CN) `NAS540' does NOT match server name!?
Feb 21 10:18:04 NAS540 httpd[3681]: [error] mod_auth_zyxel: initialized.
===> Starting crond ...
 core_checksum : 12db79e8f9a45e7e8e210507438a007c
 fwversion : V5.21(AATB.6)C0
 img_checksum : da8a9b4322d84676a9b10344bea84562
 modelid : B103
 revision : 51201
 romfile_checksum : AFB9
 zld_checksum : e92bdb96634160bf3b7b4aea2c931e35
check time zone and modify time zone
[   77.726922] bz time = 1
[   77.729379] bz status = 1
[   77.732048] bz_timer_status = 1
led_state_map_addr = 406

«1

All Replies

  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    This bootlog is far from complete, I think a whole minute is missing, and I don't see why it is beeping. AFAIK there are 2 beeping conditions, a raid array got degraded, or the fan doesn't have the desired rpm.
    Did you detach the fan to get serial access?
  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    edited February 2021
    Thanks for the quick response! I feel like an idiot, yes the fan was disconnected! I was also getting errors because I didn't put the riser card for the sata. 

    On reboot, I also get a single beep at the end.

    Here is the full output from minicom https://pastebin.com/a6N9a8fW

    I've tried putting the firmware .bin on a fat USB in all three of the ports and it doesn't seem to see it. Is it possible to update the firmware this way? 

    ipc_send:54: send IPC event OK
    Syntax error on line 24 of /etc/service_conf/httpd_zld.conf:
    Port must be specified
    [  522.300489] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    [  526.770484] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
    [  531.240501] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?


    Thanks again for all you're help and all the work you've put in!
  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    Is there a way to suppress the error messages coming from the NAS? I'm trying to enter commands but the error messages come in and make it hard to enter the commands. I opened and was trying to edit the httpd_xld.conf file from the error, but it's virtually impossible to move around in the file.
  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Is it possible to update the firmware this way?
    Which way? By simply putting a .bin file on an USB stick? No. But you can try the rescuestick:

    Is there a way to suppress the error messages coming from the NAS?
    On serial? Not that I'm aware of. Can't you start the telnet daemon, and use that?
  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    Thanks for replying. Forgive my ignorance with linux. 

    I had already tried the rescuestick and just now tried it again. It looks like it's not reading from usb. 

    I tried starting telnet with telnetd, but I get a connection refused.

    I'm at a loss as what to do next.


  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Did you flash another kernel? This one seems to have the right initramfs, but I can't correlate it's compilation date to one the firmware revisions.

    Further, have you tried all usb ports with the rescue stick? Your error messages seem all to mention only one port of a hub.

    I tried starting telnet with telnetd, but I get a connection refused.
    On which IP? Does the box request&get an IP? If not, you can manually assign one. First run 'ifconfig -a' to see the names of the ethernet interfaces, choose one, and assign an IP:
    ifconfig <interface> address <ip-address> netmask 255.255.255.0 up

  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    edited February 2021
    I got it to get an ip address and was able to get in via telnet. I'm in BusyBox but I don't know what to do next.

    I tried the rescue key in all three usb and I put the rescuekey on an SD card and tried it there.
  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    I've looked at the httpd_zld.conf file that is causing the error and there is a httpd_zld.conf.old file. On lineS 24, 25 & 26 of the .old has listen 80, listen 443, listen 8082, but the current file line 24 has listen none and 25 has listen 8082 and nothing more. But this must just be a symptom of another issue. I change the file permissions and edit the file, but on reboot the same file causing the error has the same lines as before my edits.
  • Mijzelf
    Mijzelf Posts: 2,598  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    The http_zld.conf is created dynamically as function of the configuration. Possibly your configuration is broken. You can try to erase the config partition by executing
    /usr/local/btn/reset_and_reboot.sh

  • gsshelton
    gsshelton Posts: 21  Freshman Member
    First Anniversary Friend Collector First Comment
    That did correct the http_zld.conf error! That's awesome, thank you!

    It now boots without that error, but I can't access it via webpage. I can see the samba and afp shares on my network. They both take the admin/1234 user/password, tries to connect and then errors to connection failed.

    I've attached the output from a reboot.

Consumer Product Help Center