Disks thrashing again

[tomforwood]

I've had my TS-x53Be nas for a while and I have never seen it idle. I can always here the disk heads moving and see the status lights blinking.
I tried unpluggingm it physically from the network to see if there were any outside requests keeping it busy but after 48 hours unplugged it was still going.

How can I find out what the disks are doing all the time?

firmware version 5.0.0.1932, $gb of ram, all 4 disks installed.
Cpu is normally steady in singlw figures
used memory 1.8gb
Disk activity for the last few minutes running resource monitor has been 0-1 write/sec and 0 reads

[tomforwood]

Another requeset to work out why my disks are constantly thrashing. I have never heard the disks be queit in at least a year.

QNAP TS-x53Be QTS 5.0.1.2248

Am I naive in expecting that the hard disks should shut down at some point?

The symptoms

• I can constantly hear the disk heads thrashing.
  The disk LEDs are are always flashing
  The lan light is also flashing

What I have tried

• Disconnecting the network cable
  Disabling all the services I can find
  Running the script from the sticky'd topic
  Followed this thread viewtopic.php?f=55&t=165268

The standby debug scrip prints this and then never does anything else.

Code: Select all

*******************************************************
Note: you may need to wait minutes for the first result
*******************************************************
-----1/30------
Tue Feb 14 21:58:45 GMT 2023
The NAS is currently not in Standby Mode:
0x00000000
Swap: 17307320 1763912 15543408

Looking at he output of dmesg I can see a pattern where a block is written to a md device (md09 md13 etc) and then writes to each disk in the array sb(a-d)1 which I assume is the same block being distributed over the physical disks.
The blocks being writtento most ofter map to /.logs/kmsg which appears to contain the contents of the linux debug log and a inode of 8 which doesn't appear to be a file.

So it appears to be constantly writing to the disk the debug log containing the records saying that it is constantly writing to the disk? And doing something that I am guessing is at a very low level (with a single digit inode number?)

[OneCD]

* merged with your previous topic *

[dolbyman]

Same as this

viewtopic.php?f=55&t=169725