NSA325v2 can't install Packages, claims drive Full
Kamsvag
Posts: 5 
Freshman Member
Freshman Member
So I can't install packages, even though I just cleared all my storage. It also claims my storage is full if I logon as regular user.
#NAS_November
#NAS_November
0
All Replies
-
I think the /etc/zyxel/storage/sysvol symlink is damaged. Can you open the Telnet backdoor, login over telnet (on Windows you can use PuTTY for that), and post the output of
ls -l /etc/zyxel/storage/sysvol <br>cat /proc/mounts
0 -
Ok, so I've factory restored since last post, still same issue. Here's the output as requested.
I realy appreciate you taking the time looking through the output.
----------------------------------------------------------------------------------------BusyBox v1.17.2 (2016-01-26 18:21:04 CST) built-in shell (ash)Enter 'help' for a list of built-in commands.~ # ls -l /etc/zyxel/storage/sysvollrwxrwxrwx 1 admin everyone 16 Feb 12 2017 2107bd4d -> /i-data/2107bd4ddrwxrwxrwx 1 root root 2048 Nov 30 15:00 admindrwxrwxrwx 1 root root 2048 Nov 30 15:00 musicdrwxrwxrwx 1 root root 2048 Nov 30 15:00 photodrwxrwxrwx 1 root root 2048 Nov 30 15:02 publicdrwxrwxrwx 1 root root 2048 Nov 30 15:00 video~ # cat /proc/mountsrootfs / rootfs rw 0 0/proc /proc proc rw,relatime 0 0/sys /sys sysfs rw,relatime 0 0none /proc/bus/usb usbfs rw,relatime 0 0devpts /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/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/dev/md0 /i-data/44fed8aa ext4 rw,relatime,barrier=0,data=writeback,usrquota 0 0/dev/mtdblock4 /usr/local/apache/htdocs/adv,/res/imdb_poster yaffs2 rw,relatime 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~ #----------------------------------------------------------------------------------------0 -
Right. The symlink points to a not mounted (and maybe not existing?) volume. Don't know how you managed to get that. Did you move an existing volume in another box, or did you delete your volume and create a new?
Anyway, the symlink points to /i-data/2107bd4d, while /proc/mounts says that should be /i-data/44fed8aa.
You can repair that byrm /etc/zyxel/storage/sysvol<br>ln -s /i-data/44fed8aa /etc/zyxel/storage/sysvol<br>reboot<br>
0 -
Ok, so I did as you wrote. Still same issue though...
--------------------------------------------------------------------------------------------------~ # ls -l /etc/zyxel/storage/sysvollrwxrwxrwx 1 root root 16 Dec 1 2017 44fed8aa -> /i-data/44f ed8aadrwxrwxrwx 1 root root 2048 Dec 1 2017 admindrwxrwxrwx 1 root root 2048 Dec 1 2017 musicdrwxrwxrwx 1 root root 2048 Dec 1 2017 photodrwxrwxrwx 1 root root 2048 Dec 1 2017 publicdrwxrwxrwx 1 root root 2048 Dec 1 2017 video~ # cat /proc/mountsrootfs / rootfs rw 0 0/proc /proc proc rw,relatime 0 0/sys /sys sysfs rw,relatime 0 0none /proc/bus/usb usbfs rw,relatime 0 0devpts /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/44fed8aa 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--------------------------------------------------------------------------------------------------0 -
/etc/zyxel/storage/sysvol $ ls -a. .media 44fed8aa music public.. .system admin photo video/etc/zyxel/storage/sysvol $
Seems as .zyxel is missing according to a forum. I'm trying upgrading firmware to see if it will recreate the folder.0 -
I don't have a .zyxel there either. But I do have one in /i-data:
<div>root@NSA325:~# ls -la /i-data/</div><div>drwxrwxrwx 4 root root 0 Jun 24 10:04 .</div><div>drwxr-xr-x 19 root root 0 Nov 30 17:47 ..</div><div>lrwxrwxrwx 1 root root 19 Nov 30 17:47 .system -> /i-data/md0/.system</div><div>lrwxrwxrwx 1 root root 19 Nov 30 17:47 .zyxel -> /i-data/md0/.system</div><div>drwxrwxrwx 41 root root 4096 Nov 30 18:16 3a22b091</div><div>drwxrwxrwx 18 root root 4096 Mar 21 2015 7295626c</div><div>lrwxrwxrwx 1 root root 25 Nov 30 17:46 md0 -> /etc/zyxel/storage/sysvol</div><div>lrwxrwxrwx 1 root root 16 Nov 30 17:46 md1 -> /i-data/7295626c</div><div></div>
The problem is, /i-data is a ramdrive, and so creating anything here won't survive a reboot.
Looking at your mounts I see another problem:<div>/dev/mtdblock4 /usr/local/zy-pkgs yaffs2 rw,relatime 0 0</div><div>/dev/mtdblock4 /etc/zyxel/zy-pkgs yaffs2 rw,relatime 0 0</div><div>/dev/mtdblock4 /usr/local/apache/htdocs/adv,/pkg yaffs2 rw,relatime 0 0</div><div>/dev/mtdblock4 /usr/local/apache/web_framework/data/cache yaffs2 rw,relatime 0 0</div><div>/dev/mtdblock4 /usr/local/apache/web_framework/data/config yaffs2 rw,relatime 0 0</div>
This certainly shouldn't be /dev/mtdblock4. That is a (small!) flash partition.
Can you post the output ofls -la /etc/zyxel/storage/
0 -
I don't dare to edit previous post. Something went wrong with the code tags. I wonder where ZyXEL found this platform. It's a bit, well, unpredictable.0
-
So I removed the .system folder and then I did a looong reset. It took some time for the NAS to reboot, I had to use the NAS Discovery tool and use the installation wizard but now it works.
I wouldn't use this NAS as a primary NAS ever again, it's simply going to be a storage device to serve as backup for my Synology NAS.
0 -
@Kamsvag
I understand you, but I was in the same situation and I was very angry and frustrated with Zyxel in the past, and after I test Syno and Qnap. Syno and Qnap are good but not the bests, and Zyxel is not the worst. After many tests, problem solved or not with all manufacturer.
I think Zyxel has its advantages, it is not a gas plant and works easily with great stability, it is for me its strong point, great stability when it is never restarted !!! You can use it as you wish, but never forget that they all have flaws and advantages :-)0
Guru Member
Ally MemberCategories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 101 Nebula Status and Incidents
- 5.8K Security
- 296 USG FLEX H Series
- 281 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 254 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 76 Security Highlight
