ASUSTOR NAS are not a good choice

Share your awesome tips and tricks here.

Moderator: Lillian.W@AST

nissl
Posts: 25
youtube meble na wymiar Warszawa
Joined: Sat Jan 18, 2014 10:48 pm

ASUSTOR NAS are not a good choice

Post by nissl »

Hi Folks,

i'm suffering from Data loss the third time in a short Period.
Running a Asustor 10 Bay NAS with 8x10 TB Disks in RAID5.
After a Reboot the RAID is no longer accessible by the Storage Manager. The Shares are not mounted. Data is still there but no longer accessible.
This NAS is crap!!!!!! And i'm tired of "hacking" it with SSH and shovel the data to USB Disks to rescue the important part.
This is horrible. I'm so ****ing angry right now.
Seriously hoping the tech support will help me. But no much fate in this term.

Hands Off this CRAP. Better buy Synology or something else!!!
User avatar
orion
Posts: 3482
Joined: Wed May 29, 2013 11:09 am

Re: ASUSTOR NAS are not a good choice

Post by orion »

What's your NAS model?
After a Reboot the RAID is no longer accessible by the Storage Manager. The Shares are not mounted. Data is still there but no longer accessible.
Not sure what you mean. "Data is still there" means your volume is still mounted, isn't it? Can you post pictures about Storage manager -> Volume and disk? I guess there might be 2 disk failures at the same time.
nissl
Posts: 25
Joined: Sat Jan 18, 2014 10:48 pm

Re: ASUSTOR NAS are not a good choice

Post by nissl »

Hi

no, no disk failures at all. It is just a Software issue.
I had this problem many time before. With SSH and mdadm hacks im able to mount the Volume and access the data (so it is still there and alive) but not accessible in terms of the NAS it self without manual work.

https://ibb.co/sWY8KMc

Also its inconvenient running the NAS in this state.
User avatar
orion
Posts: 3482
Joined: Wed May 29, 2013 11:09 am

Re: ASUSTOR NAS are not a good choice

Post by orion »

Sounds very weird. So, I believe you checked "Drive" status and make sure the states being good.
I have no idea why you can manually mount volume, but ADM software does not...
Can you post info about dmesg? (the output of command dmesg) There might be some clues. On the other hand, I think you should send a support request to asustor directly at the same time.
nissl
Posts: 25
Joined: Sat Jan 18, 2014 10:48 pm

Re: ASUSTOR NAS are not a good choice

Post by nissl »

Ticket is open. But as mentioned i have near to no fate that the reply will be helpful in any way. I contacted them for a similar issue already before.

Thanks for your interest in this topic:
https://pastebin.com/b3RWMGqs
this is dmesg

You can do the following when experiencing such problems:

Code: Select all

root@Caithleen:~ # mdadm --assemble --scan
mdadm: /dev/md/AS6210T-3B35:1 has been started with 8 drives.
root@Caithleen:~ # mkdir /volume1
root@Caithleen:~ # mount /dev/md127 /volume1
root@Caithleen:~ # ls /volume1/
Backups       Misc          Share         Veeam_Backup  home
Filme         Serien        Share_Public  Web           serien_ENG
After these commands also the SMB access is OK. But this is not convenience and i just don't wanna run the nas in this state.

Also this has no effect on the ADM. ADM Has no access to configuration, Storage, first nothing.

:(

Would you mind posting me the output of the command "mount" on your NAS ?
I'm just wondering if maybe the writable part of the "firmware" is no longer mountet on mine.
My mount looks like this:

Code: Select all

root@Caithleen:~ # mount
rootfs on / type rootfs (rw,size=1950660k,nr_inodes=487665)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/md0 on /volume0 type ext4 (rw,relatime,data=ordered)
/dev/loop0 on /share type ext4 (rw,relatime,block_validity,delalloc,barrier,user_xattr)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/md127 on /volume1 type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/base)
User avatar
orion
Posts: 3482
Joined: Wed May 29, 2013 11:09 am

Re: ASUSTOR NAS are not a good choice

Post by orion »

It looks like that md1 is stopped without any reasons!!

Code: Select all

[   24.862293] md/raid:md1: device sdd4 operational as raid disk 0
[   24.868460] md/raid:md1: device sde4 operational as raid disk 7
[   24.874642] md/raid:md1: device sdf4 operational as raid disk 6
[   24.880825] md/raid:md1: device sdc4 operational as raid disk 5
[   24.886977] md/raid:md1: device sdg4 operational as raid disk 4
[   24.893142] md/raid:md1: device sdh4 operational as raid disk 3
[   24.899262] md/raid:md1: device sda4 operational as raid disk 2
[   24.905489] md/raid:md1: device sdb4 operational as raid disk 1
[   24.949240] md/raid:md1: raid level 5 active with 8 out of 8 devices, algorithm 2
[   24.957120] md1: detected capacity change from 0 to 69972928757760
[   25.101852] md1: detected capacity change from 69972928757760 to 0
[   25.108306] md: md1 stopped.
Can you post the command output of "cat /proc/mdstat"?

Here is my mount status:

Code: Select all

rootfs on / type rootfs (rw,size=1863592k,nr_inodes=465898)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/md0 on /volume0 type ext4 (rw,relatime,data=ordered)
/dev/loop0 on /share type ext4 (rw,relatime,block_validity,delalloc,barrier,user_xattr)
/dev/md1 on /volume1 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/home type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/User Homes type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Public type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Web type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Download type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/PhotoGallery type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/UrBackup type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Video type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Plex type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Surveillance type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/test2 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Media type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Music type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/test1 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md1 on /share/Docker type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md2 on /volume2 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/md2 on /share/dir_vol2 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
/dev/md1 on /volume1/.@plugins/AppCentral/docker-ce/docker_lib type ext4 (rw,relatime,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.group)
overlay on /volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/ca83012e6321b1acfc628670ad967c86815107edd354c22d3d94002e8fd8bb7c/merged type overlay (rw,relatime,lowerdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/5SFO552265AEFEBMMLQERWA7SK:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/OIEUZCGUBRH64J55CFJMWNQDRV:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/WISAI3HFIQNKA5ZO37HJ67X5MN,upperdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/ca83012e6321b1acfc628670ad967c86815107edd354c22d3d94002e8fd8bb7c/diff,workdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/ca83012e6321b1acfc628670ad967c86815107edd354c22d3d94002e8fd8bb7c/work)
nsfs on /var/run/docker/netns/7602a4e93693 type nsfs (rw)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,relatime,name=systemd)
nsfs on /var/run/docker/netns/default type nsfs (rw)
overlay on /volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eac0309013bd772f30b78eabc0606e374fc03dcaa314b58d3fa447cce4df0ccf/merged type overlay (rw,relatime,lowerdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/T2V7CCBSCYEDI6IALWY46OJSGA:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/MLNQCZFBX3N2L5OUNDWOX2IYT2:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/KVOYYWQ2BSJSCXDOMSH7UTQIRN:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/IBOALSERTUFAAEON7VFQU7DP5B:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/ZY3NVUPYPDAJEMU5CJKK2DT4YY:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/2YT4Y4OEKTAEAYS6GSKTCISHIT:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/77NMHLPI2VDUOPZNWLIF2LHHLW:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/Z4S6JR3RIZ24YEBMFS44FOZZ2T:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/DJCGDL3V742UDBMUDEZSOZNXW5:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/5CUCBTU2PKO5H476IRFD57L5RF:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/XLRCD6I7OYZMRT53P2SJMVXFD5:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/EUZ7NTWUQYNJOUKEOGWK5G7F5C:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/OBV5C7FMFPTWDKJ7DOEXJ3VO6F:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/P5VNKL5OUHXL2VF2DVIRJPQWRC:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/VQE27GZVU2TFWFYVH2AONDTYJ2,upperdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eac0309013bd772f30b78eabc0606e374fc03dcaa314b58d3fa447cce4df0ccf/diff,workdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eac0309013bd772f30b78eabc0606e374fc03dcaa314b58d3fa447cce4df0ccf/work)
nsfs on /var/run/docker/netns/6c8ba6ec29b1 type nsfs (rw)
overlay on /volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eba604dd839ff0028cc65ffc64d25ae38b860b8a1abdc2e538cc9c7ef6fee040/merged type overlay (rw,relatime,lowerdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/2VJFCH2R3XAMUMTYMGT776YN2M:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/BKLNOZXILRZBRFSVXBUL7O23U6:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/4OJJJJRHEJ6V4W4RNCV2WKJAMC:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/D5OOLPX7WL3EMSLQA5OUH7N6VK:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/ZYDRYNFXGMOJDYYYGVNNVYSEU5:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/N5PBAFX6SYRNQ2I6IX7PSQ3X52:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/QP7EJCY5AKUSJ7QE5UBSHIXIYP:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/TI3DNN352UZK5RCLAKRFWLUF2B:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/37L2K5JG2P26IU4VPWJT6OOVV5:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/QXSDQY4LE2RNYXRQ5USCUZJJDJ:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/THQZ7HSWF66CLML44M4BN5J3V7:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/4PYA2A7WHD63S3GC6DMBADB3T3:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/YEJTDTNNCJCSHLUOWLJGYQPK3F:/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/l/OQ7X7PGRYBXOAQTOXUYXNFEW37,upperdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eba604dd839ff0028cc65ffc64d25ae38b860b8a1abdc2e538cc9c7ef6fee040/diff,workdir=/volume1/.@plugins/AppCentral/docker-ce/docker_lib/overlay2/eba604dd839ff0028cc65ffc64d25ae38b860b8a1abdc2e538cc9c7ef6fee040/work)
shm on /volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/cf77cedafa6b2bfdb20b63adf4a9fb59187dc7d850e8eadb84db4a40a3d5583a/mounts/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
It indeed looks like a software bug...
Last edited by orion on Wed Feb 24, 2021 7:00 pm, edited 1 time in total.
User avatar
father.mande
Posts: 1810
Joined: Sat Sep 12, 2015 2:55 am
Location: La Rochelle (France)

Re: ASUSTOR NAS are not a good choice

Post by father.mande »

Hi,
nissl wrote: Also this has no effect on the ADM. ADM Has no access to configuration, Storage, first nothing.
For this point (I only have small NAS) ADM configuration files ... are in /dev/md0 (or other number 1 for ex.) NOT in data & application volume md127 (in your case)

md0 (sdx4 x from 0 to ...) is an ext4 file system ... so assemble then mount md0 or what else the name you used ... to get access to configurations files, etc.

Philippe.
NB (no critic about your message) I own small but multiple NAS from multiple Brand (the major) ... don't expect it's better ... it's just that support have difficulty to understand and don't ask the user to get more
support is always better when he can connect him to a faulty but running system, and (for all) it's never clear what is the exact rules (responsibility) between reseller and brand. :roll:
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
nissl
Posts: 25
Joined: Sat Jan 18, 2014 10:48 pm

Re: ASUSTOR NAS are not a good choice

Post by nissl »

Code: Select all

root@Caithleen:~ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sdd4[0] sde4[7] sdf4[6] sdc4[8] sdg4[9] sdh4[3] sda4[2] sdb4[1]
      68332938240 blocks super 1.2 level 5, 64k chunk, algorithm 2 [8/8] [UUUUUUUU]

md126 : active raid1 sdd3[0] sde3[7](S) sdf3[6](S) sdc3[5](S) sdg3[4](S) sdh3[3] sda3[2] sdb3[1]
      2095104 blocks super 1.2 [4/4] [UUUU]

md0 : active raid1 sdd2[0] sdf2[6] sdc2[10] sdg2[11] sdh2[3] sda2[2] sdb2[1]
      2095104 blocks super 1.2 [10/7] [UUUUUUU___]

unused devices: <none>
nissl
Posts: 25
Joined: Sat Jan 18, 2014 10:48 pm

Re: ASUSTOR NAS are not a good choice

Post by nissl »

Meanwhile the Tech Support replied. :lol: :lol: :lol: :lol: :lol: :lol:
As expected a totally idiotic and usless reply:
Hi Dennis

Good day,

Thank you for contacting ASUSTOR technical support

Your NAS is out of DHCP range. Click on the reset button on the back of the NAS. If the NAS is still out of DHCP range, look to extend the DHCP range in your router. Also be sure to check the Ethernet cables. If that doesn't change anything, you should get a spare drive and reinstall ADM and then insert your old hard drives in their old location. Warning: your volume 1 is in degraded mode and do not invert a hard disk

Best regards
Damien - ASUSTOR
I actually don't know what for God's sake the IP range has to do at all with the Stoarge and the configuration. Also that the Raid is degraded is simply not even true.
Resetting is every time the only thing the tech support is suggesting.
This is NOT supporting anyone...

My new Synology is on its way, after the Filemigration i kick this crappy Asustor on the yard, put some gas over it and burn it.

No recommandation from my side for all time! :lol: :lol: :lol:
OzCam
Posts: 19
Joined: Thu Sep 09, 2021 6:16 pm

Re: ASUSTOR NAS are not a good choice

Post by OzCam »

I must say i picked the asustor for the natty hardware, but some of the software choices are... um... interesting.

Id really like to be able to use btrfs raid rather than lvm volumes and just direct mount the volumes directly. I find im fighting with ADM a lot for what i want to do.
Post Reply

Return to “Tips & Tricks”