NSA325 - no volume, no packages

bobby
bobby Posts: 4  Freshman Member
edited October 2019 in Personal Cloud Storage
I had a power failure and had te reset my NSA325 in order to get it back on the network. I had entware setup previously.

Now there seems something wrong. 
When I check for firmware update the popup  says: Connection to the server hung.
There are no packages on the packages tab and the buttons are greyed out. The message bar at the bottom says: This feature is not available for there is no volume.

The volume section mentions my two disks (jbod), 70% used, message bar at the bottom says: Ready.

In the log section I see 13 comments. The last one, from today reads:
Volume is FULL. It is recommended to reserve freespace for operating system to work properly.

I would like to get my system back to where is was:
- running entware
- sharing my files on the network through nfs
- etc.

I think there is something wrong, but don't know where to start.

Regards, Bobby


#NAS_Oct_2019

All Replies

  • Mijzelf
    Mijzelf Posts: 1,717  Guru Member
    Start with the Telnet Backdoor. If you have managed to get access over telnet, post the output of
    ls -l /i-data/<br>ls -l /etc/zyxel/storage/<br>cat /proc/mounts
  • bobby
    bobby Posts: 4  Freshman Member
    Hello Mijzelf,

    Thank you for the quick reply. Here are the outputs.

    ~ # ls -l /i-data/
    drwxrwxrwx   21 root     root          4096 Sep  4 09:14 58e75e09
    lrwxrwxrwx    1 root     root            25 Sep 13 18:30 md0 -> /etc/zyxel/storage/sysvol


    ~ # ls -l /etc/zyxel/storage/
    -rw-rw-rw-    1 root     root            51 Sep  1 07:10 mduuid.table
    drwxr-xr-x    1 admin    everyone      2048 Oct 13  2015 sysvol


    ~ # cat /proc/mounts 
    rootfs / rootfs rw 0 0
    /proc /proc proc rw,relatime 0 0
    /sys /sys sysfs rw,relatime 0 0
    none /proc/bus/usb usbfs rw,relatime 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    /dev/mtdblock8 /zyxel/mnt/nand yaffs2 ro,relatime 0 0
    /dev/sda1 /zyxel/mnt/sysdisk ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /ram_bin ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /usr ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/security ext2 ro,relatime,errors=continue 0 0
    /dev/loop0 /lib/modules ext2 ro,relatime,errors=continue 0 0
    /dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0
    /dev/ram0 /usr/local/var tmpfs rw,relatime,size=5120k 0 0
    /dev/mtdblock4 /etc/zyxel yaffs2 rw,relatime 0 0
    /dev/md0 /i-data/58e75e09 ext4 rw,noatime,barrier=0,data=writeback,usrquota 0 0
    /dev/mtdblock4 /usr/local/zy-pkgs yaffs2 rw,relatime 0 0
    /dev/mtdblock4 /etc/zyxel/zy-pkgs yaffs2 rw,relatime 0 0
    /dev/mtdblock4 /usr/local/apache/htdocs/adv,/pkg yaffs2 rw,relatime 0 0
    /dev/mtdblock4 /usr/local/apache/web_framework/data/cache yaffs2 rw,relatime 0 0
    /dev/mtdblock4 /usr/local/apache/web_framework/data/config yaffs2 rw,relatime 0 0

  • Mijzelf
    Mijzelf Posts: 1,717  Guru Member
    /etc/zyxel/storage/sysvol is supposed to be a symlink to the volume. In your case it's a directory. /etc/zyxel/ is the mountpoint of a flash partition, so I think your error
    Volume is FULL. It is recommended to reserve freespace for operating system to work properly.
    is caused because that directory is now treated as volume, and the flash partition is tiny.

    Solution:
    <div>rm -rf /etc/zyxel/storage/sysvol</div><div>ln -s /i-data/58e75e09 /etc/zyxel/storage/sysvol</div><div>reboot</div>





  • bobby
    bobby Posts: 4  Freshman Member
    rm -rf /etc/zyxel/storage/sysvol
    took a while to complete, but no error.
    
    ln -s /i-data/58e75e09 /etc/zyxel/storage/sysvol
    reboot
    
    After reboot the device is not on the network anymore. It hasn't receiver an IP from my gateway. Tried manual reboot with the button on the device, but same result.
    
    Should I reset it, or would I then be back where I was?
  • Mijzelf
    Mijzelf Posts: 1,717  Guru Member
    Don't know. How did you reset it last time? Keeping the button pressed until the 3th beep? If not, it was no full reset. AFAIK a full reset puts a new filesystem on the flash, and then I wouldn't expect a timestamp in 2015 on the sysvol symlink.

    Anyway, when the device doesn't show up in network you don't have much choice, do you? Unless you have a suitable serial cable.
  • bobby
    bobby Posts: 4  Freshman Member
    Well a couple of extra resets (one beep) worked!

    Thanks!