cinereus

Is this possible? I have added a new disk but in a different slot to the disk I want to replace. The wiki only explains how to replace a disk when you use the same slot: https://wiki.unraid.net/Replacing_a_Data_Drive Is it possible by rep[lacing the faulty disk with one in a different slot? I am replacing an old disk with a new one. Both are currently connected in the machine and the new one is precleared. What's the procedure for replacing a disk with a new one whilst changing slots?

touch didn't work either. I have reduced the minimum space and that seems to have fixed it for now. thanks.

ErrorWarningSystemArrayLogin EncodeManager: Tight (JPEG): EncodeManager: Full Colour: 739 rects, 4.69842 Mpixels EncodeManager: 4.18712 MiB (1:4.28253 ratio) EncodeManager: Total: 1.435 krects, 11.4521 Mpixels EncodeManager: 4.22628 MiB (1:10.3407 ratio) Connections: closed: 127.0.0.1::50868 ComparingUpdateTracker: 323.148 Mpixels in / 1.69595 Mpixels out ComparingUpdateTracker: (1:190.541 ratio) 2023-01-04 14:51:12,849 WARN received SIGTERM indicating exit request 2023-01-04 14:51:12,850 DEBG killing start (pid 78) with signal SIGTERM 2023-01-04 14:51:12,851 INFO waiting for start to die 2023-01-04 14:51:12,851 DEBG 'start' stderr output: XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 11385 requests (11382 known processed) with 0 events remaining. Process Process-16: Process Process-17: Process Process-15: Process Process-19: Process Process-18: 2023-01-04 14:51:12,852 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23455777176496 for <Subprocess at 23455777171456 with name start in state STOPPING> (stdout)> 2023-01-04 14:51:12,852 DEBG 'start' stderr output: Process Process-20: In exit Terminating child 221 2023-01-04 14:51:12,852 INFO stopped: start (exit status 143) 2023-01-04 14:51:12,852 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2023-01-04 15:00:49.944349 [info] Host is running unRAID 2023-01-04 15:00:49.985634 [info] System information Linux a389265e640d 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2023-01-04 15:00:50.029851 [info] OS_ARCH defined as 'x86-64'【𝟮𝟬 𝗺】 2023-01-04 15:00:50.074155 [info] PUID defined as '99'【𝟯𝟬 𝗺】 2023-01-04 15:00:50.121890 [info] PGID defined as '100'【𝟯𝟬 𝗺】 2023-01-04 15:00:50.212350 [info] UMASK defined as '000' 2023-01-04 15:00:50.255702 [info] Permissions already set for '/config' 2023-01-04 15:00:50.308597 [info] Deleting files in /tmp (non recursive)... 2023-01-04 15:00:50.357580 [info] WEBPAGE_TITLE defined as 'Tower' 2023-01-04 15:00:50.402083 [info] TEMP_FOLDER defined as '/config/krusader/tmp' 2023-01-04 15:00:55.790878 [info] Starting Supervisor... 2023-01-04 15:00:56,353 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing 2023-01-04 15:00:56,353 INFO Set uid to user 0 succeeded 2023-01-04 15:00:56,357 INFO supervisord started with pid 7 2023-01-04 15:00:57,359 INFO spawned: 'start' with pid 78 2023-01-04 15:00:57,360 INFO reaped unknown pid 8 (exit status 0) 2023-01-04 15:00:57,372 DEBG 'start' stderr output: cp: cannot stat '/config/krusader/.config/': No such file or directory 2023-01-04 15:00:57,372 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-01-04 15:00:57,373 DEBG 'start' stderr output: cp: cannot stat '/config/krusader/.local/': No such file or directory 2023-01-04 15:00:57,428 DEBG 'start' stderr output: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2023-01-04 15:00:57,428 DEBG 'start' stderr output: Xvnc TigerVNC 1.12.0 - built Mar 14 2022 12:48:11 Copyright (C) 1999-2021 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12009000, The X.Org Foundation Wed Jan 4 15:00:57 2023 vncext: VNC extension running! 2023-01-04 15:00:57,429 DEBG 'start' stderr output: vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 2023-01-04 15:00:57,644 DEBG 'start' stdout output: ObRender-Message: Unable to load the theme 'Shiki-Brave' 2023-01-04 15:00:57,645 DEBG 'start' stdout output: ObRender-Message: Falling back to the default theme 'Clearlooks' 2023-01-04 15:00:57,743 DEBG 'start' stderr output: WebSocket server settings: - Listen on :6080 2023-01-04 15:00:57,744 DEBG 'start' stderr output: - Web server. Web root: /usr/share/webapps/novnc - No SSL/TLS support (no cert file) 2023-01-04 15:00:57,744 DEBG 'start' stderr output: - proxying from :6080 to localhost:5900 2023-01-04 15:01:01,400 DEBG 'start' stdout output: [info] tint2 not running 2023-01-04 15:01:01,415 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2023-01-04 15:01:01,417 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 2023-01-04 15:01:01,418 DEBG 'start' stderr output: [1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96[0m tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2023-01-04 15:01:01,419 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2023-01-04 15:01:01,421 DEBG 'start' stderr output: tint2: panel items: TSC tint2: Systray composited rendering on tint2: nb monitors 1, nb monitors used 1, nb desktops 2023-01-04 15:01:01,421 DEBG 'start' stderr output: 4 [1;34mtint2: panel 1 uses scale 1 [0m 2023-01-04 15:01:01,446 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2023-01-04 15:01:01,450 DEBG 'start' stderr output: tint2: systray window 8388621 2023-01-04 15:01:01,450 DEBG 'start' stderr output: [1;32mtint2: systray started[0m 2023-01-04 15:23:48,832 WARN received SIGTERM indicating exit request 2023-01-04 15:23:48,833 DEBG killing start (pid 78) with signal SIGTERM 2023-01-04 15:23:48,833 INFO waiting for start to die 2023-01-04 15:23:48,834 DEBG 'start' stderr output: Signal: 15 XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 3099 requests (3096 known processed) with 0 events remaining. In exit 2023-01-04 15:23:48,834 DEBG 'start' stderr output: Signal: 15 2023-01-04 15:23:48,835 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22926634498704 for <Subprocess at 22926634493664 with name start in state STOPPING> (stdout)> 2023-01-04 15:23:48,835 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22926634498656 for <Subprocess at 22926634493664 with name start in state STOPPING> (stderr)> 2023-01-04 15:23:48,835 INFO stopped: start (exit status 143) 2023-01-04 15:23:48,835 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2023-01-04 15:23:54.677016 [info] Host is running unRAID 2023-01-04 15:23:54.713913 [info] System information Linux a389265e640d 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2023-01-04 15:23:54.759303 [info] OS_ARCH defined as 'x86-64'【𝟮𝟬 𝗺】 2023-01-04 15:23:54.802737 [info] PUID defined as '99'【𝟯𝟬 𝗺】 2023-01-04 15:23:54.853841 [info] PGID defined as '100'【𝟯𝟬 𝗺】 2023-01-04 15:23:54.935395 [info] UMASK defined as '000' 2023-01-04 15:23:54.977470 [info] Permissions already set for '/config' 2023-01-04 15:23:55.030433 [info] Deleting files in /tmp (non recursive)... 2023-01-04 15:23:55.078784 [info] WEBPAGE_TITLE defined as 'Tower' 2023-01-04 15:23:55.128044 [info] TEMP_FOLDER defined as '/config/krusader/tmp' 2023-01-04 15:24:00.036589 [info] Starting Supervisor... 2023-01-04 15:24:00,479 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing 2023-01-04 15:24:00,479 INFO Set uid to user 0 succeeded 2023-01-04 15:24:00,481 INFO supervisord started with pid 7 2023-01-04 15:24:01,484 INFO spawned: 'start' with pid 78 2023-01-04 15:24:01,485 INFO reaped unknown pid 8 (exit status 0) 2023-01-04 15:24:01,497 DEBG 'start' stderr output: cp: cannot stat '/config/krusader/.config/': No such file or directory 2023-01-04 15:24:01,497 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-01-04 15:24:01,498 DEBG 'start' stderr output: cp: cannot stat '/config/krusader/.local/': No such file or directory 2023-01-04 15:24:01,543 DEBG 'start' stderr output: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2023-01-04 15:24:01,544 DEBG 'start' stderr output: Xvnc TigerVNC 1.12.0 - built Mar 14 2022 12:48:11 Copyright (C) 1999-2021 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12009000, The X.Org Foundation 2023-01-04 15:24:01,544 DEBG 'start' stderr output: Wed Jan 4 15:24:01 2023 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 2023-01-04 15:24:01,725 DEBG 'start' stdout output: ObRender-Message: Unable to load the theme 'Shiki-Brave' 2023-01-04 15:24:01,726 DEBG 'start' stdout output: ObRender-Message: Falling back to the default theme 'Clearlooks' 2023-01-04 15:24:01,833 DEBG 'start' stderr output: WebSocket server settings: - Listen on :6080 2023-01-04 15:24:01,833 DEBG 'start' stderr output: - Web server. Web root: /usr/share/webapps/novnc - No SSL/TLS support (no cert file) 2023-01-04 15:24:01,833 DEBG 'start' stderr output: - proxying from :6080 to localhost:5900 2023-01-04 15:24:05,524 DEBG 'start' stdout output: [info] tint2 not running 2023-01-04 15:24:05,539 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2023-01-04 15:24:05,541 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 2023-01-04 15:24:05,541 DEBG 'start' stderr output: [1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96[0m tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2023-01-04 15:24:05,543 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2023-01-04 15:24:05,543 DEBG 'start' stderr output: tint2: panel items: TSC tint2: Systray composited rendering on tint2: nb monitors 1 2023-01-04 15:24:05,544 DEBG 'start' stderr output: , nb monitors used 1, nb desktops 4 [1;34mtint2: panel 1 uses scale 1 [0m 2023-01-04 15:24:05,566 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2023-01-04 15:24:05,569 DEBG 'start' stderr output: tint2: systray window 8388621 2023-01-04 15:24:05,570 DEBG 'start' stderr output: [1;32mtint2: systray started[0m 2023-01-04 15:48:23,848 DEBG 'start' stderr output: 192.168.0.21 - - [04/Jan/2023 15:48:23] 192.168.0.21: Plain non-SSL (ws://) WebSocket connection 192.168.0.21 - - [04/Jan/2023 15:48:23] 192.168.0.21: Path: '/websockify' 2023-01-04 15:48:23,848 DEBG 'start' stderr output: 192.168.0.21 - - [04/Jan/2023 15:48:23] connecting to: localhost:5900 2023-01-04 15:48:23,853 DEBG 'start' stderr output: Wed Jan 4 15:48:23 2023 Connections: accepted: 127.0.0.1::49314 2023-01-04 15:48:23,868 DEBG 'start' stderr output: SConnection: Client needs protocol version 3.8 2023-01-04 15:48:23,879 DEBG 'start' stderr output: SConnection: Client requests security type None(1) 2023-01-04 15:48:23,883 DEBG 'start' stderr output: VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 2023-01-04 15:48:23,938 DEBG 'start' stderr output: VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888 2023-01-04 15:48:23,957 DEBG 'start' stderr output: [1;33m/build/tint2/src/tint2/src/util/signals.c 160: triggering tint2 restart, reason: configuration change in the root window[0m ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) 2023-01-04 15:48:24,042 DEBG 'start' stderr output: [1;33mtint2: /build/tint2/src/tint2/src/main.c 782: restarting tint2...[0m 2023-01-04 15:48:24,051 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 2023-01-04 15:48:24,052 DEBG 'start' stderr output: [1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 2028x2017, DPI 96[0m tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2023-01-04 15:48:24,053 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2023-01-04 15:48:24,053 DEBG 'start' stderr output: tint2: panel items: TSC tint2: Systray composited rendering on 2023-01-04 15:48:24,054 DEBG 'start' stderr output: tint2: nb monitors 1, nb monitors used 1, nb desktops 4 [1;34mtint2: panel 1 uses scale 1 [0m 2023-01-04 15:48:24,060 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2023-01-04 15:48:24,060 DEBG 'start' stderr output: tint2: systray window 8388621 [1;32mtint2: systray started[0m 2023-01-04 16:26:34,097 DEBG 'start' stderr output: 192.168.0.21 - - [04/Jan/2023 16:26:34] 192.168.0.21: Plain non-SSL (ws://) WebSocket connection 192.168.0.21 - - [04/Jan/2023 16:26:34] 192.168.0.21: Path: '/websockify' 192.168.0.21 - - [04/Jan/2023 16:26:34] connecting to: localhost:5900 2023-01-04 16:26:34,107 DEBG 'start' stderr output: Wed Jan 4 16:26:34 2023 Connections: accepted: 127.0.0.1::41690 2023-01-04 16:26:34,124 DEBG 'start' stderr output: SConnection: Client needs protocol version 3.8 2023-01-04 16:26:34,131 DEBG 'start' stderr output: SConnection: Client requests security type None(1) 2023-01-04 16:26:34,131 DEBG 'start' stderr output: VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 2023-01-04 16:26:34,157 DEBG 'start' stderr output: VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888 2023-01-04 16:26:36,769 DEBG 'start' stderr output: Wed Jan 4 16:26:36 2023 VNCSConnST: closing 127.0.0.1::41690: Clean disconnection EncodeManager: Framebuffer updates: 99 EncodeManager: Tight: EncodeManager: Solid: 172 rects, 2.46466 Mpixels EncodeManager: 2.6875 KiB (1:3583.1 2023-01-04 16:26:36,769 DEBG 'start' stderr output: ratio) EncodeManager: Bitmap RLE: 3 rects, 4.609 kpixels EncodeManager: 107 B (1:172.636 ratio) EncodeManager: Indexed RLE: 39 rects, 109.751 kpixels EncodeManager: 7.38477 KiB (1:58.1158 ratio) EncodeManager: Tight (JPEG): EncodeManager: Full Colour: 469 rects, 3.11052 Mpixels EncodeManager: 3.31042 MiB (1:3.58596 ratio) EncodeManager: Total: 683 rects, 5.68954 Mpixels EncodeManager: 3.32036 MiB (1:6.53895 ratio) Connections: closed: 127.0.0.1::41690 ComparingUpdateTracker: 6.11119 Gpixels in / 37.2352 Mpixels out ComparingUpdateTracker: (1:164.124 ratio)

Here fs-diagnostics-20230104-1627.zip

One of my shares won't let me create any more files or folders. I get the same error in Krusader. I get the same error by the command line: webadmin clearly says there's 1TB free: I have moved files out of the share. I have deleted files from the share's recycle bin. I still get the same error. What can I do?!

Here. fs-diagnostics-20230104-1533.zip

On further testing this is also now crashing Krusader every single time. Both Krusader and Explorer crash when trying to navigate to this share and this share only.

Okay, but is everything else as I wrote?

Currently have 8 x 12TB drives. I'm going to buy 18 TB drive and parity swap it into Parity1 then use the old 12TB drive as a new data drive. This will add 12TB of space? Then next drive I buy will be 18TB which I will swap for Parity2 and I can then add old 12TB as a new data drive? This process will add 12TB of space? Only with the 3rd 18TB drive I buy will I begin to add the full 18TB of space each time?

How do I restore just one container not every single one at once?

Unfortunately I'm still getting this issue

Thanks. I worked it out myself. It turns out you don't even need to do that. If you just set DNS in eth0, even if it's a different subnet to eth1 and eth0 is not active unraid will happily use this DNS for eth1.

Curiouser and curiouser. eth0 refused to connect to my router after trying multiple cables. However, after moving the router connection to eth1, eth0 now works fine with other connections. Several hours of testing later And the cable that was previously limited to 100 Mbps is now very happy at 1 Gbps. Not sure whether diagnostics say anything sensible about this? fs-diagnostics-20221007-1603.zip

There's no internet connection on my server. I can ping the gateway 192.168.0.1. All other devices connected to the gateway have internet access. I can ping 8.8.8.8 and 8.8.4.4. But I can't ping google.com The network settings won't let me set DNS for eth1 only for eth0 (which is not connected to anything). Why doesn't eth1 let me access the internet?

It's hard to tell. They ha e been working solidly for the last couple of days. I don't understand these errors in the syslog.

Here are diagnostics after a fresh reboot where eth0 is still not working. fs-diagnostics-20221007-1425.zip

eth0 has been stuck at 100 Mbps since my reboot. Just bought a new cable for eth0 and now get this: Oct 7 13:55:33 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Oct 7 13:55:35 fs ntpd[1467]: Deleting interface #36 eth0, 192.168.0.250#123, interface stats: received=696, sent=696, dropped=0, active_time=176867 secs Oct 7 13:55:35 fs ntpd[1467]: 216.239.35.0 local addr 192.168.0.250 -> <null> Oct 7 13:55:35 fs ntpd[1467]: 216.239.35.4 local addr 192.168.0.250 -> <null> Oct 7 13:55:35 fs ntpd[1467]: 216.239.35.8 local addr 192.168.0.250 -> <null> Oct 7 13:55:35 fs ntpd[1467]: 216.239.35.12 local addr 192.168.0.250 -> <null> Oct 7 13:55:35 fs ntpd[1467]: Deleting interface #37 eth0, fe80::ec4:7aff:fe59:76ee%5#123, interface stats: received=0, sent=0, dropped=0, active_time=176867 secs Oct 7 14:07:37 fs ntpd[1467]: Listen normally on 38 eth0 192.168.0.250:123 Oct 7 14:07:37 fs ntpd[1467]: Listen normally on 39 eth0 [fe80::ec4:7aff:fe59:76ee%5]:123 Oct 7 14:07:37 fs ntpd[1467]: new interface(s) found: waking up resolver Oct 7 14:07:40 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down Oct 7 14:07:42 fs ntpd[1467]: Deleting interface #38 eth0, 192.168.0.250#123, interface stats: received=2, sent=8, dropped=0, active_time=5 secs Oct 7 14:07:42 fs ntpd[1467]: 216.239.35.0 local addr 192.168.0.250 -> <null> Oct 7 14:07:42 fs ntpd[1467]: 216.239.35.4 local addr 192.168.0.250 -> <null> Oct 7 14:07:42 fs ntpd[1467]: 216.239.35.8 local addr 192.168.0.250 -> <null> Oct 7 14:07:42 fs ntpd[1467]: 216.239.35.12 local addr 192.168.0.250 -> <null> Oct 7 14:07:42 fs ntpd[1467]: Deleting interface #39 eth0, fe80::ec4:7aff:fe59:76ee%5#123, interface stats: received=0, sent=0, dropped=0, active_time=5 secs Oct 7 14:12:39 fs ntpd[1467]: no peer for too long, server running free now Dashboard says "interface down" with brand new cable. Swapping to old cable also says "interface down" not even the 100 Mbps I had before. What gives?!

It doesn't seem possible to alter this. The option is greyed out. So we still aren't getting closer to understanding why my disks won't spin down. If I manually spin them down they all start up again shortly afterwards...

Sure but then how do I find out what is accessing them? I just clicked "Spin Down" and they have all stayed down! EDIT: Does this log show SMART checks waking them up? Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdj Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdh Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdg Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdd Oct 5 12:13:52 fs emhttpd: spinning down /dev/sde Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdb Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdf Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdc Oct 5 12:13:52 fs emhttpd: spinning down /dev/sdi Oct 5 12:13:55 fs emhttpd: read SMART /dev/sdj Oct 5 12:24:43 fs emhttpd: read SMART /dev/sdg Oct 5 12:24:43 fs emhttpd: read SMART /dev/sde Oct 5 12:24:43 fs emhttpd: read SMART /dev/sdb Oct 5 12:24:43 fs emhttpd: read SMART /dev/sdf Oct 5 12:24:43 fs emhttpd: read SMART /dev/sdi Oct 5 12:24:53 fs emhttpd: read SMART /dev/sdh Oct 5 12:24:53 fs emhttpd: read SMART /dev/sdd Oct 5 12:24:53 fs emhttpd: read SMART /dev/sdc

So what now? Why are they not spinning down?

fs-diagnostics-20221004-2321.zip

Thanks. So I will be okay going from 6.11.0 to 6.9.x?

I have all drive set to spin down after 1 hour. I have checked with the File Activity plugin and nothing is showing up. But having left my server for 12+ hours several times the drives never seem to spin down. What else can I check to find out what's going wrong here?

Thanks for this. Why do you need to reassign cache pool?