AS3102T initialisation problems: FW update and new drive setup

[Andrii]

Hi!

I'm having problems to re-initialize my NAS with a new drive. I've been using it with previous HDD for a couple of years, but that HDD died and I decided to buy new one. Now I'm trying to do a setup, but it fails.

From the web interface I tried to:

1. Update firmware, but it fails with the strange error "Unknown error. (Ref. 5052)"

Image #2 and #3 in attachments

I tried both - internet update and manual download of X64_G3_3.5.1.R8C1.img followed by manual ADM update - both are failing with the same error

2. Then I gave up updating firmware and tried just to initialize ADM with the new HDD, but it also failed! Now with the error "Unknown error. (Ref. 5401)"

I tried with another one HDD from my old computer - the error was the same!

Image #1 in attachments

Is there any existing solution for these two problems? Knowledge base knows nothing about that Google is also not helping me - Error 5052 is seems to be related to some certificate to be installed using ADM, but I can't even reach there!

Please assist, because I'm starting to think about to give up with Asustor

Thanks in advance!

[Andrii]

Just a quick note about drives I was using. I tried already three fully functional drives actually (prior to insert them I deleted all partitions from these drives to have them "like new"):

HDD TOSHIBA DT01ACA300 3TB
HDD Samsung HD753LJ 750Gb
SSD OCZ Agility3 500Gb

None of them allowed me to pass that Error 5401

[orion]

I don't know why I cannot see the attached pictures above?! I cannot understand what's the error without those pictures... Can you check them?

[Andrii]

Google photos closed URL access for some reason, sorry I will update initial post.

Here they are:

[orion]

Oops, it's really new for me. You got an error when NAS creates system volume?! It's odd. Creating partition table is successful. But creating system volume is failed. Hardware error? I doubt.

Anyway, I can only suggest you to send a support request to asustor directly. https://support.asustor.com/

[Andrii]

Yes, this error is pretty odd since I'm getting exactly the same result for three different hard drives Already created a support ticket, they suggested to setup a live screen session, I gave my timeslots and waiting for reply.

Also I think that there should be the way to use command line in order to update firmware, but I'm not really sure that everything will work for me.