May 3, 201214 yr 2X 2TB drives (one data, one parity) until I add the next drive. Did setup of everything. Networking, preclears 2 cycles without any errors on either drive. Then moved data to data drive, let parity run overnight. everything fine (this is about a week ago). These are on my to-do list but NONE have been completed yet: "Push power button and have clean shutdown" "setup monthly parity check" Tried running parity (Just to see and learn what is supposed to happen on regular basis) and got 32 errors. Decided not to be stupid and figure it out for myself so I am asking what does this mean? My "GUESS" is that data is fine but parity had some sort of problem? If I were to click on button that said "check and repair parity" is this a GOOD or BAD thing to do? I just copied and pasted this from syslog. If you need more info tell me what to do and I will try to supply it. Thank you for your help May 3 00:42:39 Tower emhttp: Spinning up all drives... (Other emhttp) May 3 00:42:39 Tower kernel: md: import disk0: [8,0] (sda) WDC WD20EARX-00P WD-WMAZA5545857 size: 1953514552 (Drive related) May 3 00:42:39 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD20EARX-00P WD-WMAZA7558525 size: 1953514552 (Drive related) May 3 00:42:39 Tower kernel: mdcmd (1): set md_num_stripes 1280 (unRAID engine) May 3 00:42:39 Tower kernel: mdcmd (2): set md_write_limit 768 (unRAID engine) May 3 00:42:39 Tower kernel: mdcmd (3): set md_sync_window 288 (unRAID engine) May 3 00:42:39 Tower kernel: mdcmd (4): set spinup_group 0 0 (unRAID engine) May 3 00:42:39 Tower kernel: mdcmd (5): set spinup_group 1 0 (unRAID engine) May 3 00:42:39 Tower kernel: mdcmd (6): spinup 0 (Routine) May 3 00:42:39 Tower kernel: mdcmd (7): spinup 1 (Routine) May 3 00:42:39 Tower emhttp: shcmd (4): /usr/local/sbin/set_ncq sda 1 >/dev/null (Drive related) May 3 00:42:39 Tower emhttp: shcmd (5): /usr/local/sbin/set_ncq sdb 1 >/dev/null (Drive related) May 3 00:42:39 Tower kernel: mdcmd (: start STOPPED (unRAID engine) May 3 00:42:39 Tower kernel: unraid: allocating 13240K for 1280 stripes (2 disks) May 3 00:42:39 Tower kernel: md1: running, size: 1953514552 blocks (Drive related) May 3 00:42:39 Tower emhttp: shcmd (6): udevadm settle (Other emhttp) May 3 00:42:39 Tower emhttp: shcmd (7): mkdir /mnt/disk1 (Routine) May 3 00:42:39 Tower emhttp: shcmd (: set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>$stuff$1 | logger (Other emhttp) May 3 00:42:39 Tower kernel: mdcmd (9): check (unRAID engine) May 3 00:42:39 Tower kernel: md: recovery thread woken up ... (unRAID engine) May 3 00:42:39 Tower kernel: md: recovery thread checking parity... (unRAID engine) May 3 00:42:39 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine) May 3 00:42:39 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal (Routine) May 3 00:42:39 Tower kernel: REISERFS (device md1): using ordered data mode (Routine) May 3 00:42:39 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) May 3 00:42:39 Tower kernel: REISERFS (device md1): checking transaction log (md1) (Routine) May 3 00:42:43 Tower ntpd_initres[1994]: host name not found: pool.ntp.org May 3 00:42:43 Tower ntpd_initres[1994]: couldn't resolve `pool.ntp.org', giving up on it May 3 00:44:41 Tower kernel: REISERFS (device md1): replayed 446 transactions in 122 seconds (Minor Issues) May 3 00:44:41 Tower kernel: REISERFS (device md1): Using r5 hash to sort names (Routine) May 3 00:44:42 Tower emhttp: shcmd (9): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp) May 3 00:44:42 Tower emhttp: _shcmd: shcmd (9): exit status: 1 (Other emhttp) May 3 00:44:42 Tower emhttp: shcmd (10): cp /etc/exports- /etc/exports (Other emhttp) May 3 00:44:42 Tower emhttp: shcmd (11): mkdir /mnt/user (Other emhttp) May 3 00:44:42 Tower emhttp: shcmd (12): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions (Other emhttp) May 3 00:44:43 Tower emhttp: shcmd (13): killall -HUP smbd (Minor Issues) May 3 00:44:43 Tower emhttp: shcmd (14): /etc/rc.d/rc.nfsd restart | logger (Other emhttp) May 3 00:47:45 Tower in.telnetd[2030]: connect from 10.0.0.11 (10.0.0.11) (Routine) May 3 00:47:48 Tower login[2031]: ROOT LOGIN on `pts/0' from `10.0.0.11' (Logins) May 3 00:47:56 Tower unmenu-status: Starting unmenu web-server May 3 02:23:15 Tower kernel: mdcmd (10): nocheck (unRAID engine) May 3 02:23:15 Tower kernel: md: md_do_sync: got signal, exit... (unRAID engine) May 3 02:23:15 Tower kernel: md: recovery thread sync completion status: -4 (unRAID engine) May 3 03:57:45 Tower kernel: mdcmd (11): check CORRECT (unRAID engine) May 3 03:57:45 Tower kernel: md: recovery thread woken up ... (unRAID engine) May 3 03:57:45 Tower kernel: md: recovery thread checking parity... (unRAID engine) May 3 03:57:45 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine) May 3 11:49:29 Tower kernel: md: parity incorrect: 3812031336 (Errors) May 3 11:49:29 Tower kernel: md: parity incorrect: 3812031848 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812096752 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812099368 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812101256 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812109912 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812156664 (Errors) May 3 11:49:30 Tower kernel: md: parity incorrect: 3812157072 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812159216 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812170360 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812173328 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812177544 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812205704 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812220808 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812222184 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812225232 (Errors) May 3 11:49:31 Tower kernel: md: parity incorrect: 3812247472 (Errors) May 3 11:49:32 Tower kernel: md: parity incorrect: 3812251640 (Errors) May 3 11:49:32 Tower kernel: md: parity incorrect: 3812256912 (Errors) May 3 11:49:32 Tower kernel: md: parity incorrect: 3812257296 (Errors) May 3 12:04:52 Tower kernel: md: sync done. time=29230sec rate=66832K/sec (unRAID engine) May 3 12:04:52 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine) May 3 12:34:54 Tower kernel: mdcmd (12): spindown 0 (Routine) May 3 12:34:54 Tower kernel: mdcmd (13): spindown 1 (Routine) May 3 13:16:39 Tower in.telnetd[6991]: connect from 10.0.0.11 (10.0.0.11) (Routine) May 3 13:16:42 Tower login[6992]: ROOT LOGIN on `pts/0' from `10.0.0.11' (Logins) May 3 13:20:49 Tower kernel: mdcmd (14): check CORRECT (unRAID engine) May 3 13:20:49 Tower kernel: md: recovery thread woken up ... (unRAID engine) May 3 13:20:49 Tower kernel: md: recovery thread checking parity... (unRAID engine) May 3 13:20:49 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine) May 3 13:44:00 Tower kernel: mdcmd (15): nocheck (unRAID engine) May 3 13:44:00 Tower kernel: md: md_do_sync: got signal, exit... (unRAID engine) May 3 13:44:00 Tower kernel: md: recovery thread sync completion status: -4 (unRAID engine) May 3 13:59:22 Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. (System)
Archived
This topic is now archived and is closed to further replies.