teejay Posted April 14, 2011 Share Posted April 14, 2011 I've just recently replaced my parity drive with a larger drive, and then replaced an old drive with the parity drive. I was doing parity checks at every step and didn't run into any errors. I copied a bunch of new data to the server and to be safe ran another parity test. This one came up with 384 errors a smart report showed a few reallocated sectors but I'm not sure that is the problem. My parity drive is 2tb, while the other 2 data drives are 1.5 tb. It looks to me like the incorrect blocks all fall after 1.5 Tb so should I not be concerned? Thanks for the help here are the relevant syslog lines: Apr 12 23:06:32 SM-Storage kernel: md: import disk0: [8,0] (sda) Hitachi HDS5C302 ML0221F305T66D size: 1953514552 Apr 12 23:06:32 SM-Storage kernel: md: import disk1: [8,16] (sdb) WDC WD15EADS-00P WD-WMAVU1632520 size: 1465138552 Apr 12 23:06:32 SM-Storage kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD154UI S1XWJ1KZ214109 size: 1465138552 Apr 14 11:31:22 SM-Storage kernel: mdcmd (20): check NOCORRECT Apr 14 11:31:22 SM-Storage kernel: Apr 14 11:31:22 SM-Storage kernel: md: recovery thread woken up ... Apr 14 11:31:22 SM-Storage kernel: md: recovery thread checking parity... Apr 14 11:31:22 SM-Storage kernel: md: using 1152k window, over a total of 1953514552 blocks. Apr 14 12:45:36 SM-Storage ntpd[1281]: no servers reachable Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184568 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184576 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184584 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184592 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184600 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184608 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184616 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184624 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184632 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184640 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184648 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184656 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184664 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184672 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184680 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184688 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184696 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184704 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184712 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184720 Link to comment
vca Posted April 15, 2011 Share Posted April 15, 2011 here are the relevant syslog lines: Apr 12 23:06:32 SM-Storage kernel: md: import disk0: [8,0] (sda) Hitachi HDS5C302 ML0221F305T66D size: 1953514552 Apr 12 23:06:32 SM-Storage kernel: md: import disk1: [8,16] (sdb) WDC WD15EADS-00P WD-WMAVU1632520 size: 1465138552 Apr 12 23:06:32 SM-Storage kernel: md: import disk2: [8,32] (sdc) SAMSUNG HD154UI S1XWJ1KZ214109 size: 1465138552 The sizes you show above are quoted in 1K byte blocks, which agrees with your stated drive sizes. But unRAID uses 512 byte blocks when it reports the location of parity errors (which is something that really should be changed so these two numbers are consistent), so your problems: Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184568 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184576 Apr 14 14:45:20 SM-Storage kernel: md: parity incorrect: 1896184584 ... are somewhere just above the 900GB mark, so could be caused by an issue on any of your drives. Regards, Stephen Link to comment
dgaschk Posted April 17, 2011 Share Posted April 17, 2011 See this: http://lime-technology.com/forum/index.php?topic=9880.0 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.