JoshHolme

Hello, I'm trying to run a node script at a set interval (like every 30 minutes or so). I've found User Scripts and tried seeing up the script to run in there, but I get an error `node: command not found`. I'm assuming this context doesn't have node installed. Is there a way for me to install node here? Or am I using this incorrectly?

Hello, one of my drives “failed” recently and I tried to replace it. I swapped the failed 4TB drive out with a 6TB and during the rebuild the 6TB failed. I think my SATA controller is failing (I just bought one from the forum of approved PCIe sata controllers). I tried to put the 4TB back in and swapped the ports and it recognized it, but wouldn’t let me enable it because it’s lower than the 6TB now. I’m stuck now where the 6 TB keeps failing the rebuild and I can’t get the 4 TB to replace it. Is there any way I can force the 4 TB back into that spot? Any suggestions on how to move forward? apollo-diagnostics-20230504-2135.zip

@ChatNoir Here are my diagnostics. It was working last night. I restarted it today to replace some SATA cables and now it's doing it again apollo-diagnostics-20220201-2002.zip

I'm getting issues with the official plex docker where on run it gives the following error: PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server Stopping Plex Media Server. I tried repairing the permissions to no avail, if anyone has any thoughts I'd appreciate it.

The drives were powered by a cable with many sata power connectors on it. I reseated all sata data and power cables. Sata data cables must be at least 10 years old, passed on from another old server. I have new cables to replace those coming Monday, but for now I was able to get the rebuild to finish, and I think we’re in the clear. Thank you everyone!

My SATA cables are fairly old. I just ordered all new cables and hopefully that fixes the issue. They should be here Monday

@JorgeB I'm hesitant to think that it could be an issue with that since I've done parity rebuilds with this same controller, sata cables and other hardware before. The disk that it's trying to rebuild used to be my parity drive, but now is being used as Disk 1 in my system. It starts out fine but then always fails after a few minutes. Does this extra info help out at all for other ideas you think it might be?

Weird. It’s been running fine for months before this. I’ll have to check the connectors

Hello everyone. I had a dead drive and bought a replacement. I want to move my drives to 6TB eventually, so I bought a 6TB to replace my 4TB and followed the parity swap procedure to do so. The parity drive rebuilt fine, and then I was trying to rebuild the array, but it keeps failing on my old parity drive that is now my disk 1. Any help or pointers? apollo-diagnostics-20220125-1638.zip

Hey trurl, You’ve helped me a lot in prior posts to this as well, so I want to collectively thank you for all of the help you’ve given me along the way. After a couple hours more of troubleshooting, seems like 2 of my sata ports died out on me. Very frustrating since they’re the sata ports on my motherboard and not my expansion card, but oh well. Thank you again for the help.

Hello, When I had first set up my array about an hour later one of my drives failed. It was an old drive and I didn’t have any data loaded onto it yet, so I didn’t really care or feel like taking my server apart to get rid of it. Well during a reboot today as I was trying to install Plex, one of my other hard drives magically stopped being recognized. All because of a reboot. I can’t get any other drives to add to the array to replace them, and I don’t know why, or where to go next. Thanks in advance. Josh

Got it, thanks for the info!

I have attached my smart report to this comment. I attempted to run the extended smart test but it gave the message "Errors occurred - Check SMART report". smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.88-Unraid] (local build) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: **-************ LU WWN Device Id: 5 0014ee 2b8719700 Firmware Version: 82.00A82 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Mar 12 01:41:55 2020 EDT 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, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (51120) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 512) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1818 3 Spin_Up_Time POS--K 193 175 021 - 7350 4 Start_Stop_Count -O--CK 100 100 000 - 113 5 Reallocated_Sector_Ct PO--CK 192 192 140 - 243 7 Seek_Error_Rate -OSR-K 200 200 000 - 5 9 Power_On_Hours -O--CK 065 065 000 - 25790 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 110 192 Power-Off_Retract_Count -O--CK 200 200 000 - 50 193 Load_Cycle_Count -O--CK 194 194 000 - 18983 194 Temperature_Celsius -O---K 123 119 000 - 29 196 Reallocated_Event_Count -O--CK 166 166 000 - 34 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1 ||||||_ 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 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test 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 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb6 GPL,SL VS 1 Device vendor specific log 0xb7 GPL,SL VS 39 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 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 (6 sectors) Device Error Count: 314 (device log contains only the most recent 24 errors) CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 314 [1] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 e0 c8 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2e0c8 = 144892104 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 df f8 e0 08 1d+20:17:18.823 READ DMA EXT 35 00 00 01 68 00 00 08 a2 d3 28 e0 08 1d+20:17:18.820 WRITE DMA EXT ca 00 00 00 50 00 00 08 a2 d0 40 e8 08 1d+20:17:18.816 WRITE DMA 35 00 00 02 d8 00 00 08 a2 c5 b8 e0 08 1d+20:17:18.813 WRITE DMA EXT 35 00 00 00 20 00 00 d1 46 31 c0 e0 08 1d+20:17:18.809 WRITE DMA EXT Error 313 [0] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 28 00 00 08 a2 dd b0 e0 00 Error: UNC 296 sectors at LBA = 0x08a2ddb0 = 144891312 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 01 28 00 00 08 a2 dc 90 e0 08 1d+20:17:10.616 READ DMA EXT 25 00 00 04 00 00 00 08 a2 d8 90 e0 08 1d+20:17:08.837 READ DMA EXT 25 00 00 04 00 00 00 08 a2 d4 90 e0 08 1d+20:17:04.826 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:17:04.823 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:17:04.820 IDENTIFY DEVICE Error 312 [23] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 d3 28 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2d328 = 144888616 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 d0 90 e0 08 1d+20:16:57.909 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:57.905 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:16:57.903 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 1d+20:16:57.884 SET FEATURES [Set transfer mode] 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:57.879 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 311 [22] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 d0 40 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2d040 = 144887872 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 cc 90 e0 08 1d+20:16:52.161 READ DMA EXT 25 00 00 04 00 00 00 08 a2 c8 90 e0 08 1d+20:16:47.987 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:47.983 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:16:47.981 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 1d+20:16:47.961 SET FEATURES [Set transfer mode] Error 310 [21] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 c5 b8 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2c5b8 = 144885176 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 c4 90 e0 08 1d+20:16:42.004 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:41.998 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:16:41.996 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 1d+20:16:41.976 SET FEATURES [Set transfer mode] 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:41.972 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 309 [20] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 c2 d0 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2c2d0 = 144884432 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 c0 90 e0 08 1d+20:16:36.966 READ DMA EXT ea 00 00 00 00 00 00 08 a2 ba 3f e0 08 1d+20:16:34.910 FLUSH CACHE EXT 35 00 00 02 78 00 00 08 a2 b7 c8 e0 08 1d+20:16:34.908 WRITE DMA EXT 35 00 00 02 68 00 00 08 a2 af d8 e0 08 1d+20:16:34.907 WRITE DMA EXT ea 00 00 00 00 00 00 57 63 38 57 e0 08 1d+20:16:34.157 FLUSH CACHE EXT Error 308 [19] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 bb 68 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2bb68 = 144882536 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 ba 40 e0 08 1d+20:16:26.176 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:26.171 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:16:26.131 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 1d+20:16:26.113 SET FEATURES [Set transfer mode] 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:26.108 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 307 [18] occurred at disk power-on lifetime: 25757 hours (1073 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 04 00 00 00 08 a2 b7 c8 e0 00 Error: UNC 1024 sectors at LBA = 0x08a2b7c8 = 144881608 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 04 00 00 00 08 a2 b6 40 e0 08 1d+20:16:20.146 READ DMA EXT 25 00 00 04 00 00 00 08 a2 b2 40 e0 08 1d+20:16:17.879 READ DMA EXT 27 00 00 00 00 00 00 00 00 00 00 e0 08 1d+20:16:17.874 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 00 00 00 00 00 a0 08 1d+20:16:17.871 IDENTIFY DEVICE ef 00 03 00 46 00 00 00 00 00 00 a0 08 1d+20:16:17.852 SET FEATURES [Set transfer mode] SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 25790 140874088 # 2 Extended offline Completed: read failure 90% 25790 140874088 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): 258 (0x0102) Device State: Active (0) Current Temperature: 29 Celsius Power Cycle Min/Max Temperature: 19/30 Celsius Lifetime Min/Max Temperature: 3/32 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (29) Index Estimated Time Temperature Celsius 30 2020-03-11 17:44 28 ********* ... ..( 43 skipped). .. ********* 74 2020-03-11 18:28 28 ********* 75 2020-03-11 18:29 27 ******** 76 2020-03-11 18:30 28 ********* 77 2020-03-11 18:31 27 ******** ... ..( 9 skipped). .. ******** 87 2020-03-11 18:41 27 ******** 88 2020-03-11 18:42 28 ********* ... ..( 20 skipped). .. ********* 109 2020-03-11 19:03 28 ********* 110 2020-03-11 19:04 27 ******** ... ..( 21 skipped). .. ******** 132 2020-03-11 19:26 27 ******** 133 2020-03-11 19:27 28 ********* ... ..( 72 skipped). .. ********* 206 2020-03-11 20:40 28 ********* 207 2020-03-11 20:41 29 ********** ... ..( 15 skipped). .. ********** 223 2020-03-11 20:57 29 ********** 224 2020-03-11 20:58 28 ********* ... ..(208 skipped). .. ********* 433 2020-03-12 00:27 28 ********* 434 2020-03-12 00:28 27 ******** ... ..( 50 skipped). .. ******** 7 2020-03-12 01:19 27 ******** 8 2020-03-12 01:20 28 ********* ... ..( 20 skipped). .. ********* 29 2020-03-12 01:41 28 ********* SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-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 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 278077 Vendor specific

apollo-diagnostics-20200310-1612.zip @johnnie.black Here are my diagnostics. This is a late response, but they are now up to 9745 errors on my parity drive.

Hello everyone, One of my parity drives has read errors, and I didn't notice until one of my other drives failed, and I had to rebuild the parity. The parity seems to have succeeded, except it says it had 454 errors (number of read errors in my parity drive. Is this data lost? How can I tell where the errors are/how do I fix them? Thanks for the help in advance!