Jump to content
SSD

Areca Contoller Configuration for unRAID

112 posts in this topic Last Reply

Recommended Posts

I'm using this card on unRaid 5.0.6 (thanks guys) and would like to upgrade to the latest stable unRaid 6.  Would the steps be:

 

1. run the 6.01 Upgrade Plugin for V5 and reboot

2. verify that 60-persistent-storage.rules is still at \\tower\flash

3. update the fresh ‘go’ file with the 4 lines of script before loading emhttp and reboot

 

Yes, I think this is all that is needed.

 

I have one server on 6.2rc2 and another on 6.1.9 with the 1231ML gen cards with bios 1.49 and it continues to behave as normal.  One thing different on 6.2rc2 is that the temperatures now show up  in the dashboard for Areca connected drives.  Has anybody else noticed this?

Share this post


Link to post

I'm using this card on unRaid 5.0.6 (thanks guys) and would like to upgrade to the latest stable unRaid 6.  Would the steps be:

 

1. run the 6.01 Upgrade Plugin for V5 and reboot

2. verify that 60-persistent-storage.rules is still at \\tower\flash

3. update the fresh ‘go’ file with the 4 lines of script before loading emhttp and reboot

 

Yes, I think this is all that is needed.

 

I have one server on 6.2rc2 and another on 6.1.9 with the 1231ML gen cards with bios 1.49 and it continues to behave as normal.  One thing different on 6.2rc2 is that the temperatures now show up  in the dashboard for Areca connected drives.  Has anybody else noticed this?

 

Just updated to 6.2RC3 and I have temps now too. Still needed the extra driver load in Go. Be nice if we could get rid of that.

 

cp /boot/60-persistent-storage.rules /lib/udev/rules.d
udevadm control --reload-rules
udevadm trigger

Share this post


Link to post

Just updated to 6.2RC3 and I have temps now too. Still needed the extra driver load in Go. Be nice if we could get rid of that.

 

cp /boot/60-persistent-storage.rules /lib/udev/rules.d
udevadm control --reload-rules
udevadm trigger

 

A Dynamix plugin exists to do the persistent rules update automatically, but it may become natively available in a next version of unRAID.

Share this post


Link to post

Just updated to 6.2RC3 and I have temps now too. Still needed the extra driver load in Go. Be nice if we could get rid of that.

 

cp /boot/60-persistent-storage.rules /lib/udev/rules.d
udevadm control --reload-rules
udevadm trigger

 

A Dynamix plugin exists to do the persistent rules update automatically, but it may become natively available in a next version of unRAID.

 

Cool. Will look into that once my monthly parity check is done.

Share this post


Link to post

Drive failure on ARC-1200

 

I have been using my ARC-1200 with two Hitachi 3T drives (total of 6T in a RAID0 configuration) as parity. It has been a great setup. The Hitachi drives have outstanding long-term reliability characteristics, and this setup has served me well for more than 5 years.

 

This weekend I was doing a bit of housecleaning and copying some data to my array. Suddenly the array became largely unresponsive, and several minutes later I determined that the parity drive had been kicked from the array. Upon further investigation, I discovered that the drive was offline from the controller and was invisible to the OS. Here is what was in the syslog:

(previous log message was several hours old)
Jan  1 13:59:13 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: scsi id = 0 lun = 0 ccb = '0xffff88041acb1280' poll command abort successfully 
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:14 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:39 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:39 Shark kernel: arcmsr1: scsi id = 0 lun = 0 ccb = '0xffff88041ac8e380' poll command abort successfully 
Jan  1 13:59:39 Shark kernel: arcmsr1: abort device command of scsi id = 0 lun = 0
Jan  1 13:59:39 Shark kernel: arcmsr: executing bus reset eh.....num_resets = 0, num_aborts = 10 
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
... repeated lines removed ...
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 ad 7d db c8 00 00 04 00 00 00
Jan  1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 7205673928
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673864
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673872
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673880
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673888
Jan  1 13:59:39 Shark kernel: md: recovery thread woken up ...
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673896
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673904
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673912
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673920
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673928
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: rejecting I/O to offline device
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673936
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] killing request
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673944
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 45 e9 ec d0 00 00 00 20 00 00
Jan  1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 5467925712
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673952
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673960
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
Jan  1 13:59:39 Shark kernel: sd 1:0:0:0: [sdb] CDB: opcode=0x8a 8a 00 00 00 00 01 ad 7d aa 68 00 00 01 08 00 00
Jan  1 13:59:39 Shark kernel: blk_update_request: I/O error, dev sdb, sector 7205661288
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673968
Jan  1 13:59:39 Shark kernel: md: disk0 write error, sector=7205673976
... repeated write errors ...

 

I was able to stop the array and powerdown/reboot. Upon rebooting I expected to find the ARC-1200 to have some information about the incident, but found nothing hunting through its BIOS.

 

I ran smartctl checks on both of the drives in Areca RAIDset, and learned that both were exhibiting some concerning issues.

 

Member Disk1

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 7K3000
Device Model:     Hitachi HDS723030ALA640
Serial Number:    MK0311YHG5xxxx
LU WWN Device Id: 5 000cca 225c26876
Firmware Version: MKAOA3B0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Jan  2 21:13:06 2017 EST
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

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   093   093   016    Pre-fail  Always       -       34
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       83
  3 Spin_Up_Time            0x0007   126   126   024    Pre-fail  Always       -       613 (Average 615)
  4 Start_Stop_Count        0x0012   099   099   000    Old_age   Always       -       4745
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       56
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   133   133   020    Pre-fail  Offline      -       27
  9 Power_On_Hours          0x0012   094   094   000    Old_age   Always       -       47675
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       188
192 Power-Off_Retract_Count 0x0032   096   096   000    Old_age   Always       -       5220
193 Load_Cycle_Count        0x0012   096   096   000    Old_age   Always       -       5220
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 8/38)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       61
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
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.

 

Member Disk2

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 7K3000
Device Model:     Hitachi HDS723030ALA640
Serial Number:    MK0311YHG4xxxx
LU WWN Device Id: 5 000cca 225c1f2ca
Firmware Version: MKAOA3B0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Jan  2 21:13:22 2017 EST
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

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   132   132   054    Pre-fail  Offline      -       94
  3 Spin_Up_Time            0x0007   125   125   024    Pre-fail  Always       -       616 (Average 615)
  4 Start_Stop_Count        0x0012   099   099   000    Old_age   Always       -       4746
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   133   133   020    Pre-fail  Offline      -       27
  9 Power_On_Hours          0x0012   094   094   000    Old_age   Always       -       47652
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       191
192 Power-Off_Retract_Count 0x0032   096   096   000    Old_age   Always       -       5209
193 Load_Cycle_Count        0x0012   096   096   000    Old_age   Always       -       5209
194 Temperature_Celsius     0x0002   222   222   000    Old_age   Always       -       27 (Min/Max 8/36)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 10 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 10 occurred at disk power-on lifetime: 47487 hours (1978 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 08 fc 9d 07  Error: UNC at LBA = 0x079dfc08 = 127794184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 20 08 35 9f 40 08      04:05:26.311  READ FPDMA QUEUED
  60 00 18 08 34 9f 40 08      04:05:26.302  READ FPDMA QUEUED
  60 00 d8 08 33 9f 40 08      04:05:26.293  READ FPDMA QUEUED
  60 00 c8 08 32 9f 40 08      04:05:26.284  READ FPDMA QUEUED
  60 00 f0 08 31 9f 40 08      04:05:26.274  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 47487 hours (1978 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 08 fc 9d 07  Error: WP at LBA = 0x079dfc08 = 127794184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 f0 08 6e 9d 40 08      04:05:20.750  WRITE FPDMA QUEUED
  61 00 e8 08 6d 9d 40 08      04:05:20.745  WRITE FPDMA QUEUED
  61 00 e0 08 6c 9d 40 08      04:05:20.745  WRITE FPDMA QUEUED
  61 00 d8 08 6b 9d 40 08      04:05:20.745  WRITE FPDMA QUEUED
  61 00 d0 08 6a 9d 40 08      04:05:20.741  WRITE FPDMA QUEUED

Error 8 occurred at disk power-on lifetime: 47483 hours (1978 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 08 89 b4 07  Error: UNC at LBA = 0x07b48908 = 129272072

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 f0 08 a4 b4 40 08      00:25:45.071  READ FPDMA QUEUED
  60 00 e8 08 a3 b4 40 08      00:25:45.071  READ FPDMA QUEUED
  60 00 e0 08 a2 b4 40 08      00:25:45.046  READ FPDMA QUEUED
  60 00 d8 08 a1 b4 40 08      00:25:45.046  READ FPDMA QUEUED
  60 00 d0 08 a0 b4 40 08      00:25:45.046  READ FPDMA QUEUED

Error 7 occurred at disk power-on lifetime: 44041 hours (1835 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 08 d8 45 06  Error: UNC at LBA = 0x0645d808 = 105240584

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 78 08 dd 45 40 08   1d+16:31:50.071  READ FPDMA QUEUED
  60 00 70 08 dc 45 40 08   1d+16:31:50.071  READ FPDMA QUEUED
  60 00 68 08 db 45 40 08   1d+16:31:50.071  READ FPDMA QUEUED
  60 00 60 08 da 45 40 08   1d+16:31:50.071  READ FPDMA QUEUED
  60 00 58 08 d9 45 40 08   1d+16:31:50.071  READ FPDMA QUEUED

Error 6 occurred at disk power-on lifetime: 44041 hours (1835 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 ff 09 2a 22 0e  Error: UNC at LBA = 0x0e222a09 = 237120009

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 78 08 2d 22 40 08   1d+15:59:13.488  READ FPDMA QUEUED
  60 00 70 08 2c 22 40 08   1d+15:59:13.488  READ FPDMA QUEUED
  60 00 68 08 2b 22 40 08   1d+15:59:13.488  READ FPDMA QUEUED
  60 00 60 08 2a 22 40 08   1d+15:59:13.488  READ FPDMA QUEUED
  60 00 58 08 29 22 40 08   1d+15:59:13.488  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
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.

 

If you look closely, Member Disk1 you'll see that there are 56 reallocated sectors. Not a good thing but not a disaster. This was checked not more than a month ago, so all of these are new.

 

But Member Disk2 has other problems. There is a single reallocated sector, and another pending sector. But there are several items in the SMART log, the first 2 are very very recent (look at power on hours).

 

The drives have been powered on for over 5 years (physical age probably closer to 6). I am no longer going to keep these in my array - maybe will look to move them into backup service.

 

But the interesting thing, and reason I am posting here, is how the Areca controller reacted. I would have expected that it would have detected the drive issues and logged something. Suppose I had had a parity1 RAID, I would have expected it would have noticed "bad things happening" and dropped one of the drives, leaving the single drive and asking for a replacement for the bad one. I was disappointed, leaving me feeling just a bit shaky as to whether the controller did what it was supposed to in this situation.

 

I happened to have a precleared 6T drive available, and popped it in as parity. The build is nearing completion and it is working fine. It is going considerably faster than with the RAID0 parity pair. For now, the ARC-1200 and its two drives are still installed and idle.

 

I decided to post this as this type of information is hard to come by, and thought someone might find it useful. Even after owning my ARC-1200 for 6 years, this is the first opportunity to witness how it behaves when drives start to fail.

 

Cheers!

Share this post


Link to post

Hi,

 

i have some problem to get the smart informations get work on the unraid web interface

 

in the shell it works great:

 

root@Bunker:~# lsscsi -g
[0:0:0:0]    disk    Sony     Storage Media    PMAP  /dev/sda   /dev/sg0
[1:0:0:0]    disk    Hitachi  HDS5C3030ALA630  R001  /dev/sdb   /dev/sg1
[1:0:0:1]    disk    Hitachi  HUA723030ALA640  R001  /dev/sdc   /dev/sg2
[1:0:0:3]    disk    Seagate  ST4000DM004-2CV1 R001  /dev/sdd   /dev/sg3
[1:0:16:0]   process Areca    RAID controller  R001  -          /dev/sg4
[3:0:0:0]    disk    ATA      Corsair Force GS 5.07  /dev/sde   /dev/sg5
[5:0:0:0]    disk    ATA      Hitachi HDS5C303 A5C0  /dev/sdf   /dev/sg6
[8:0:0:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdg   /dev/sg7
[8:0:1:0]    disk    ATA      ST4000DM004-2CV1 0001  /dev/sdh   /dev/sg8

The Smartctl:

root@Bunker:~# smartctl --all --device=areca,1 /dev/sg4
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.49-unRAID] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 5K3000
Device Model:     Hitachi HDS5C3030ALA630
Serial Number:    MJ1311YNG4KDGA
LU WWN Device Id: 5 000cca 228c212cf
Firmware Version: MEAOA5C0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5700 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Jul 15 11:55:32 2018 CEST
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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                (36667) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 611) minutes.
SCT capabilities:              (0x003d) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   133   133   054    Pre-fail  Offline      -       115
  3 Spin_Up_Time            0x0007   127   127   024    Pre-fail  Always       -       550 (Average 549)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       524
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   132   132   020    Pre-fail  Offline      -       32
  9 Power_On_Hours          0x0012   095   095   000    Old_age   Always       -       38994
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       77
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1105
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       1105
194 Temperature_Celsius     0x0002   150   150   000    Old_age   Always       -       40 (Min/Max 18/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
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.

so i set it up in unRiad

unraid_smart.thumb.png.05dc648fa40d66388fa2d1d869d47aac.png

 

and unRaid get this error

unraid_smart2.thumb.png.d3f1e6a98dc093d1a5f91729799840e9.png

 

any idea to resolve this?

Share this post


Link to post
2 hours ago, chi110r said:

Hi,

 

i have some problem to get the smart informations get work on the unraid web interface

 

in the shell it works great:

 

I am not 100% sure. Looks like you have it set up properly.

 

It may have something to do with the volume name (areca_disk#01_enc#01). I know that the "#" can cause issues.

 

@bonienl might be best to support you on this.

Share this post


Link to post
On 7/15/2018 at 3:13 PM, SSD said:

 

I am not 100% sure. Looks like you have it set up properly.

 

It may have something to do with the volume name (areca_disk#01_enc#01). I know that the "#" can cause issues.

 

@bonienl might be best to support you on this.

yes.. i don't know but the "areca_disk#01_enc#01" is only on the webinterface. on the cli it usese this format "smartctl --all  --device=areca,1/1 /dev/ sg4"

Share this post


Link to post
10 hours ago, chi110r said:

yes.. i don't know but the "areca_disk#01_enc#01" is only on the webinterface. on the cli it usese this format "smartctl --all  --device=areca,1/1 /dev/ sg4"

 

Did you upgrade from an earlier version of unRAID?

 

Earlier versions of smartctl, it used a different format, which may still be stored (see file smart-one.cfg in the /config folder on your flash device). It should look like this (example):

[disk8]
smType="-d areca"
smPort1="1"
smDevice="sdg4"

When you re-apply the settings it should get updated to the new format.

Share this post


Link to post
On 7/18/2018 at 8:20 AM, bonienl said:

 

Did you upgrade from an earlier version of unRAID?

 

Earlier versions of smartctl, it used a different format, which may still be stored (see file smart-one.cfg in the /config folder on your flash device). It should look like this (example):


[disk8]
smType="-d areca"
smPort1="1"
smDevice="sdg4"

When you re-apply the settings it should get updated to the new format.

HI,

 

my config looks like this

# cat /boot/config/smart-one.cfg
[disk2]
smType="-d areca"
hotTemp=""
maxTemp=""
warning=""
critical=""
smPort1="1"
smDevice="sg4"
[disk4]
smType="-d areca"
hotTemp=""
maxTemp=""
warning=""
critical=""
smPort1="2"
smDevice="sg4"
[cache2]
smType=" "
[disk5]
smType="-d areca"
hotTemp=""
maxTemp=""
warning=""
critical=""
smPort1="4"
smDevice="sg4"

 

 

i started with unraid 6.3, i think

Share this post


Link to post

Hi.

 

I am on RC8 and want to use a areca 1880i.

 

Do I just follow the instruction in the first post to get it working with smart and temp reading?

Share this post


Link to post

ok, this is driving me crazy.

 

There is so much information in this thread, but most of it is really old so not sure whats needed to make this work with the new version of unRaid.

 

Can someone please point me in the right direction? JBOD or Passthrough disk in Areca?

 

Any other settings in Areca I need to change?

 

Do I need the 60-persistent-storage.rules?

 

Then I add this to user scipt and run at startup?

cp /boot/60-persistent-storage.rules /lib/udev/rules.d udevadm control --reload-rules udevadm trigger

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.