View topic - Kernel 3.7 problems with LIAN LI Controller :: aptosid.com :: aptosid

Kernel 3.7 problems with LIAN LI Controller

aptosid.com Forum Index » Support Forums » Hardware

Author

Message

debaba

Post subject: Kernel 3.7 problems with LIAN LI Controller

Posted: 24.12.2012, 11:09

Joined: 2010-09-11
Posts: 54
Location: Hessen
Status: Offline

Merry Christmas everybody,

unfortunately there is a continuation of the problems i had with kernel 3.6.
see http://www.aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=2464

This time the controller is shutting down completely, so the RAID which is partially based on the controllers disks fails. This happens after 2-3 days running with no messages in kern.log or syslog. No messages from smartd either.
excerpt from kern.log:

Code:

Dec 24 06:27:38 siduxbox kernel: [73904.895108] ata9.00: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895130] ata9.01: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895139] ata9.02: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895147] ata9.03: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895154] ata9.04: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895161] ata9.05: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895169] ata9.06: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895176] ata9.07: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895183] ata9.08: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895190] ata9.09: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895197] ata9.10: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895205] ata9.11: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895212] ata9.12: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895219] ata9.13: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895226] ata9.14: failed to read SCR 1 (Emask=0x40)

Dec 24 06:27:38 siduxbox kernel: [73904.895241] ata9.15: exception Emask 0x4 SAct 0x0 SErr 0x400001 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895253] ata9.15: SError: { RecovData Handshk }

Dec 24 06:27:38 siduxbox kernel: [73904.895268] ata9.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895277] ata9.00: failed command: WRITE DMA

Dec 24 06:27:38 siduxbox kernel: [73904.895295] ata9.00: cmd ca/00:01:08:08:00/00:00:00:00:00/e0 tag 0 dma 512 out

Dec 24 06:27:38 siduxbox kernel: [73904.895295]          res 40/00:01:09:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Dec 24 06:27:38 siduxbox kernel: [73904.895304] ata9.00: status: { DRDY }

Dec 24 06:27:38 siduxbox kernel: [73904.895318] ata9.01: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895332] ata9.02: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895346] ata9.03: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895360] ata9.04: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895374] ata9.05: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895387] ata9.06: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895401] ata9.07: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895414] ata9.08: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895428] ata9.09: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895442] ata9.10: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895455] ata9.11: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895469] ata9.12: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895483] ata9.13: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895497] ata9.14: exception Emask 0x100 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 24 06:27:38 siduxbox kernel: [73904.895514] ata9.15: hard resetting link

Dec 24 06:27:43 siduxbox kernel: [73910.406939] ata9.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 24 06:27:43 siduxbox kernel: [73910.407542] ata9.00: hard resetting link

Dec 24 06:27:49 siduxbox kernel: [73915.868590] ata9.00: link is slow to respond, please be patient (ready=0)

Dec 24 06:27:53 siduxbox kernel: [73920.403282] ata9.00: softreset failed (device not ready)

Dec 24 06:27:56 siduxbox kernel: [73923.400453] ata9.15: qc timeout (cmd 0xe4)

Dec 24 06:27:56 siduxbox kernel: [73923.400479] ata9.00: failed to read SCR 0 (Emask=0x4)

Dec 24 06:27:56 siduxbox kernel: [73923.400487] ata9.00: reset failed, giving up

Dec 24 06:27:56 siduxbox kernel: [73923.400503] ata9.15: hard resetting link

Dec 24 06:28:02 siduxbox kernel: [73928.864416] ata9.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Dec 24 06:28:02 siduxbox kernel: [73928.864932] ata9.00: hard resetting link

Dec 24 06:28:07 siduxbox kernel: [73934.369057] ata9.00: link is slow to respond, please be patient (ready=0)

Dec 24 06:28:12 siduxbox kernel: [73938.905883] ata9.00: softreset failed (device not ready)

Dec 24 06:28:15 siduxbox kernel: [73941.903056] ata9.15: qc timeout (cmd 0xe4)

Dec 24 06:28:15 siduxbox kernel: [73941.903082] ata9.00: failed to read SCR 0 (Emask=0x4)

Dec 24 06:28:15 siduxbox kernel: [73941.903090] ata9.00: reset failed, giving up

Dec 24 06:28:15 siduxbox kernel: [73941.903107] ata9.15: hard resetting link

Dec 24 06:28:25 siduxbox kernel: [73951.896572] ata9.15: softreset failed (device not ready)

Dec 24 06:28:25 siduxbox kernel: [73951.896591] ata9.15: hard resetting link

Dec 24 06:28:35 siduxbox kernel: [73961.891228] ata9.15: softreset failed (device not ready)

Dec 24 06:28:35 siduxbox kernel: [73961.891248] ata9.15: hard resetting link

Dec 24 06:28:45 siduxbox kernel: [73972.348909] ata9.15: link is slow to respond, please be patient (ready=0)

Dec 24 06:29:10 siduxbox kernel: [73996.879980] ata9.15: softreset failed (device not ready)

Dec 24 06:29:10 siduxbox kernel: [73996.880001] ata9.15: limiting SATA link speed to 1.5 Gbps

Dec 24 06:29:10 siduxbox kernel: [73996.880010] ata9.15: hard resetting link

Dec 24 06:29:15 siduxbox kernel: [74002.031033] ata9.15: softreset failed (device not ready)

Dec 24 06:29:15 siduxbox kernel: [74002.031056] ata9.15: failed to reset PMP, giving up

Dec 24 06:29:15 siduxbox kernel: [74002.031063] ata9.15: Port Multiplier detaching

Dec 24 06:29:15 siduxbox kernel: [74002.031073] ata9.00: disabled

Dec 24 06:29:15 siduxbox kernel: [74002.031083] ata9.01: disabled

Dec 24 06:29:15 siduxbox kernel: [74002.031090] ata9.02: disabled

Dec 24 06:29:15 siduxbox kernel: [74002.031096] ata9.03: disabled

Dec 24 06:29:15 siduxbox kernel: [74002.031111] ata9.00: disabled

Dec 24 06:29:15 siduxbox kernel: [74002.031155] sd 8:1:0:0: rejecting I/O to offline device

Dec 24 06:29:15 siduxbox kernel: [74002.031167] sd 8:1:0:0: [sdi] killing request

Dec 24 06:29:15 siduxbox kernel: [74002.031186] sd 8:2:0:0: rejecting I/O to offline device

Dec 24 06:29:15 siduxbox kernel: [74002.031195] sd 8:2:0:0: [sdj] killing request

Dec 24 06:29:15 siduxbox kernel: [74002.031205] sd 8:3:0:0: rejecting I/O to offline device

Dec 24 06:29:15 siduxbox kernel: [74002.031213] sd 8:3:0:0: [sdk] killing request

Dec 24 06:29:15 siduxbox kernel: [74002.031264] sd 8:1:0:0: rejecting I/O to offline device

Dec 24 06:29:15 siduxbox kernel: [74002.031280] md: super_written gets error=-5, uptodate=0

Dec 24 06:29:15 siduxbox kernel: [74002.031293] md/raid:md0: Disk failure on sdi1, disabling device.

Dec 24 06:29:15 siduxbox kernel: [74002.031293] md/raid:md0: Operation continuing on 7 devices.

Dec 24 06:29:15 siduxbox kernel: [74002.031337] sd 8:2:0:0: rejecting I/O to offline device

Dec 24 06:29:15 siduxbox kernel: [74002.031348] md: super_written gets error=-5, uptodate=0

Dec 24 06:29:15 siduxbox kernel: [74002.031356] md/raid:md0: Disk failure on sdj1, disabling device.

Dec 24 06:29:15 siduxbox kernel: [74002.031356] md/raid:md0: Operation continuing on 6 devices.

Dec 24 06:29:15 siduxbox kernel: [74002.031431] sd 8:3:0:0: [sdk] Unhandled error code

Dec 24 06:29:15 siduxbox kernel: [74002.031439] sd 8:3:0:0: [sdk]  

Dec 24 06:29:15 siduxbox kernel: [74002.031445] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.031452] sd 8:3:0:0: [sdk] CDB: 

Dec 24 06:29:15 siduxbox kernel: [74002.031457] Write(10): 2a 00 00 00 08 08 00 00 01 00

Dec 24 06:29:15 siduxbox kernel: [74002.031483] end_request: I/O error, dev sdk, sector 2056

Dec 24 06:29:15 siduxbox kernel: [74002.031493] end_request: I/O error, dev sdk, sector 2056

Dec 24 06:29:15 siduxbox kernel: [74002.031499] md: super_written gets error=-5, uptodate=0

Dec 24 06:29:15 siduxbox kernel: [74002.031508] md/raid:md0: Disk failure on sdk1, disabling device.

Dec 24 06:29:15 siduxbox kernel: [74002.031508] md/raid:md0: Operation continuing on 5 devices.

Dec 24 06:29:15 siduxbox kernel: [74002.042133] sd 8:0:0:0: [sdh]  

Dec 24 06:29:15 siduxbox kernel: [74002.042144] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Dec 24 06:29:15 siduxbox kernel: [74002.042149] sd 8:0:0:0: [sdh]  

Dec 24 06:29:15 siduxbox kernel: [74002.042152] Sense Key : Aborted Command [current] [descriptor]

Dec 24 06:29:15 siduxbox kernel: [74002.042158] Descriptor sense data with sense descriptors (in hex):

Dec 24 06:29:15 siduxbox kernel: [74002.042161]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 

Dec 24 06:29:15 siduxbox kernel: [74002.042174]         00 00 00 08 

Dec 24 06:29:15 siduxbox kernel: [74002.042180] sd 8:0:0:0: [sdh]  

Dec 24 06:29:15 siduxbox kernel: [74002.042184] Add. Sense: No additional sense information

Dec 24 06:29:15 siduxbox kernel: [74002.042188] sd 8:0:0:0: [sdh] CDB: 

Dec 24 06:29:15 siduxbox kernel: [74002.042190] Write(10): 2a 00 00 00 08 08 00 00 01 00

Dec 24 06:29:15 siduxbox kernel: [74002.042202] end_request: I/O error, dev sdh, sector 2056

Dec 24 06:29:15 siduxbox kernel: [74002.042208] md: super_written gets error=-5, uptodate=0

Dec 24 06:29:15 siduxbox kernel: [74002.042215] md/raid:md0: Disk failure on sdh1, disabling device.

Dec 24 06:29:15 siduxbox kernel: [74002.042215] md/raid:md0: Operation continuing on 4 devices.

Dec 24 06:29:15 siduxbox kernel: [74002.042287] ata9: EH complete

Dec 24 06:29:15 siduxbox kernel: [74002.042310] ata9.00: detaching (SCSI 8:0:0:0)

Dec 24 06:29:15 siduxbox kernel: [74002.047581] sd 8:0:0:0: [sdh] Stopping disk

Dec 24 06:29:15 siduxbox kernel: [74002.047673] sd 8:0:0:0: [sdh] START_STOP FAILED

Dec 24 06:29:15 siduxbox kernel: [74002.047682] sd 8:0:0:0: [sdh]  

Dec 24 06:29:15 siduxbox kernel: [74002.047689] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.047762] ata9.01: detaching (SCSI 8:1:0:0)

Dec 24 06:29:15 siduxbox kernel: [74002.050966] sd 8:1:0:0: [sdi] Synchronizing SCSI cache

Dec 24 06:29:15 siduxbox kernel: [74002.051095] sd 8:1:0:0: [sdi]  

Dec 24 06:29:15 siduxbox kernel: [74002.051104] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.051111] sd 8:1:0:0: [sdi] Stopping disk

Dec 24 06:29:15 siduxbox kernel: [74002.051145] sd 8:1:0:0: [sdi] START_STOP FAILED

Dec 24 06:29:15 siduxbox kernel: [74002.051153] sd 8:1:0:0: [sdi]  

Dec 24 06:29:15 siduxbox kernel: [74002.051158] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.051225] ata9.02: detaching (SCSI 8:2:0:0)

Dec 24 06:29:15 siduxbox kernel: [74002.053134] sd 8:2:0:0: [sdj] Synchronizing SCSI cache

Dec 24 06:29:15 siduxbox kernel: [74002.053251] sd 8:2:0:0: [sdj]  

Dec 24 06:29:15 siduxbox kernel: [74002.053259] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.053266] sd 8:2:0:0: [sdj] Stopping disk

Dec 24 06:29:15 siduxbox kernel: [74002.053299] sd 8:2:0:0: [sdj] START_STOP FAILED

Dec 24 06:29:15 siduxbox kernel: [74002.053307] sd 8:2:0:0: [sdj]  

Dec 24 06:29:15 siduxbox kernel: [74002.053312] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.053386] ata9.03: detaching (SCSI 8:3:0:0)

Dec 24 06:29:15 siduxbox kernel: [74002.055706] sd 8:3:0:0: [sdk] Synchronizing SCSI cache

Dec 24 06:29:15 siduxbox kernel: [74002.055821] sd 8:3:0:0: [sdk]  

Dec 24 06:29:15 siduxbox kernel: [74002.055829] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.055837] sd 8:3:0:0: [sdk] Stopping disk

Dec 24 06:29:15 siduxbox kernel: [74002.055868] sd 8:3:0:0: [sdk] START_STOP FAILED

Dec 24 06:29:15 siduxbox kernel: [74002.055876] sd 8:3:0:0: [sdk]  

Dec 24 06:29:15 siduxbox kernel: [74002.055881] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Dec 24 06:29:15 siduxbox kernel: [74002.321151] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.321168]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.321177]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.321183]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.321189]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.321195]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.321201]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.321206]  disk 5, o:0, dev:sdi1

Dec 24 06:29:15 siduxbox kernel: [74002.321211]  disk 6, o:0, dev:sdh1

Dec 24 06:29:15 siduxbox kernel: [74002.321217]  disk 7, o:0, dev:sdk1

Dec 24 06:29:15 siduxbox kernel: [74002.323861] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.323877]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.323886]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.323893]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.323899]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.323905]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.323910]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.323916]  disk 5, o:0, dev:sdi1

Dec 24 06:29:15 siduxbox kernel: [74002.323921]  disk 6, o:0, dev:sdh1

Dec 24 06:29:15 siduxbox kernel: [74002.323935] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.323939]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.323944]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.323949]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.323954]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.323958]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.323963]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.323968]  disk 5, o:0, dev:sdi1

Dec 24 06:29:15 siduxbox kernel: [74002.323973]  disk 6, o:0, dev:sdh1

Dec 24 06:29:15 siduxbox kernel: [74002.325168] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.325179]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.325187]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.325194]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.325200]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.325206]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.325212]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.325217]  disk 5, o:0, dev:sdi1

Dec 24 06:29:15 siduxbox kernel: [74002.325232] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.325236]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.325241]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.325246]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.325251]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.325256]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.325260]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.325265]  disk 5, o:0, dev:sdi1

Dec 24 06:29:15 siduxbox kernel: [74002.328866] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.328883]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.328892]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.328898]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.328905]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.328910]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.328916]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.328930] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.328934]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.328939]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.328944]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.328949]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.328954]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.328958]  disk 4, o:0, dev:sdj1

Dec 24 06:29:15 siduxbox kernel: [74002.332084] RAID conf printout:

Dec 24 06:29:15 siduxbox kernel: [74002.332101]  --- level:5 rd:8 wd:4

Dec 24 06:29:15 siduxbox kernel: [74002.332110]  disk 0, o:1, dev:sdb1

Dec 24 06:29:15 siduxbox kernel: [74002.332117]  disk 1, o:1, dev:sdc1

Dec 24 06:29:15 siduxbox kernel: [74002.332123]  disk 2, o:1, dev:sdd1

Dec 24 06:29:15 siduxbox kernel: [74002.332129]  disk 3, o:1, dev:sde1

Dec 24 06:29:15 siduxbox kernel: [74002.384013] Aborting journal on device md0-8.

Dec 24 06:29:15 siduxbox kernel: [74002.384081] EXT4-fs error (device md0) in ext4_reserve_inode_write:4538: Journal has aborted

Dec 24 06:29:15 siduxbox kernel: [74002.384194] Buffer I/O error on device md0, logical block 426803200

Dec 24 06:29:15 siduxbox kernel: [74002.384201] lost page write due to I/O error on md0

Dec 24 06:29:15 siduxbox kernel: [74002.384222] Buffer I/O error on device md0, logical block 0

Dec 24 06:29:15 siduxbox kernel: [74002.384227] lost page write due to I/O error on md0

Dec 24 06:29:15 siduxbox kernel: [74002.384323] EXT4-fs (md0): Remounting filesystem read-only

Dec 24 06:29:15 siduxbox kernel: [74002.390266] JBD2: Error -5 detected when updating journal superblock for md0-8.

I had the problem with every 3.7 Version i installed. The Raid was failing 3 times until now.
Setting it up again with mdadm --create worked very good. There were no errors.

Thanks for your attention.

Wolfen

Last edited by debaba on 07.01.2013, 09:57; edited 1 time in total

DeepDayze

Post subject: RE: Kernel 3.7 problems with LIAN LI Controller

Posted: 26.12.2012, 15:07

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

Maybe there were some internal changes within the 3.7 kernel that caused issues with your old RAID configuration that caused the issues you had?

debaba

Post subject: RE: Kernel 3.7 problems with LIAN LI Controller

Posted: 28.12.2012, 12:41

Joined: 2010-09-11
Posts: 54
Location: Hessen
Status: Offline

Pardon?

slh

Post subject: RE: Kernel 3.7 problems with LIAN LI Controller

Posted: 30.12.2012, 22:10

Joined: 2010-08-25
Posts: 962

Status: Offline

Hmm, I really hoped this was settled with late 3.6-stable…

You problems actually make (potential) bisecting harder, because you're apparently dealing with two independent bugs between the reasonable trace points (v3.5 and v3.7).

That said, if I didn't know the previous story, these Emask and DRDY typically sounds like problems with your harddisk (or your SATA cables). Can you really rule out hardware problems? Does it work reliably with kernel 3.5 and/ or late ('fixed') 3.6?
Especially with RAID 1/5, one failing consumer drive (in contrasts to dedicated RAID disks) has a potential to cause issues like this, because dying consumer drives try for quite a long time read a sector, while dedicated RAID drives simply bail out and report the error, in order let the RAID deal with the fallout.

Can you describe your controller and drive arrangements a bit closer? How many drives (PATA or SATA) are connected to which controller? What kind or RAID arrays are configured and do you really use port-multipliers (because due to your reported issues, I don't immediately believe the log messages)?

debaba

Post subject: RE: Kernel 3.7 problems with LIAN LI Controller

Posted: 07.01.2013, 09:56

Joined: 2010-09-11
Posts: 54
Location: Hessen
Status: Offline

good morning out there in space,

after failing, removing, re-adding and resyncing every disk in the raid, i checked out that one disk seems to have one sector error. While the raid resync is running without any problems, a subsequent complete write with dd ends in an degraded array with one failed disk. The error is always at the same sector of the same hard disk according to /proc/mdstat. Shouldn't the firmware mark this sector as bad and then use another?
I don't believe the raid-software is able to address the hardware sector directly without involving the firmware. Am i right?
Looks like this disk has an older seagate firmware than the others.
This older firmware version only is shown by linux smartmon. The windows firmware tools from Seagate i used to test the disks show the actual firmware version. Strange....
Unfortunately I cant find an previously existing link to the new firmware on Seagate's homepage. The guarantee of these disks (ST9500420ASG) has finished. Shame on Seagate for removing the firmware...

I use a software raid 5 with 8 drives. four of them connected to the internal SATA-III Ports and four connected to the pci-e LIAN LI Controller (Sata-II). Neither proprietary controller drivers are used nor do i use the raid options the onboard or the LIAN-LI controller offers.
This raid was running with this setup under 3.5, 3.6, 3.7. Before the same disks were running with another 8 port pci-x controller under 2.6.xx to 3.4. Had to change as the previous motherboard died. The raid (3,5 TB) maximally had been filled up to 85 %. Over the whole runtime i had to replace 4 of the 8 disks. The disks are quick but with a lousy firmware.
Will now be trying to flash the disk (if i find the damned firmware-file) to use it further on. Elsewise i'll need to buy another one or shrink the raid.

As the error seems to be with the harddisks i'm going to close this thread. I hope so for now.
Thanks for your attention
with a little bit exhausted greetings Wink

Wolfen

All times are GMT - 12 Hours

aptosid.com Forum Index » Support Forums » Hardware

Menu

Rootserver Sponsor

Donations

News

Blog