• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

mdadm with smartmontools

T

tabm0de

n00b
Joined
Jun 22, 2011
Messages
3
Sorry if i posted this in wrong thread.

My question is does anyone have a good configuration for smartd with mdadm?

For some reason my disk keep dropping from the raid when running smartd.
The disks are connected to lsi controllers.
 
That's odd, i am running 2x IBM 1015s LSI chipsets (one in IT mode and one not) with mdadm raid 6. Seems to be working fine with me. Interesting fact though one of the controllers wouldn't do smart till I change distro's from Ubuntu to Openmediavault (debian) now I get full smart readings +1 for OMV its pretty slick.

What os are you using?
 
I have 40+ SATA disks running on lsi sas controllers (serving mdadm raid6) and I monitor the arrays with smartmontools however I do not run smartd. I am using nagios to periodically execute smartctrl for each disk and examine the results of 5 different smart parameters. Also a similar amount of drives for raidz2/3 with lsi controllers and nagios monitoring using smartctl. All LSI SAS controllers are in IT mode.
 
Last edited:
Which type of disks? There were a specific revision of Samsung HD204UJ drives that generated errors when SMART commands were executed during IO.
 
I Thought i remembered it was a series of Seagate disks that showed this behavior. Dropping out of raid during IO and a parallel smart request.
 
omniscence said:
Which type of disks? There were a specific revision of Samsung HD204UJ drives that generated errors when SMART commands were executed during IO.
Click to expand...

I had those at home and found this bug and verified that the new firmware fixed the issue. smartctl should warn of this drive however.

Code: 
jmd0 current # smartctl --all /dev/sdd
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.3-gentoo-jmd0-zfs-0.6.4-git-20150109] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AF)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2HGJDWZ806051
LU WWN Device Id: 5 0024e9 003e82eb2
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 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 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Mon Jan 26 08:30:26 2015 EST

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
http://www.smartmontools.org/wiki/SamsungF4EGBadBlocks

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:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
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:                (20880) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 348) minutes.
SCT capabilities:              (0x003f) 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     0x002f   100   100   051    Pre-fail  Always       -       4
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   067   066   025    Pre-fail  Always       -       10066
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       118
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       32210
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       134
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       79
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       2615
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   059   000    Old_age   Always       -       27 (Min/Max 17/41)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       53
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       121

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 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    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.
 
Litel late reply to you guys,

Basically it doesnt matter what type off disk it is, here is a example of errors from the log.
Code: 
Dec  4 18:37:21 LinuxX kernel: [104319.537398] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply
Dec  4 18:37:26 LinuxX kernel: [104323.951433]  end_device-4:8: mptsas: ioc1: removing sata device: fw_channel 0, fw_id 13, phy 2,sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:37:26 LinuxX kernel: [104323.951439]  phy-4:2: mptsas: ioc1: delete phy 2, phy-obj (0xffff8800373b2400)
Dec  4 18:37:26 LinuxX kernel: [104323.951449]  port-4:8: mptsas: ioc1: delete port 8, sas_addr (0xdd5f3d43c2a49e7f)
Dec  4 18:37:26 LinuxX kernel: [104323.952086] sd 4:0:8:0: [sdr] Synchronizing SCSI cache
Dec  4 18:37:26 LinuxX kernel: [104323.952193] sd 4:0:8:0: [sdr]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:37:26 LinuxX kernel: [104323.952279] scsi target4:0:8: mptsas: ioc1: delete device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:37:54 LinuxX kernel: [104352.024931] mptsas: ioc1: attaching sata device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:37:54 LinuxX kernel: [104352.037384] scsi 4:0:9:0: Direct-Access     ATA      WDC WD20EARS-00S 0A80 PQ: 0 ANSI: 5
Dec  4 18:37:54 LinuxX kernel: [104352.039178] sd 4:0:9:0: Attached scsi generic sg12 type 0
Dec  4 18:37:54 LinuxX kernel: [104352.040162] sd 4:0:9:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec  4 18:37:54 LinuxX kernel: [104352.069608] sd 4:0:9:0: [sdl] Write Protect is off
Dec  4 18:37:54 LinuxX kernel: [104352.069613] sd 4:0:9:0: [sdl] Mode Sense: 73 00 00 08
Dec  4 18:37:54 LinuxX kernel: [104352.081222] sd 4:0:9:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec  4 18:37:54 LinuxX kernel: [104352.133673]  sdl:
Dec  4 18:37:54 LinuxX kernel: [104352.197300] sd 4:0:9:0: [sdl] Attached SCSI disk
Dec  4 18:38:25 LinuxX kernel: [104382.539445] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply
Dec  4 18:38:29 LinuxX kernel: [104386.804706]  end_device-4:9: mptsas: ioc1: removing sata device: fw_channel 0, fw_id 13, phy 2,sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:38:29 LinuxX kernel: [104386.804709]  phy-4:2: mptsas: ioc1: delete phy 2, phy-obj (0xffff8800373b2400)
Dec  4 18:38:29 LinuxX kernel: [104386.804715]  port-4:9: mptsas: ioc1: delete port 9, sas_addr (0xdd5f3d43c2a49e7f)
Dec  4 18:38:29 LinuxX kernel: [104386.805155] sd 4:0:9:0: [sdl] Synchronizing SCSI cache
Dec  4 18:38:29 LinuxX kernel: [104386.805180] sd 4:0:9:0: [sdl]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:38:29 LinuxX kernel: [104386.805219] scsi target4:0:9: mptsas: ioc1: delete device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:38:34 LinuxX kernel: [104391.676303] mptsas: ioc1: attaching sata device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:38:34 LinuxX kernel: [104391.688477] scsi 4:0:10:0: Direct-Access     ATA      WDC WD20EARS-00S 0A80 PQ: 0 ANSI: 5
Dec  4 18:38:34 LinuxX kernel: [104391.690350] sd 4:0:10:0: Attached scsi generic sg12 type 0
Dec  4 18:38:34 LinuxX kernel: [104391.691273] sd 4:0:10:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec  4 18:38:34 LinuxX kernel: [104391.720740] sd 4:0:10:0: [sdl] Write Protect is off
Dec  4 18:38:34 LinuxX kernel: [104391.720745] sd 4:0:10:0: [sdl] Mode Sense: 73 00 00 08
Dec  4 18:38:34 LinuxX kernel: [104391.732301] sd 4:0:10:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec  4 18:38:34 LinuxX kernel: [104391.788240]  sdl:
Dec  4 18:38:34 LinuxX kernel: [104391.852270] sd 4:0:10:0: [sdl] Attached SCSI disk
Dec  4 18:39:59 LinuxX kernel: [104476.850893] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply
Dec  4 18:40:00 LinuxX kernel: [104478.117232]  end_device-4:10: mptsas: ioc1: removing sata device: fw_channel 0, fw_id 13, phy 2,sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:40:00 LinuxX kernel: [104478.117238]  phy-4:2: mptsas: ioc1: delete phy 2, phy-obj (0xffff8800373b2400)
Dec  4 18:40:00 LinuxX kernel: [104478.117248]  port-4:10: mptsas: ioc1: delete port 10, sas_addr (0xdd5f3d43c2a49e7f)
Dec  4 18:40:00 LinuxX kernel: [104478.118042] sd 4:0:10:0: [sdl] Synchronizing SCSI cache
Dec  4 18:40:00 LinuxX kernel: [104478.118092] sd 4:0:10:0: [sdl]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:00 LinuxX kernel: [104478.118142] scsi target4:0:10: mptsas: ioc1: delete device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:40:01 LinuxX /USR/SBIN/CRON[29561]: (root) CMD (vnstat -u -i eth0 >> /dev/null 2>&1)
Dec  4 18:40:03 LinuxX kernel: [104481.088104] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.088273] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.088456] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.088643] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.088828] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.089008] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:03 LinuxX kernel: [104481.089199] mptbase: ioc1: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done
Dec  4 18:40:04 LinuxX kernel: [104481.586951] mptbase: ioc1: LogInfo(0x31130000): Originator={PL}, Code={IO Not Yet Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
Dec  4 18:40:04 LinuxX kernel: [104481.586986] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.586991] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.587004] sd 4:0:3:0: [sdm] CDB: Write(10): 2a 00 00 00 00 08 00 00 01 00
Dec  4 18:40:04 LinuxX kernel: [104481.587130] end_request: I/O error, dev sdm, sector 8
Dec  4 18:40:04 LinuxX kernel: [104481.587198] md: super_written gets error=-5, uptodate=0
Dec  4 18:40:04 LinuxX kernel: [104481.587203] md/raid:md1: Disk failure on sdm, disabling device.
Dec  4 18:40:04 LinuxX kernel: [104481.587204] md/raid:md1: Operation continuing on 8 devices.
Dec  4 18:40:04 LinuxX kernel: [104481.589342]  end_device-4:3: mptsas: ioc1: removing sata device: fw_channel 0, fw_id 14, phy 3,sas_addr 0x1f605d2e6d7e4c4e
Dec  4 18:40:04 LinuxX kernel: [104481.589350]  phy-4:3: mptsas: ioc1: delete phy 3, phy-obj (0xffff8800373ae400)
Dec  4 18:40:04 LinuxX kernel: [104481.589361]  port-4:3: mptsas: ioc1: delete port 3, sas_addr (0x1f605d2e6d7e4c4e)
Dec  4 18:40:04 LinuxX kernel: [104481.589412] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589414] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.589416] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 5c 00
Dec  4 18:40:04 LinuxX kernel: [104481.589419] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589421] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.589423] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 5c 00 00 03 e0 00
Dec  4 18:40:04 LinuxX kernel: [104481.589428] end_request: I/O error, dev sdm, sector 3022478336
Dec  4 18:40:04 LinuxX kernel: [104481.589430] md/raid:md1: read error not correctable (sector 3022478336 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589432] md/raid:md1: read error not correctable (sector 3022478344 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589433] md/raid:md1: read error not correctable (sector 3022478352 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589435] md/raid:md1: read error not correctable (sector 3022478360 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589436] md/raid:md1: read error not correctable (sector 3022478368 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589438] md/raid:md1: read error not correctable (sector 3022478376 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589439] md/raid:md1: read error not correctable (sector 3022478384 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589440] md/raid:md1: read error not correctable (sector 3022478392 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589442] md/raid:md1: read error not correctable (sector 3022478400 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589443] md/raid:md1: read error not correctable (sector 3022478408 on sdm).
Dec  4 18:40:04 LinuxX kernel: [104481.589469]  00 04 00 00
Dec  4 18:40:04 LinuxX kernel: [104481.589471] end_request: I/O error, dev sdm, sector 3022478336
Dec  4 18:40:04 LinuxX kernel: [104481.589482] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589483] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.589484] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 5f e0 00 00 20 00
Dec  4 18:40:04 LinuxX kernel: [104481.589487] end_request: I/O error, dev sdm, sector 3022479328
Dec  4 18:40:04 LinuxX kernel: [104481.589492] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589493] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.589494] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 60 00 00 00 e8 00
Dec  4 18:40:04 LinuxX kernel: [104481.589497] end_request: I/O error, dev sdm, sector 3022479360
Dec  4 18:40:04 LinuxX kernel: [104481.589512] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589513] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:04 LinuxX kernel: [104481.589514] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 60 e8 00 02 18 00
Dec  4 18:40:04 LinuxX kernel: [104481.589516] end_request: I/O error, dev sdm, sector 3022479592
Dec  4 18:40:04 LinuxX kernel: [104481.589550] sd 4:0:3:0: [sdm] Unhandled error code
Dec  4 18:40:04 LinuxX kernel: [104481.589552] sd 4:0:3:0: [sdm] CDB: Read(10): 28 00 b4 27 63 00 00 01 00 00
Dec  4 18:40:04 LinuxX kernel: [104481.589554] end_request: I/O error, dev sdm, sector 3022480128
Dec  4 18:40:04 LinuxX kernel: [104481.590033] sd 4:0:3:0: [sdm] Synchronizing SCSI cache
Dec  4 18:40:04 LinuxX kernel: [104481.590051] sd 4:0:3:0: [sdm]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec  4 18:40:07 LinuxX kernel: [104484.679312] mptsas: ioc1: attaching sata device: fw_channel 0, fw_id 13, phy 2, sas_addr 0xdd5f3d43c2a49e7f
Dec  4 18:40:07 LinuxX kernel: [104484.691777] scsi 4:0:11:0: Direct-Access     ATA      WDC WD20EARS-00S 0A80 PQ: 0 ANSI: 5
Dec  4 18:40:07 LinuxX kernel: [104484.693618] sd 4:0:11:0: Attached scsi generic sg12 type 0
Dec  4 18:40:07 LinuxX kernel: [104484.695022] mptsas: ioc1: attaching sata device: fw_channel 0, fw_id 14, phy 3, sas_addr 0x1f605d2e6d7e4c4e
Dec  4 18:40:07 LinuxX kernel: [104484.695805] sd 4:0:11:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec  4 18:40:07 LinuxX kernel: [104484.697678] scsi 4:0:12:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32 PQ: 0 ANSI: 5
Dec  4 18:40:07 LinuxX kernel: [104484.699516] sd 4:0:12:0: Attached scsi generic sg13 type 0
Dec  4 18:40:07 LinuxX kernel: [104484.700626] sd 4:0:12:0: [sdr] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Dec  4 18:40:07 LinuxX kernel: [104484.725479] sd 4:0:11:0: [sdl] Write Protect is off
Dec  4 18:40:07 LinuxX kernel: [104484.725483] sd 4:0:11:0: [sdl] Mode Sense: 73 00 00 08
Dec  4 18:40:07 LinuxX kernel: [104484.737176] sd 4:0:11:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec  4 18:40:07 LinuxX kernel: [104484.754716] sd 4:0:12:0: [sdr] Write Protect is off
Dec  4 18:40:07 LinuxX kernel: [104484.754720] sd 4:0:12:0: [sdr] Mode Sense: 73 00 00 08
Dec  4 18:40:07 LinuxX kernel: [104484.766438] sd 4:0:12:0: [sdr] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec  4 18:40:07 LinuxX kernel: [104484.787173]  sdl:
Dec  4 18:40:07 LinuxX kernel: [104484.844149]  sdr:
Dec  4 18:40:07 LinuxX kernel: [104484.851102] sd 4:0:11:0: [sdl] Attached SCSI disk
Dec  4 18:40:07 LinuxX kernel: [104484.918884] sd 4:0:12:0: [sdr] Attached SCSI disk
I have surfed test like 4-5 disk that gave error and there were nothing wrong with them, even all my new 4tb disk had the same problems.

I have two lsi cards, LSISAS2008 and LSISAS1068E.

The 4tb diskes are connected to the lsi sas 2008 since 1068e cant take them and 2tb disk are connected to lsi sas 1068e, but as i said same problem with both cards as soon i start smartd. I heard some thing about "periodic" but didnt really get that to work.
 
check source code mpi_log.h for mpt2sas kernel module, which explain everything.
http://www.cs.fsu.edu/~baker/device...ers/message/fusion/lsi/mpi_log_sas.h?v=2.6.25


your error.
LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done

LogInfo(0x31110d00) means
MPI_IOCLOGINFO_TYPE_SAS (3) >> ( 0x30000000)
PL_LOGINFO_CODE_RESET >> (0x00110000)
IOC_LOGINFO_ORIGINATOR_PL >> (0x01000000)
PL_LOGINFO_SUB_CODE_SATA_LINK_DOWN >> (0x00000D00)

your card reporting sending RESET to Drives, due on Input/Output error that triggered by drive SATA link was down

most the issue, is Drives(HD) do not have stable power from PSU or bad cable.
check Drives power cables, sata cables(or minisas cable) , and PSU power especially on 12V line (could be PSU does not provide enough current)
 
Last edited:
Interesting. I wonder if the same behavior is in a more recent kernel. It's been several years since I have used a 2.6.X kernel.
 
drescherjm said:
Interesting. I wonder if the same behavior is in a more recent kernel. It's been several years since I have used a 2.6.X kernel.
Click to expand...

two my systems are good on kernel 3.10.X with ZoL on sas2 expander.
I just replaced one bad drive last week, honestly quite a surprised since nothing bad happend to kernel (just logging many errors, and zfs mark as a failed drive that put my raidz2 into degraded) due on falied drve

happened with one old AIC case with 2U PSU with 14 drives. that throw many kernel error with reseting some certain harddrive locations .

I digged to kernel source code for mpt2sas, (THANKS for open souce)
and know what the kernel complaining...

actually kernel will try to reset many time, when sense connection is down.... bombarding kernel log with many mostly identical error from mpt2sas kernel module.

I figure out at the end that the PSU was not give enough current. this is 500W PSU:D...
 
You must log in or register to reply here.
Back
Top