It’s my first post on the forum, so here is my config :
NAS TS453A 8 GB RAM accessed from a single port by Win 10 & 11 computers ; the NAS is not accessible from the web.
Firmware version 5.2.7 3297 Build 20251024 BIOS QX47AR23
1st pool : 2 drives WD RED PLUS 4 To in RAID1
2nd pool : 2 drives WD RED PLUS 4 To in RAID1
I have 2 problems :
there is a lot of zombies process running in my NAS, what are they doing ? some of them are using the processor and other don’t do.
Even when there is nothing to do the disks 1 and 2 of the first pool are working the leds are continuously blinking for a couple of seconds then are off for a couple of second … why ?
Here is the process activity where a copy of about 640 Go is running
I would say open a ticket with QNAP and have them check why all these processes are there (none of my NAS have that many, mostly up to a dozen at a time), but make sure you switch your UI from french to English when submitting screenshots, to either the forum or to a ticket)
I’ve seen this happen before. Sometimes the NAS just spawns them. You can SSH into your NAS and start killing these processes via the PID number. QNAP can also clean them up for you.
Do check that they are sticking around. A lot of times they will be there for a while and then the OS will kill them on its own. Other times, they do get stuck for some reason.
I tried to delete some of those zombies and the result was either “not found” because the process has disapeared before I could enter his PID ( and the zombie comes back with another PID !!! ) or “not allowed”.
So, as suggested by DolbyMan, I will open a ticket with QNAP … and will switch my UI to English.
Not a great idea to random kill processes, even if they are marked as zombie. You never know what it may be in the middle of doing. Hopefully QNAP support will be able to investigate and give you a proper fix / answer.
A zombie process is just that - zombie. It’s what’s left over after a process has completed. QNAP has killed them on my machine.
A zombie process is a process that has completed execution but still has an entry in the process table because its parent process has not yet read its exit status. It does not consume system resources like CPU or memory, but can clutter the process table if not properly handled.
If that’s the case then some parent process is spawning these and they are not closing out. You could try rebooting as well and see if they come back. The ticket is also a good idea.
