NAS326 suddenly no longer has access and folders gone.
Superdafi
Posts: 7 
Freshman Member
Freshman Member
Good Morning,
a few days ago I couldn't get into the interface. The page starts but login is not accepted. There is no mistake. If I go over it via FTP then all files are gone.
I've already done the rest.
Kind regards, Daniel
#NAS_Jan_2020
#NAS_Jan_2020
0
All Replies
-
Can you get to the interface after the reset? If not, remove the disks, and try again.
0 -
I just did it. The two hard drives removed and a reset performed. I'm coming back into the interfaceNow the message "Volume is down. Please go to Storage Manager for repair." I click OK then I get into the hard disk management. Then see volume in the hard disk array and a red one! (Crashed / Full). But see no way to make a repair.Kind regards, Daniel0
-
Meanwhile you put the disk(s) back I suppose? Can you enable the ssh server (somewhere in control panel) login over ssh (you can use PuTTY for that) and post the output ofcat /proc/mountscat /proc/partitionsdf -hcat /proc/mdstat0
-
This issue was with hard drives:login as: adminadmin@192.168.178.3's password:BusyBox v1.19.4 (2019-09-04 14:02:35 CST) built-in shell (ash)Enter 'help' for a list of built-in commands.~ $ cat /proc/mountsrootfs / rootfs rw 0 0/proc /proc proc rw,relatime 0 0/sys /sys sysfs rw,relatime 0 0devpts /dev/pts devpts rw,relatime,mode=600 0 0ubi4:ubi_rootfs1 /firmware/mnt/nand ubifs ro,relatime 0 0/dev/md0 /firmware/mnt/sysdisk ext4 ro,relatime,data=ordered 0 0/dev/loop0 /ram_bin ext2 ro,relatime 0 0/dev/loop0 /usr ext2 ro,relatime 0 0/dev/loop0 /lib/security ext2 ro,relatime 0 0/dev/loop0 /lib/modules ext2 ro,relatime 0 0/dev/loop0 /lib/locale ext2 ro,relatime 0 0/dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0/dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0ubi2:ubi_config /etc/zyxel ubifs rw,relatime 0 0configfs /sys/kernel/config configfs rw,relatime 0 0~ $ cat /proc/partitionsmajor minor #blocks name7 0 146432 loop031 0 2048 mtdblock031 1 2048 mtdblock131 2 10240 mtdblock231 3 15360 mtdblock331 4 108544 mtdblock431 5 15360 mtdblock531 6 108544 mtdblock68 0 1953514584 sda8 1 1998848 sda18 2 1999872 sda28 3 1949514752 sda38 16 1953514584 sdb8 17 1998848 sdb18 18 1999872 sdb28 19 1949514752 sdb39 0 1997760 md09 1 1998784 md19 2 3899029376 md2253 0 102400 dm-0253 1 3898925056 dm-1~ $ df -hFilesystem Size Used Available Use% Mounted onubi4:ubi_rootfs1 88.1M 48.2M 35.4M 58% /firmware/mnt/nand/dev/md0 1.8G 145.9M 1.6G 8% /firmware/mnt/sysdisk/dev/loop0 138.5M 121.8M 16.7M 88% /ram_bin/dev/loop0 138.5M 121.8M 16.7M 88% /usr/dev/loop0 138.5M 121.8M 16.7M 88% /lib/security/dev/loop0 138.5M 121.8M 16.7M 88% /lib/modules/dev/loop0 138.5M 121.8M 16.7M 88% /lib/locale/dev/ram0 5.0M 4.0K 5.0M 0% /tmp/tmpfs/dev/ram0 5.0M 4.0K 5.0M 0% /usr/local/etcubi2:ubi_config 2.2M 132.0K 2.0M 6% /etc/zyxel~ $ cat /proc/mdstatPersonalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]md2 : active linear sda3[0] sdb3[1]3899029376 blocks super 1.2 64k roundingmd1 : active raid1 sda2[2] sdb2[1]1998784 blocks super 1.2 [2/2] [UU]md0 : active raid1 sda1[2] sdb1[1]1997760 blocks super 1.2 [2/2] [UU]unused devices: <none>~ $0
-
This edition is without hard drives:login as: adminadmin@192.168.178.3's password:BusyBox v1.19.4 (2019-09-04 14:02:35 CST) built-in shell (ash)Enter 'help' for a list of built-in commands.~ $ cat /proc/mountsrootfs / rootfs rw 0 0/proc /proc proc rw,relatime 0 0/sys /sys sysfs rw,relatime 0 0devpts /dev/pts devpts rw,relatime,mode=600 0 0ubi4:ubi_rootfs1 /firmware/mnt/nand ubifs ro,relatime 0 0none /firmware/mnt/sysdisk ramfs ro,relatime 0 0/dev/loop0 /ram_bin ext2 ro,relatime 0 0/dev/loop0 /usr ext2 ro,relatime 0 0/dev/loop0 /lib/security ext2 ro,relatime 0 0/dev/loop0 /lib/modules ext2 ro,relatime 0 0/dev/loop0 /lib/locale ext2 ro,relatime 0 0/dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0/dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0ubi2:ubi_config /etc/zyxel ubifs rw,relatime 0 0configfs /sys/kernel/config configfs rw,relatime 0 0~ $ cat /proc/partitionsmajor minor #blocks name7 0 146432 loop031 0 2048 mtdblock031 1 2048 mtdblock131 2 10240 mtdblock231 3 15360 mtdblock331 4 108544 mtdblock431 5 15360 mtdblock531 6 108544 mtdblock6~ $ df -hFilesystem Size Used Available Use% Mounted onubi4:ubi_rootfs1 88.1M 48.2M 35.4M 58% /firmware/mnt/nand/dev/loop0 138.5M 121.8M 16.7M 88% /ram_bin/dev/loop0 138.5M 121.8M 16.7M 88% /usr/dev/loop0 138.5M 121.8M 16.7M 88% /lib/security/dev/loop0 138.5M 121.8M 16.7M 88% /lib/modules/dev/loop0 138.5M 121.8M 16.7M 88% /lib/locale/dev/ram0 5.0M 4.0K 5.0M 0% /tmp/tmpfs/dev/ram0 5.0M 4.0K 5.0M 0% /usr/local/etcubi2:ubi_config 2.2M 136.0K 2.0M 6% /etc/zyxel~ $ cat /proc/mdstatPersonalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]unused devices: <none>~ $~ $~ $~ $~ $~ $~ $~ $ BusyBox v1.19.4 (2019-09-04 14:02:35 CST) built-in shell (ash)-sh: syntax error: unexpected "("~ $ Enter 'help' for a list of built-in commands.-sh: Enter: not found~ $~ $ ~ $ cat /proc/mounts~ $ df -hFilesystem Size Used Available Use% Mounted onubi4:ubi_rootfs1 88.1M 48.2M 35.4M 58% /firmware/mnt/nand/dev/loop0 138.5M 121.8M 16.7M 88% /ram_bin/dev/loop0 138.5M 121.8M 16.7M 88% /usr/dev/loop0 138.5M 121.8M 16.7M 88% /lib/security/dev/loop0 138.5M 121.8M 16.7M 88% /lib/modules/dev/loop0 138.5M 121.8M 16.7M 88% /lib/locale/dev/ram0 5.0M 4.0K 5.0M 0% /tmp/tmpfs/dev/ram0 5.0M 4.0K 5.0M 0% /usr/local/etcubi2:ubi_config 2.2M 136.0K 2.0M 6% /etc/zyxel~ $ cat /proc/mdstatPersonalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]unused devices: <none>-sh: /home/shares: Permission denied~ $ rootfs / rootfs rw 0 0-sh: rootfs: not found~ $ /proc /proc proc rw,relatime 0 0-sh: /proc: Permission denied~ $ /sys /sys sysfs rw,relatime 0 0-sh: /sys: Permission denied~ $ devpts /dev/pts devpts rw,relatime,mode=600 0 0-sh: devpts: not found~ $ ubi4:ubi_rootfs1 /firmware/mnt/nand ubifs ro,relatime 0 0-sh: ubi4:ubi_rootfs1: not found~ $ none /firmware/mnt/sysdisk ramfs ro,relatime 0 0-sh: none: not found~ $ /dev/loop0 /ram_bin ext2 ro,relatime 0 0-sh: /dev/loop0: Permission denied~ $ /dev/loop0 /usr ext2 ro,relatime 0 0-sh: /dev/loop0: Permission denied~ $ /dev/loop0 /lib/security ext2 ro,relatime 0 0-sh: /dev/loop0: Permission denied~ $ /dev/loop0 /lib/modules ext2 ro,relatime 0 0-sh: /dev/loop0: Permission denied~ $ /dev/loop0 /lib/locale ext2 ro,relatime 0 0-sh: /dev/loop0: Permission denied~ $ /dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0-sh: /dev/ram0: Permission denied~ $ /dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0-sh: /dev/ram0: Permission denied~ $ ubi2:ubi_config /etc/zyxel ubifs rw,relatime 0 0-sh: ubi2:ubi_config: not found~ $ configfs /sys/kernel/config configfs rw,relatime 0 0-sh: configfs: not found~ $ ~ $ cat /proc/partitions-sh: /home/shares: Permission denied~ $ major minor #blocks name-sh: major: not found~ $~ $ 7 0 146432 loop0-sh: 7: not found~ $ 31 0 2048 mtdblock0-sh: 31: not found~ $ 31 1 2048 mtdblock1-sh: 31: not found~ $ 31 2 10240 mtdblock2-sh: 31: not found~ $ 31 3 15360 mtdblock3-sh: 31: not found~ $ 31 4 108544 mtdblock4-sh: 31: not found~ $ 31 5 15360 mtdblock5-sh: 31: not found~ $ 31 6 108544 mtdblock6-sh: 31: not found~ $ ~ $ df -h-sh: /home/shares: Permission denied~ $ Filesystem Size Used Available Use% Mounted on-sh: Filesystem: not found~ $ ubi4:ubi_rootfs1 88.1M 48.2M 35.4M 58% /firmware/mnt/nand-sh: ubi4:ubi_rootfs1: not found~ $ /dev/loop0 138.5M 121.8M 16.7M 88% /ram_bin-sh: /dev/loop0: Permission denied~ $ /dev/loop0 138.5M 121.8M 16.7M 88% /usr-sh: /dev/loop0: Permission denied~ $ /dev/loop0 138.5M 121.8M 16.7M 88% /lib/security-sh: /dev/loop0: Permission denied~ $ /dev/loop0 138.5M 121.8M 16.7M 88% /lib/modules-sh: /dev/loop0: Permission denied~ $ /dev/loop0 138.5M 121.8M 16.7M 88% /lib/locale-sh: /dev/loop0: Permission denied~ $ /dev/ram0 5.0M 4.0K 5.0M 0% /tmp/tmpfs-sh: /dev/ram0: Permission denied~ $ /dev/ram0 5.0M 4.0K 5.0M 0% /usr/local/etc-sh: /dev/ram0: Permission denied~ $ ubi2:ubi_config 2.2M 136.0K 2.0M 6% /etc/zyxel-sh: ubi2:ubi_config: not found~ $ ~ $ cat /proc/mdstat-sh: /home/shares: Permission denied~ $ Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]-sh: Personalities: not found~ $ unused devices: <none>-sh: syntax error: unexpected newline~ $~ $0
-
Your data array is assembledmd2 : active linear sda3[0] sdb3[1]3899029376 blocks super 1.2 64k roundingbut not mounted. So I guess there is some filesystem error. You can try to repair that.sue2fsck /dev/md2
0 -
BusyBox v1.19.4 (2019-09-04 14:02:35 CST) built-in shell (ash)Enter 'help' for a list of built-in commands.~ # e2fsck /dev/md2e2fsck 1.42.12 (29-Aug-2014)/dev/md2 is in use.e2fsck: Cannot continue, aborting.~ #0
-
How do I get the data on the two hard drives that were running in raid mode? The method of repair doesn't seem to work. I used this NAS326 to reliably back up my data.
0 -
/dev/md2 is in use.Can you check if meanwhile the device is mounted? (cat /proc/mounts). If not find which process is using it.lsof | grep /dev/md2How do I get the data on the two hard drives that were running in raid mode?By assembling, repairing & mounting the array.I used this NAS326 to reliably back up my data.In that case you made a strange decision for your volume. A linear array is almost the most vulnerable for hardware errors.
0 -
~ # e2fsck /dev/md2e2fsck 1.42.12 (29-Aug-2014)/dev/md2 is in use.e2fsck: Cannot continue, aborting.~ #~ # lsof | grep /dev/md2~ #0
Guru Member
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 277 USG FLEX H Series
- 277 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 395 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 75 Security Highlight
