LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 04-02-2014, 01:52 AM   #1
Sidus
LQ Newbie
 
Registered: Apr 2014
Posts: 2

Rep: Reputation: Disabled
RAID5 fails with nForce controller


Hi!

I've recently set up a RAID5 data disk under Ubuntu, running on an old Striker II Extreme m/b running the nForce 790i chipset.

Whenever I put the RAID under pressure, I lose 2 disks simultaneously. This have been happening multiple times a day for as long as I've been trying to resolve this issue.

Syslog produces the following:
Code:
Mar 30 02:16:30 ithaca kernel: [160137.020022] ata4: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1
Mar 30 02:16:30 ithaca kernel: [160137.020029] ata4: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0
Mar 30 02:16:30 ithaca kernel: [160137.020029]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Mar 30 02:16:30 ithaca kernel: [160137.020033] ata4: ATA_REG 0x40 ERR_REG 0x0
Mar 30 02:16:30 ithaca kernel: [160137.020035] ata4: tag : dhfis dmafis sdbfis sactive
Mar 30 02:16:30 ithaca kernel: [160137.020038] ata4: tag 0x0: 0 0 0 1  
Mar 30 02:16:30 ithaca kernel: [160137.020047] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
Mar 30 02:16:30 ithaca kernel: [160137.020051] ata4.00: failed command: WRITE FPDMA QUEUED
Mar 30 02:16:30 ithaca kernel: [160137.020056] ata4.00: cmd 61/01:00:08:20:00/00:00:00:00:00/40 tag 0 ncq 512 out
Mar 30 02:16:30 ithaca kernel: [160137.020056]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:16:30 ithaca kernel: [160137.020060] ata4.00: status: { DRDY }
Mar 30 02:16:30 ithaca kernel: [160137.020064] ata4: hard resetting link
Mar 30 02:16:30 ithaca kernel: [160137.020067] ata4: nv: skipping hardreset on occupied port
Mar 30 02:16:31 ithaca kernel: [160137.488024] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:16:36 ithaca kernel: [160142.496023] ata4.00: qc timeout (cmd 0x27)
Mar 30 02:16:36 ithaca kernel: [160142.496029] ata4.00: failed to read native max address (err_mask=0x4)
Mar 30 02:16:36 ithaca kernel: [160142.496031] ata4.00: HPA support seems broken, skipping HPA handling
Mar 30 02:16:36 ithaca kernel: [160142.496034] ata4.00: revalidation failed (errno=-5)
Mar 30 02:16:36 ithaca kernel: [160142.496040] ata4: hard resetting link
Mar 30 02:16:36 ithaca kernel: [160142.496042] ata4: nv: skipping hardreset on occupied port
Mar 30 02:16:36 ithaca kernel: [160142.964027] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:16:36 ithaca kernel: [160142.988144] ata4.00: configured for UDMA/133
Mar 30 02:16:36 ithaca kernel: [160142.988150] ata4.00: device reported invalid CHS sector 0
Mar 30 02:16:36 ithaca kernel: [160142.988157] ata4: EH complete
Mar 30 02:17:00 ithaca kernel: [160167.132029] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 30 02:17:00 ithaca kernel: [160167.132035] ata3.00: failed command: FLUSH CACHE EXT
Mar 30 02:17:00 ithaca kernel: [160167.132041] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 30 02:17:00 ithaca kernel: [160167.132041]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:17:00 ithaca kernel: [160167.132045] ata3.00: status: { DRDY }
Mar 30 02:17:00 ithaca kernel: [160167.132050] ata3: hard resetting link
Mar 30 02:17:00 ithaca kernel: [160167.132052] ata3: nv: skipping hardreset on occupied port
Mar 30 02:17:01 ithaca kernel: [160167.600026] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:17:01 ithaca CRON[3223]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 30 02:17:06 ithaca kernel: [160172.608023] ata3.00: qc timeout (cmd 0x27)
Mar 30 02:17:06 ithaca kernel: [160172.608028] ata3.00: failed to read native max address (err_mask=0x4)
Mar 30 02:17:06 ithaca kernel: [160172.608031] ata3.00: HPA support seems broken, skipping HPA handling
Mar 30 02:17:06 ithaca kernel: [160172.608034] ata3.00: revalidation failed (errno=-5)
Mar 30 02:17:06 ithaca kernel: [160172.608040] ata3: hard resetting link
Mar 30 02:17:06 ithaca kernel: [160172.608042] ata3: nv: skipping hardreset on occupied port
Mar 30 02:17:06 ithaca kernel: [160173.076053] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:17:06 ithaca kernel: [160173.100140] ata3.00: configured for UDMA/133
Mar 30 02:17:06 ithaca kernel: [160173.100145] ata3.00: retrying FLUSH 0xea Emask 0x4
Mar 30 02:17:07 ithaca kernel: [160174.044023] ata4: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1
Mar 30 02:17:07 ithaca kernel: [160174.044029] ata4: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0
Mar 30 02:17:07 ithaca kernel: [160174.044029]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Mar 30 02:17:07 ithaca kernel: [160174.044033] ata4: ATA_REG 0x40 ERR_REG 0x0
Mar 30 02:17:07 ithaca kernel: [160174.044036] ata4: tag : dhfis dmafis sdbfis sactive
Mar 30 02:17:07 ithaca kernel: [160174.044038] ata4: tag 0x0: 0 0 0 1  
Mar 30 02:17:07 ithaca kernel: [160174.044048] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
Mar 30 02:17:07 ithaca kernel: [160174.044051] ata4.00: failed command: WRITE FPDMA QUEUED
Mar 30 02:17:07 ithaca kernel: [160174.044057] ata4.00: cmd 61/01:00:08:20:00/00:00:00:00:00/40 tag 0 ncq 512 out
Mar 30 02:17:07 ithaca kernel: [160174.044057]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:17:07 ithaca kernel: [160174.044061] ata4.00: status: { DRDY }
Mar 30 02:17:07 ithaca kernel: [160174.044065] ata4: hard resetting link
Mar 30 02:17:07 ithaca kernel: [160174.044068] ata4: nv: skipping hardreset on occupied port
Mar 30 02:17:08 ithaca kernel: [160174.512031] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:17:08 ithaca kernel: [160174.536143] ata4.00: configured for UDMA/133
Mar 30 02:17:08 ithaca kernel: [160174.536149] ata4.00: device reported invalid CHS sector 0
Mar 30 02:17:08 ithaca kernel: [160174.536165] ata4: EH complete
Mar 30 02:17:21 ithaca kernel: [160188.100019] ata3.00: qc timeout (cmd 0xea)
Mar 30 02:17:21 ithaca kernel: [160188.100025] ata3.00: FLUSH failed Emask 0x4
Mar 30 02:17:21 ithaca kernel: [160188.100029] ata3: limiting SATA link speed to 1.5 Gbps
Mar 30 02:17:21 ithaca kernel: [160188.100032] ata3.00: limiting speed to UDMA/133:PIO3
Mar 30 02:17:21 ithaca kernel: [160188.100036] ata3: hard resetting link
Mar 30 02:17:21 ithaca kernel: [160188.100038] ata3: nv: skipping hardreset on occupied port
Mar 30 02:17:22 ithaca kernel: [160188.568025] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:17:22 ithaca kernel: [160188.592140] ata3.00: configured for UDMA/133
Mar 30 02:17:22 ithaca kernel: [160188.592144] ata3.00: retrying FLUSH 0xea Emask 0x4
Mar 30 02:17:37 ithaca kernel: [160203.592023] ata3.00: qc timeout (cmd 0xea)
Mar 30 02:17:37 ithaca kernel: [160203.592029] ata3.00: FLUSH failed Emask 0x4
Mar 30 02:17:37 ithaca kernel: [160203.592031] ata3.00: disabled
Mar 30 02:17:37 ithaca kernel: [160203.592037] ata3.00: device reported invalid CHS sector 0
Mar 30 02:17:37 ithaca kernel: [160203.592045] ata3: hard resetting link
Mar 30 02:17:37 ithaca kernel: [160204.472025] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 30 02:17:37 ithaca kernel: [160204.472039] ata3: EH complete
Mar 30 02:17:37 ithaca kernel: [160204.472071] sd 2:0:0:0: [sdc] Unhandled error code
Mar 30 02:17:37 ithaca kernel: [160204.472082] sd 2:0:0:0: [sdc]  
Mar 30 02:17:37 ithaca kernel: [160204.472085] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 30 02:17:37 ithaca kernel: [160204.472088] sd 2:0:0:0: [sdc] CDB: 
Mar 30 02:17:37 ithaca kernel: [160204.472090] Write(10): 2a 00 00 00 20 08 00 00 01 00
Mar 30 02:17:37 ithaca kernel: [160204.472101] end_request: I/O error, dev sdc, sector 8200
Mar 30 02:17:37 ithaca kernel: [160204.472106] end_request: I/O error, dev sdc, sector 8200
Mar 30 02:17:37 ithaca kernel: [160204.472108] md: super_written gets error=-5, uptodate=0
Mar 30 02:17:37 ithaca kernel: [160204.472113] md/raid:md127: Disk failure on sdc1, disabling device.
Mar 30 02:17:37 ithaca kernel: [160204.472113] md/raid:md127: Operation continuing on 3 devices.
Mar 30 02:17:37 ithaca kernel: [160204.472134] sd 2:0:0:0: [sdc] READ CAPACITY(16) failed
Mar 30 02:17:37 ithaca kernel: [160204.472144] sd 2:0:0:0: [sdc]  
Mar 30 02:17:37 ithaca kernel: [160204.472152] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 30 02:17:37 ithaca kernel: [160204.472171] sd 2:0:0:0: [sdc] Sense not available.
Mar 30 02:17:37 ithaca kernel: [160204.472196] sd 2:0:0:0: [sdc] READ CAPACITY failed
Mar 30 02:17:37 ithaca kernel: [160204.472198] sd 2:0:0:0: [sdc]  
Mar 30 02:17:37 ithaca kernel: [160204.472199] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 30 02:17:37 ithaca kernel: [160204.472201] sd 2:0:0:0: [sdc] Sense not available.
Mar 30 02:17:37 ithaca kernel: [160204.472232] sd 2:0:0:0: [sdc] Asking for cache data failed
Mar 30 02:17:37 ithaca kernel: [160204.472235] sd 2:0:0:0: [sdc] Assuming drive cache: write through
Mar 30 02:17:37 ithaca kernel: [160204.472240] sdc: detected capacity change from 2000398934016 to 0
Mar 30 02:17:37 ithaca udisksd[27389]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST2000DM001_1CH164_S1E1TKLE: Error updating SMART data: sk_disk_check_sleep_mode: Operation not supported (udisks-error-quark, 0)
Mar 30 02:17:38 ithaca kernel: [160205.020022] ata4: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1
Mar 30 02:17:38 ithaca kernel: [160205.020026] ata4: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0
Mar 30 02:17:38 ithaca kernel: [160205.020026]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Mar 30 02:17:38 ithaca kernel: [160205.020030] ata4: ATA_REG 0x40 ERR_REG 0x0
Mar 30 02:17:38 ithaca kernel: [160205.020033] ata4: tag : dhfis dmafis sdbfis sactive
Mar 30 02:17:38 ithaca kernel: [160205.020035] ata4: tag 0x0: 0 0 0 1  
Mar 30 02:17:38 ithaca kernel: [160205.020044] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
Mar 30 02:17:38 ithaca kernel: [160205.020048] ata4.00: failed command: WRITE FPDMA QUEUED
Mar 30 02:17:38 ithaca kernel: [160205.020054] ata4.00: cmd 61/01:00:08:20:00/00:00:00:00:00/40 tag 0 ncq 512 out
Mar 30 02:17:38 ithaca kernel: [160205.020054]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:17:38 ithaca kernel: [160205.020057] ata4.00: status: { DRDY }
Mar 30 02:17:38 ithaca kernel: [160205.020062] ata4: hard resetting link
Mar 30 02:17:38 ithaca kernel: [160205.020064] ata4: nv: skipping hardreset on occupied port
Mar 30 02:17:39 ithaca kernel: [160205.488024] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:17:39 ithaca kernel: [160205.512140] ata4.00: configured for UDMA/133
Mar 30 02:17:39 ithaca kernel: [160205.512144] ata4.00: device reported invalid CHS sector 0
Mar 30 02:17:39 ithaca kernel: [160205.512156] ata4: EH complete
Mar 30 02:18:09 ithaca kernel: [160235.996018] ata4: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1
Mar 30 02:18:09 ithaca kernel: [160235.996024] ata4: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0
Mar 30 02:18:09 ithaca kernel: [160235.996024]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Mar 30 02:18:09 ithaca kernel: [160235.996029] ata4: ATA_REG 0x40 ERR_REG 0x0
Mar 30 02:18:09 ithaca kernel: [160235.996032] ata4: tag : dhfis dmafis sdbfis sactive
Mar 30 02:18:09 ithaca kernel: [160235.996034] ata4: tag 0x0: 0 0 0 1  
Mar 30 02:18:09 ithaca kernel: [160235.996042] ata4.00: NCQ disabled due to excessive errors
Mar 30 02:18:09 ithaca kernel: [160235.996046] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
Mar 30 02:18:09 ithaca kernel: [160235.996051] ata4.00: failed command: WRITE FPDMA QUEUED
Mar 30 02:18:09 ithaca kernel: [160235.996057] ata4.00: cmd 61/01:00:08:20:00/00:00:00:00:00/40 tag 0 ncq 512 out
Mar 30 02:18:09 ithaca kernel: [160235.996057]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:18:09 ithaca kernel: [160235.996060] ata4.00: status: { DRDY }
Mar 30 02:18:09 ithaca kernel: [160235.996065] ata4: hard resetting link
Mar 30 02:18:09 ithaca kernel: [160235.996067] ata4: nv: skipping hardreset on occupied port
Mar 30 02:18:09 ithaca kernel: [160236.464026] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:18:10 ithaca kernel: [160236.488144] ata4.00: configured for UDMA/133
Mar 30 02:18:10 ithaca kernel: [160236.488149] ata4.00: device reported invalid CHS sector 0
Mar 30 02:18:10 ithaca kernel: [160236.488156] ata4: EH complete
Mar 30 02:18:40 ithaca kernel: [160267.036025] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 30 02:18:40 ithaca kernel: [160267.036032] ata4.00: failed command: WRITE DMA
Mar 30 02:18:40 ithaca kernel: [160267.036038] ata4.00: cmd ca/00:01:08:20:00/00:00:00:00:00/e0 tag 0 dma 512 out
Mar 30 02:18:40 ithaca kernel: [160267.036038]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:18:40 ithaca kernel: [160267.036042] ata4.00: status: { DRDY }
Mar 30 02:18:40 ithaca kernel: [160267.036046] ata4: hard resetting link
Mar 30 02:18:40 ithaca kernel: [160267.036049] ata4: nv: skipping hardreset on occupied port
Mar 30 02:18:41 ithaca kernel: [160267.504020] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:18:41 ithaca kernel: [160267.528139] ata4.00: configured for UDMA/133
Mar 30 02:18:41 ithaca kernel: [160267.528144] ata4.00: device reported invalid CHS sector 0
Mar 30 02:18:41 ithaca kernel: [160267.528151] ata4: EH complete
Mar 30 02:19:11 ithaca kernel: [160298.012024] ata4: limiting SATA link speed to 1.5 Gbps
Mar 30 02:19:11 ithaca kernel: [160298.012029] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 30 02:19:11 ithaca kernel: [160298.012034] ata4.00: failed command: WRITE DMA
Mar 30 02:19:11 ithaca kernel: [160298.012040] ata4.00: cmd ca/00:01:08:20:00/00:00:00:00:00/e0 tag 0 dma 512 out
Mar 30 02:19:11 ithaca kernel: [160298.012040]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:19:11 ithaca kernel: [160298.012043] ata4.00: status: { DRDY }
Mar 30 02:19:11 ithaca kernel: [160298.012048] ata4: hard resetting link
Mar 30 02:19:11 ithaca kernel: [160298.012050] ata4: nv: skipping hardreset on occupied port
Mar 30 02:19:11 ithaca kernel: [160298.480027] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:19:12 ithaca kernel: [160298.504144] ata4.00: configured for UDMA/133
Mar 30 02:19:12 ithaca kernel: [160298.504149] ata4.00: device reported invalid CHS sector 0
Mar 30 02:19:12 ithaca kernel: [160298.504157] sd 3:0:0:0: [sdd]  
Mar 30 02:19:12 ithaca kernel: [160298.504165] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 30 02:19:12 ithaca kernel: [160298.504167] sd 3:0:0:0: [sdd]  
Mar 30 02:19:12 ithaca kernel: [160298.504168] Sense Key : Aborted Command [current] [descriptor]
Mar 30 02:19:12 ithaca kernel: [160298.504171] Descriptor sense data with sense descriptors (in hex):
Mar 30 02:19:12 ithaca kernel: [160298.504172]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
Mar 30 02:19:12 ithaca kernel: [160298.504180]         00 00 00 00 
Mar 30 02:19:12 ithaca kernel: [160298.504184] sd 3:0:0:0: [sdd]  
Mar 30 02:19:12 ithaca kernel: [160298.504186] Add. Sense: No additional sense information
Mar 30 02:19:12 ithaca kernel: [160298.504188] sd 3:0:0:0: [sdd] CDB: 
Mar 30 02:19:12 ithaca kernel: [160298.504189] Write(10): 2a 00 00 00 20 08 00 00 01 00
Mar 30 02:19:12 ithaca kernel: [160298.504196] end_request: I/O error, dev sdd, sector 8200
Mar 30 02:19:12 ithaca kernel: [160298.504199] end_request: I/O error, dev sdd, sector 8200
Mar 30 02:19:12 ithaca kernel: [160298.504201] md: super_written gets error=-5, uptodate=0
Mar 30 02:19:12 ithaca kernel: [160298.504204] md/raid:md127: Disk failure on sdd1, disabling device.
Mar 30 02:19:12 ithaca kernel: [160298.504204] md/raid:md127: Operation continuing on 2 devices.
Mar 30 02:19:12 ithaca kernel: [160298.504223] ata4: EH complete
Mar 30 02:19:12 ithaca kernel: [160298.548341] RAID conf printout:
Mar 30 02:19:12 ithaca kernel: [160298.548343]  --- level:5 rd:4 wd:2
Mar 30 02:19:12 ithaca kernel: [160298.548346]  disk 0, o:0, dev:sdc1
Mar 30 02:19:12 ithaca kernel: [160298.548348]  disk 1, o:1, dev:sde1
Mar 30 02:19:12 ithaca kernel: [160298.548350]  disk 2, o:1, dev:sdf1
Mar 30 02:19:12 ithaca kernel: [160298.548352]  disk 3, o:0, dev:sdd1
Mar 30 02:19:12 ithaca kernel: [160298.562703] RAID conf printout:
Mar 30 02:19:12 ithaca kernel: [160298.562706]  --- level:5 rd:4 wd:2
Mar 30 02:19:12 ithaca kernel: [160298.562709]  disk 1, o:1, dev:sde1
Mar 30 02:19:12 ithaca kernel: [160298.562711]  disk 2, o:1, dev:sdf1
Mar 30 02:19:12 ithaca kernel: [160298.562713]  disk 3, o:0, dev:sdd1
Mar 30 02:19:12 ithaca kernel: [160298.562718] RAID conf printout:
Mar 30 02:19:12 ithaca kernel: [160298.562720]  --- level:5 rd:4 wd:2
Mar 30 02:19:12 ithaca kernel: [160298.562722]  disk 1, o:1, dev:sde1
Mar 30 02:19:12 ithaca kernel: [160298.562724]  disk 2, o:1, dev:sdf1
Mar 30 02:19:12 ithaca kernel: [160298.562726]  disk 3, o:0, dev:sdd1
Mar 30 02:19:12 ithaca kernel: [160298.574354] RAID conf printout:
Mar 30 02:19:12 ithaca kernel: [160298.574357]  --- level:5 rd:4 wd:2
Mar 30 02:19:12 ithaca kernel: [160298.574359]  disk 1, o:1, dev:sde1
Mar 30 02:19:12 ithaca kernel: [160298.574361]  disk 2, o:1, dev:sdf1
Mar 30 02:19:12 ithaca kernel: [160298.574382] Buffer I/O error on device dm-5, logical block 271581257
Mar 30 02:19:12 ithaca kernel: [160298.574385] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574392] Buffer I/O error on device dm-5, logical block 271581258
Mar 30 02:19:12 ithaca kernel: [160298.574394] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574399] Buffer I/O error on device dm-5, logical block 271581261
Mar 30 02:19:12 ithaca kernel: [160298.574401] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574406] Buffer I/O error on device dm-5, logical block 271581262
Mar 30 02:19:12 ithaca kernel: [160298.574408] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574413] Buffer I/O error on device dm-5, logical block 271581263
Mar 30 02:19:12 ithaca kernel: [160298.574415] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574420] Buffer I/O error on device dm-5, logical block 271581270
Mar 30 02:19:12 ithaca kernel: [160298.574421] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574426] Buffer I/O error on device dm-5, logical block 271581271
Mar 30 02:19:12 ithaca kernel: [160298.574428] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.574433] Buffer I/O error on device dm-5, logical block 271581272
Mar 30 02:19:12 ithaca kernel: [160298.574435] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.591354] Buffer I/O error on device dm-5, logical block 271581282
Mar 30 02:19:12 ithaca kernel: [160298.591357] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.591408] EXT4-fs warning (device dm-5): ext4_end_bio:332: I/O error writing to inode 67895314 (offset 0 size 0 starting block 49404059)
Mar 30 02:19:12 ithaca kernel: [160298.591412] Buffer I/O error on device dm-5, logical block 49404059
Mar 30 02:19:12 ithaca kernel: [160298.591428] Aborting journal on device dm-5-8.
Mar 30 02:19:12 ithaca kernel: [160298.591566] EXT4-fs warning (device dm-5): ext4_end_bio:332: I/O error writing to inode 67896443 (offset 0 size 385024 starting block 590347008)
Mar 30 02:19:12 ithaca kernel: [160298.591569] Buffer I/O error on device dm-5, logical block 590347008
Mar 30 02:19:12 ithaca kernel: [160298.591571] Buffer I/O error on device dm-5, logical block 590347009
Mar 30 02:19:12 ithaca kernel: [160298.591573] Buffer I/O error on device dm-5, logical block 590347010
Mar 30 02:19:12 ithaca kernel: [160298.591575] Buffer I/O error on device dm-5, logical block 590347011
Mar 30 02:19:12 ithaca kernel: [160298.591576] Buffer I/O error on device dm-5, logical block 590347012
Mar 30 02:19:12 ithaca kernel: [160298.591578] Buffer I/O error on device dm-5, logical block 590347013
Mar 30 02:19:12 ithaca kernel: [160298.591580] Buffer I/O error on device dm-5, logical block 590347014
Mar 30 02:19:12 ithaca kernel: [160298.591582] Buffer I/O error on device dm-5, logical block 590347015
Mar 30 02:19:12 ithaca kernel: [160298.591583] Buffer I/O error on device dm-5, logical block 590347016
Mar 30 02:19:12 ithaca kernel: [160298.591626] Buffer I/O error on device dm-5, logical block 402685952
Mar 30 02:19:12 ithaca kernel: [160298.591628] lost page write due to I/O error on dm-5
Mar 30 02:19:12 ithaca kernel: [160298.591635] JBD2: Error -5 detected when updating journal superblock for dm-5-8.
Mar 30 02:19:12 ithaca kernel: [160298.591677] EXT4-fs error (device dm-5): ext4_journal_check_start:56: Detected aborted journal
Mar 30 02:19:12 ithaca kernel: [160298.591681] EXT4-fs (dm-5): Remounting filesystem read-only
Mar 30 02:19:12 ithaca kernel: [160298.591684] EXT4-fs (dm-5): previous I/O error to superblock detected
Mar 30 02:19:12 ithaca mdadm[1608]: Fail event detected on md device /dev/md127, component device /dev/sdc1
Mar 30 02:19:12 ithaca mdadm[1608]: Fail event detected on md device /dev/md127
Mar 30 02:19:12 ithaca mdadm[1608]: FailSpare event detected on md device /dev/md127, component device /dev/sdd1
Mar 30 02:19:19 ithaca kernel: [160305.980226] ata4: drained 512 bytes to clear DRQ
Mar 30 02:19:19 ithaca kernel: [160305.980238] ata4.00: limiting speed to UDMA/100:PIO4
Mar 30 02:19:19 ithaca kernel: [160305.980241] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 30 02:19:19 ithaca kernel: [160305.980250] ata4.00: failed command: IDENTIFY DEVICE
Mar 30 02:19:19 ithaca kernel: [160305.980254] ata4.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Mar 30 02:19:19 ithaca kernel: [160305.980254]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:19:19 ithaca kernel: [160305.980256] ata4.00: status: { DRDY }
Mar 30 02:19:19 ithaca kernel: [160305.980260] ata4: hard resetting link
Mar 30 02:19:19 ithaca kernel: [160305.980262] ata4: nv: skipping hardreset on occupied port
Mar 30 02:19:19 ithaca kernel: [160306.448025] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:19:19 ithaca kernel: [160306.472145] ata4.00: configured for UDMA/100
Mar 30 02:19:19 ithaca kernel: [160306.472158] ata4: EH complete
Mar 30 02:19:27 ithaca kernel: [160313.980021] ata4.00: limiting speed to UDMA/33:PIO4
Mar 30 02:19:27 ithaca kernel: [160313.980025] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 30 02:19:27 ithaca kernel: [160313.980029] ata4.00: failed command: CHECK POWER MODE
Mar 30 02:19:27 ithaca kernel: [160313.980035] ata4.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
Mar 30 02:19:27 ithaca kernel: [160313.980035]          res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Mar 30 02:19:27 ithaca kernel: [160313.980038] ata4.00: status: { DRDY }
Mar 30 02:19:27 ithaca kernel: [160313.980042] ata4: hard resetting link
Mar 30 02:19:27 ithaca kernel: [160313.980044] ata4: nv: skipping hardreset on occupied port
Mar 30 02:19:27 ithaca kernel: [160314.448025] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 30 02:19:27 ithaca kernel: [160314.472140] ata4.00: configured for UDMA/33
Mar 30 02:19:27 ithaca kernel: [160314.472152] ata4: EH complete
I have many such snippets, but they are all similar in content. It does seem odd that it's always ata3&ata4 that fails together, and ata5&ata6 together at other times. This is primarily what leads me to believe it's a chipset issue.

I've tried so far:
  • Replacing the SATA Cables
  • Changing BIOS settings [RAID/AHCI/off]
  • Forcing legacy SATA Speeds by boot directives: libata.force=5:1.5G

Things I'm still trying:
  • Turning off any HDD feature I can find (ncq, etc)

But I don't think that's going to solve my issue, and even if it does, at perhaps too great a cost.

I don't think the HDD's are at fault, since they are relatively new, it's not always the same drives that fail, the SmartCHK and all other tests return fine, I haven't lost any data, they fail in 2's, etc.

Any input would be GREATLY appreciated!
 
Old 04-02-2014, 04:50 PM   #2
frostschutz
Member
 
Registered: Apr 2004
Distribution: Gentoo
Posts: 80

Rep: Reputation: 22
If none of the kernel options help and if it has a free PCIe slot you could get a cheap Asmedia 2xSATA III controller card (ASM106x chip). They cost around $15 and work fine in Linux. I have three of them, one onboard and two cards, to provide me enough SATA ports for 7xHDD, 1xSSD, DVD, eSATA, Hotswap-bay... Using a different controller could take some load off your onboard one and verify your theory whether it's the onboard controller at fault.
 
Old 04-03-2014, 02:24 AM   #3
Sidus
LQ Newbie
 
Registered: Apr 2014
Posts: 2

Original Poster
Rep: Reputation: Disabled
Thanks, frost

I'll keep that in mind. Progress since last post is that I've disabled NCQ in the boot directives and I'm up 24hrs so far without a crash. This morning I restored full SATA speed to 3gb/s, so the only change in effect is NCQ off.

If I stay up for a week I'll declare the culprit found and post my findings here. Other posts on the net do lead me to believe NCQ on nForce chipsets are a bit dodgy, but nothing directly relates to the issues I find.

I'm still hopeful that someone reading this can help me fix the problem (once I find it), instead of just working around it by turning off features.

Regards,
J
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
CentOS 5.2 and NVIDIA nForce Networking Controller Pascal Linux - Hardware 2 01-18-2009 12:33 PM
Problems with NVIDIA nForce Networking Controller CompiMan Slackware 22 07-19-2008 12:39 AM
what is NVIDIA Nforce MCP Networking Controller goldpony Linux - General 3 11-23-2006 01:03 PM
Troubles with ethernet, nvidia nforce networking controller sparka Debian 1 05-03-2006 07:59 AM
NVIDIA nForce MCP Networking Controller ph34r Linux - Networking 1 08-11-2004 11:37 PM


All times are GMT -5. The time now is 02:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration