ADM 3.0.5.RDU1 ERROR
-
- Posts: 6
- youtube meble na wymiar Warszawa
- Joined: Sat Feb 08, 2014 3:51 pm
ADM 3.0.5.RDU1 ERROR
Any AS-202TE owner successfully updated to ADM 3.0.5.RDU1 out there? Or is this another booboo by Asustor?
- Attachments
-
- naserror.png (110.39 KiB) Viewed 7453 times
-
- Posts: 2
- Joined: Thu Aug 24, 2017 9:26 pm
Re: ADM 3.0.5.RDU1 ERROR
I have the same issue
-
- Posts: 39
- Joined: Wed Apr 29, 2015 1:10 pm
Re: ADM 3.0.5.RDU1 ERROR
Same failure with the same reference code (Ref. 6210) at the same point during install.
The update equally fails at the 24% point when manually loaded instead of using the update route offered by the pop-up message. The manual process doesn't offer a reference code though, it just stops at 24% and won't move from there no matter how long you wait.
Despite having a file called "AS-2XX_3.0.5.RDU1.img" (143,441 KB) downloaded directly from Asustor, I get the following email notification when I try to apply the update:
Event Level: INFO
Date: 01/31/2018 AM 05:43
User: SYSTEM
Event: [ADM Update] Firmware update failed. (The firmware file for updating does not support the model of your NAS.)
I wonder if this is a 32 vs. 64 bit problem but the specific file aimed at the 2XX series for this update seems to say otherwise.
Could it be that Asustor didn't test an OS update before pushing it out? Again?
The update equally fails at the 24% point when manually loaded instead of using the update route offered by the pop-up message. The manual process doesn't offer a reference code though, it just stops at 24% and won't move from there no matter how long you wait.
Despite having a file called "AS-2XX_3.0.5.RDU1.img" (143,441 KB) downloaded directly from Asustor, I get the following email notification when I try to apply the update:
Event Level: INFO
Date: 01/31/2018 AM 05:43
User: SYSTEM
Event: [ADM Update] Firmware update failed. (The firmware file for updating does not support the model of your NAS.)
I wonder if this is a 32 vs. 64 bit problem but the specific file aimed at the 2XX series for this update seems to say otherwise.
Could it be that Asustor didn't test an OS update before pushing it out? Again?
-
- Posts: 82
- Joined: Tue Jun 27, 2017 1:05 pm
Re: ADM 3.0.5.RDU1 ERROR
You guys must be feeling very lucky to be doing this ADM update survival exercise to your NAS every so often.
Or maybe gamble in the hope that the developers will get themselves lucky someday and get it right for once?
(Just joking... )
Or maybe gamble in the hope that the developers will get themselves lucky someday and get it right for once?
(Just joking... )
- orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: ADM 3.0.5.RDU1 ERROR
I got the same error. Just sent a support request to asustor. I'll recommend you can send a support ticket too. This way can push the solution out faster.
-
- Posts: 39
- Joined: Wed Apr 29, 2015 1:10 pm
Re: ADM 3.0.5.RDU1 ERROR
The gambling analogy is a fair comparison. If the NAS was holding years worth of mission critical business data I'd adopt a much more cautious approach but it is really 95% dedicated to my media collection.
I'm coming up on a decision about upgrading/expanding my NAS setup and this kind of untested messing around with the OS is quickly putting Asustor in last place. I'll probably build my own next time or consider a bigger, more powerful unit from one of the competitors.
I'm coming up on a decision about upgrading/expanding my NAS setup and this kind of untested messing around with the OS is quickly putting Asustor in last place. I'll probably build my own next time or consider a bigger, more powerful unit from one of the competitors.
- orion
- Posts: 3485
- Joined: Wed May 29, 2013 11:09 am
Re: ADM 3.0.5.RDU1 ERROR
They fixed it. I can upgrade successfully now.
-
- Posts: 39
- Joined: Wed Apr 29, 2015 1:10 pm
Re: ADM 3.0.5.RDU1 ERROR
Thanks for the heads up Orion. I can confirm that the update has been fixed and installed properly for me.
I'm glad that they were prompt in fixing the problem but Asustor should stop shooting themselves in the foot as soon as possible. They're displaying Intel levels of sloppiness.
I'm glad that they were prompt in fixing the problem but Asustor should stop shooting themselves in the foot as soon as possible. They're displaying Intel levels of sloppiness.