mksm

I did that earlier and will try it again tomorrow. I can't easily replace the cables because they're not "regular" SATA cables. They're similar to these: https://www.amazon.com/3WARE-Cable-Multi-lane-Internal-SFF-8087/dp/B000FBYS2U. The drive is inside an ICYDOCK cage. There's another drive in there that's working just fine. PSU could be failing perhaps? It's a 4+ year old 420W Seventeam PSU. So many things that can go wrong. *sigh*. I'll post updates. Thanks for the help so far.

@trurl, thanks! No, it's still green but stats are all weird. If I stop the array it says the disk is missing and doesn't show it anymore. smartctl doesn't work either: root@Atomsk:~# smartctl -a /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: W Product: IaoR׬Ny=] Revision: 5^ User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 3320169920 bytes Lowest aligned LBA: 14896 scsiModePageOffset: raw_curr too small, offset=198 resp_len=173 bd_len=194 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Howdy! I'm running unRAID 5.0.5 and one of the drives keeps going offline after being used for a while. If I do a reboot it comes back online and I can start the array without any issues. Faulty drive is /dev/sdg. I'm running transmission plugin as well and the torrent I'm fetching is trying to write to this disk. SMART: smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00DC0B0 Serial Number: WD-WCC1T0551971 LU WWN Device Id: 5 0014ee 208224f0b Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical 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 Apr 27 14:02:25 2017 BRT 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: (40980) 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: ( 411) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x70b5) SCT Status 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 184 179 021 Pre-fail Always - 5791 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 642 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 10365 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 45 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 162 162 000 Old_age Always - 114294 194 Temperature_Celsius 0x0022 121 108 000 Old_age Always - 29 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 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% 10150 - 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. syslog around the time it went missing: Apr 27 13:38:52 Atomsk avahi-daemon[2249]: Received response from host 192.168.1.10 with invalid source port 32788 on interface 'eth0.0' Apr 27 13:39:52 Atomsk last message repeated 2 times Apr 27 13:41:21 Atomsk last message repeated 3 times Apr 27 13:42:51 Atomsk last message repeated 3 times Apr 27 13:44:20 Atomsk last message repeated 3 times Apr 27 13:45:50 Atomsk last message repeated 3 times Apr 27 13:46:50 Atomsk last message repeated 2 times Apr 27 13:47:01 Atomsk crond[1105]: exit status 1 from user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Apr 27 13:47:01 Atomsk kernel: crond[13656]: segfault at 4001e51c ip 4001e51c sp bf9d7324 error 15 in ld-2.11.1.so[4001e000+1000] Apr 27 13:47:20 Atomsk avahi-daemon[2249]: Received response from host 192.168.1.10 with invalid source port 32788 on interface 'eth0.0' Apr 27 13:48:20 Atomsk last message repeated 2 times Apr 27 13:49:50 Atomsk last message repeated 3 times Apr 27 13:50:50 Atomsk last message repeated 2 times Apr 27 13:51:08 Atomsk kernel: sd 2:0:6:0: [sdh] command ca478b40 timed out Apr 27 13:51:08 Atomsk kernel: sd 2:0:6:0: [sdh] command ca4780c0 timed out Apr 27 13:51:08 Atomsk kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2 Apr 27 13:51:08 Atomsk kernel: sas: trying to find task 0xf7453c00 Apr 27 13:51:08 Atomsk kernel: sas: sas_scsi_find_task: aborting task 0xf7453c00 Apr 27 13:51:08 Atomsk kernel: sas: sas_scsi_find_task: task 0xf7453c00 is aborted Apr 27 13:51:08 Atomsk kernel: sas: sas_eh_handle_sas_errors: task 0xf7453c00 is aborted Apr 27 13:51:08 Atomsk kernel: sas: trying to find task 0xf7453900 Apr 27 13:51:08 Atomsk kernel: sas: sas_scsi_find_task: aborting task 0xf7453900 Apr 27 13:51:08 Atomsk kernel: sas: sas_scsi_find_task: task 0xf7453900 is aborted Apr 27 13:51:08 Atomsk kernel: sas: sas_eh_handle_sas_errors: task 0xf7453900 is aborted Apr 27 13:51:08 Atomsk kernel: sas: ata9: end_device-2:6: cmd error handler Apr 27 13:51:08 Atomsk kernel: sas: ata3: end_device-2:0: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata4: end_device-2:1: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata5: end_device-2:2: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata6: end_device-2:3: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata7: end_device-2:4: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata8: end_device-2:5: dev error handler Apr 27 13:51:08 Atomsk kernel: sas: ata9: end_device-2:6: dev error handler Apr 27 13:51:08 Atomsk kernel: ata9.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen Apr 27 13:51:08 Atomsk kernel: ata9.00: failed command: READ FPDMA QUEUED Apr 27 13:51:08 Atomsk kernel: ata9.00: cmd 60/00:00:00:8d:9d/01:00:05:00:00/40 tag 0 ncq 131072 in Apr 27 13:51:08 Atomsk kernel: res 40/00:04:40:00:3c/00:00:1b:01:00/40 Emask 0x4 (timeout) Apr 27 13:51:08 Atomsk kernel: ata9.00: status: { DRDY } Apr 27 13:51:08 Atomsk kernel: ata9.00: failed command: READ FPDMA QUEUED Apr 27 13:51:08 Atomsk kernel: ata9.00: cmd 60/00:00:00:8e:9d/01:00:05:00:00/40 tag 1 ncq 131072 in Apr 27 13:51:08 Atomsk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 13:51:08 Atomsk kernel: ata9.00: status: { DRDY } Apr 27 13:51:08 Atomsk kernel: ata9: hard resetting link Apr 27 13:51:10 Atomsk kernel: sas: sas_form_port: phy6 belongs to port6 already(1)! Apr 27 13:51:12 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[6]:rc= 0 Apr 27 13:51:12 Atomsk kernel: ata9.00: configured for UDMA/133 Apr 27 13:51:12 Atomsk kernel: ata9.00: device reported invalid CHS sector 0 Apr 27 13:51:12 Atomsk kernel: ata9: EH complete Apr 27 13:51:12 Atomsk kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Apr 27 13:51:20 Atomsk avahi-daemon[2249]: Received response from host 192.168.1.10 with invalid source port 32788 on interface 'eth0.0' Apr 27 13:51:42 Atomsk kernel: sd 2:0:6:0: [sdh] command ca478b40 timed out Apr 27 13:51:45 Atomsk kernel: sd 2:0:5:0: [sdg] command ce7da300 timed out Apr 27 13:51:45 Atomsk kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2 Apr 27 13:51:45 Atomsk kernel: sas: trying to find task 0xd4b3d000 Apr 27 13:51:45 Atomsk kernel: sas: sas_scsi_find_task: aborting task 0xd4b3d000 Apr 27 13:51:45 Atomsk kernel: sas: sas_scsi_find_task: task 0xd4b3d000 is aborted Apr 27 13:51:45 Atomsk kernel: sas: sas_eh_handle_sas_errors: task 0xd4b3d000 is aborted Apr 27 13:51:45 Atomsk kernel: sas: trying to find task 0xd4b3dd00 Apr 27 13:51:45 Atomsk kernel: sas: sas_scsi_find_task: aborting task 0xd4b3dd00 Apr 27 13:51:45 Atomsk kernel: sas: sas_scsi_find_task: task 0xd4b3dd00 is aborted Apr 27 13:51:45 Atomsk kernel: sas: sas_eh_handle_sas_errors: task 0xd4b3dd00 is aborted Apr 27 13:51:45 Atomsk kernel: sas: ata9: end_device-2:6: cmd error handler Apr 27 13:51:45 Atomsk kernel: sas: ata8: end_device-2:5: cmd error handler Apr 27 13:51:45 Atomsk kernel: sas: ata3: end_device-2:0: dev error handler Apr 27 13:51:45 Atomsk kernel: sas: ata4: end_device-2:1: dev error handler Apr 27 13:51:45 Atomsk kernel: sas: ata5: end_device-2:2: dev error handler Apr 27 13:51:45 Atomsk kernel: sas: ata6: end_device-2:3: dev error handler Apr 27 13:51:45 Atomsk kernel: sas: ata7: end_device-2:4: dev error handler Apr 27 13:51:45 Atomsk kernel: sas: ata8: end_device-2:5: dev error handler Apr 27 13:51:45 Atomsk kernel: ata8.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen Apr 27 13:51:45 Atomsk kernel: ata8.00: failed command: READ FPDMA QUEUED Apr 27 13:51:45 Atomsk kernel: ata8.00: cmd 60/08:00:40:00:60/00:00:48:00:00/40 tag 0 ncq 4096 in Apr 27 13:51:45 Atomsk kernel: res 40/00:04:40:00:4c/00:00:72:00:00/40 Emask 0x4 (timeout) Apr 27 13:51:45 Atomsk kernel: ata8.00: status: { DRDY } Apr 27 13:51:45 Atomsk kernel: ata8: hard resetting link Apr 27 13:51:45 Atomsk kernel: sas: ata9: end_device-2:6: dev error handler Apr 27 13:51:47 Atomsk kernel: ata9.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6 frozen Apr 27 13:51:47 Atomsk kernel: ata9.00: failed command: READ FPDMA QUEUED Apr 27 13:51:47 Atomsk kernel: ata9.00: cmd 60/00:00:00:8d:9d/01:00:05:00:00/40 tag 1 ncq 131072 in Apr 27 13:51:47 Atomsk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 13:51:47 Atomsk kernel: ata9.00: status: { DRDY } Apr 27 13:51:47 Atomsk kernel: ata9: hard resetting link Apr 27 13:51:48 Atomsk kernel: sas: sas_form_port: phy6 belongs to port6 already(1)! Apr 27 13:51:48 Atomsk kernel: mvsas 0000:01:00.0: Phy5 : No sig fis Apr 27 13:51:48 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[5]:rc= 0 Apr 27 13:51:49 Atomsk kernel: sas: sas_form_port: phy5 belongs to port5 already(1)! Apr 27 13:51:49 Atomsk avahi-daemon[2249]: Received response from host 192.168.1.10 with invalid source port 32788 on interface 'eth0.0' Apr 27 13:51:50 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[6]:rc= 0 Apr 27 13:51:50 Atomsk kernel: ata9.00: configured for UDMA/133 Apr 27 13:51:50 Atomsk kernel: ata9.00: device reported invalid CHS sector 0 Apr 27 13:51:50 Atomsk kernel: ata9: EH complete Apr 27 13:51:54 Atomsk kernel: ata8.00: qc timeout (cmd 0x27) Apr 27 13:51:54 Atomsk kernel: ata8.00: failed to read native max address (err_mask=0x4) Apr 27 13:51:54 Atomsk kernel: ata8.00: HPA support seems broken, skipping HPA handling Apr 27 13:51:54 Atomsk kernel: ata8.00: revalidation failed (errno=-5) Apr 27 13:51:54 Atomsk kernel: ata8: hard resetting link Apr 27 13:51:56 Atomsk kernel: mvsas 0000:01:00.0: Phy5 : No sig fis Apr 27 13:51:57 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[5]:rc= 0 Apr 27 13:52:00 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1957:Release slot [0] tag[0], task [f7453300]: Apr 27 13:52:00 Atomsk kernel: sas: sas_ata_task_done: SAS error 8a Apr 27 13:52:00 Atomsk kernel: ata8.00: failed to set xfermode (err_mask=0x11) Apr 27 13:52:00 Atomsk kernel: ata8.00: limiting speed to UDMA/133:PIO3 Apr 27 13:52:00 Atomsk kernel: sas: sas_form_port: phy5 belongs to port5 already(1)! Apr 27 13:52:02 Atomsk kernel: ata8: hard resetting link Apr 27 13:52:07 Atomsk kernel: ata8.00: qc timeout (cmd 0xec) Apr 27 13:52:07 Atomsk kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x5) Apr 27 13:52:07 Atomsk kernel: ata8.00: revalidation failed (errno=-5) Apr 27 13:52:07 Atomsk kernel: ata8.00: disabled Apr 27 13:52:07 Atomsk kernel: ata8: hard resetting link Apr 27 13:52:09 Atomsk kernel: mvsas 0000:01:00.0: Phy5 : No sig fis Apr 27 13:52:10 Atomsk kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[5]:rc= 0 Apr 27 13:52:10 Atomsk kernel: ata8: EH complete Apr 27 13:52:10 Atomsk kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Unhandled error code Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Apr 27 13:52:10 Atomsk kernel: Result: hostbyte=0x04 driverbyte=0x00 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] CDB: Apr 27 13:52:10 Atomsk kernel: cdb[0]=0x88: 88 00 00 00 00 00 48 60 00 40 00 00 00 08 00 00 Apr 27 13:52:10 Atomsk kernel: end_request: I/O error, dev sdg, sector 1214251072 Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1214251008 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Unhandled error code Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Apr 27 13:52:10 Atomsk kernel: Result: hostbyte=0x04 driverbyte=0x00 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] CDB: Apr 27 13:52:10 Atomsk kernel: cdb[0]=0x88: 88 00 00 00 00 00 48 64 00 40 00 00 00 08 00 00 Apr 27 13:52:10 Atomsk kernel: end_request: I/O error, dev sdg, sector 1214513216 Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1214513152 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] READ CAPACITY(16) failed Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Apr 27 13:52:10 Atomsk kernel: Result: hostbyte=0x04 driverbyte=0x00 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Sense not available. Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Unhandled error code Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Apr 27 13:52:10 Atomsk kernel: Result: hostbyte=0x04 driverbyte=0x00 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] CDB: Apr 27 13:52:10 Atomsk kernel: cdb[0]=0x88: 88 00 00 00 00 00 48 68 00 40 00 00 00 08 00 00 Apr 27 13:52:10 Atomsk kernel: end_request: I/O error, dev sdg, sector 1214775360 Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1214775296 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] READ CAPACITY failed Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Apr 27 13:52:10 Atomsk kernel: Result: hostbyte=0x04 driverbyte=0x00 Apr 27 13:52:10 Atomsk kernel: sd 2:0:5:0: [sdg] Sense not available. Apr 27 13:52:10 Atomsk kernel: sdg: detected capacity change from 3000592982016 to 0 Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1215037440 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1215299584 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1215561728 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1215823872 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block Apr 27 13:52:10 Atomsk kernel: md: disk4 read error, sector=1216086016 Apr 27 13:52:10 Atomsk kernel: REISERFS warning (device md4): sh-2029: %%s: bitmap block (#%%u) reading failed reiserfs_read_bitmap_block: reiserfs_read_bitmap_block (... 30k similar lines ...) Apr 27 13:52:14 Atomsk kernel: REISERFS error (device md4): clm-6001 reiserfs_truncate_file: grab_tail_page failed -5 Apr 27 13:52:14 Atomsk kernel: REISERFS (device md4): Remounting filesystem read-only Apr 27 13:52:14 Atomsk shfs/user: shfs_write: write: (5) Input/output error Apr 27 13:52:14 Atomsk kernel: md: disk4 read error, sector=665085016 Apr 27 13:52:14 Atomsk kernel: REISERFS error (device md4): clm-6001 reiserfs_truncate_file: grab_tail_page failed -5 Apr 27 13:52:14 Atomsk shfs/user: shfs_write: write: (5) Input/output error Apr 27 13:52:14 Atomsk kernel: md: disk4 read error, sector=649087040 Apr 27 13:52:14 Atomsk kernel: REISERFS error (device md4): clm-6001 reiserfs_truncate_file: grab_tail_page failed -5 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=5462438240 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=368 Apr 27 13:52:14 Atomsk kernel: Buffer I/O error on device md4, logical block 46 Apr 27 13:52:14 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=376 Apr 27 13:52:14 Atomsk kernel: Buffer I/O error on device md4, logical block 47 Apr 27 13:52:14 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=384 Apr 27 13:52:14 Atomsk kernel: Buffer I/O error on device md4, logical block 48 Apr 27 13:52:14 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=392 Apr 27 13:52:14 Atomsk kernel: Buffer I/O error on device md4, logical block 49 Apr 27 13:52:14 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:14 Atomsk kernel: md: disk4 write error, sector=400 Apr 27 13:52:14 Atomsk kernel: Buffer I/O error on device md4, logical block 50 Apr 27 13:52:14 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk avahi-daemon[2249]: Received response from host 192.168.1.10 with invalid source port 32788 on interface 'eth0.0' Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438248 Apr 27 13:52:19 Atomsk kernel: Buffer I/O error on device md4, logical block 682804781 Apr 27 13:52:19 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438256 Apr 27 13:52:19 Atomsk kernel: Buffer I/O error on device md4, logical block 682804782 Apr 27 13:52:19 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438264 Apr 27 13:52:19 Atomsk kernel: Buffer I/O error on device md4, logical block 682804783 Apr 27 13:52:19 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438272 Apr 27 13:52:19 Atomsk kernel: Buffer I/O error on device md4, logical block 682804784 Apr 27 13:52:19 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438280 Apr 27 13:52:19 Atomsk kernel: Buffer I/O error on device md4, logical block 682804785 Apr 27 13:52:19 Atomsk kernel: lost page write due to I/O error on md4 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438288 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438296 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438304 Apr 27 13:52:19 Atomsk kernel: md: disk4 write error, sector=5462438312 I checked SATA/power cables and all seems fine. All other drives are working as expected. Any thoughts? Thanks in advance. Best, mksm