dopeytree

Have you got the virtual driver as the 1st graphics card in the VM options? Should be able to login on vnc then set up Microsoft remote desktop for better quality remote experience. Then getting video out to a monitor should be as simple as going to graphics or video settings. I'm no expert just trying to point in the right direction.

On latest release. Anyway why would docker lock up the GUI's nginx SSL layer?

Thanks hmm ok weird. For me a I have a 13500H and it only happens very rarely usually after a container update. Specifically this happened after updating 'netdata' while the server was doing some other intensive tasks. It would also happen occasionally on the old server. Hence looking for a solution other than shutdown / reboot the server which can cause a parity error if its locked up something else. When I do a search for '504 nginx' its quite common but no one seems to have built this kind of script into the OS yet.

Is it possible to add a list of backups & their date & file size? Just be easier to track then than manually browsing the backup share. I have it set to keep at least 2x backups but it's keeping 4x with a total size of 1.6TB which is a bit big.

Ace! Yeah just the unraid GUI nginx instance locks up & becomes un reachable, but ping all ok & all other sevices (shares, docker, VMs) are working and accessible. It's rare but it's annoying when it does happen.

Hi, Would this script work to monitor the GUI's nginx instance & restart if necessary? I'm trying to find out if "504 Gateway Time-out" actually appears in the log or is just displayed. #!/bin/bash NGINX_LOG="/var/log/nginx/error.log" # Monitor NGINX error log for specific error messages tail -n0 -F ${NGINX_LOG} | while read LINE; do if echo $LINE | grep -q "504 Gateway Time-out"; then echo "NGINX error detected: $LINE" echo "Restarting NGINX..." systemctl restart nginx fi done Its very occasionally but I want to avoid the GUI locking up like this:

Ok here's a user script. #!/bin/bash NGINX_LOG="/var/log/nginx/error.log" # Monitor NGINX error log for specific error messages tail -n0 -F ${NGINX_LOG} | while read LINE; do if echo $LINE | grep -q "504 Gateway Time-out"; then echo "NGINX error detected: $LINE" echo "Restarting NGINX..." systemctl restart nginx fi done and schedules to run every minute with * * * * *

Occasionally the main GUI nginx instance crashes. I'd like to know if anyone has a solution for this. Is there a script I can run to detect a crash and re-start the main GUI NGINX? Other services are always working but no access to server. I currently keep SSH turned off. Currently new server build has no soft power button on my server to initiate a restart. Although have now bought one on amazon.

Thanks, some progress it now prints this:

@limetech can we please backport this LSOF cpu spike fix above?

/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_5aa28a0ce09ced11947d7dfaa7669f5d-if00-port0

Getting this on the silabs [04:46:31:062449] Info : ENCRYPTION IS DISABLED [04:46:31:062452] Info : Starting daemon in normal mode [04:46:31:062485] *** ASSERT *** : FATAL system call in function 'driver_uart_open' in file /usr/src/cpc-daemon/driver/driver_uart.c at line #323 : No such file or directory [04:46:32:062637] Info : Daemon exiting with status EXIT_FAILURE Logger buffer size = 28672, highwater mark = 2215 : 7.73%. Lost logs : 0 2024-04-15 04:46:32 [INFO] CPC ended with exit code 1 (signal 0)... 2024-04-15 04:46:33 [INFO] Starting cpcd... [04:46:33:158676] Info : [CPCd v4.3.1.0] [Library API v3] [RCP Protocol v4] [04:46:33:158720] Info : Git commit: 133b29678b3d0bc7578e098d2f46b4d5bcd2ebb4 / branch: [04:46:33:158722] Info : Sources hash: ff8300587e7e4ab1def7a89a272c0baef32f9eb3bff9b0ba06b94e655d652367 [04:46:33:158728] WARNING : In function 'main' in file /usr/src/cpc-daemon/main.c at line #186 : Running CPCd as 'root' is not recommended. Proceed at your own risk. [04:46:33:158742] Info : Reading cli arguments [04:46:33:158745] Info : /usr/local/bin/cpcd [04:46:33:158860] Info : Reading configuration [04:46:33:158861] Info : file_path = /usr/local/etc/cpcd.conf [04:46:33:158862] Info : instance_name = cpcd_0 [04:46:33:158863] Info : socket_folder = /dev/shm [04:46:33:158864] Info : operation_mode = MODE_NORMAL [04:46:33:158865] Info : use_encryption = false [04:46:33:158866] Info : binding_key_file = /root/.cpcd/binding.key [04:46:33:158867] Info : stdout_tracing = false [04:46:33:158868] Info : file_tracing = false [04:46:33:158869] Info : lttng_tracing = false [04:46:33:158870] Info : enable_frame_trace = false [04:46:33:158871] Info : traces_folder = /dev/shm/cpcd-traces [04:46:33:158872] Info : bus = UART [04:46:33:158873] Info : uart_baudrate = 460800 [04:46:33:158874] Info : uart_hardflow = true [04:46:33:158875] Info : uart_file = /dev/thread [04:46:33:158876] Info : fu_recovery_pins_enabled = false [04:46:33:158877] Info : fu_connect_to_bootloader = false [04:46:33:158878] Info : fu_enter_bootloader = false [04:46:33:158879] Info : restart_cpcd = false [04:46:33:158880] Info : application_version_validation = false [04:46:33:158881] Info : print_secondary_versions_and_exit = false [04:46:33:158882] Info : use_noop_keep_alive = false [04:46:33:158883] Info : reset_sequence = true [04:46:33:158883] Info : stats_interval = 0 [04:46:33:158885] Info : rlimit_nofile = 2000 [04:46:33:158885] Info : ENCRYPTION IS DISABLED [04:46:33:158886] Info : Starting daemon in normal mode [04:46:33:158891] *** ASSERT *** : FATAL system call in function 'driver_uart_open' in file /usr/src/cpc-daemon/driver/driver_uart.c at line #323 : No such file or directory [04:46:34:158969] Info : Daemon exiting with status EXIT_FAILURE Logger buffer size = 28672, highwater mark = 2215 : 7.73%. Lost logs : 0

Great value for money. 13500H is way more efficient than my 11900t but there is a problem again with ASPM so no acheiving extra low power states. However I am using a HBA card to run my 20disks. If you use without it will idle much lower.

Ok new drive in and all rebuilt. took 1 day and 6 hours average 106MB/s Also added 2nd parity after. Original drive completley dead as a dodo nothing on mac or linux machine. No noise. No spinning vibration. It was a Seagate 8TB drive shucked from a usb caddy. Quite old but not the oldest.. bit of a sudden death! Found old diagnostic from a few days before and it wasn't a battle hardened drive it should have lasted longer.. It was a SMR drive though? Most of my other drives are enterprise seagate ironwolf or Seagate Exos X16 smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.82-Unraid] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate BarraCuda 3.5 (SMR) Device Model: ST8000DM004-2CX188 Serial Number: WCT0D9SJ LU WWN Device Id: 5 000c50 0acc34338 Firmware Version: 0001 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5425 rpm Device is: In smartctl database 7.3/5598 ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Mar 29 07:23:12 2024 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Unavailable === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 955) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 079 064 006 - 79766168 3 Spin_Up_Time PO---- 091 091 000 - 0 4 Start_Stop_Count -O--CK 094 094 020 - 6164 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 7 Seek_Error_Rate POSR-- 074 060 045 - 25598382 9 Power_On_Hours -O--CK 082 082 000 - 16016h+53m+20.947s 10 Spin_Retry_Count PO--C- 100 100 097 - 0 12 Power_Cycle_Count -O--CK 100 100 020 - 137 183 Runtime_Bad_Block -O--CK 100 100 000 - 0 184 End-to-End_Error -O--CK 100 100 099 - 0 187 Reported_Uncorrect -O--CK 100 100 000 - 0 188 Command_Timeout -O--CK 100 100 000 - 1 1 1 189 High_Fly_Writes -O-RCK 100 100 000 - 0 190 Airflow_Temperature_Cel -O---K 081 050 040 - 19 (Min/Max 18/38) 191 G-Sense_Error_Rate -O--CK 100 100 000 - 0 192 Power-Off_Retract_Count -O--CK 100 100 000 - 141 193 Load_Cycle_Count -O--CK 097 097 000 - 6185 194 Temperature_Celsius -O---K 019 050 000 - 19 (0 14 0 0 0) 195 Hardware_ECC_Recovered -O-RC- 079 064 000 - 79766168 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 240 Head_Flying_Hours ------ 100 253 000 - 978h+15m+08.462s 241 Total_LBAs_Written ------ 100 253 000 - 49765445146 242 Total_LBAs_Read ------ 100 253 000 - 23881764830 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 5 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x08 GPL R/O 2 Power Conditions log 0x09 SL R/W 1 Selective self-test log 0x0c GPL R/O 2048 Pending Defects log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x24 GPL R/O 512 Current Device Internal Status Data log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 GPL,SL VS 24 Device vendor specific log 0xa2 GPL VS 8160 Device vendor specific log 0xa6 GPL VS 192 Device vendor specific log 0xa8-0xa9 GPL,SL VS 136 Device vendor specific log 0xab GPL VS 1 Device vendor specific log 0xb0 GPL VS 9048 Device vendor specific log 0xbe-0xbf GPL VS 65535 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL,SL VS 16 Device vendor specific log 0xc3 GPL,SL VS 8 Device vendor specific log 0xc4 GPL,SL VS 24 Device vendor specific log 0xd1 GPL VS 264 Device vendor specific log 0xd3 GPL VS 1920 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (5 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 522 (0x020a) Device State: Active (0) Current Temperature: 18 Celsius Power Cycle Min/Max Temperature: 17/38 Celsius Lifetime Min/Max Temperature: 14/50 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 3 minutes Temperature Logging Interval: 59 minutes Min/Max recommended Temperature: 14/55 Celsius Min/Max Temperature Limit: 10/60 Celsius Temperature History Size (Index): 128 (90) Index Estimated Time Temperature Celsius 91 2024-03-24 02:17 18 - 92 2024-03-24 03:16 19 - 93 2024-03-24 04:15 18 - 94 2024-03-24 05:14 18 - 95 2024-03-24 06:13 18 - 96 2024-03-24 07:12 17 - 97 2024-03-24 08:11 18 - 98 2024-03-24 09:10 20 * 99 2024-03-24 10:09 18 - 100 2024-03-24 11:08 17 - 101 2024-03-24 12:07 18 - 102 2024-03-24 13:06 18 - 103 2024-03-24 14:05 19 - 104 2024-03-24 15:04 22 *** 105 2024-03-24 16:03 20 * 106 2024-03-24 17:02 21 ** 107 2024-03-24 18:01 20 * 108 2024-03-24 19:00 18 - 109 2024-03-24 19:59 18 - 110 2024-03-24 20:58 20 * 111 2024-03-24 21:57 18 - 112 2024-03-24 22:56 18 - 113 2024-03-24 23:55 23 **** ... ..( 2 skipped). .. **** 116 2024-03-25 02:52 23 **** 117 2024-03-25 03:51 22 *** 118 2024-03-25 04:50 20 * 119 2024-03-25 05:49 19 - 120 2024-03-25 06:48 19 - 121 2024-03-25 07:47 18 - ... ..( 2 skipped). .. - 124 2024-03-25 10:44 18 - 125 2024-03-25 11:43 26 ******* 126 2024-03-25 12:42 22 *** 127 2024-03-25 13:41 19 - 0 2024-03-25 14:40 19 - 1 2024-03-25 15:39 20 * 2 2024-03-25 16:38 19 - 3 2024-03-25 17:37 19 - 4 2024-03-25 18:36 20 * 5 2024-03-25 19:35 20 * 6 2024-03-25 20:34 21 ** 7 2024-03-25 21:33 20 * 8 2024-03-25 22:32 27 ******** 9 2024-03-25 23:31 24 ***** 10 2024-03-26 00:30 25 ****** 11 2024-03-26 01:29 22 *** 12 2024-03-26 02:28 21 ** 13 2024-03-26 03:27 20 * 14 2024-03-26 04:26 20 * 15 2024-03-26 05:25 20 * 16 2024-03-26 06:24 23 **** 17 2024-03-26 07:23 24 ***** 18 2024-03-26 08:22 22 *** 19 2024-03-26 09:21 19 - 20 2024-03-26 10:20 19 - 21 2024-03-26 11:19 19 - 22 2024-03-26 12:18 22 *** 23 2024-03-26 13:17 20 * 24 2024-03-26 14:16 19 - ... ..( 2 skipped). .. - 27 2024-03-26 17:13 19 - 28 2024-03-26 18:12 22 *** 29 2024-03-26 19:11 22 *** 30 2024-03-26 20:10 20 * 31 2024-03-26 21:09 20 * 32 2024-03-26 22:08 19 - 33 2024-03-26 23:07 19 - 34 2024-03-27 00:06 21 ** 35 2024-03-27 01:05 21 ** 36 2024-03-27 02:04 20 * 37 2024-03-27 03:03 19 - 38 2024-03-27 04:02 18 - 39 2024-03-27 05:01 18 - 40 2024-03-27 06:00 18 - 41 2024-03-27 06:59 23 **** 42 2024-03-27 07:58 19 - 43 2024-03-27 08:57 18 - 44 2024-03-27 09:56 18 - 45 2024-03-27 10:55 22 *** 46 2024-03-27 11:54 20 * 47 2024-03-27 12:53 19 - ... ..( 3 skipped). .. - 51 2024-03-27 16:49 19 - 52 2024-03-27 17:48 22 *** 53 2024-03-27 18:47 24 ***** 54 2024-03-27 19:46 26 ******* 55 2024-03-27 20:45 27 ******** 56 2024-03-27 21:44 37 ****************** 57 2024-03-27 22:43 35 **************** 58 2024-03-27 23:42 30 *********** 59 2024-03-28 00:41 31 ************ 60 2024-03-28 01:40 30 *********** 61 2024-03-28 02:39 23 **** 62 2024-03-28 03:38 20 * 63 2024-03-28 04:37 20 * 64 2024-03-28 05:36 26 ******* 65 2024-03-28 06:35 21 ** 66 2024-03-28 07:34 19 - 67 2024-03-28 08:33 20 * 68 2024-03-28 09:32 29 ********** 69 2024-03-28 10:31 22 *** 70 2024-03-28 11:30 22 *** 71 2024-03-28 12:29 19 - ... ..( 5 skipped). .. - 77 2024-03-28 18:23 19 - 78 2024-03-28 19:22 20 * 79 2024-03-28 20:21 21 ** 80 2024-03-28 21:20 25 ****** 81 2024-03-28 22:19 19 - 82 2024-03-28 23:18 22 *** 83 2024-03-29 00:17 19 - 84 2024-03-29 01:16 18 - ... ..( 2 skipped). .. - 87 2024-03-29 04:13 18 - 88 2024-03-29 05:12 22 *** 89 2024-03-29 06:11 18 - 90 2024-03-29 07:10 18 - SCT Error Recovery Control command not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 137 --- Lifetime Power-On Resets 0x01 0x010 4 16016 --- Power-on Hours 0x01 0x018 6 49765498002 --- Logical Sectors Written 0x01 0x020 6 148351632 --- Number of Write Commands 0x01 0x028 6 23885853723 --- Logical Sectors Read 0x01 0x030 6 91430091 --- Number of Read Commands 0x01 0x038 6 - --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 2094 --- Spindle Motor Power-on Hours 0x03 0x010 4 1037 --- Head Flying Hours 0x03 0x018 4 6185 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 0 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors 0x03 0x040 4 141 --- Number of High Priority Unload Events 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 1 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 18 --- Current Temperature 0x05 0x010 1 20 --- Average Short Term Temperature 0x05 0x018 1 22 --- Average Long Term Temperature 0x05 0x020 1 50 --- Highest Temperature 0x05 0x028 1 0 --- Lowest Temperature 0x05 0x030 1 44 --- Highest Average Short Term Temperature 0x05 0x038 1 18 --- Lowest Average Short Term Temperature 0x05 0x040 1 37 --- Highest Average Long Term Temperature 0x05 0x048 1 22 --- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 55 --- Specified Maximum Operating Temperature 0x05 0x060 4 1308 --- Time in Under-Temperature 0x05 0x068 1 13 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 33 --- Number of Hardware Resets 0x06 0x010 4 17 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 19 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS Seagate FARM log (GP Log 0xa6) supported [try: -l farm]

Here's some m.2 adapters with a built in pcie switch chip. This enables motherboards that DO NOT SUPPORT Bifurcation to read from multiple NVMe drives on a single adapter PCIe adapter. PCIe adapter to 4x NVMe's qnap - https://www.amazon.co.uk/QNAP-QM2-4P-384-interface-adapter-Internal/dp/B07LF4GRNZ/ref=sr_1_3?crid=1LIMHRDKZKCXQ&dib=eyJ2IjoiMSJ9.sTL9NYHfQf2TErkKffg4qEdDKO68rn5-YZqjmI5bYtimupCISx7wgyhmyrFVguDplz5fYe-o-gXKcEcXBqOFNlw7E7TXYb79XLUmnTaPzGsTqLgv8ow7RZwsXo_h6PGHIp2ZdTyCwZSckOeoIfkPlj_bAhC7Y3Hs975-8lnLCCcO2xpwNQspvG8sJ2kihhzImffdSMkMGg2wRWpM2DB-gFgfwvYv5BobQIpuTve9grE.4rth76vcdUAhGRwlfZJ8RCahLhpnfJP3r4C-_jtrRvA&dib_tag=se&keywords=qnap+m.2&qid=1712924912&sprefix=qnap+m.2%2Caps%2C90&sr=8-3&ufe=app_do%3Aamzn1.fos.d7e5a2de-8759-4da3-993c-d11b6e3d217f sabrent https://www.amazon.co.uk/SABRENT-4-Drive-NVMe-Adapter-PC-P3X4/dp/B0BRYQH443/ref=pd_ci_mcx_pspc_dp_d_2_t_2?pd_rd_w=JAWoo&content-id=amzn1.sym.8db49f41-2d78-4c1c-bc3b-fb9e44b9efb4&pf_rd_p=8db49f41-2d78-4c1c-bc3b-fb9e44b9efb4&pf_rd_r=WKN6PNTZQJ51C8VWG5P8&pd_rd_wg=AZVYk&pd_rd_r=cc357dcf-7d21-4321-aaa6-3b6097336b8c&pd_rd_i=B0BRYQH443

Any update on this feature request?

Thanks. Tried in a different slot & nothing so presume it's deceased. Have noticed the rebuild is much faster than previous array operations it's averaging 160MB/s where as before it would be around 50MB/s. Although that was write and this is read but still maybe that was indicator of bad disk?

Changed my system to a newer 13th gen from 11th gen for power efficiency. Only has 2 RAM slots so went from 128GB down to 64GB. Still plenty!

Diagnostics after reboot. Am going with a re-silver on a new drive. Will add 2nd parity after. And have some more drives ready pre-cleared. moulin-rouge-diagnostics-20240408-1611.zip

Had a disk fail. Used this plugin to locate drive. Then added 2x new drives in spare bays then rebooted. For some reason it has messed up the disk location database. Its labelling some drives as cache (I do no use the term cache) I have a luna, merlin & cctv pools. Also why is it putting unassigned drives into the allocated bays? odd. Parity should be upper left corner. There are only 4x merlin drives. It is saying there are more but putting them in cache... moulin-rouge-diagnostics-20240408-1611.zip moulin-rouge-diagnostics-20240408-1512.zip

Seems to be missing. So think something physical at drive end.

Question is this a good time to add a 2nd parity drive while its already reading all the drives to replace the possible dead drive?

Hi just rebooted array and it's saying one of the array drives is now disabled then on reboot its missing [Disk 9 Not installed]. It's in a 12x bay backplane and all other drives are good. Just rebooting now and have added another drive ready to replace it plus another that could be used for a 2nd parity.. How do I test if the drive is actually dead? It didn't show any warning but thats how the cookies rolls sometimes I guess? moulin-rouge-diagnostics-20240408-1512.zip

Nice

https://github.com/linuxserver/docker-digikam/issues/new/choose