chris0583

I did see that Areca has a "Driver" for 6.10. Does this drive differ from what is in the main distro?

I have two 1882i cards Latest firmware. Both cards are identical except for IP and S/N. I will d/l the cli tool today and try to spin down the 4 TB drive which is not part of the array. I use it as a stand alone backup drive to some data. the 6 TB drive is drive passed thru to a BlueIRIS windows VM for my security system. Again is can not thank you enough for spending cycle on this. IOMMU group 29:[17d3:1880] 03:00.0 RAID bus controller: Areca Technology Corp. ARC-188x series PCIe 2.0/3.0 to SAS/SATA 6/12Gb RAID Controller (rev 05) [1:0:0:0] disk Seagate ST6000NM0024-1HT R001 /dev/sdb 6.00TB [1:0:0:1] disk Seagate ST14000NM001G-2K R001 /dev/sdc 14.0TB [1:0:0:2] disk Seagate ST12000NM0008-2H R001 /dev/sdd 12.0TB [1:0:0:3] disk Seagate ST12000NM001G-2M R001 /dev/sde 12.0TB [1:0:0:4] disk Seagate ST10000NM0016-1T R001 /dev/sdf 10.0TB [1:0:0:5] disk Seagate ST10000NM0016-1T R001 /dev/sdh 10.0TB [1:0:0:6] disk Seagate ST10000NM0086-2A R001 /dev/sdi 10.0TB [1:0:0:7] disk Seagate ST10000NM0086-2A R001 /dev/sdj 10.0TB IOMMU group 30:[17d3:1880] 02:00.0 RAID bus controller: Areca Technology Corp. ARC-188x series PCIe 2.0/3.0 to SAS/SATA 6/12Gb RAID Controller (rev 05) [8:0:0:0] disk Seagate ST10000NM0016-1T R001 /dev/sdm 10.0TB [8:0:0:1] disk Seagate ST10000NM0016-1T R001 /dev/sdn 10.0TB [8:0:0:2] disk Seagate ST10000NM0016-1T R001 /dev/sdo 10.0TB [8:0:0:3] disk Seagate ST10000NM0016-1T R001 /dev/sdp 10.0TB [8:0:0:5] disk WDC WD4002FYYZ-01B7C R001 /dev/sdq 4.00TB [8:0:0:7] disk Seagate ST6000VN0041-2EL R001 /dev/sdr 6.00TB

One of the main reason I went to unraid was for the spin down feature. I have been running QNAP's for years and those drives would spin all day. Now i can not live without it. I have turned so many people on to it. unfortunately i am their tech support arm whenever they want to do something new with their systems

i have an extra ARC-1280 ML V2. I would of shipped it to you. thank you for going the extra mile on this.

Just wanted to report. I upgraded to the last RC version (Version: 6.10.0-rc7) still no change in spin down behavior. i do get this in the logs. looks like the system is issuing commands to spin down but the drives are not listening except for the parity which are connected to the main board. May 10 14:54:59 STORAGE2 kernel: sdb: sdb1 May 10 14:54:59 STORAGE2 kernel: sdp: sdp1 May 10 14:57:03 STORAGE2 emhttpd: spinning down /dev/sdq May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdm May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdh May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdg May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdd May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdb May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdf May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdn May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdo May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdi May 10 15:07:02 STORAGE2 emhttpd: spinning down /dev/sdp May 10 15:07:32 STORAGE2 emhttpd: spinning down /dev/sdk May 10 15:07:32 STORAGE2 emhttpd: spinning down /dev/sdl May 10 15:09:51 STORAGE2 emhttpd: spinning down /dev/sdr May 10 15:12:04 STORAGE2 emhttpd: spinning down /dev/sdq May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdm May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdh May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdg May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdd May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdb May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdf May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdn May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdo May 10 15:22:03 STORAGE2 emhttpd: spinning down /dev/sdi May 10 15:24:52 STORAGE2 emhttpd: spinning down /dev/sdr May 10 15:25:37 STORAGE2 kernel: sdb: sdb1 May 10 15:25:37 STORAGE2 kernel: sdp: sdp1 May 10 15:27:05 STORAGE2 emhttpd: spinning down /dev/sdq May 10 15:29:46 STORAGE2 emhttpd: read SMART /dev/sdk May 10 15:29:46 STORAGE2 emhttpd: read SMART /dev/sdl May 10 15:39:53 STORAGE2 emhttpd: spinning down /dev/sdr May 10 15:42:06 STORAGE2 emhttpd: spinning down /dev/sd

Something odd happened. Drives 9 & 10 went X on me. Thank the lord for 2 parity drives. System is rebuilding. I will try and issue more commands once rebuilt and 100%. Again, thank you for all the help and suggestions. I am trying to avoid buying a new adapter and there is nothing working with the ones I have. Something changed in 6.9.2 that broke spin down or compatibility for Areca adapters. I even logged into the adapter web UI and both have the same config …

root@STORAGE2:~# lsscsi -g|grep "Areca" [1:0:16:0] process Areca RAID controller R001 - /dev/sg10 [8:0:16:0] process Areca RAID controller R001 - /dev/sg19 root@STORAGE2:~# sg_map /dev/sg0 /dev/sda /dev/sg1 /dev/sdb /dev/sg2 /dev/sdc /dev/sg3 /dev/sdd /dev/sg4 /dev/sde /dev/sg5 /dev/sdf /dev/sg6 /dev/sdg /dev/sg7 /dev/sdh /dev/sg8 /dev/sdi /dev/sg9 /dev/sdj /dev/sg10 /dev/sg11 /dev/sdk /dev/sg12 /dev/sdl /dev/sg13 /dev/sdm /dev/sg14 /dev/sdn /dev/sg15 /dev/sdo /dev/sg16 /dev/sdp /dev/sg17 /dev/sdq /dev/sg18 /dev/sdr /dev/sg19 root@STORAGE2:~# hdparm -y /dev/sg9 /dev/sg9: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@STORAGE2:~# hdparm -C /dev/sg9 /dev/sg9: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby root@STORAGE2:~# smartctl -n never /dev/sg9 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.35-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Device is in ACTIVE mode SCSI device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information root@STORAGE2:~#

Thank you for all help ! root@STORAGE2:~# smartctl -s standby,now /dev/sdj smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.35-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org SCSI STANDBY command failed: SCSI device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information root@STORAGE2:~# smartctl -n stanby /dev/sdj smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.35-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org =======> INVALID ARGUMENT TO -n: stanby =======> VALID ARGUMENTS ARE: never, sleep[,STATUS[,STATUS2]], standby[,STATUS[,STATUS2]], idle[,STATUS[,STATUS2]] <======= Use smartctl -h to get a usage summary root@STORAGE2:~# hdparm -C /dev/sdj /dev/sdj: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby root@STORAGE2:~# hdparm -y /dev/sdj /dev/sdj: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@STORAGE2:~# lsscsi -g|grep "Areca" [1:0:16:0] process Areca RAID controller R001 - /dev/sg10 < Arcea 1881i drives 1 - 8 (sdb > sdi) > [8:0:16:0] process Areca RAID controller R001 - /dev/sg19 < Arcea 1881i drives 1 - 8 (sdj > sdq) > root@STORAGE2:~# smartctl -a -d areca,1,2 /dev/sg19 < device 1 on controller 2 > Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Enterprise Capacity 3.5 HDD Device Model: ST10000NM0016-1TT101 Serial Number: ZA24S56L LU WWN Device Id: 5 000c50 0afaeae7f Firmware Version: SND0 User Capacity: 10,000,831,348,736 bytes [10.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.3/5360 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: Sat May 7 17:28:13 2022 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Warning! SMART Attribute Data Structure error: invalid SMART checksum.

6.9.1 Was the last version of unRAID that the drives spun down properly.

Thanks for assisting with this issue. Drive spin down always worked until a UNraid OS update. The config of the system has not changed since the system was built years ago. Something changed in the OS. Party drives and other drives not connected drives pin down as they should.

Party Drives are connected to the onboard controller and the data drives are on Arcea 1882 Controllers. This config has not changed since the day the system was built. root@STORAGE2:~# hdparm -y /dev/sdh /dev/sdh: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Absolutely . Diags attached. Whatever you need from me to help diagnose the issue I am willing to put the time and effort in to resolving. storage2-diagnostics-20220506-1508.zip

I know this issue is specifically for the Party drives not spinning down. But my system, is still suffering from my data drives not spinning down. It is very frustrating. Has there been any progress made on this issue. Everything was working just fine with spin down until a unRAID OS update that is now preventing them.

BC thanks for the update. Glad your issue have been resolved. I have a bit of hope that maybe there is a fix out there for me . Would prefer not to buy a new card / cards to get this to work.

Are there any updates on the Spindown issue. I have upgraded to the latest RC and my drives still continue to spin all day every day..

I removed the spindown plugin as it did not help anyways....

root@STORAGE2:~# sdparm -ip di_target /dev/sdf /dev/sdf: Seagate ST10000NM0016-1T R001 Device identification VPD page: root@STORAGE2:~# sdparm -C sense /dev/sdf /dev/sdf: Seagate ST10000NM0016-1T R001 Decode response as sense data: Fixed format, current; Sense key: Illegal Request Additional sense: Invalid command operation code

root@STORAGE2:~# sdparm -ip di_target /dev/sdf /dev/sdf: Seagate ST10000NM0016-1T R001 Device identification VPD page:

and just to give some more info to my setup. (which has not changed since the day i build the server over 2 years ago) root@STORAGE2:~# lsscsi -g|grep "Areca" [1:0:16:0] process Areca RAID controller R001 - /dev/sg9 < Arcea 1881i drives 1 - 8 (sdb > sdi) > [8:0:16:0] process Areca RAID controller R001 - /dev/sg19 < Arcea 1881i drives 1 - 8 (sdj > sdq) > root@STORAGE2:~# smartctl -a -d areca,5,1 /dev/sg9 < device 5 on controller 1 /dev/sdf > smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Enterprise Capacity 3.5 HDD Device Model: ST10000NM0016-1TT101 Serial Number: ZA22MCLK LU WWN Device Id: 5 000c50 0a49e2c70 Firmware Version: SNCC User Capacity: 10,000,831,348,736 bytes [10.0 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] 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: Tue Aug 24 16:01:27 2021 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === 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: ( 575) 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: ( 858) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x50bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 078 064 044 Pre-fail Always - 63226944 3 Spin_Up_Time 0x0003 093 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 094 094 020 Old_age Always - 6360 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 095 060 045 Pre-fail Always - 3274812715 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 28268 (58 45 0) 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 180 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 008 008 000 Old_age Always - 92 190 Airflow_Temperature_Cel 0x0022 061 044 040 Old_age Always - 39 (Min/Max 33/52) 191 G-Sense_Error_Rate 0x0032 089 089 000 Old_age Always - 22800 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 102 193 Load_Cycle_Count 0x0032 061 061 000 Old_age Always - 79774 194 Temperature_Celsius 0x0022 039 056 000 Old_age Always - 39 (0 23 0 0 0) 195 Hardware_ECC_Recovered 0x001a 009 003 000 Old_age Always - 63226944 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12558h+46m+30.045s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 284713550384 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1800659171012 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 65 - # 2 Short offline Completed without error 00% 39 - # 3 Short offline Completed without error 00% 31 - 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.

Here ya go root@STORAGE2:~# smartctl -id test /dev/sdf smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdf: Device of type 'scsi' [SCSI] detected /dev/sdf: Device of type 'scsi' [SCSI] opened

root@STORAGE2:~# smartctl -in never /dev/sdf smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Seagate Product: ST10000NM0016-1T Revision: R001 Compliance: SPC-3 User Capacity: 10,000,831,348,736 bytes [10.0 TB] Logical block size: 512 bytes Rotation Rate: 10000 rpm Logical Unit id: 0x001b4d20611aecf9 Serial number: ZA22MCLK Device type: disk Transport protocol: Fibre channel (FCP-2) Local Time is: Tue Aug 24 14:42:34 2021 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported Power mode is: ACTIVE root@STORAGE2:~# smartctl -is standby,now /dev/sdf smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Seagate Product: ST10000NM0016-1T Revision: R001 Compliance: SPC-3 User Capacity: 10,000,831,348,736 bytes [10.0 TB] Logical block size: 512 bytes Rotation Rate: 10000 rpm Logical Unit id: 0x001b4d20611aecf9 Serial number: ZA22MCLK Device type: disk Transport protocol: Fibre channel (FCP-2) Local Time is: Tue Aug 24 14:42:46 2021 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported Device placed in STANDBY mode

I'm assuming the screenshots you attached are from a 6.10.0-rc1 system? Please correct me if I'm wrong, this is an important data point. You are Correct 6.10.0-rc1 Your drives are SATA. The SAS Spindown plugin will not do anything for you, unfortunately (will do no harm either) - it deals exclusively with SAS drives. 2 Parity Drives are connected to the onboard sata ports (these drives spin down) as well as the cache drive. The rest of the drives are connected to two (2) Areca 1882I's in JBOD mode. The drives have stopped spinning down Meanwhile, would you mind selecting one of the drives that does not have any activity against it, and on an Unraid command shell, issue these commands (replace /dev/sdX with the drive you selected): root@STORAGE2:~# hdparm -y /dev/sdf /dev/sdf: issuing standby command SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@STORAGE2:~# hdparm -C /dev/sdf /dev/sdf: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby root@STORAGE2:~# sleep 1 root@STORAGE2:~# hdparm -C /dev/sdf /dev/sdf: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby root@STORAGE2:~#

Sorry for the late reply. I was traveling I pick one drive on each of the two Aerca 1882i Controller in the system. root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdd down SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@STORAGE2:~# echo $? 0 root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdd root@STORAGE2:~# echo $? 0 root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdm down SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@STORAGE2:~# echo $? 0 root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdm root@STORAGE2:~# echo $? 0 root@STORAGE2:~#

All Segate

I loaded the SAS plug-in and my drives connected to my Areca 1882’s are NOT spinning down. The two party drives connected to the main board are spinning down like they always did. (The parity drives were never the problem for me) i bounced the box yesterday to perform a fresh load of the plugins and the system when into a parity check …. I paused it and waited and no drives spun down . I tired to manually to spin them down … Not working I resumed the parity check … still running . I will report when it is completed As I saw this topic is “solved” should I/we start a new one to continue the problem resolution discussion ?