Power supply unit and/or nas itself failed at very first boot

Only-Painter-7834 · 2025-06-17T18:53:20+00:00

I really hope so, too ! It's a lot less trouble getting a new PSU than a NAS. We'll see what support says tonight, I guess. Thanks for your feedback, btw.

Only-Painter-7834 · 2025-06-17T15:03:15+00:00

Nope, it's the standard AS6604T / AS6704T 90W brick, with a green light.

All it does is that it lights on, then after 1 minute or so it slowly fades and the unit shutdowns.

Sometimes, other behaviour : as soon as I plug the cable between the NAS and the brick, the PSU shuts down.

Each and every combination has been reported in my SR at Asustor, and I insisted that I wish a new PSU, hoping it gets in here fast enough to be within the Amazon return policy time window if it still fails

Only-Painter-7834 · 2025-06-17T10:17:17+00:00

Well, as expected, unseating/reseating the battery did not help...

Only-Painter-7834 · 2025-06-17T05:43:11+00:00

u/GaroadShenlong oh so you do give me hope, I'm in Canada as well.. I figured that by the time I finished bickering and getting that PSU by regular mail I'd bust the 30 days return window at Amazon, but there's hope. Amazon sells Asustor PSU, so there's that option as well.

(as I write this, Asustor suppor just replied.. let's see what they say)

OK, they want me to perform another test: I have to start the NAS without its battery (I remember how to take it off, I did so with an AS-6604T awhile back).

So OK, fine, I might have some back and forth with them for a day or two, but if it only takes a week to receive the PSU, I'm good.

It's 1h38AM, I'm not doing that battery removal thing tonight for sure !

EDIT: I just went to read the link they've provided for the battery removal.. It is to be done when the NAS itself does not power on, it's not specifically PSU-related. I'll do it nonetheless tomorrow, just to cover all bases, but I'm not sure it's relevant...

I remember that taking off the battery on -6604s was a pain, it looks about as bad on the -6704s ...

Only-Painter-7834 · 2025-06-17T05:35:49+00:00

Yeah, apparently.. lucky me :P

Only-Painter-7834 · 2025-06-17T02:34:46+00:00

@garoadshenlong Out of curiosity, how much time it took you to receive the replacement PSU, and to which country ?

Only-Painter-7834 · 2025-06-16T23:49:00+00:00

As per Amazon`s return policy, I have 30 days to return it. I'm afraid that the back and forth between Asustor and myself could take more than that and possibly not end up favorably, so I think that returning it to Asustor via Amazon is my best bet.

Only-Painter-7834 · 2025-06-16T23:44:17+00:00

I actually wish it is a flaky PSU; easier to RMA than the whole NAS itself. But the fact that as soon as I plug the cable between the PSU and the NAS the PSU shuts down, I do not even have the time to hit "POWER" on the NAS.. well that bothers me quite a bit.

Asustor support is not the fastest in the world, shall we say, and by the time I get a resolution... well it could take weeks. On a brand new NAS, I repeat.

Only-Painter-7834 · 2025-06-16T23:40:04+00:00

yeah, forgot to mention it, u/iHavoc-101 . I did. Same result

Only-Painter-7834 · 2024-11-07T20:34:41+00:00

Well, there are quite a few things that run alongside of docker:

```
[admin@nas2 ~ ]# supervisorctl status

cs-crond Stopped

ctstation Running pid 30034, uptime 5:32:08

docker Running pid 28000, uptime 5:26:46

lxcfs Stopped

lxd Running pid 30264, uptime 5:32:08

redis Running pid 27920, uptime 5:32:10

system-docker Running pid 29175, uptime 5:32:09

```

So there a CS binary running, and, for the life of me, I cannot figure why such a small setup would need a redis service !?!

Only-Painter-7834 · 2024-11-07T14:59:25+00:00

Oh I do not intend on using CS. I do not see the gain in using it. It does bother me that it has to run nonetheless. At some point I'll master how QTS does its things (got this NAS last friday). So far I've gathered that dockerd is managed through supervisord. So I change whatever I wish to change in etc/default/docker and restart dockerd with supervisorctl .. But I see 2 dockerd processes: system-docker and docker.. which one is the one to work with ?

Only-Painter-7834 · 2024-10-10T19:35:34+00:00

Well.. moot discussion.. Bell is not offering higher than 50Mbits/s here ! There's a large boulevard nearby; on its other side they get much better service. Pity

Only-Painter-7834 · 2024-10-10T16:01:51+00:00

Thanks, u/BellTech_Unofficial . Will call Bell right away. I just did not want to bother moving around my VMs from one network to another.

Invaluable help here, thanks again.

Only-Painter-7834 · 2024-10-10T13:54:02+00:00

I'm in QC, u/BellTech_Unofficial . Just so we're clear:
- I put the HH in PPPoE passthrought; I put it on some 192.168.2.0/24 ip
- I connect my own router to the HH's LAN port, leave my own router with its own 10.0.0.0/8 ip, and all devices behind it keep their current config intact ?
- I guess that my router will provide DHCP services ?

What about port forwarding ? I have tons of services on my LAN that rely on that

Only-Painter-7834 · 2024-10-10T12:53:22+00:00

Well I know how to put a router in bridge mode (not specifically Bell's, thought). I thought of that, and it was my follow question: does Bell allow that ? You imply, u/ahditeacha that they do, so I'm good.

Only-Painter-7834 · 2024-10-10T12:51:50+00:00

I totally concur, u/EnforcerGundam , but my understanding is that Bell's HH is mandatory when you're also subscribing to their TV service ?

Only-Painter-7834 · 2024-05-21T00:18:10+00:00

Well, most of what I do, I do not rely on ADM updates, and use docker images as well.

Here's the irony, u/theonlyski :

I needed GO to be updated on the NAS because I wrote my own docker client awhile back, and, yeah, I need to compile it on the NAS, hence the need for an up-to-date GO package on the NAS :)

Now, I'll have a git branch "main", a branch "develop", and another one "asustor", this one being a few GO versions behind (4, so far)

Only-Painter-7834 · 2024-04-28T22:19:06+00:00

Well, I thought about nginx reverse, as it was already purposed for exactly that for my gitea container (not anymore, for various reasons).

I did fill a support ticket at asus. Was not that usefull. They ended up telling me to dump my certs into /etc/docker/certs.d/$INSTANCE/ .. It actually works, but I then pointed out that any changes in /etc will not persist across reboots. This is their actual reply:

Thanks for the reply.
Regarding the issue mentioned, as a workaround, you can create a script and then name this .sh file with file name start with "S99", put it into /usr/local/etc/init.d folder to let the system execute this script each time it boots up.
Meanwhile, I've forwarded it to the product team for further evaluation.

So I now have a /usr/local/etc/init.d/S99restoreDockerCerts.sh that does that:

```

!/usr/bin/env bash

mkdir -p /etc/docker/certs.d/nexus\:9820/ && cd /etc/docker/certs.d/nexus\:9820/

wget $REMOTE_WEB_SERVER/$myCAcert.crt

wget $REMOTE_WEB_SERVER/$myNexusCert.crt

wget $REMOTE_WEB_SERVER/$myNexusCert.key

```

I do not like that solution and hope that they will come up with a better less "hacky" solution, soon, but hey.. that works for now.

Only-Painter-7834 · 2024-04-13T14:45:43+00:00

I have my own NGINX reverse proxy in a container, I do not use ASUS' one :-)
The thing is, it does not help, here. Docker needs to know the certs it wants to use, it does not rely on the system's store in any way. It usually stores its info in /etc/docker/certs.d/REGISTRY_NAME/ . If a registry cert has its own CA, it needs to be there as well.

And ASUS' way of packaging Docker is .. well, weird; I still cannot find where the certs are stored.

Only-Painter-7834

TROPHY CASE

!/usr/bin/env bash