March 11, 201214 yr my syslog is 21mb!!!! its full of this error message. Any ideas how to fix it? i've been using this machine for almost a year now albeit not regularly (i just start it up when i need to make backups). a month ago when i tried to check parity. i got over 25k errors. When i transfer my files it suddenly stops (im using macOS). I tried to correct parity again but its of no use. i desperately need some help. anyone have an idea what i need to do? for the full log (http://dl.dropbox.com/u/9487103/syslog-2012-03-11.txt) http://dl.dropbox.com/u/9487103/Screen%20shot%202012-03-11%20at%20AM%2011.53.06.png Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762021960/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762021968/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762021976/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762021984/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762021992/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022000/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022008/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022016/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022024/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022032/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022040/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022048/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022056/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022064/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022072/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022080/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022088/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022096/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022104/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022112/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022120/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022128/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022136/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022144/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022152/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022160/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error Mar 10 04:10:08 Yaiba kernel: handle_stripe read error: 762022168/0, count: 1 Mar 10 04:10:08 Yaiba kernel: md: disk0 read error
March 11, 201214 yr I did mean the parity disk, but it appears the parity disk is "ata1" Mar 10 03:25:10 Yaiba kernel: ata1: EH complete Mar 10 03:25:13 Yaiba kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 10 03:25:13 Yaiba kernel: ata1.00: BMDMA stat 0x65 Mar 10 03:25:13 Yaiba kernel: ata1.00: failed command: READ DMA EXT Mar 10 03:25:13 Yaiba kernel: ata1.00: cmd 25/00:80:78:ea:79/00:01:27:00:00/e0 tag 0 dma 196608 in Mar 10 03:25:13 Yaiba kernel: res 51/40:3f:b0:eb:79/40:00:27:00:00/e0 Emask 0x9 (media error) Mar 10 03:25:13 Yaiba kernel: sd 0:0:0:0: [sda] Unhandled sense code Mar 10 03:25:13 Yaiba kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Mar 10 03:25:13 Yaiba kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Mar 10 03:25:13 Yaiba kernel: Descriptor sense data with sense descriptors (in hex): Mar 10 03:25:13 Yaiba kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Mar 10 03:25:13 Yaiba kernel: 27 79 eb b0 Mar 10 03:25:13 Yaiba kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Mar 10 03:25:13 Yaiba kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 27 79 ea 78 00 01 80 00 Mar 10 03:25:13 Yaiba kernel: end_request: I/O error, dev sda, sector 662301616 Mar 10 03:25:13 Yaiba kernel: ata1: EH complete Mar 10 03:25:13 Yaiba kernel: md: disk0 read error
Archived
This topic is now archived and is closed to further replies.