A lot of your customers are having serious problems after they upgraded to ADM 2.5.2.RCG2 and so far you have said nothing in your community.
No offense, but thats not how you gain respect!
Some were lucky they visited forum before upgrading, others were lucky your support could help through teamviewer but a lot is looking at a dead nas containing valuable data.
Your only "public" action since release of faulty ADM was to remove it.....
Please show some respect at your customers and -
- Release a guide on how to fix your faulty ADM
- Release a proper procedure on how to return their bricked nas for those not able to follow above guide
- At least admit you made a mistake - we are only humans
Please Asustor
-
Nittenti
- Posts: 22
- youtube meble na wymiar Warszawa
- Joined: Sat Oct 18, 2014 6:51 am
Please Asustor
AS-604T (3GB RAM) with 4*WD Red 2TB in RAID5
Not the HTPC I thought I bought!
I wonder when Asustor is gonna throw some ressources/manpower/knowledge getting it to work, we did pay a decent amount of money for this - for the moment piece of furniture!
Not the HTPC I thought I bought!
I wonder when Asustor is gonna throw some ressources/manpower/knowledge getting it to work, we did pay a decent amount of money for this - for the moment piece of furniture!
-
Shawn.S@AST
- Posts: 181
- Joined: Fri May 25, 2012 3:10 pm
Re: Please Asustor
Hi Nittenti,
Thanks for the reminder! Yes, we did make the mistake of not detecting the over logging of surveillance in our regular testing; either be it the samples we tested are not enough in quantity or that we missed some of the key steps. This is our negligence and mistake.
We have released the steps of how to clear the volume 0 jammed logs in another thread: http://forum.asustor.com/viewtopic.php?f=29&t=7128
If you are not familiar with the procedure or not comfortable in doing it, please kindly allow our support engineer to assist. You only have to write a ticket to us and we will assist right away.
We will also implement beta testing first before putting the new 2.5.2 for upgrade to make the official release can be even more reliable.
Thanks for the reminder! Yes, we did make the mistake of not detecting the over logging of surveillance in our regular testing; either be it the samples we tested are not enough in quantity or that we missed some of the key steps. This is our negligence and mistake.
We have released the steps of how to clear the volume 0 jammed logs in another thread: http://forum.asustor.com/viewtopic.php?f=29&t=7128
If you are not familiar with the procedure or not comfortable in doing it, please kindly allow our support engineer to assist. You only have to write a ticket to us and we will assist right away.
We will also implement beta testing first before putting the new 2.5.2 for upgrade to make the official release can be even more reliable.